Hi and apologies if this is the wrong place to post but I'm having a problem with a form which when submitted in FireFox it works fine, but if I submit it using IE7 it fails?
The form is here: https://www.vitamix.co.uk/index.php?option=com_content&view=article&id=92 and is simply a newsletter sign-up with a targetted landing page.
In FireFox, the form submits and the correct landing page appears, but in IE7 submitting the form instead displays "You are not allowed to access this URL" ?
The session lifetime is set to 150 Minutes, so I am assuming that it can't be a timeout issue, especially as the form is so short?
Any advice would be appreciated.
Thanks in advance.
Dave.
The form is here: https://www.vitamix.co.uk/index.php?option=com_content&view=article&id=92 and is simply a newsletter sign-up with a targetted landing page.
In FireFox, the form submits and the correct landing page appears, but in IE7 submitting the form instead displays "You are not allowed to access this URL" ?
The session lifetime is set to 150 Minutes, so I am assuming that it can't be a timeout issue, especially as the form is so short?
Any advice would be appreciated.
Thanks in advance.
Dave.
Hi Dave,
I'm guessing wildly here but could this to be with sessions and https?? Try turning the Security token check off in the Form General Tab and see if that makes a difference.
Bob
I'm guessing wildly here but could this to be with sessions and https?? Try turning the Security token check off in the Form General Tab and see if that makes a difference.
Bob
security token made no difference. IE doesnt' like something. its definitely a major problem.
Thanks guys for your replies...but I can't see where the tab is for a security token check when I go to edit the form itself? Should I be looking under a different area?
Thanks,
Dave.
Thanks,
Dave.
Hi Dave,
In the latest release it's the 'check Token' item under Other Form Setting on the General Tab.
Bob
In the latest release it's the 'check Token' item under Other Form Setting on the General Tab.
Bob
Hi Bob,
I don't seem to have that option? How do I know what version of CF I am running?
Under Modules it says: Chrono Contact 3.1RC1 16.02.2009
Couuld this be my problem - i.e. not using the latest version?
Thanks,
Dave.
I don't seem to have that option? How do I know what version of CF I am running?
Under Modules it says: Chrono Contact 3.1RC1 16.02.2009
Couuld this be my problem - i.e. not using the latest version?
Thanks,
Dave.
Hi proteus,
You can see the version numbers from the tabs on the Joomla Installer page - the current release is RC 5.3 for the component and RC5.2 for the Plugin & Module (I think that's correct).
You should upgrade if you can - Max has made some improvements with this problem.
Bob
You can see the version numbers from the tabs on the Joomla Installer page - the current release is RC 5.3 for the component and RC5.2 for the Plugin & Module (I think that's correct).
You should upgrade if you can - Max has made some improvements with this problem.
Bob
Thanks,
I'll take a look at the upgrade. What will happen to the original forms? Will they change during an upgrade? I'm reluctant to change things too much for fear of loosing some other functionality.
Thanks for you help so far Bob, it's much appreciated.
Dave.
I'll take a look at the upgrade. What will happen to the original forms? Will they change during an upgrade? I'm reluctant to change things too much for fear of loosing some other functionality.
Thanks for you help so far Bob, it's much appreciated.
Dave.
Hi Dave,
Have a look on the downlaod page - I think that the upgrade from 3.1 is just to install over the existing installation (best to back up forms and database first though).
Bob
Have a look on the downlaod page - I think that the upgrade from 3.1 is just to install over the existing installation (best to back up forms and database first though).
Bob
Hi Bob,
We upgraded just as you said to V3.1 RC5.3 (after some problems in Joomla which required us changing the path the tmp folder) and then we were able to proceed with the upgrade which installed over the top of the old version. We then performed the SQL update and unchecked the "check token" box as you suggested.
Everything now works! 😀
Thanks for all your help.
Dave.
We upgraded just as you said to V3.1 RC5.3 (after some problems in Joomla which required us changing the path the tmp folder) and then we were able to proceed with the upgrade which installed over the top of the old version. We then performed the SQL update and unchecked the "check token" box as you suggested.
Everything now works! 😀
Thanks for all your help.
Dave.
This topic is locked and no more replies can be posted.