Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 1.8.1
-
Fix Version/s: 1.8.1
-
Component/s: Zend_Application
-
Labels:None
Description
the class_exists() method in BootstrapAbstract::registerPluginResource is launching the autoloader, and tries to include resources without the proper paths. The second parameter in this method should be false so that it doesn't launch the autoload.
Note, you need to do this to get the errors:
$autoloader->suppressNotFoundWarnings(false);
as they are not on by default (another bug)
This was created by the fix for:
http://framework.zend.com/issues/browse/ZF-6543
Removing autoloading would break some functionality that was corrected, however. What is the exact problem?
The idea here is that if the class exists – i.e., has been or can be autoloaded – we need to treat it differently so as to ensure that it registers with the bootstrap correctly (which prevents naming collisions). If we do not allow class_exists() to attempt to autoload the class, then we lose this ability.
Is there an actual problem that occurs if autoloading fails to find the class? Or are you simply getting logged notices? You've marked the issue as "critical", but not really indicated what the issue is exactly.