zem_contact_reborn v4.5.0.0: contact mail form processing

GugUser · 2017-01-18 13:17:47

I downloaded from Github the zem_contact_reborn_v4.5.0.0_en.es.fr.pt_textpack.txt. I translated it to German and made some changes in the Spanish part.

After that, I was looking for a way to share the new textpack. The only editable textpack I found was inside the plugin code. But to my surprise there was already a German translation at the end.

How can the two German and Spanish versions be integrated now, and who decides which version or combination will be used?

GugUser · 2017-01-18 13:36:43

An other question: Why the quotation marks in the textpack are in HTML Unicode, for example “ or ”?

GugUser · 2017-01-18 16:34:13

Now I understand nothing. In Differences from previous version I read:

Disable or remove the zem_contact_lang plugin. Language strings are now bundled as part of the plugin itself.

But in v4.5.0.0-beta.4 no language string is bundled.

What I’m misunderstanding?

Last edited by GugUser (2017-01-18 16:40:55)

Bloke · 2017-01-18 17:18:28

GugUser wrote #303619:

How can the two German and Spanish versions be integrated now, and who decides which version or combination will be used?

Sorry about the mix-up. The German translation was added by Robert (wet) but it was added after the release was bundled up. Hence it’s in the master code base ready for the (final) release but not in the beta.

If you have changes to the es pack and have put the work into the de pack, please send the packs to me and I’ll roll them into the plugin. I’ll figure out any necessary combining that needs to be done.

GugUser · 2017-01-18 17:28:25

Here are my versions of the German and Spanish parts:

#@public
#@language de-de
zem_contact_checkbox => Auswahlkästchen
zem_contact_contact => Kontakt
zem_contact_email => E-Mail
zem_contact_email_subject => {site} > Anfrage
zem_contact_email_thanks => Vielen Dank. Ihre Nachricht wurde versandt.
zem_contact_field_missing => Eingabe erforderlich, &#8222;<strong>{field}</strong>&#8220; fehlt.
zem_contact_format_warning => Der Wert {value} in &#8222;<strong>{field}</strong>&#8220; ist nicht im erwarteten Format.
zem_contact_form_expired => Das Formular ist abgelaufen, bitte versuchen Sie es erneut.
zem_contact_form_used => Dieses Formular wurde bereits versandt, bitte füllen Sie ein neues Formular aus.
zem_contact_general_inquiry => Allgemeine Anfrage
zem_contact_invalid_email => &#8222;<strong>{email}</strong>&#8220; ist keine gültige E-Mail-Adresse.
zem_contact_invalid_host => &#8222;<strong>{host}</strong>&#8220; ist kein gültiger E-Mail-Server.
zem_contact_invalid_utf8 => &#8222;<strong>{field}</strong>&#8220; enthält ungültige UTF-8-Zeichen.
zem_contact_invalid_value => Ungültiger Wert für &#8222;<strong>{field}</strong>&#8220;, &#8222;<strong>{value}</strong>&#8220; ist keine der verfügbaren Optionen.
zem_contact_mail_sorry => Entschuldigung, die Nachricht konnte nicht versandt werden.
zem_contact_maxval_warning => &#8222;<strong>{field}</strong>&#8220; darf höchstens {value} sein.
zem_contact_max_warning => &#8222;<strong>{field}</strong>&#8220; darf höchstens {value} Zeichen lang sein.
zem_contact_message => Nachricht
zem_contact_minval_warning => &#8222;<strong>{field}</strong>&#8220; muss mindestens {value} sein.
zem_contact_min_warning => &#8222;<strong>{field}</strong>&#8220; muss mindestens {value} Zeichen lang sein.
zem_contact_name => Name
zem_contact_option => Option
zem_contact_pattern_warning => &#8222;<strong>{field}</strong>&#8220; entspricht nicht dem Muster {value}.
zem_contact_radio => Optionsfeld
zem_contact_recipient => Empfänger
zem_contact_refresh => Folgen Sie diesem Link, falls die Seite nicht automatisch neu geladen wird.
zem_contact_secret => Geheimnis
zem_contact_send => Senden
zem_contact_send_article => Artikel senden
zem_contact_spam => Danke, Spam-Mail wird nicht akzeptiert!
zem_contact_text => Text
zem_contact_to_missing => Die E-Mail-Adresse des &#8222;<strong>Empfängers</strong>&#8220; fehlt.
#@public
#@language es-es
zem_contact_checkbox => Casilla de verificación
zem_contact_contact => Contacto
zem_contact_email => Correo electrónico
zem_contact_email_subject => {site} > Consulta
zem_contact_email_thanks => Gracias, el mensaje ha sido enviado.
zem_contact_field_missing => Falta el campo obligatorio &#8220;<strong>{field}</strong>&#8221;.
zem_contact_format_warning => El valor {value} en &#8220;<strong>{field}</strong>&#8221; no está en el formato esperado.
zem_contact_form_expired => El formulario ha caducado, por favor inténtelo de nuevo.
zem_contact_form_used => El formulario ya había sido enviado, por favor rellene el formulario de nuevo.
zem_contact_general_inquiry => Consulta general
zem_contact_invalid_email => La dirección de correo electrónico &#8220;<strong>{email}</strong>&#8221; no es válida.
zem_contact_invalid_host => El dominio de correo electrónico &#8220;<strong>{host}</strong>&#8221; no es válido.
zem_contact_invalid_utf8 => &#8220;<strong>{field}</strong>&#8221; contiene caracteres UTF-8 no válidos.
zem_contact_invalid_value => Valor incorrecto para &#8220;<strong>{field}</strong>&#8221;, &#8220;<strong>{value}</strong>&#8221; no es una de las opciones disponibles.
zem_contact_mail_sorry => Lo siento, el correo electrónico no pudo ser enviado.
zem_contact_maxval_warning => &#8220;<strong>{field}</strong>&#8221; no debe exceder {value}.
zem_contact_max_warning => &#8220;<strong>{field}</strong>&#8221; no debe contener más de {value} caracteres.
zem_contact_message => Mensaje
zem_contact_minval_warning => &#8220;<strong>{field}</strong>&#8221; debe tener al menos {value}.
zem_contact_min_warning => &#8220;<strong>{field}</strong>&#8221; debe contener al menos {value} caracteres.
zem_contact_name => Nombre
zem_contact_option => Opción
zem_contact_pattern_warning => &#8220;<strong>{field}</strong>&#8221; no encaja con el patrón {value}.
zem_contact_radio => Botón de opción
zem_contact_recipient => Destinatario
zem_contact_refresh => Siga este enlace si la página no se recarga automáticamente.
zem_contact_secret => Secreto
zem_contact_send => Enviar
zem_contact_send_article => Enviar artículo
zem_contact_spam => Gracias, ¡pero no se acepta correos electrónicos basura!
zem_contact_text => Texto
zem_contact_to_missing => Falta la dirección de correo electrónico del &#8220;<strong>destinatario</strong>&#8221;.

