Skip to content

Samuel Aguilera Posts

Taller de “Seguridad en WordPress” en Congreso Web

El próximo viernes 2 de junio de 16:10 a 18:10 en la “Sala WordPress” estaré dando un taller sobre seguridad en WordPress en el Congreso Web (CW17).

Seguridad en WordPress, CW17Según tengo entendido este congreso está orientado principalmente a profesionales del marketing, por lo que doy por hecho que el nivel técnico de los asistentes no es muy alto, así que el taller irá orientado a dicho perfil de usuario, tratando que la gente que no tiene grandes conocimientos técnicos sea capaz de entender la importancia de la seguridad en WordPress y como sentar las bases para tener un WordPress protegido ante los ataques más habituales.

Use Stripe coupons with Gravity Forms

Gravity Forms has a Stripe add-on that allows you to charge your users at form submission using your account, but this add-on doesn’t support (currently) coupons created at your Stripe account.

Gravity Forms has a also its own Coupons add-on. Using this add-on you can create a workaround for the mentioned limitation of the Stripe add-on.

Basically we’re going to use the coupon at, a coupon created in the Gravity Forms Coupons add-on with the same name and discount, and a little snippet of code. Simply follow the steps below.

Gravity Forms merge tags as Default Value for form fields

If you’re new to Gravity Forms merge tags you may think, what the hell is a merge tag? Well they’re placeholders that are replaced dynamically by the value associated to them when used in some places like notifications or confirmations content and the default value setting for fields that supports it.

By default Gravity Forms provides a bunch of useful merge tags to insert values like the first name or the email of the currently logged user, the IP of the user, the title or ID of the page from where the user is submitting the form, or even the value of a custom post meta, and many other interesting data, I would recommend you to take a look to the Gravity Forms merge tags doc page to check them all.

I’m going to show you some real use case examples of how you can use the merge tags based on commonly asked questions that we see in support.

Charla “Introducción a Gravity Forms”

El pasado 25 de enero di una pequeña charla de introducción al uso de Gravity Forms en la Meetup WordPress Zaragoza. Que todo sea dicho de paso me olvidé de anunciar aquí…

A continuación os dejo el enlace a la presentación, si bien en esta ocasión la charla era más práctica que teórica, así que la presentación es más bien un guión de lo que fui desarrollando en la charla.

ERROR for site owner: Stoken disabled in reCAPTCHA field for Gravity Forms

reCAPTCHA Stoken Expired error
reCAPTCHA Stoken Expired error

Since Gravity Forms 2.0 the new “no captcha” reCAPTCHA  API is included in Gravity Forms. This was a highly requested feature and works pretty fine for most users, but sometimes specially if you’re using old reCAPTCHA keys or the reCAPTCHA authentication in Gravity Forms settings was done using previous API version you can get one of the following pretty cryptic message in your reCAPTCHA field:

ERROR for site owner: Stoken disabled or Error for site owner: Stoken expired