https://legacy.forums.gravityhelp.com/topic/support-for-custom-content-directory Gravity Support Forums Topic: Support for custom content directory en-US Tue, 21 Apr 2026 01:59:21 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/support-for-custom-content-directory#post-41737 Mon, 21 Nov 2011 15:36:31 +0000 Carl Hancock 41737@https://legacy.forums.gravityhelp.com/ <p>As Alex mentioned above, we are aware of this issue. It impacts any functionality that calls PHP outside of WordPress which is isolated to a handful (not all, and not the primary) of features in Gravity Forms. We will be correcting this in an upcoming release and it only impacts sites where the wp-content folder is being called from a custom location. </p> https://legacy.forums.gravityhelp.com/topic/support-for-custom-content-directory#post-41699 Sun, 20 Nov 2011 23:07:37 +0000 Alex Cancado 41699@https://legacy.forums.gravityhelp.com/ <p>Yes, we realize calling these files directly is a problem. We are looking for ways to change that so that those pages run within WordPress. That will solve all these problems. This change will be done for 1.7 or even before that. </p> https://legacy.forums.gravityhelp.com/topic/support-for-custom-content-directory#post-40999 Mon, 14 Nov 2011 08:14:38 +0000 WiklanderConsulting 40999@https://legacy.forums.gravityhelp.com/ <p>BTW, the same problem is in download.php and print-entry.php. </p> https://legacy.forums.gravityhelp.com/topic/support-for-custom-content-directory#post-40996 Mon, 14 Nov 2011 08:09:04 +0000 WiklanderConsulting 40996@https://legacy.forums.gravityhelp.com/ <p>I’m having the same problem. My public_html contains:</p> <pre><code>assets // what used to be wp-content/upload custom // what used to be wp-content/ wordpress // The rest of WordPress, unchanged from upstream wp-config.php</code></pre> <p>The code in question is in the top of preview.php</p> <pre><code>&lt;?php for ( $i = 0; $i &lt; $depth = 10; $i++ ) { $wp_root_path = str_repeat( &#39;../&#39;, $i ); if ( file_exists(&quot;{$wp_root_path}wp-load.php&quot; ) ) { require_once(&quot;{$wp_root_path}wp-load.php&quot;); require_once(&quot;{$wp_root_path}wp-admin/includes/admin.php&quot;); RGForms::maybe_process_form(); break; } }</code></pre> <p>instead of wp-load.php, I think the the script should look for wp-config.php </p> https://legacy.forums.gravityhelp.com/topic/support-for-custom-content-directory#post-40949 Sun, 13 Nov 2011 16:24:04 +0000 Anonymous 40949@https://legacy.forums.gravityhelp.com/ <p>Hi,</p> <p>The way we have our wordpress installations is that we use a custom wp-content directory:<br /> /public_html/<br /> /wordpress<br /> /wp-content<br /> /wp-admin<br /> /wp-includes<br /> /wp-content &lt;!-- this is the wp-content used, path is defined in wp-config.php</p> <p>this allows easy wordpress upgrades as its as an svn external and we get to keep our project repositories separate from wordpress.</p> <p>However, when previewing a from for example it queries directly gravity-forms/preview.php<br /> which can't find wp-load.php.</p> <p>Is support for custom content directories something that we can expect in future version. Are there any easy changes we can do to the code in the meanwhile?</p> <p>thanks </p>