https://legacy.forums.gravityhelp.com/topic/dont-hardcode-wp-content-bad-things-happen Gravity Support Forums Topic: Don't hardcode wp-content - bad things happen en-US Mon, 20 Apr 2026 19:58:42 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/dont-hardcode-wp-content-bad-things-happen#post-36217 Mon, 26 Sep 2011 10:23:31 +0000 Alex Cancado 36217@https://legacy.forums.gravityhelp.com/ <p>Thanks for the tip Ptah.<br /> However, the GRAVITY_MANAGER_URL refers to the URL in our server (so we can trust on the location of the wp-content folder). I will look at the affected files and try to use your snippet. </p> https://legacy.forums.gravityhelp.com/topic/dont-hardcode-wp-content-bad-things-happen#post-36190 Sun, 25 Sep 2011 23:10:36 +0000 ptahdunbar 36190@https://legacy.forums.gravityhelp.com/ <p>Given that WordPress allows you to move the wp-content directory, you can't hardcode it's location. There are all sorts of broken issues like not being able to preview forms because of this.</p> <p>Affected constants:<br /> GRAVITY_MANAGER_URL, use WP_PLUGIN_URL</p> <p>Affected files:</p> <ul> <li>downloads.php</li> <li>preview.php</li> <li>print-entry.php</li> <li>select-columns.php</li> </ul> <p>If you need access to WordPress functions, or need to find dynamic paths like wp-content, I wrote some code that allows you to do this:<br /> <a href="https://gist.github.com/1241505" rel="nofollow">https://gist.github.com/1241505</a> </p>