{"id":1177,"date":"2012-02-05T22:01:41","date_gmt":"2012-02-05T22:01:41","guid":{"rendered":"http:\/\/gr-01.de\/whitepapers.grafik-und-redaktion.de\/?p=1177"},"modified":"2013-06-03T03:43:30","modified_gmt":"2013-06-03T01:43:30","slug":"paths-for-building-wordpress-themes-or-plugins","status":"publish","type":"post","link":"https:\/\/whitepapers.grafik-und-redaktion.de\/?p=1177","title":{"rendered":"Paths For Building WordPress Themes or Plugins"},"content":{"rendered":"

(Quelle: computeraxe.com\/paths-building-wordpress-themes-pl…<\/a>) When tinkering with the code that runs WordPress it\u2019s very important to get the correct path to a file. Of course it is or else the files can\u2019t be found and your new functionality won\u2019t work.<\/p>\n

According to the Codex<\/p>\n

In Version 2.6, users were given the ability to move their \/wp-content\/ directory to anywhere they want, and many users already keep all WordPress files (like \/wp-admin\/ and \/wp-includes\/) in an unusual place.<\/p><\/blockquote>\n

In case you\u2019ve moved the files for your WP installation, you probably have a good handle on paths and how to traverse them. For those who don\u2019t, it can be a hair-pulling experience to find the right path. Once the right path is found, work can continue.<\/p>\n

WordPress Paths<\/h2>\n

To help avoid those DUH! <\/em>moments, here are some functions and constants that WordPress has defined regarding paths. Once you\u2019re familiar with these functions, writing useful and working code should become easier. Optional parameters may be of use in modifying the output for several of the following templates, including $path, $file or $scheme.<\/p>\n

\n
plugin_basename()<\/dt>\n
Usage: plugin_basename(__FILE__); Returns: the name of the plugin and file, such as \u201cmyPlugin\/myPlugin.php\u201d<\/dd>\n
get_theme_root()<\/dt>\n
Usage: get_theme_root(); Returns: path to themes directory. No<\/strong> trailing slash.<\/dd>\n
get_theme_root_uri()<\/dt>\n
Usage: get_theme_root_uri(); Returns: URI for themes directory. No<\/strong> trailing slash.<\/dd>\n
get_theme_roots()<\/dt>\n
Usage: get_theme_roots(); Returns: Themes directory with a leading<\/em> slash, like \u201c\/themes\u201d.<\/dd>\n
site_url()<\/dt>\n
Usage: site_url(); Returns: Site directory with no<\/strong> trailing slash.<\/p>\n

www.site.com<\/a> OR www.site.com\/wordpress<\/a><\/dd>\n

admin_url()<\/dt>\n
Usage: admin_url(); Returns: Admin directory with trailing slash.<\/p>\n

www.site.com\/wp-admin\/<\/a><\/dd>\n

content_url()<\/dt>\n
Usage: content_url(); Returns: Content directory with trailing slash.<\/p>\n

www.site.com\/wp-content\/<\/a><\/p>\n<\/dd>\n

plugins_url()<\/dt>\n
Usage: plugins_url(); Returns: Plugins directory with trailing slash.<\/p>\n

www.site.com\/wp-content\/plugins\/<\/a><\/dd>\n

includes_url()<\/dt>\n
Usage: includes_url(); Returns: Includes directory with trailing slash.<\/p>\n

www.site.com\/wp-includes\/<\/a><\/dd>\n

home_url()<\/dt>\n
Usage: home_url(); Returns: Home directory with no<\/strong> trailing slash.<\/p>\n

www.site.com<\/a><\/p>\n<\/dd>\n

ABSPATH (constant)<\/dt>\n
Usage: ABSPATH. Returns: Home directory with no<\/strong> trailing slash.<\/dd>\n
TEMPLATEPATH (constant)<\/dt>\n
Usage: TEMPLATEPATH. Returns: Path to current theme with no<\/strong> trailing slash.<\/dd>\n<\/dl>\n

There are a few more functions for multisite installations and backwards capability<\/a> specified in the Codex.<\/p>\n

PHP Paths<\/h2>\n

Some PHP functions worth noting –<\/p>\n