{"id":865,"date":"2008-07-02T00:10:10","date_gmt":"2008-07-01T22:10:10","guid":{"rendered":"http:\/\/planetozh.com\/blog\/?p=865"},"modified":"2008-07-02T08:32:19","modified_gmt":"2008-07-02T06:32:19","slug":"what-plugin-coders-must-know-about-wordpress-26","status":"publish","type":"post","link":"https:\/\/planetozh.com\/blog\/2008\/07\/what-plugin-coders-must-know-about-wordpress-26\/","title":{"rendered":"What Plugin Coders Must Know About WordPress 2.6"},"content":{"rendered":"

\"\"A WordPress install is a bunch of directories and files, but two of them are particular: the file wp-config.php<\/tt> and the directory wp-content\/<\/tt> are personal and don't get overwritten when you upgrade your blog. In WordPress 2.6, they get so<\/em> personal that you can even move them out of the WordPress root. This must bring a major change to your coding habits.<\/p>\n

Plugin coders sometimes need their script to guess the location of their own directory (for example to require() files), or to include wp-config.php<\/tt> to make a file live alone in a WordPressized environment.<\/p>\n

Guessing the path of wp-content<\/tt><\/h2>\n

WordPress 2.6 allows advanced users to specify the location (physical and URL) of this directory with a constant define, so the directory might not be where it used to be.<\/p>\n

What you used to do:<\/p>\n

\n\n\t\t
\n\n\t\t
\n\t\t\t\t\t\t< View plain text<\/span> ><\/a>\n\t\t\t\t\t<\/div>\n\n\t\t
php<\/div>\n\n\t\t\n\t\t
\n\n\t<\/div>\n\t\n\t
\n\t\t
  1. $plugin_path<\/span> =<\/span> ABSPATH .<\/span> '\/wp-content\/plugins\/'<\/span> .<\/span> plugin_basename(<\/span>dirname<\/span>(<\/span>__FILE__<\/span>)<\/span>)<\/span>;<\/span><\/div><\/li>\n
  2. $plugin_url<\/span> =<\/span> get_option(<\/span>'siteurl'<\/span>)<\/span> .<\/span> '\/wp-content\/plugins\/'<\/span> .<\/span> plugin_basename(<\/span>dirname<\/span>(<\/span>__FILE__<\/span>)<\/span>)<\/span>;<\/span><\/div><\/li>\n<\/ol>\t<\/div>\n\n<\/div>\n\n

    What you will have to do, now that this directory can hide anywhere:<\/p>\n

    \n\n\t\t
    \n\n\t\t
    \n\t\t\t\t\t\t< View plain text<\/span> ><\/a>\n\t\t\t\t\t<\/div>\n\n\t\t
    php<\/div>\n\n\t\t\n\t\t
    \n\n\t<\/div>\n\t\n\t
    \n\t\t
    1. \/\/ Pre-2.6 compatibility<\/span><\/div><\/li>\n
    2. if<\/span> (<\/span> !<\/span>defined<\/span>(<\/span>'WP_CONTENT_URL'<\/span>)<\/span> )<\/span><\/div><\/li>\n
    3.     define<\/span>(<\/span> 'WP_CONTENT_URL'<\/span>,<\/span> get_option(<\/span>'siteurl'<\/span>)<\/span> .<\/span> '\/wp-content'<\/span>)<\/span>;<\/span><\/div><\/li>\n
    4. if<\/span> (<\/span> !<\/span>defined<\/span>(<\/span>'WP_CONTENT_DIR'<\/span>)<\/span> )<\/span><\/div><\/li>\n
    5.     define<\/span>(<\/span> 'WP_CONTENT_DIR'<\/span>,<\/span> ABSPATH .<\/span> 'wp-content'<\/span> )<\/span>;<\/span><\/div><\/li>\n
    6.  <\/div><\/li>\n
    7. \/\/ Guess the location<\/span><\/div><\/li>\n
    8. $plugin_path<\/span> =<\/span> WP_CONTENT_DIR.<\/span>'\/plugins\/'<\/span>.<\/span>plugin_basename(<\/span>dirname<\/span>(<\/span>__FILE__<\/span>)<\/span>)<\/span>;<\/span><\/div><\/li>\n
    9. $plugin_url<\/span> =<\/span> WP_CONTENT_URL.<\/span>'\/plugins\/'<\/span>.<\/span>plugin_basename(<\/span>dirname<\/span>(<\/span>__FILE__<\/span>)<\/span>)<\/span>;<\/span><\/div><\/li>\n<\/ol>\t<\/div>\n\n<\/div>\n\n

      In WordPress 2.6, constants WP_CONTENT_DIR and WP_CONTENT_URL are either user defined or set in wp-settings.php<\/tt><\/p>\n

      Including wp-config.php<\/h2>\n

      In WordPress 2.6 you can either leave wp-config.php<\/tt> in the blog root directory, or move it to the parent folder (which makes sense if this takes this critical file off of the webserver's document root)<\/p>\n

      What you used to do:<\/p>\n

      \n\n\t\t
      \n\n\t\t
      \n\t\t\t\t\t\t< View plain text<\/span> ><\/a>\n\t\t\t\t\t<\/div>\n\n\t\t
      php<\/div>\n\n\t\t\n\t\t
      \n\n\t<\/div>\n\t\n\t
      \n\t\t
      1. require_once<\/span>(<\/span>'..\/..\/..\/wp-config.php'<\/span>)<\/span>;<\/span><\/div><\/li>\n<\/ol>\t<\/div>\n\n<\/div>\n\n

        What you must do now:<\/p>\n

        \n\n\t\t
        \n\n\t\t
        \n\t\t\t\t\t\t< View plain text<\/span> ><\/a>\n\t\t\t\t\t<\/div>\n\n\t\t
        php<\/div>\n\n\t\t\n\t\t
        \n\n\t<\/div>\n\t\n\t
        \n\t\t
        1. $root<\/span> =<\/span> dirname<\/span>(<\/span>dirname<\/span>(<\/span>dirname<\/span>(<\/span>dirname<\/span>(<\/span>__FILE__<\/span>)<\/span>)<\/span>)<\/span>)<\/span>;<\/span><\/div><\/li>\n
        2. if<\/span> (<\/span>file_exists<\/span>(<\/span>$root<\/span>.<\/span>'\/wp-load.php'<\/span>)<\/span>)<\/span> {<\/span><\/div><\/li>\n
        3.     \/\/ WP 2.6<\/span><\/div><\/li>\n
        4.     require_once<\/span>(<\/span>$root<\/span>.<\/span>'\/wp-load.php'<\/span>)<\/span>;<\/span><\/div><\/li>\n
        5. }<\/span> else<\/span> {<\/span><\/div><\/li>\n
        6.     \/\/ Before 2.6<\/span><\/div><\/li>\n
        7.     require_once<\/span>(<\/span>$root<\/span>.<\/span>'\/wp-config.php'<\/span>)<\/span>;<\/span><\/div><\/li>\n
        8. }<\/span><\/div><\/li>\n<\/ol>\t<\/div>\n\n<\/div>\n\n

          Basically in WordPress 2.6 the file responsible for loading the environment is, in first instance, wp-load.php in place of the good old wp-config.php.<\/p>\n

          However, as pointed out by GamerZ in the comments, this still may not work. Why? Because not only the config file may not be there anymore, but the relative path to it may have changed since wp-content<\/tt> might have been moved too.<\/p>\n

          At this point though, there is no way I can think of to guess the locations of both wp-config and wp-content. To be 100% foolproof, such a "standalone" file needing to include wp-config should be editable so that advanced users moving their wp-content directory could manually edit a location path (the $root<\/tt> variable in the previous example)<\/p>\n

          Summary<\/h2>\n

          Coders, revisit your old plugins to make sure they won't eventually break on WordPress 2.6 :)<\/p>\n","protected":false},"excerpt":{"rendered":"

          A WordPress install is a bunch of directories and files, but two of them are particular: the file wp-config.php and the directory wp-content\/ are personal and don't get overwritten when you upgrade your blog. In WordPress 2.6, they get so personal that you can even move them out of the WordPress root. This must bring […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21],"tags":[2,85,76,245],"class_list":["post-865","post","type-post","status-publish","format-standard","hentry","category-published","tag-code","tag-plugins","tag-tips","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts\/865","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/comments?post=865"}],"version-history":[{"count":0,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts\/865\/revisions"}],"wp:attachment":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/media?parent=865"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/categories?post=865"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/tags?post=865"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}