Comments on: What Plugin Coders Must Know About WordPress 2.6 http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/?source=rss A bit of my personal life, mainly focused on my kids. A bit of code, mainly focused on Wordpress and PHP. Overall, bits of nothing in particular. Thu, 18 Mar 2010 02:31:00 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: DLE http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/comment-page-3/#comment-96331 DLE Sun, 18 Oct 2009 03:47:41 +0000 http://planetozh.com/blog/?p=865#comment-96331 Thank you! By adding the code you posted, I was able to fix a much needed older plugin that failed after I moved my config file. Thank you! By adding the code you posted, I was able to fix a much needed older plugin that failed after I moved my config file.

]]> By: An email from wordpress! | PROSS.ORG.UK http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/comment-page-3/#comment-92903 An email from wordpress! | PROSS.ORG.UK Tue, 26 May 2009 20:31:27 +0000 http://planetozh.com/blog/?p=865#comment-92903 [...] The code itself works with a default install of wordpress, but a few people out there might define a different folder for wp-content/themes.. so after som hefty google-fu I found this http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/ [...] [...] The code itself works with a default install of wordpress, but a few people out there might define a different folder for wp-content/themes.. so after som hefty google-fu I found this http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/ [...]

]]> By: primer dí­a con wordpress 2.6 : apirronarse http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/comment-page-3/#comment-92027 primer dí­a con wordpress 2.6 : apirronarse Fri, 24 Apr 2009 15:23:34 +0000 http://planetozh.com/blog/?p=865#comment-92027 [...] tengo que acomodar varias cosas. algunos plugin dejaron de funcionar, habrá que esperar a que los desarrolladores de plugin los [...] [...] tengo que acomodar varias cosas. algunos plugin dejaron de funcionar, habrá que esperar a que los desarrolladores de plugin los [...]

]]> By: Scott Allen http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/comment-page-3/#comment-88074 Scott Allen Thu, 12 Feb 2009 10:41:14 +0000 http://planetozh.com/blog/?p=865#comment-88074 Ozh, This is a great post. All WP plugin developers really do need to read this. Thanks for sharing. Ozh,

This is a great post. All WP plugin developers really do need to read this. Thanks for sharing.

]]> By: Organize Series 2.0.8 released http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/comment-page-3/#comment-86171 Organize Series 2.0.8 released Wed, 24 Dec 2008 06:22:51 +0000 http://planetozh.com/blog/?p=865#comment-86171 [...] wp-config.php to allow for users customizing the location of their wp-config.php file (see http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/ for reference [...] [...] wp-config.php to allow for users customizing the location of their wp-config.php file (see http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/ for reference [...]

]]> By: Marco Cimmino http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/comment-page-3/#comment-85690 Marco Cimmino Tue, 16 Dec 2008 19:32:07 +0000 http://planetozh.com/blog/?p=865#comment-85690 Unluckily for people that changed wp-content location all code mentioned (both site and comments) doesn't work to find wp-config.php Unluckily for people that changed wp-content location all code mentioned (both site and comments) doesn’t work to find wp-config.php

]]> By: Eric http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/comment-page-2/#comment-85244 Eric Tue, 09 Dec 2008 04:31:14 +0000 http://planetozh.com/blog/?p=865#comment-85244 @SEOAdsenseThemes - You are very correct! I just found that out today. Here is the updated code that is independent of the directory names. Not sure why I didn't do it this way in the first place... [php] $rootPath = dirname(__FILE__); $rootPathArray = explode("/",$rootPath); $numDirs = count($rootPathArray); for ($i=1; $i<=$numDirs; $i++) { $path = implode("/", $rootPathArray); if (file_exists($path.'/wp-load.php')) { require_once($path.'/wp-load.php'); break; } elseif (file_exists($path.'/wp-config.php')) { require_once($path.'/wp-config.php'); break; } array_pop($rootPathArray); } [/php] Anyway, this seems to solve all conflict with directory names. Eric @SEOAdsenseThemes - You are very correct! I just found that out today.

