Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Anti spam fields not verified | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Anti spam fields not verified

Anti spam fields not verified

Posted: January 7, 2013 at 9:36 am

Viewing 4 reply threads


Randy

January 7, 2013 at 9:36 am

After upgrading to 3.1.29.1.P today I am now getting error messages after clicking to confirm a registration. This is error message:

Sorry, an error occured and the anti-spam fields could not be verified. Please contact the site admin or click your browser’s back button and try again.

Any suggestions? I have recaptcha turned on and it seems to accept my input and return me to the confirm registration page but when clicking to confirm I get the error.


Josh

January 7, 2013 at 10:24 am

Hi Randy,

I looks like there may be out of date template files in /wp-content/uploads/espresso/templates. Can you check there for files that may have been copied over from a prior version? You can re-name that directory so that the current version’s template files will be used instead.


Randy

January 7, 2013 at 12:57 pm

All the files in the templates folder are dated 4/19/2012 which is when we initially installed everything. When I did the last update these files were not replaced and I’m not clear on where the newest template files would be found.

On the templates page was a button to click to change the name of the templates folder which it did and the problem with the anti spam fields error is resolved. I now need to replace one file that I made a change to which is the payments_page.php file.

My question now is when clicking the button the wp-content/uploads/espresso/templates folder is still named /templates and not the name that the button on the templates settings page said it should be which is wp-content/uploads/espresso/templates-2013-01-07-13-37-09/ and I was curious why the change isn’t seen when I FTP into my site?

Thanks for your help.


Josh

January 7, 2013 at 1:46 pm

Hi Randy,

Templates should only be copied to /wp-content/uploads/espresso/templates if there are going to be modifications made to them. The templates that are included with Event Espresso are in the wp-content/plugins/event-espresso/templates. Please be sure to copy over a fresh version of payment_page.php from the current version and modify that file instead of copying over the older one.

When you click the button on the Event Espresso>Templates page to rename the templates directory, it will rename the old one and create a new /templates directory. You may need to refresh your FTP client in order to see the change.


Randy

January 8, 2013 at 1:00 pm

Thanks Josh, I got it all figured out. I appreciate your help.
Viewing 4 reply threads

The support post ‘Anti spam fields not verified’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

The original Forum description...

Status: closed

Updated by Randy 12 years ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server