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.

Form does not appear

  1. I've just discovered since upgrading to WP32 and Thesis 182 that the Gravity Form does not appear on the Contact Page I designed at http://www.halfwaytoconcord.com

    <h2><p class="alert">Send BGR a message in the form below</p></h2>

    [gravityform id=3 name=CONTACT HALFWAY TO CONCORD ajax=true]

    The form appears in the PREVIEW mode of the plugin, but not in the preview mode for the page itself.

    I have checked against all plugins and twenbty eleven and same problem:.

    Posted 13 years ago on Monday July 11, 2011 | Permalink
  2. It sounds like something is wrong, either with the page content or your WordPress site. If the shortcode is being displayed then your WordPress site isn't parsing shortcodes. I would first suggest editing that page, delete the shortcode and then re-add it and save the page again. Then check it.

    Posted 13 years ago on Monday July 11, 2011 | Permalink
  3. Yep, we have other users who've upgraded to the latest WordPress and Thesis versions and their forms are still working properly. It's most likely unrelated to either one directly.

    Posted 13 years ago on Monday July 11, 2011 | Permalink
  4. deleted short code and renetered no change.

    duplicated and created new form as copy 1 but now doesn't preview within plugin.

    Posted 13 years ago on Monday July 11, 2011 | Permalink
  5. ANy compatibility issues with W3TC? But I turned off all plugins...

    Posted 13 years ago on Monday July 11, 2011 | Permalink
  6. I created a simple new form and it works. I may just have to recreate the form by hand.

    Posted 13 years ago on Monday July 11, 2011 | Permalink
  7. There are no compatibility issues, but that doesn't mean you won't run into issues in certain situations. If W3TC cached that page before the shortcode was parsed... then that would explain it. Make sure you have completely cleared your W3TC cache. Caching can cause all sorts of quirks and issues if the cache isn't correct.

    Posted 13 years ago on Monday July 11, 2011 | Permalink