<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Gravity Support Forums Topic: Form worked for a while and then disappeared</title>
		<link>https://legacy.forums.gravityhelp.com/topic/form-worked-for-a-while-and-then-disappeared</link>
		<description>Gravity Support Forums Topic: Form worked for a while and then disappeared</description>
		<language>en-US</language>
		<pubDate>Fri, 10 Apr 2026 03:42:47 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.1</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>https://legacy.forums.gravityhelp.com/search.php</link>
		</textInput>
		<atom:link href="https://legacy.forums.gravityhelp.com/rss/topic/form-worked-for-a-while-and-then-disappeared" rel="self" type="application/rss+xml" />

		<item>
			<title>ideaturf on "Form worked for a while and then disappeared"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/form-worked-for-a-while-and-then-disappeared#post-6411</link>
			<pubDate>Thu, 17 Jun 2010 04:00:19 +0000</pubDate>
			<dc:creator>ideaturf</dc:creator>
			<guid isPermaLink="false">6411@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Hi guys,&#60;/p&#62;
&#60;p&#62;Thanks for your help.&#60;/p&#62;
&#60;p&#62;Yes the [noformat] code did the trick without having to change any code.&#60;/p&#62;
&#60;p&#62;Thanks and cheers to you!!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Chris Hajer on "Form worked for a while and then disappeared"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/form-worked-for-a-while-and-then-disappeared#post-6408</link>
			<pubDate>Wed, 16 Jun 2010 22:59:20 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">6408@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Thanks Carl.  That's what I've been doing and I'm glad to know you came up with the same solution.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Carl Hancock on "Form worked for a while and then disappeared"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/form-worked-for-a-while-and-then-disappeared#post-6401</link>
			<pubDate>Wed, 16 Jun 2010 16:32:11 +0000</pubDate>
			<dc:creator>Carl Hancock</dc:creator>
			<guid isPermaLink="false">6401@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;YES.  The same issue would happen with the RAW shortcode above.  The problem is while that function call doesn't process the shortcode using the wpautop function call if the shortcode matches RAW (or in this themes case NOFORMAT), it then applies it to all other shortcodes.  It shouldn't be applying it to ANY shortcodes.  But thats what happens.&#60;/p&#62;
&#60;p&#62;*BUT* I came up with a work around that requires NO code changes on either end.  It's actually quite funny.  The function call causing the problem doesn't apply the autoformatting if the shortcode you use matches what is specific in the function call.  So what I did is wrap the Gravity Forms shortcode within that shortcode and it works!&#60;/p&#62;
&#60;p&#62;So instead of:&#60;/p&#62;
&#60;p&#62;[gravityform id=1 name=My Form Title]&#60;/p&#62;
&#60;p&#62;Do:&#60;/p&#62;
&#60;p&#62;[noformat][gravityform id=39 name=ContactMe][/noformat]&#60;/p&#62;
&#60;p&#62;It worked testing locally and the conditional logic form output and submitted fine.&#60;/p&#62;
&#60;p&#62;If your function call uses [raw] instead of [noformat] you would just switch it out.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Chris Hajer on "Form worked for a while and then disappeared"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/form-worked-for-a-while-and-then-disappeared#post-6399</link>
			<pubDate>Wed, 16 Jun 2010 16:20:00 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">6399@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Hi Carl/Kevin, this is interesting.  Would  this snippet of code cause the same problem?&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://www.catswhocode.com/blog/top-10-wordpress-hacks-from-june-09&#34; rel=&#34;nofollow&#34;&#62;http://www.catswhocode.com/blog/top-10-wordpress-hacks-from-june-09&#60;/a&#62;&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;function my_formatter($content) {
	$new_content = &#38;#39;&#38;#39;;
	$pattern_full = &#38;#39;{(\[raw\].*?\[/raw\])}is&#38;#39;;
	$pattern_contents = &#38;#39;{\[raw\](.*?)\[/raw\]}is&#38;#39;;
	$pieces = preg_split($pattern_full, $content, -1, PREG_SPLIT_DELIM_CAPTURE);

	foreach ($pieces as $piece) {
		if (preg_match($pattern_contents, $piece, $matches)) {
			$new_content .= $matches[1];
		} else {
			$new_content .= wptexturize(wpautop($piece));
		}
	}

	return $new_content;
}

