https://legacy.forums.gravityhelp.com/topic/multi-page-forms-seem-broken-in-162 Gravity Support Forums Topic: Multi-page forms seem broken in 1.6.2 en-US Sat, 04 Apr 2026 18:19:01 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/multi-page-forms-seem-broken-in-162#post-44304 Sat, 17 Dec 2011 09:09:58 +0000 Rob Harrell 44304@https://legacy.forums.gravityhelp.com/ <p>Thanks for letting us know! </p> https://legacy.forums.gravityhelp.com/topic/multi-page-forms-seem-broken-in-162#post-44303 Sat, 17 Dec 2011 09:02:02 +0000 webcom 44303@https://legacy.forums.gravityhelp.com/ <p>This seemed to be a conflict with one of our plugins. A fresh WP install with Gravity worked fine. </p> https://legacy.forums.gravityhelp.com/topic/multi-page-forms-seem-broken-in-162#post-43062 Sun, 04 Dec 2011 15:56:21 +0000 Chris Hajer 43062@https://legacy.forums.gravityhelp.com/ <p>Did you migrate hosts or domains or anything like that? That error is common in that situation.</p> <p>If not, sounds like a theme or plugin conflict, which would be weird because you are experiencing it in preview mode. </p> <p>It's not a common problem as I was just working with a 10 page form on 1.6.2. So there is something weird going on in your installation. Any ideas what else might have been changed at the same time, or recently? </p> https://legacy.forums.gravityhelp.com/topic/multi-page-forms-seem-broken-in-162#post-43055 Sun, 04 Dec 2011 11:32:44 +0000 webcom 43055@https://legacy.forums.gravityhelp.com/ <p>Hmm...same thing seems to happen in 1.5.3. Am I missing something? </p> https://legacy.forums.gravityhelp.com/topic/multi-page-forms-seem-broken-in-162#post-43054 Sun, 04 Dec 2011 11:24:48 +0000 webcom 43054@https://legacy.forums.gravityhelp.com/ <p>Removed Gravity 1.5.3</p> <p>Installed Gravity 1.6.2</p> <p>Created a 2-page form with a single text-entry field on each page. Hit 'preview'. Page 1 comes up, but page 2 says "oops, we could not locate your form".</p> <p>Same behavior when trying to view the published form normally. </p>