[Not a bug] Developer Tool Kit can't find files with "local" configure.php

[lat9]

Running 1.5.0 release, on localhost using a "local" version of the configure.php files present in /includes/local and /MYADMIN/includes/local. The file /MYADMIN/includes/local/configure.php is a copy of the file that was created during the 1.5.0 install.

When I used the Developers Tool Kit, searching in all files for the string logger in both Catalog and Admin files, php-only, not case sensitive ... no files were returned. That was odd to me, because the file /MYADMIN/includes/classes/logger.php contains that string!

The problem occurs because of the enhanced version of the configure.php file that "auto-detects" the name of the ZC admin directory and uses that information to create the file-system path name:

define('DIR_FS_ADMIN', realpath(dirname(__FILE__) . '../'));

When that code is present in /MYADMIN/includes/local, the base file-system path becomes /MYADMIN/includes instead of /MYADMIN ... resulting in none of the admin-specific files ever being included in the search.

I was able to work around the problem by changing the definition to:

define('DIR_FS_ADMIN', 'c:/xampp/htdocs/xxxx/myadmin');

At a minimum, it would be good if the next version of the admin's configure.php (and dist-configure.php?) included a comment for those using the "local" override regarding this issue.

[Ajeh]

Could you check that on the final release of v1.5 and see if you are still having this issue?

[lat9]

I am running the final release ... but the configure.php file that's in my admin's /includes/local directory was created with a previous 1.5.0 beta version. When I changed the DIR_FS_ADMIN to use the construct in the 1.5.0 final release

define('DIR_FS_ADMIN', realpath(dirname(__FILE__) . '/../') . '/');

... it's all better.

Sorry for the false report ...