https://legacy.forums.gravityhelp.com/topic/failed-upload-folder-could-not-be-created-1 Gravity Support Forums Topic: FAILED (Upload folder could not be created.) en-US Mon, 20 Apr 2026 03:24:57 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/failed-upload-folder-could-not-be-created-1#post-10640 Fri, 01 Oct 2010 00:38:55 +0000 FormsDude 10640@https://legacy.forums.gravityhelp.com/ <p>Indeed you were correct.</p> <p>I noticed safe mode was still 'on' even though the web host told me it was 'off'. However we figured out the problem. The site was actually a 'sub-domain' and they needed to extend access for it in addition to the normal site.</p> <p>All working fine now.</p> <p>Thanks. </p> https://legacy.forums.gravityhelp.com/topic/failed-upload-folder-could-not-be-created-1#post-10421 Mon, 27 Sep 2010 11:59:15 +0000 Carl Hancock 10421@https://legacy.forums.gravityhelp.com/ <p>There is no fix as there is nothing to fix in Gravity Forms itself. It's an issue with your server, not the plugin. You may want to work with your web host support on it to see if they can figure out what is going on. It's a server file permissions or security issue. </p> https://legacy.forums.gravityhelp.com/topic/failed-upload-folder-could-not-be-created-1#post-10404 Mon, 27 Sep 2010 09:20:43 +0000 FormsDude 10404@https://legacy.forums.gravityhelp.com/ <p>Sorry to post again on this. I tried everything suggested including:<br /> 777 on wp-content, 777 on uploads, 777 on gravity_forms.<br /> I checked with my host that safe-mode was definitely off.</p> <p>I kept getting the error and the only fix was to use the method of altering forms_model.php in this post:<br /> <a href="http://forum.gravityhelp.com/topic/resolving-failed-upload-folder-could-not-be-created" rel="nofollow">http://forum.gravityhelp.com/topic/resolving-failed-upload-folder-could-not-be-created</a> by Idealien.</p> <p>I am using Gravity Forms 1.4.3.1<br /> Wordpress 3.0.1</p> <p>Was hoping there might be a fix to this. </p>