Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#145 2016-12-15 20:23:52

els
Moderator
From: The Netherlands
Registered: 2004-06-06
Posts: 7,458

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

maverick wrote #303275:

“Els wrote”

Els!! :)

Nice to see you chime in! You’ve been missed.

Thank you Mike :) I have not disappeared, just being invisible for a while ;) I’ll be back on a more regular basis soon I hope!

Offline

#146 2016-12-16 13:20:50

maverick
Member
From: Southeastern Michigan, USA
Registered: 2005-01-14
Posts: 976
Website

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

Els wrote #303277:

I’ll be back on a more regular basis soon I hope!

Good to hear!

Offline

#147 2016-12-18 21:15:19

RedFox
Member
From: Netherlands
Registered: 2005-03-25
Posts: 805
Website

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

@Els: Do you have a raw copy (.txt) of the .inc file? Maybe I can help to look into the NL translation … :)

@Everybody: Where do I find the EN textpack (.txt)? So I can try to make a NL version …

Last edited by RedFox (2016-12-19 12:14:15)

Offline

#148 2016-12-19 16:19:26

kuopassa
Plugin Author
From: Porvoo, Finland
Registered: 2008-12-03
Posts: 228
Website

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

^ Bloke’s Github page has this file.

Offline

#149 2016-12-19 17:14:49

RedFox
Member
From: Netherlands
Registered: 2005-03-25
Posts: 805
Website

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

Thanks Petri for the link …. :)

Last edited by RedFox (2016-12-19 18:41:34)

Offline

#150 2016-12-23 19:40:31

els
Moderator
From: The Netherlands
Registered: 2004-06-06
Posts: 7,458

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

RedFox wrote #303296:

@Els: Do you have a raw copy (.txt) of the .inc file? Maybe I can help to look into the NL translation … :)

Hi Joop, apologies for the belated reply (I’ve been out of the country for a couple of days). I honestly don’t know how to turn the .inc file into a text file… if you have a Txp site with MLP and zem_contact_reborn, you can import it (MLP > Plugins).

Offline

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

GugUser
Member
From: Quito (Ecuador)
Registered: 2007-12-16
Posts: 1,473

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

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?

Offline

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

GugUser
Member
From: Quito (Ecuador)
Registered: 2007-12-16
Posts: 1,473

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

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

Offline

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

GugUser
Member
From: Quito (Ecuador)
Registered: 2007-12-16
Posts: 1,473

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

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)

Offline

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

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 11,251
Website GitHub

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

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.


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

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

GugUser
Member
From: Quito (Ecuador)
Registered: 2007-12-16
Posts: 1,473

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

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)

Offline

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

maniqui
Member
From: Buenos Aires, Argentina
Registered: 2004-10-10
Posts: 3,070
Website

Re: zem_contact_reborn v4.5.0.0: contact mail form processing

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.


La música ideas portará y siempre continuará

TXP Builders – finely-crafted code, design and txp

Offline

Board footer

Powered by FluxBB