<?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: site documentation needs area for comments. Please!</title>
		<link>https://legacy.forums.gravityhelp.com/topic/site-documentation-needs-area-for-comments-please</link>
		<description>Gravity Support Forums Topic: site documentation needs area for comments. Please!</description>
		<language>en-US</language>
		<pubDate>Thu, 09 Apr 2026 07:49:36 +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/site-documentation-needs-area-for-comments-please" rel="self" type="application/rss+xml" />

		<item>
			<title>Carl Hancock on "site documentation needs area for comments. Please!"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/site-documentation-needs-area-for-comments-please#post-35776</link>
			<pubDate>Tue, 20 Sep 2011 16:21:26 +0000</pubDate>
			<dc:creator>Carl Hancock</dc:creator>
			<guid isPermaLink="false">35776@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;What are you doing that requires 50 forms? The enqueue is form specific and you do not pass multiple form id's to it.  So no, that would not work the way you have shown in your example.  You would have to execute a function call for each one, and 50 forms seems inefficient and would require a lot of function calls.&#60;/p&#62;
&#60;p&#62;If you are doing something that requires so many forms then you are probably going about things the wrong way.  Typically you don't need that many forms.  The ideal way to use forms is going to be to incorporate dynamic population of some fields so that you can dynamically populate fields based on post data or passing data to the form and then use a single form for multiple purposes.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>sammet on "site documentation needs area for comments. Please!"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/site-documentation-needs-area-for-comments-please#post-35726</link>
			<pubDate>Tue, 20 Sep 2011 01:42:58 +0000</pubDate>
			<dc:creator>sammet</dc:creator>
			<guid isPermaLink="false">35726@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Thanks Dwenaus!!!!&#60;/p&#62;
&#60;p&#62;I have been struggling all night to get this working with the help of the documentation. It did not work with the code provided.&#60;/p&#62;
&#60;p&#62;I tried yours above and YES now it is working! Thanks a million! You are absolutely right - the documentation should allow comments! It would save us all a lots of time!&#60;/p&#62;
&#60;p&#62;Just one question - If I need about 50 forms to be &#34;called&#34; in the same way - is this still the best option? Just lining up all 50 ID  in a row with coma? With or without spaces? As you see I am a total newcomer to PHP and now you can imagine how much you helped me! Thanks again!&#60;/p&#62;
&#60;p&#62;For example:&#60;br /&#62;
&#60;pre&#62;&#60;code&#62;[php]
function rt_gf_init() {
	if ( ! is_admin() &#38;amp;&#38;amp; function_exists(&#38;#39;gravity_form_enqueue_scripts&#38;#39;)){
		gravity_form_enqueue_scripts(1, 2, 3, 4, 5, 6, false);
	}
}
add_action(&#38;#39;init&#38;#39;, &#38;#39;rt_gf_init&#38;#39;);&#60;/code&#62;&#60;/pre&#62;</description>
		</item>
		<item>
			<title>dwenaus on "site documentation needs area for comments. Please!"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/site-documentation-needs-area-for-comments-please#post-25513</link>
			<pubDate>Fri, 13 May 2011 18:39:09 +0000</pubDate>
			<dc:creator>dwenaus</dc:creator>
			<guid isPermaLink="false">25513@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;your documentation would be made much better if you allowed for comments. Similar to how the php website is made. &#60;/p&#62;
&#60;p&#62;For example: on this page &#60;a href=&#34;http://www.gravityhelp.com/documentation/page/Gravity_form_enqueue_scripts&#34; rel=&#34;nofollow&#34;&#62;http://www.gravityhelp.com/documentation/page/Gravity_form_enqueue_scripts&#60;/a&#62;&#60;br /&#62;
much is missing, and there is no way to inform others or the developers that this page is lacking.&#60;br /&#62;
just adding:&#60;br /&#62;
&#60;pre&#62;&#60;code&#62;gravity_form_enqueue_scripts(4, true);&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;will not work because you need to add it in the init hook, a little more like this:&#60;/p&#62;
&#60;pre&#62;&#60;code&#62;function rt_gf_init() {
	if ( ! is_admin() &#38;amp;&#38;amp; function_exists(&#38;#39;gravity_form_enqueue_scripts&#38;#39;)){
		gravity_form_enqueue_scripts(1, false);
	}
}
add_action(&#38;#39;init&#38;#39;, &#38;#39;rt_gf_init&#38;#39;);&#60;/code&#62;&#60;/pre&#62;
&#60;p&#62;in the functions.php&#60;/p&#62;
&#60;p&#62;but now that I'm writing this here, no one who reads the documentation will get that message. even as I revisit it, i forget how it works. please make you documentation allow comments or wiki style editing. &#60;/p&#62;
&#60;p&#62;thanks,&#60;br /&#62;
Deryk
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
