<?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: Error auto upgrading Gravity Forms</title>
		<link>https://legacy.forums.gravityhelp.com/topic/error-auto-upgrading-gravity-forms</link>
		<description>Gravity Support Forums Topic: Error auto upgrading Gravity Forms</description>
		<language>en-US</language>
		<pubDate>Sat, 04 Apr 2026 11:03: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/error-auto-upgrading-gravity-forms" rel="self" type="application/rss+xml" />

		<item>
			<title>David Peralty on "Error auto upgrading Gravity Forms"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/error-auto-upgrading-gravity-forms#post-62526</link>
			<pubDate>Thu, 14 Jun 2012 08:38:10 +0000</pubDate>
			<dc:creator>David Peralty</dc:creator>
			<guid isPermaLink="false">62526@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Are you able to upload/update other plugins currently? If not, then it is a permissions issue. Making sure your wp-content folder can be written to by plugins as they make their temporary files for installing and upgrading is key.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>wexler on "Error auto upgrading Gravity Forms"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/error-auto-upgrading-gravity-forms#post-62359</link>
			<pubDate>Tue, 12 Jun 2012 21:37:56 +0000</pubDate>
			<dc:creator>wexler</dc:creator>
			<guid isPermaLink="false">62359@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I've experienced this issue with gravityforms_1.6.4.4 and I believe it might be more of a permissions issue but I can't be sure.  Specifically, in my case, I have a site on Amazon EC2 on IIS and it might have something to do with some assumption that it's setup on Apache/cPanel.   &#60;/p&#62;
&#60;p&#62;Certainly one could manually upload via FTP however I leverage the installer though InfiniteWP (www.InfiniteWP.com) which enables me to manage all my sites from a single dashboard.&#60;/p&#62;
&#60;p&#62;So - I'd like to know of a solution that will work with the WordPress Installer.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>idealists on "Error auto upgrading Gravity Forms"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/error-auto-upgrading-gravity-forms#post-14771</link>
			<pubDate>Mon, 20 Dec 2010 05:33:46 +0000</pubDate>
			<dc:creator>idealists</dc:creator>
			<guid isPermaLink="false">14771@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Thanks Carl&#60;/p&#62;
&#60;p&#62;I guess there error itself is a bit generic, and doesn't specify that the directory already exists, just that it can't create the temporary directory, possibly for other reasons.&#60;br /&#62;
I have checked and there are no subdirectories in the upgrade/ directory.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Carl Hancock on "Error auto upgrading Gravity Forms"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/error-auto-upgrading-gravity-forms#post-14744</link>
			<pubDate>Sun, 19 Dec 2010 22:49:51 +0000</pubDate>
			<dc:creator>Carl Hancock</dc:creator>
			<guid isPermaLink="false">14744@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I haven't encountered this issue so i'm not 100% sure how to get them working again.  You may want to try the WordPress.org support forums to see if there are other users with the same issue.  If the directory doesn't exist, WordPress shouldn't be throwing an error and saying it does.  Soit's very odd.&#60;/p&#62;
&#60;p&#62;Upgrading Gravity Forms manually via FTP is no different than installing Gravity Forms the first time via FTP with the exception being you are overwriting the files instead of upgrading from scratch.&#60;/p&#62;
&#60;p&#62;Installation directions are here:&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://www.gravityhelp.com/documentation/installing-gravity-forms/&#34; rel=&#34;nofollow&#34;&#62;http://www.gravityhelp.com/documentation/installing-gravity-forms/&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;You don't need to do anything to the DB, just replace the existing Gravity Forms files with the new Gravity Forms plugin files and then activate Gravity Forms and it will make any DB updates it needs to make.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>idealists on "Error auto upgrading Gravity Forms"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/error-auto-upgrading-gravity-forms#post-14742</link>
			<pubDate>Sun, 19 Dec 2010 22:35:56 +0000</pubDate>
			<dc:creator>idealists</dc:creator>
			<guid isPermaLink="false">14742@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Hi Carl&#60;/p&#62;
&#60;p&#62;Which directory already exists? I can verify that the &#34;wp-content/upgrade/gravityforms_1.tmp/gravityforms&#34; directory doesn't exist. (but &#34;&#34;wp-content/upgrade/&#34; does exist of course in all WP installs)&#60;br /&#62;
Is there a known solution to get automatic updates to work again?&#60;br /&#62;
Also I couldn't find a &#34;how to&#34; on how hot manually update (FTP files, DB as well?). Sorry if I missed it.&#60;br /&#62;
Thanks much,
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Carl Hancock on "Error auto upgrading Gravity Forms"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/error-auto-upgrading-gravity-forms#post-14726</link>
			<pubDate>Sun, 19 Dec 2010 22:04:56 +0000</pubDate>
			<dc:creator>Carl Hancock</dc:creator>
			<guid isPermaLink="false">14726@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Sometimes the WordPress automatic upgrade routine doesn't function properly.  When it has an issue you will need to manually upgrade via FTP.  It's unable to create the directory because it already exists and WordPress isn't handling the upgrade properly and overwriting it.  So you will need to upgrade via FTP.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>idealists on "Error auto upgrading Gravity Forms"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/error-auto-upgrading-gravity-forms#post-14684</link>
			<pubDate>Sat, 18 Dec 2010 02:19:32 +0000</pubDate>
			<dc:creator>idealists</dc:creator>
			<guid isPermaLink="false">14684@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Current version: 1.3.13.1&#60;br /&#62;
Trying to automatic upgrade to 1.4.5
&#60;/p&#62;</description>
		</item>
		<item>
			<title>idealists on "Error auto upgrading Gravity Forms"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/error-auto-upgrading-gravity-forms#post-14683</link>
			<pubDate>Sat, 18 Dec 2010 02:08:22 +0000</pubDate>
			<dc:creator>idealists</dc:creator>
			<guid isPermaLink="false">14683@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;This isn't a GF specific error, but I am trying to upgrade (using WP Automatic Upgrade) and I am getting the following error:&#60;br /&#62;
Updating Plugin Gravity Forms (1/1)&#60;/p&#62;
&#60;p&#62;Downloading update from &#60;a href=&#34;http://s3.amazonaws.com/gravityforms/releases...&#34; rel=&#34;nofollow&#34;&#62;http://s3.amazonaws.com/gravityforms/releases...&#60;/a&#62;.&#60;br /&#62;
Unpacking the update…&#60;/p&#62;
&#60;p&#62;An error occured while updating Gravity Forms: Could not create directory. /home/g...t/public_html/wp-content/upgrade/gravityforms_1.tmp/gravityforms.&#60;/p&#62;
&#60;p&#62;Disabling Maintenance mode…&#60;/p&#62;
&#60;p&#62;I've tried changing permissions to 777 and no luck.&#60;br /&#62;
Not sure what else to do. Can't find much other suggestions on the WWW. :(
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
