how to avoid back button clearing form data
Permalink
I'm moving a website from dreamweaver to concrete5. One webpage has a large form of input fields. When the user clicks submit, a php script runs and echos text to the screen. The user clicks the back button to go back to the form.
In the Dreamweaver website, the form data displays after the user clicks the back button. In the concrete5 version using the same html and javascript, the form data is cleared after the user clicks the back button.
Is there a way to have the form data exist after hitting the back button? Is it something in concrete5 that causes this, or perhaps Apache webserver (or htaccess)?
For example, if I visitwww.www.mydomain.com/this-is-my-page/,... does concrete5 map this to some other URL, and this mapping process causes the page to reload?
I'm using pretty URLs.
In the Dreamweaver website, the form data displays after the user clicks the back button. In the concrete5 version using the same html and javascript, the form data is cleared after the user clicks the back button.
Is there a way to have the form data exist after hitting the back button? Is it something in concrete5 that causes this, or perhaps Apache webserver (or htaccess)?
For example, if I visitwww.www.mydomain.com/this-is-my-page/,... does concrete5 map this to some other URL, and this mapping process causes the page to reload?
I'm using pretty URLs.
Forms in concrete5 are not a trivial thing. Existing forms rarely import well because they don't have a matching controller.php file that does the processing in concrete5. I usually re-create these forms either using the built-in Form block or with ProForms or Formidable or some other 'premium' form add-on from the marketplace.
