PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Setup a testsite on local machine, but form will not save and fields are lost

  1. Hi.
    I have a huge form setup on this site. http://forsikringsdeal.dk/. Unfortunately, you have to be logged ind to see the form.
    We run the latest version of WP 3.5.1, but have not updated to the latest version of GravityForms. We need to do some testing first and also we plan to make some big changes to the site, hence I have setup a copy of the site on a local machine. The Gravityforms version we use now is 1.6.12.
    However, I am having problems getting the form to work on the local machine. I have exported the data with phpMyAdmin. I have read that it can cause issues and have also installed and run the meta recovery plugin. But still, when I try to make changes to the form, it returns with a page where I have to create a new form. I have testet it in GravityForms 1.6.12 and 1.7.2. See screenshot: https://www.evernote.com/shard/s3/sh/6be961c6-40b4-416a-8dbc-1ea749a886d3/bb126703cdbbf90e2ed0ef81667a911a

    The fields are not lost, so when I exit the page and go back into the form editor, the fields are back. But it will not let me save any modifications.

    I need all the entries for this form, hence I cannot just export and import xml data, as this creates a new form without all the entries.

    Is there anything I can do to fix this?
    It worries me a bit actually, as of right now, we don't have a functioning backup process if our site is hacked and data is lost. I mean, we have a backup, but the backup will not get us a functioning form again.
    Hope there is a solution.
    Thanks
    Vayu

    Posted 10 years ago on Wednesday May 8, 2013 | Permalink
  2. Handling via priority support.

    Posted 10 years ago on Monday May 13, 2013 | Permalink

This topic has been resolved and has been closed to new replies.