<?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: Dev License Key for Multi-Site</title>
		<link>https://legacy.forums.gravityhelp.com/topic/dev-license-key-for-multi-site</link>
		<description>Gravity Support Forums Topic: Dev License Key for Multi-Site</description>
		<language>en-US</language>
		<pubDate>Thu, 16 Apr 2026 04:43:58 +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/dev-license-key-for-multi-site" rel="self" type="application/rss+xml" />

		<item>
			<title>Carl Hancock on "Dev License Key for Multi-Site"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/dev-license-key-for-multi-site#post-7230</link>
			<pubDate>Fri, 09 Jul 2010 17:36:44 +0000</pubDate>
			<dc:creator>Carl Hancock</dc:creator>
			<guid isPermaLink="false">7230@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Good idea Matt, we completely didn't think to see about leveraging wp-config.php to store the key.  We will work this into 1.3.13 Beta 2 and then the license key will survive updates and it will be more seamless.  Thanks for the suggestion!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Matt Wiebe on "Dev License Key for Multi-Site"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/dev-license-key-for-multi-site#post-7229</link>
			<pubDate>Fri, 09 Jul 2010 17:30:42 +0000</pubDate>
			<dc:creator>Matt Wiebe</dc:creator>
			<guid isPermaLink="false">7229@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I've been looking at this for an upcoming project too, so glad to know it's in the works.&#60;/p&#62;
&#60;p&#62;Wouldn't it make more sense to put a constant in wp-config.php ? It'd survive updates that way.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Carl Hancock on "Dev License Key for Multi-Site"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/dev-license-key-for-multi-site#post-7205</link>
			<pubDate>Fri, 09 Jul 2010 11:12:33 +0000</pubDate>
			<dc:creator>Carl Hancock</dc:creator>
			<guid isPermaLink="false">7205@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Currently there is not support for automating multi-site license key input.&#60;/p&#62;
&#60;p&#62;BUT we will go ahead and add it to the to do list for v1.3.13 which is currently in Beta.  We will include it in either Beta 2 or Beta 3 depending on time.  If I remember correctly you have to edit the Akismet plugin file and hardcode the license key for it to then automatically use that value.  This will work the same way.&#60;/p&#62;
&#60;p&#62;A couple caveats:&#60;/p&#62;
&#60;p&#62;- It will only populate when initially activated on a site that didn't have Gravity Forms installed before as it will run as part of the install routine that creates setup data.&#60;/p&#62;
&#60;p&#62;- It will mean when you upgrade to a new version of Gravity Forms you will have to do this again as the hardcoded value would be overridden by the upgrade.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Anonymous on "Dev License Key for Multi-Site"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/dev-license-key-for-multi-site#post-7153</link>
			<pubDate>Thu, 08 Jul 2010 14:04:58 +0000</pubDate>
			<dc:creator>Anonymous</dc:creator>
			<guid isPermaLink="false">7153@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I did a search, and didn't see any threads on this, but was wondering if there's a way to set the license key once for all sites in a WPMU/multi-site environment, ala akismet?
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
