Skip to content

Samuel Aguilera Posts

Reply-To field ignored by email client

In this article I’ll try to give you an easy view of what’s the Reply-To field, and a common issue that you may find specifically if you’re using Gmail/G Suite as email client, althought you can find userful information also if you’re experiencing this issue with any other email client.

What’s the Reply-To field?

Its name explain by itself, it’s a field where you put an email address that should be used to reply the email. An extended version of the field name would be “reply to this address not to the one in the from address!”.

Do you want a more technical explanation? Ok, per RFC 5322, the technical document that sets the starndard for emails, the Reply-To field is part of the originator fields for an email and:

When the “Reply-To:” field is present, it
indicates the address(es) to which the author of the message suggests
that replies be sent. In the absence of the “Reply-To:” field,
replies SHOULD by default be sent to the mailbox(es) specified in the
“From:” field unless otherwise specified by the person composing the
reply.

Pay attention to the word suggests in the above quote from the RFC document, it’s important. That means your email client is not required to follow your indication.

How to use it?

Just put whatever valid email address(es) you want on it. That’s all buddy! No special setup needed, no magic, it’s just another field of the email message where you put an email address, just like the From or the To fields.

This means an important thing. It doesn’t matter what you’re using to create the email, it can be an email client, a WordPress plugin or whatever, as long as the email created by the software you’re using has the email address you wanted in the Reply-To field, its job is done. If your email client is not using the Reply-To address, that’s a completely different story.

Casilla para política de privacidad en Gravity Forms

Tener una casilla de aceptación de la política de privacidad en un formulario ya sea de contacto o de suscripción a un boletín es algo que ya era obligado para cumplir con las leyes de protección de datos vigentes en España.

Pero con la inminente entrada en vigor de los cambios a nivel europeo (la llamada GDPR), los que no la tenían se están animando a ponerla ahora…

Hacer esto en Gravity Forms es muy sencillo, pero si no tienes tienes mucha experiencia en el uso de Gravity Forms o sencillamente nunca lo has usado y te preguntas como te podría ayudar Gravity Forms con este tema, sigue leyendo y saldrás de dudas.

Formularios supervitaminados con Gravity Forms

Este pasado fin de semana estuve dando una pequeña charla en WordCamp Zaragoza sobre casos de uso habituales con Gravity Forms. El objetivo de mi charla era mostrar a los asistentes algunas de las cosas que se pueden hacer con este plugin, ya que a pesar de que su nombre es muy conocido entre el público español, no lo son tanto sus capacidades.

Validar un NIF con Gravity Forms

Cuando pedimos a un usuario que introduzca su NIF en un campo de un formulario, tan importante como guardar ese dato es validar el dato antes de guardarlo, pues no tiene ningún sentido guardar un dato que no es válido y por tanto no vamos a poder usar para cualquiera que sea el cometido para el que le hemos pedido al usuario que nos lo proporcione.

Aunque Gravity Forms no trae de serie un tipo de campo específico para validar el NIF, afortunadamente, pone a nuestra disposición filtros con los que podemos validar cualquier dato introducido en un campo del formulario con nuestra propia función de validación. De esta manera no sólo podemos validar un NIF sino cualquier otro tipo de dato que necesitemos validar.

cURL error 28 in WordPress

So you’re trying to use your favorite WordPress plugin but an ugly cURL error 28 is being displayed in your screen or error log… Something like

cURL error 28: Connection timed out after X milliseconds

or

cURL error 28: Operation timed out after X milliseconds with 0 out of 0 bytes received

What’s going on? If you search in Google you will find that in fact it’s a very common issue and it’s not tied to any plugin or WordPress itself, it’s something directly related with a server component, the cURL library, so it can affect to any web software using cURL.

In this article I’m going to explain you a few things that hopefully will help you to understand what’s the issue and things that you may check in order to fix it.

But what the hell is cURL?

cURL LogoWhen talking about WordPress, cURL is a PHP library that helps WordPress to communicate with other sites. Being a PHP library means that if you’re using an obsolete PHP version (anything older than PHP 7.0) you’re for sure also using an obsolete cURL version. So the first thing you need to do if you’re having issues with cURL is to upgrade your PHP version to at least 7.0.x or the latest PHP 7.x stable release.

Note that on some server setups (e.g. cheap shared hosting) selecting a newer PHP version to run your site doesn’t necessarily means that you’re going to use a recent cURL version.