This is usefull and recommended in a production environment, you don’t want to parse all folders each time.

On a development environment, you may want not to generate that cache file and therefore not use the setSaveFile, so whenever you add a new class or modify where files are located, your app will automatically rediscover those updates and still work.

I am processing a Wordpress tree from a different Wordpress program - so the classes may not be the same either because the core is a different version or different plugins etc are included. Active and inactive plugins/themes need to be included because I am using the information to modify the database and I kept coming across serialised objects that weren’t in a class.

It’s a pity the basic __autoload function assumes the class filename is the same as the class - this certainly isn’t case for most of Wordpress!

It did work ‘out of the box’ when I extended the test code to instantiate a class within the defined folder, i.e.

$autoloadManager = new AutoloadManager();
$autoloadManager->setSaveFile(’autoload.php’);
$autoloadManager->addFolder(’BridgeDesignPattern’);
$autoloadManager->excludeFolder(’BridgeDesignPattern/report_plugins’);
$autoloadManager->register();

$diag = new ManageDiagnostics(); // class within folder ‘BridgeDesignPattern’
$diag->setLocalArgs(10, array(10,20,30), __FILE__);
print_r($diag->getLocalArgs());

The last three lines of test code triggered the creation of the ‘SaveFile’.

Eventually got it to generate array in ‘SaveFile’ by adding ‘$this->generate();’ at end of function ‘register’

Used the following test code:

$autoloadManager = new AutoloadManager();
$autoloadManager->setSaveFile(’autoload.php’);
$autoloadManager->addFolder(’BridgeDesignPattern’);
$autoloadManager->register();

Is that all that is required?