https://legacy.forums.gravityhelp.com/topic/form-fields-do-not-display-in-back-end-after-upgrade Gravity Support Forums Topic: Form Fields do not display in back end after upgrade en-US Tue, 21 Apr 2026 11:30:31 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/form-fields-do-not-display-in-back-end-after-upgrade#post-357187 Tue, 02 Jul 2013 04:12:17 +0000 OD 357187@https://legacy.forums.gravityhelp.com/ <p>Ok Solved for me. This requires Setting&gt; Uninstall and after a Re-Download GravityForm. To have your forms, don't forget to export it before uninstall GF. The automatique upgrade seems to be the issue. </p> https://legacy.forums.gravityhelp.com/topic/form-fields-do-not-display-in-back-end-after-upgrade#post-357088 Tue, 02 Jul 2013 03:19:19 +0000 OD 357088@https://legacy.forums.gravityhelp.com/ <p>Same issue for me. I have this message "This form has not all fields." instead of my fields! Even after "Meta Recovery Tool" which indicated that the operation was successful. GF 1.7.6 and WP 3.5 </p> https://legacy.forums.gravityhelp.com/topic/form-fields-do-not-display-in-back-end-after-upgrade#post-356460 Mon, 01 Jul 2013 20:28:07 +0000 cirrusdev 356460@https://legacy.forums.gravityhelp.com/ <p>Was this resolved? I have a similar issue and the Meta Recovery Tool returned "This form's meta could not be recovered." for all my forms. </p> https://legacy.forums.gravityhelp.com/topic/form-fields-do-not-display-in-back-end-after-upgrade#post-232493 Wed, 01 May 2013 17:37:05 +0000 leoraw 232493@https://legacy.forums.gravityhelp.com/ <p>Sent. </p> https://legacy.forums.gravityhelp.com/topic/form-fields-do-not-display-in-back-end-after-upgrade#post-232488 Wed, 01 May 2013 17:30:21 +0000 David Peralty 232488@https://legacy.forums.gravityhelp.com/ <p>Can you send me an admin login to <a href="mailto:peralty@rocketgenius.com">peralty@rocketgenius.com</a> so I can log in and take a look please? </p> https://legacy.forums.gravityhelp.com/topic/form-fields-do-not-display-in-back-end-after-upgrade#post-232453 Wed, 01 May 2013 16:23:44 +0000 leoraw 232453@https://legacy.forums.gravityhelp.com/ <p>No, did not work. I tried two forms. For both, I get:<br /> "This form doesn't have any fields yet. Follow the steps below to get started." </p> https://legacy.forums.gravityhelp.com/topic/form-fields-do-not-display-in-back-end-after-upgrade#post-232447 Wed, 01 May 2013 16:20:25 +0000 David Peralty 232447@https://legacy.forums.gravityhelp.com/ <p>Go to Forms -&gt; Meta Recovery and select the form you want to recover and click submit. Let me know if this helps. </p> https://legacy.forums.gravityhelp.com/topic/form-fields-do-not-display-in-back-end-after-upgrade#post-232438 Wed, 01 May 2013 16:15:44 +0000 leoraw 232438@https://legacy.forums.gravityhelp.com/ <p>OK, I installed and activated the Meta Recovery plugin. How do I run it? </p> https://legacy.forums.gravityhelp.com/topic/form-fields-do-not-display-in-back-end-after-upgrade#post-232435 Wed, 01 May 2013 16:11:41 +0000 David Peralty 232435@https://legacy.forums.gravityhelp.com/ <p>Forms are stored in the database, but the upgrade might not have gone well. Can I have you download and install the Meta Recovery plugin from the Downloads page please? <a href="http://www.gravityhelp.com/downloads/" rel="nofollow">http://www.gravityhelp.com/downloads/</a> </p> https://legacy.forums.gravityhelp.com/topic/form-fields-do-not-display-in-back-end-after-upgrade#post-232434 Wed, 01 May 2013 16:10:13 +0000 leoraw 232434@https://legacy.forums.gravityhelp.com/ <p>WP 3.5.1<br /> "Do your forms show up on the pages they are embedded into? " no<br /> See: <a href="http://www.scotlib.org/contact-the-childrens-room/" rel="nofollow">http://www.scotlib.org/contact-the-childrens-room/</a><br /> Form preview: "Oops! We could not locate your form."</p> <p>When I try to add a field to Test Form, it complains that there already is a form with that name. I created that form today - cannot add any fields to it.</p> <p>I'm wondering if there is underlying file permission problems (we are on a state server). </p>