Here is the updated code that is independent of the directory names. Not sure why I didn't do it this way in the first place...

PLAIN TEXT
PHP:
  1. $rootPath = dirname(__FILE__);
  2. $rootPathArray = explode("/",$rootPath);
  3. $numDirs = count($rootPathArray);
  4. for ($i=1; $i&lt;=$numDirs; $i++) {
  5.     $path = implode("/", $rootPathArray);
  6.     if (file_exists($path.'/wp-load.php')) {
  7.         require_once($path.'/wp-load.php');
  8.         break;
  9.     } elseif (file_exists($path.'/wp-config.php')) {
  10.         require_once($path.'/wp-config.php');
  11.         break;
  12.     }
  13.     array_pop($rootPathArray);
  14. }

Anyway, this seems to solve all conflict with directory names.

Eric

]]> By: SEOAdsenseThemes http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/comment-page-2/#comment-85111 SEOAdsenseThemes Fri, 05 Dec 2008 16:38:38 +0000 http://planetozh.com/blog/?p=865#comment-85111 " ... For finding and loading either wp-load.php or wp-config.php, what about something like this ... " Eric This part of the code: <code>$rootPath = str_replace('/'.$rootArray[$i], '', $rootPath);</code> will mess things up if we have two directories in the hierarchy that has the same name, for instance: /opt/lampp/htdocs/blog/wp-content/plugins/myplugin/blog/data two directories are named 'blog' might give unexpected results. " ... For finding and loading either wp-load.php or wp-config.php, what about something like this ... " Eric

This part of the code:

$rootPath = str_replace('/'.$rootArray[$i], '', $rootPath);

will mess things up if we have two directories in the hierarchy that has the same name, for instance:

/opt/lampp/htdocs/blog/wp-content/plugins/myplugin/blog/data

two directories are named 'blog' might give unexpected results.

]]> By: Organize Series 2.0.8beta Release « Unfolding Neurons http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/comment-page-2/#comment-78464 Organize Series 2.0.8beta Release « Unfolding Neurons Fri, 10 Oct 2008 06:16:30 +0000 http://planetozh.com/blog/?p=865#comment-78464 [...] Added fix for any calls made to the ‘wp-config.php’ file in orgSeries (see here for my reference) [...] [...] Added fix for any calls made to the ‘wp-config.php’ file in orgSeries (see here for my reference) [...]

]]> By: Eric http://planetozh.com/blog/2008/07/what-plugin-coders-must-know-about-wordpress-26/comment-page-2/#comment-72771 Eric Wed, 10 Sep 2008 14:56:10 +0000 http://planetozh.com/blog/?p=865#comment-72771 For finding and loading either wp-load.php or wp-config.php, what about something like this: [php]$rootPath = dirname(__FILE__); $rootArray = explode("/",$rootPath); $countRootArray = count($rootArray); for($i=($countRootArray-1); $i>=0; $i--) { $rootPath = str_replace('/'.$rootArray[$i], '', $rootPath); if (file_exists($rootPath.'/wp-load.php')) { require_once($rootPath.'/wp-load.php'); break; } elseif (file_exists($rootPath.'/wp-config.php')) { require_once($rootPath.'/wp-config.php'); break; } } [/php] For finding and loading either wp-load.php or wp-config.php, what about something like this:

PLAIN TEXT
PHP:
  1. $rootPath = dirname(__FILE__);
  2. $rootArray = explode("/",$rootPath);
  3. $countRootArray = count($rootArray);
  4. for($i=($countRootArray-1); $i&gt;=0; $i--) {
  5.     $rootPath = str_replace('/'.$rootArray[$i], '', $rootPath);
  6.     if (file_exists($rootPath.'/wp-load.php')) {
  7.         require_once($rootPath.'/wp-load.php');
  8.         break;
  9.     } elseif (file_exists($rootPath.'/wp-config.php')) {
  10.         require_once($rootPath.'/wp-config.php');
  11.         break;
  12.     }
  13. }

]]>