remove_filter(&#38;#39;the_content&#38;#39;, &#38;#39;wpautop&#38;#39;);
remove_filter(&#38;#39;the_content&#38;#39;, &#38;#39;wptexturize&#38;#39;);

add_filter(&#38;#39;the_content&#38;#39;, &#38;#39;my_formatter&#38;#39;, 99);&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;It's not part of my theme (saw &#60;a href=&#34;http://twitter.com/carlhancock/status/16311817769&#34; rel=&#34;nofollow&#34;&#62;your tweet&#60;/a&#62; :-) ), but I do use that in functions.php to disable autop formatting by wrapping my content in a shortcode.  I've had problems with nextgen gallery shortcode outputting invalid XHTML unless I wrap in [raw] shortcode, and the same with Gravity Forms.  I recall asking about it once before:&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://forum.gravityhelp.com/topic/page-will-not-validate-with-form-in-it-unless-i-remove-filters&#34; rel=&#34;nofollow&#34;&#62;http://forum.gravityhelp.com/topic/page-will-not-validate-with-form-in-it-unless-i-remove-filters&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;I would be very happy to know that the problem is coming from the use of this shortcode (or rather, the fact that the shortcode is in my functions.php and the invalid code comes from &#60;strong&#62;NOT&#60;/strong&#62; using the [raw] shortcode around the gravity forms or nextgen gallery shortcodes.)&#60;/p&#62;
&#60;p&#62;So, Kevin, if the invalid XHTML is because caused by this raw shortcode being added to functions.php, how can I do something similar but not mess up the order in which the filters are processed?  I know it's not Gravity Forms, but I am hoping to resolve this long-simmering issue.&#60;/p&#62;
&#60;p&#62;Thank you guys very much.  Sorry to hijack the thread.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Carl Hancock on "Form worked for a while and then disappeared"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/form-worked-for-a-while-and-then-disappeared#post-6394</link>
			<pubDate>Wed, 16 Jun 2010 13:52:41 +0000</pubDate>
			<dc:creator>Carl Hancock</dc:creator>
			<guid isPermaLink="false">6394@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;The issue is a shortcode that the Next Elements theme introduces causes a problem with how WordPress outputs shortcode content.&#60;/p&#62;
&#60;p&#62;Edit This File:&#60;/p&#62;
&#60;p&#62;nextelement/admin/includes/shortcodes/shortcodes.php&#60;/p&#62;
&#60;p&#62;Remove this block of code which begins around line 30 of the above file:&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;// DISABLE AUTOFORMATING POSTS
function my_formatter($content) {
	$new_content = &#38;#39;&#38;#39;;
	$pattern_full = &#38;#39;{(\[noformat\].*?\[/noformat\])}is&#38;#39;;
	$pattern_contents = &#38;#39;{\[noformat\](.*?)\[/noformat\]}is&#38;#39;;
	$pieces = preg_split($pattern_full, $content, -1, PREG_SPLIT_DELIM_CAPTURE);
	foreach ($pieces as $piece) {
		if (preg_match($pattern_contents, $piece, $matches)) {
			$new_content .= $matches[1];
		} else {
			$new_content .= wptexturize(wpautop($piece));
		}
	}
	return $new_content;
}
remove_filter(&#38;#39;the_content&#38;#39;, &#38;#39;wpautop&#38;#39;);
remove_filter(&#38;#39;the_content&#38;#39;, &#38;#39;wptexturize&#38;#39;);
add_filter(&#38;#39;the_content&#38;#39;, &#38;#39;my_formatter&#38;#39;, 99);&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;This block of code disrupts how WordPress handles shortcodes and causes it to process all other shortcode output using the wpautop function that adds HTML paragraph tags where line breaks exist.  So while the above shortcode WILL allow you to place unformatted code in your post body, it's side effect is it then applies the wpautop to all other shortcodes because it changes the order in which filters are executed.&#60;/p&#62;
&#60;p&#62;Removing the above code will allow the Next Element theme and Gravity Forms to play nicely together.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Kevin Flahaut on "Form worked for a while and then disappeared"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/form-worked-for-a-while-and-then-disappeared#post-6390</link>
			<pubDate>Wed, 16 Jun 2010 10:50:54 +0000</pubDate>
			<dc:creator>Kevin Flahaut</dc:creator>
			<guid isPermaLink="false">6390@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;The issue is definitely theme related (if you'll notice, the form preview in the admin works properly)&#60;/p&#62;
&#60;p&#62;So, that being said, we're pretty sure this is related to a shortcode in your theme. They tout 54 shortcodes for this theme, so it's hard to say what it might be without seeing the theme files.&#60;/p&#62;
&#60;p&#62;Could you email me a copy of the theme zip file? If so, we could test it here and hopefully help you get it fixed. If not, I can point you in the general direction and you can work with the theme provider to debug it.&#60;/p&#62;
&#60;p&#62;Please send it to &#60;a href=&#34;mailto:kevin@rocketgenius.com&#34;&#62;kevin@rocketgenius.com&#60;/a&#62;
&#60;/p&#62;</description>
		</item>
		<item>
			<title>ideaturf on "Form worked for a while and then disappeared"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/form-worked-for-a-while-and-then-disappeared#post-6388</link>
			<pubDate>Wed, 16 Jun 2010 10:30:38 +0000</pubDate>
			<dc:creator>ideaturf</dc:creator>
			<guid isPermaLink="false">6388@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Oppss... I had a feeling it was to do with the theme or a conflict with some other plugin.&#60;/p&#62;
&#60;p&#62;I'll disable the conditional logic for now and wait to hear from you.&#60;/p&#62;
&#60;p&#62;Thanks.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Carl Hancock on "Form worked for a while and then disappeared"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/form-worked-for-a-while-and-then-disappeared#post-6387</link>
			<pubDate>Wed, 16 Jun 2010 10:21:09 +0000</pubDate>
			<dc:creator>Carl Hancock</dc:creator>
			<guid isPermaLink="false">6387@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I have received the login and we are looking into this issue.  It is a theme conflict.  Something in the Panda Themes Next Element theme is causing problems with shortcode output which is causing a conflict with the conditional logic javascript that Gravity Forms uses.&#60;/p&#62;
&#60;p&#62;This is an issue we have only encountered with the Panda Themes Next Element theme.  We are looking into it to see why it is happening but it is most likely due to poor coding within the theme.  We will get back to you with some sort of fix, but it will probably require changing something within your theme.&#60;/p&#62;
&#60;p&#62;Just FYI, you were waiting 4 hours for a response because you purchased our product in the middle of the night.  We were sleeping. We don't provide 24/7 support.  We have standard business hours and you purchased the plugin and posted your support request outside of those business hours.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Kevin Flahaut on "Form worked for a while and then disappeared"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/form-worked-for-a-while-and-then-disappeared#post-6385</link>
			<pubDate>Wed, 16 Jun 2010 09:48:03 +0000</pubDate>
			<dc:creator>Kevin Flahaut</dc:creator>
			<guid isPermaLink="false">6385@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Okay, thanks. We'll check it out as soon as we can and let you know what we find.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>ideaturf on "Form worked for a while and then disappeared"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/form-worked-for-a-while-and-then-disappeared#post-6384</link>
			<pubDate>Wed, 16 Jun 2010 09:43:43 +0000</pubDate>
			<dc:creator>ideaturf</dc:creator>
			<guid isPermaLink="false">6384@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Hi Kevin,&#60;/p&#62;
&#60;p&#62;I tried the positive and negative for the conditional logic and the form disappears.&#60;/p&#62;
&#60;p&#62;I sent you the login details to the wp-admin via the contact form. Look forward to your assistance.
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
