Developer Tool: Redefines the functions plugin_dir_url, plugins_url to work properly if you have symbolic links in your WordPress installation.

manojtd

Some of the built in functions (e.g., <code>plugin_dir_url</code> and <code>plugins_url</code>) may not work properly if you have non-standard WP installation with <code>wp-content</code> as a symbolic link. This plugin lets you redefine such functions without having to edit the WP core files.
This plugin is meant for advanced users or plugin developers. The reason for developing it was that some of my favorite plugins (term-management-tools, subscribe2, wp-dtree-30) didn’t work properly when I had a non-standard WP installation. My installation consists of a blog assets folder containing all the stuff that I want to keep unchanged acrross multiple WP versions, and it contains <code>wp-content</code> as well. But unfortunately, the functions <code>plugin_dir_url</code> and <code>plugins_url</code> that many plugin authors make use of give unexpected results in this setup. If I modified the plugin code, it would be impossible to updrade the plugins automatically (without obliterating my modifications). If I modified the functions in WP core files to make the plugins work again, it would be impossible to painlessly upgrade my WP installation. Redefining the offending functions using a separate plugin was the right choice.
Note that this plugin uses a <code>pecl</code> package called <code>apd</code> which provides the <code>rename_function</code>. You could easily change the code to make it use <code>runkit</code>, but it didn’t work for me. If all that is Greek to you, perhaps you shouldn’t use this plugin.
Once again, this plugin is meant for advanced users and may make your blog installation unstable or even unusable. It gives a very niche, non-standard functionality that may be useful for some plugin or PHP developers.

Alternatives to Function Tweaker

Top alternatives