<?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: Scripts in the footer</title>
		<link>https://legacy.forums.gravityhelp.com/topic/scripts-in-the-footer</link>
		<description>Gravity Support Forums Topic: Scripts in the footer</description>
		<language>en-US</language>
		<pubDate>Mon, 20 Apr 2026 09:30:28 +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/scripts-in-the-footer" rel="self" type="application/rss+xml" />

		<item>
			<title>David Peralty on "Scripts in the footer"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/scripts-in-the-footer#post-100104</link>
			<pubDate>Fri, 07 Dec 2012 15:13:53 +0000</pubDate>
			<dc:creator>David Peralty</dc:creator>
			<guid isPermaLink="false">100104@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;This change is already in progress. All my best!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>boxcarpress on "Scripts in the footer"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/scripts-in-the-footer#post-100102</link>
			<pubDate>Fri, 07 Dec 2012 15:12:24 +0000</pubDate>
			<dc:creator>boxcarpress</dc:creator>
			<guid isPermaLink="false">100102@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;OK, thanks for confirming this. &#60;/p&#62;
&#60;p&#62;I guess the purpose of my post is to point out that this (unpublished?) requirement of Gravity Forms causes headaches for developers downstream. I hope that you would consider rewriting how Javascript is enqueued and localized so that it doesn't pollute the DOM in future releases of Gravity Forms. Wordpress makes this process very easy, thankfully. Thanks for listening!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>David Peralty on "Scripts in the footer"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/scripts-in-the-footer#post-100098</link>
			<pubDate>Fri, 07 Dec 2012 15:04:05 +0000</pubDate>
			<dc:creator>David Peralty</dc:creator>
			<guid isPermaLink="false">100098@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;That's correct. JQuery needs to be in the header for Gravity Forms to work.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>boxcarpress on "Scripts in the footer"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/scripts-in-the-footer#post-100082</link>
			<pubDate>Fri, 07 Dec 2012 13:46:43 +0000</pubDate>
			<dc:creator>boxcarpress</dc:creator>
			<guid isPermaLink="false">100082@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Thanks for the response, I was not aware of this filter. &#60;/p&#62;
&#60;p&#62;Even after applying, I still have the conditional_logic.js script loading in the head. Looking at the wp_enqueue_script code for this asset, it appears to be hard-coded to output in the head. So, without looking into Gform_init_scripts_footer filter too much, I don't know how this would put conditional_logic.js in the footer. Then naturally, its dependencies put gravityforms.js and jquery.js into the head as well. So, no luck there. &#60;/p&#62;
&#60;p&#62;Even if we got that far, it doesn't appear that jQuery can be in the footer, due to the Javascript snippets PHP outputs throughout the page. Correct me if I'm wrong, but your plugin doesn't allow jQuery in the footer.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Richard Vav on "Scripts in the footer"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/scripts-in-the-footer#post-99928</link>
			<pubDate>Fri, 07 Dec 2012 04:12:56 +0000</pubDate>
			<dc:creator>Richard Vav</dc:creator>
			<guid isPermaLink="false">99928@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;If you check the documentation there is a function for loading the scripts in the footer instead of the head, &#60;a href=&#34;http://www.gravityhelp.com/documentation/page/Gform_init_scripts_footer&#34; rel=&#34;nofollow&#34;&#62;http://www.gravityhelp.com/documentation/page/Gform_init_scripts_footer&#60;/a&#62;
&#60;/p&#62;</description>
		</item>
		<item>
			<title>boxcarpress on "Scripts in the footer"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/scripts-in-the-footer#post-99886</link>
			<pubDate>Fri, 07 Dec 2012 01:41:41 +0000</pubDate>
			<dc:creator>boxcarpress</dc:creator>
			<guid isPermaLink="false">99886@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I see some others requesting scripts in the footer in this forum, but I don't see this concern taken too seriously in the responses. It's fairly well established that this is important for site performance. Also, in my case Gravity Forms breaks my script minification because the plugin doesn't behave as Wordpress recommends. Out of 30 or so plugins that I run on our site, this is the only one that I have been unable to get into the footer. So, after reading the code and seeing how you use inline JS and various snippets of JS in &#38;lt;head&#38;gt;, I hope that you realize this causes headaches downstream. You could accomplish all that you're doing and be making better use of wp_enqueue_script and wp_localize_script to separate the JS from &#38;lt;head&#38;gt; and DOM elements in future releases. It would certainly help developers who expect plugins to behave in a certain way--and I imagine it would help your development process as well. Thanks for considering this!
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
