I have the latest version of ChronoForms & Joomla. I have a problem where if a user types in all their information on their browser, and hits the back or forward button and comes back to the form page they will lose all the data entry they have typed. I have tested this on IE8, firefox 3.5, and latest version of opera and this problem occurs on all of them. I have cache enabled in my global configuration and I still have this issue.
If anyone can give me any suggestions, I would appreciate it.
Hi jebediah,
That's more or less how browsers work. Not all of them will keep the data if you leave the page (though I seem to recall that FireFox does sometimes). You could add a message suggesting that that stay on the page until they hit the submit button?
If you turn on "Republish fields if error occured" in the Form General Tab then ChronoForms will republish the data when it can - but this may not include leaving the page and returning.
Bob
Thank you for your response. It's odd because usually in other forms, order forms, contact us forms you can hit back and come back and the data is still there. I'll put that verbiage there then warning users their data will get lost😟. Appreciate your assistance.
That makes sense nml375. I know in Joomla Configuration you can enable cache, but in my case that did no good. I wonder if there is a way to alter the settings so it keeps everything in cache. If so, then that would be one huge headache out of the way for a lot of users who utilize chronoforms for their visitors.
Would this be called header.php? Any idea where I can find it to modify the settings?
nml375, thank you so much. Your code worked and I personally think this code should be applied to future versions of chronoforms as it would prove very beneficial and convenient.
Hi Stephen & Bob,
There's indeed a flaw in my previous post, I'll update that as soon as I'm done with this.
The getExpire() method may not be called as a class-method, but only as an instance-method. Thus, the proper call should be $session->getExpire() (in addition to calling the JFactory::getSession() method as described by Bob).
/Fredrik