Last edited by GugUser (2017-01-18 17:29:23)

maniqui · 2017-02-01 23:24:59

Feature request: to be able to craft different email bodies for contact form recipient and “copysender” recipient.

Use case: you may want to have some hidden/secret fields on your contact form message and only include them on the email sent to the contact form recipient, while excluding them from the “copysender” recipient. Or maybe you want to add some extra message for the “copysender” recipient so to explain him why is he receiving a copy of the email or whatever.

I thought that testing for copysender value inside body_form could be a solution, but I checked the plugin source code and it seems that the $msg payload is the same for both messages.

Thanks.

maniqui · 2017-02-02 20:20:12

Another feature request: make the appending of the URL fragment (the one that identifies & anchors to the contact form element: e.g. #zcr1234567abcdefg) to the action attribute optional, as it may affect the functionality of the redirect option.
How does the appending of the URL fragment to the action attribute affect the redirect functionality?
After submitting the form, when the destination URL also has the contact form rendered (for example, in a site-wide contact form present in the site footer), the user gets scrolled down to the form again, instead of being presented with whatever is in the redirect URL (usually, a “thank you” message and some call to actions).

I’d say that it might be safe to make them mutually exclusive: if the redirect option is used, it seems undesirable/unnecessary to have the URL fragment appended to the action attribute.

PS: should I re-post this feature request and the previous one as issues on the GH page for ZCR?

Bloke · 2017-02-03 00:06:43

Thanks for the feature requests, maniqui. Both worth considering I think.

Please if you would open issues for them in GitHub it’ll be easier for me to track (and not forget about them). Feel free to just reference these posts instead of writing it all out again in the Issue text. Thanks.

lythande · 2017-02-12 15:14:56

Hi,

Iam not sure to understand. I using the actually textpattern-cms-version and this plugin zem_contact_reborn v4.5.0.0 and is activated.
I have installing zem_contact_lang-de too and is activated. But it seem that the zem_contact_lang-de don’t work.

How I can install the language German for output the error-info or output-message in german after send the contact-formular?

GugUser · 2017-02-12 18:15:05

In the form tag you can include a thanks_form.

<txp:zem_contact to="x@y" … form="kontakt" thanks_form="kontakt-danke" copysender="1" />

Respect to the error message, it seems that the textpack doesn’t work correctly. If a required field is empty, so the error message is:

Required field, “<strong>{field}</strong>” is missing.

The German translation from line 199 in the textpack isn’t used:

zem_contact_field_missing => Erforderliche Eingabe im Feld “<strong>{field}</strong>” fehlt.

kees-b · 2017-02-13 11:11:15

nl-nl.textpack added in github

kees

Bloke · 2017-02-13 23:33:29

GugUser wrote #303991:

Respect to the error message, it seems that the textpack doesn’t work correctly.

It should. Pat64 raised this issue and I addressed it so error messages appear in the site language. In 4.6.2 it defaults of course to the admin-side language in use, but if your site content is in German, add lang="de-de" to your <txp:zem_contact> tag and the errors should come out in that language. And “de-de” can be injected programmatically via other tags if you run (for example) MLP or some other language capable plugin.

kees-b wrote #303995:

nl-nl.textpack added in github

Awesome, thanks. I’ll merge that in when I can.

Last edited by Bloke (2017-02-13 23:34:51)

GugUser · 2017-02-14 00:51:05

Bloke wrote #304011:

In 4.6.2 it defaults of course to the admin-side language in use, but if your site content is in German, add lang="de-de" to your <txp:zem_contact> tag and the errors should come out in that language. And “de-de” can be injected programmatically via other tags if you run (for example) MLP or some other language capable plugin.

In the case of the site I’m working, this is not so. The admin language is German and now I added the lang="de-de" attribute to the <txp:zem_contact /> tag, but the error messages still are in English. I tried the same with lang="fr-fr". It also doesn’t work.

Last edited by GugUser (2017-02-20 03:36:27)

lythande · 2017-02-16 17:09:26

GugUser wrote #304012:

In the case of the site I’m working, this is not so. The admin language is German an now I added the lang="de-de" attribute to the <txp:zem_contact /> tag, but the error messages still are in English. I tried the same with lang="fr-fr". It also doesn’t work.

On my site too, the error is still in english. I have lang="de-de" inside <txp:zem_contact /> tag.
Edit: you can testing it on www.artwesertor.de/kontakt

How I can make a “*” after a label-text, if this is required?

Last edited by lythande (2017-02-16 17:10:38)

uli · 2017-02-16 22:23:42

lythande wrote #304058:

How I can make a “*” after a label-text, if this is required?

You could simply use CSS and a rule like this:

.zemRequired::after {
    content: " *";
    color: red;
    font-weight: bold;
}

In case you’d also want to cover browsers without CSS support or switched off you’d need some PHP in order to alter the HTML, e.g.

<txp:php>echo preg_replace('/CODE TO LOOK FOR/','REPLACEMENT CODE', parse('<txp:YOUR ZEM_CONTACT_TAG />'));</txp:php>

Leave the slashes around the search term, it won’t work otherwise. And make sure both your CODE TO LOOK FOR and your REPLACEMENT CODE do not contain single quotes.

Textpattern CMS

Textpattern CMS support forum

#151 2017-01-18 13:17:47

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

#152 2017-01-18 13:36:43

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

#153 2017-01-18 16:34:13

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

#154 2017-01-18 17:18:28

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

GugUser wrote #303619:

#155 2017-01-18 17:28:25

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

#156 2017-02-01 23:24:59

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

#157 2017-02-02 20:20:12

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

#158 2017-02-03 00:06:43

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

#159 2017-02-12 15:14:56

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

#160 2017-02-12 18:15:05

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

#161 2017-02-13 11:11:15

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

#162 2017-02-13 23:33:29

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

GugUser wrote #303991:

kees-b wrote #303995:

#163 2017-02-14 00:51:05

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

Bloke wrote #304011:

#164 2017-02-16 17:09:26

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

GugUser wrote #304012:

#165 2017-02-16 22:23:42

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

lythande wrote #304058:

Board footer