{"id":2224070,"date":"2011-08-03T19:25:54","date_gmt":"2011-08-03T19:25:54","guid":{"rendered":"https:\/\/wordpress.org\/support\/topic\/hardcoded-file-paths\/"},"modified":"2016-08-20T01:48:05","modified_gmt":"2016-08-20T01:48:05","slug":"hardcoded-file-paths","status":"closed","type":"topic","link":"https:\/\/wordpress.org\/support\/topic\/hardcoded-file-paths\/","title":{"rendered":"Hardcoded file paths"},"content":{"rendered":"<p>This is yet another plugin that is failing because it has filepaths hardcoded in the PHP code rather then correctly reading the paths from the wp-config file. It&#8217;s getting quite annoying by now since I&#8217;ve been trying to find a decent plugin for about an hour now!<\/p>\n<p>I have no &#8220;wp-content&#8221; folder, but just a &#8220;content&#8221; folder instead.<br \/>\nI have no &#8220;plugins&#8221; folder within a &#8220;wp-content&#8221; or &#8220;content&#8221; folder, but just in the root.<\/p>\n<p>Why do developers insist on hardcoding these paths while these are all options that can be set in the wp-config file.<\/p>\n","protected":false},"template":"","class_list":["post-2224070","topic","type-topic","status-closed","hentry"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/2224070","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/2224070\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=2224070"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}