Module

Developer
Supported

EE 1
EE 2
ProForm Drag and Drop Form Builder

Back to this add-on's main page
View Other Add-ons From Isaac Raway

     

You must be logged in to post.

[Resolved] Request could not be authenticated

Support Request

anthonycollini
anthonycollini

I just purchased the addon, but cannot get it to work. I am using the example form template with the form_name parameter changed to my form name.

I am receiving a white page with the error message : Request could not be authenticated

I am using the newest version of the proform addon as well as EE. It’s the only form on the contact page along with a google map.

Please advise.

ac.

airways
# 1
Developer
airways

Is the form hosted in a template that is the target of a POST from another location such as a registration form, shopping cart, or something else?

Also make sure you have setup an encryption_key according to these instructions. The encryption key should be set in your system/expressionengine/config/config.php file and needs to be 32 characters long.

anthonycollini
# 2
anthonycollini

Nope, the form is just on a contact page using the template group > template system (domain.com/contact). I do have an encryption key set up similar to this one: C3FDD0439E6C628EC5E28B10AAEB746319BAE130ADA2392A0425FAC71DC8B158

airways
# 3
Developer
airways

It looks like that key is 64 characters long. Can you try it with a 32 character key?

anthonycollini
# 4
anthonycollini

Okay, cut it down to 32 characters, and the form loads now.  However, the error still happens if you refresh the page while on the contact page.

airways
# 5
Developer
airways

Are you refreshing a form submission? Form submissions can only be used once, and this error message is shown when a previously submitted form is submitted again.

The next version should have an option to disable this. For now you can comment out this line in mod.proform.php, on or around line 989:

if ($this->EE->security->check_xid($this->EE->input->post('XID')) == FALSE) exit('Request could not be authenticated'); 

However I do not recommend doing this as it is part of how ProForm is able to prevent spam: a spam script must first load the form to get a valid XID to submit along with the form submission, which is more complicated than most spammers bother with.

airways
# 6
Developer
airways

Hi Anthony,

Where you able to resolve this?

airways
# 7
Developer
airways

Hi Anthony, I’m going to close this thread since there hasn’t been any activity. If you are having a specific issue other than with the XID as noted above, please post a new request.

Also, I have added the option I described above that would disable XID checking without needing this hack. This will come with the next release.