July 3, 2008

In WordPress 2.6 a lot of plugins could fail if they are not updated. The changes are explained by Ozh in What plugin coders know about WordPress 2.6.

The change allows WordPress users to move their config file and the contents of the wp-content folder to a different directory, which seems like a good move for security purposes but can make it difficult to code for since you often need to know where these files are before you can access any WordPress variables.

I need to update all my plugins, that’s a given, but I also need to update the plugin generator. I think I have a handy solution but I want to open it up to feedback before I make any changes.

My solution is to use the following function which will check each directory for the presence of either of the critical files, wp-load.php or wp-config.php; for example:

[php]
function get_config(){
$root = dirname(__FILE__);
while(!file_exists($root.'/wp-load.php') && !file_exists($root.'/wp-config.php')){
$root = dirname($root)
}
return $root;
}


I think it is also worth checking the plugin directory, i.e. the directory that is wp-content/plugins/ by default for a specifically named text file, perhaps plugin-paths.txt or similar so that the information can be provided manually by the blog owner.

I would appreciate any thoughts you might have on this.

  every 2005s, 1s ago, in 0.03s.