<?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: 1.6 upgrade data loss</title>
		<link>https://legacy.forums.gravityhelp.com/topic/16-upgrade-data-loss</link>
		<description>Gravity Support Forums Topic: 1.6 upgrade data loss</description>
		<language>en-US</language>
		<pubDate>Sun, 19 Apr 2026 23:31:14 +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/16-upgrade-data-loss" rel="self" type="application/rss+xml" />

		<item>
			<title>valleyinternet on "1.6 upgrade data loss"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/16-upgrade-data-loss#post-39805</link>
			<pubDate>Thu, 03 Nov 2011 00:12:24 +0000</pubDate>
			<dc:creator>valleyinternet</dc:creator>
			<guid isPermaLink="false">39805@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Also wanted to say that I could not find any code that does this in the plugin code so there may be user error here. &#60;/p&#62;
&#60;p&#62;It did change at the 1.6 update though. Its mysterious.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>valleyinternet on "1.6 upgrade data loss"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/16-upgrade-data-loss#post-39804</link>
			<pubDate>Thu, 03 Nov 2011 00:01:09 +0000</pubDate>
			<dc:creator>valleyinternet</dc:creator>
			<guid isPermaLink="false">39804@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;So we upgraded to 1.6.  Bad move :)&#60;/p&#62;
&#60;p&#62;Due to a problem with the API hooks we had altered our database to make the form value be 2048 characters (rather then the 200 default, you can't store a PGP encrypted entity in 200 characters..).&#60;/p&#62;
&#60;p&#62;Anyhow, it was working great in 1.5.x but the update to 1.6 seems to have reset this field to 200 characters?&#60;/p&#62;
&#60;p&#62;Boom, data, gone. No warning.&#60;/p&#62;
&#60;p&#62;Was this intentional or a side-effect? Was it in a release note I missed? I had just posted to the forums that we were doing this since we could not get the data we needed and were told that 'if it works for you, it works' so we were super surprised to have this happen.
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
