[fw-general] Unexpected dispatcher behaviour

2007-12-10 Thread Łukasz Wojciechowski
I use __call() function in my system. The problem is that there is
class_exists() used in Zend_Controller_Dispatch_Standard witch tries
to autoload class (i.e. IndexController) witch obviously fails ;) ...
In 2 places (line 282 and 165) I added 2nd parameter to class_exists
(witch is disabling autoload) and it works perfectly.

Wondering if this behaviour is in purpouse?

Using Zend 1.0.3

-- 
Łukasz Wojciechowski


Re: [fw-general] Unexpected dispatcher behaviour

2007-12-10 Thread Karol Grecki

Use  http://www.php.net/manual/en/function.spl-autoload-register.php
spl_autoload_register()  instead of plain __autoload()


Karol


Łukasz Wojciechowski-3 wrote:
 
 I of course meaned __autoload not __call ;) sorry for that
 
 -- 
 Łukasz Wojciechowski
 
 

-- 
View this message in context: 
http://www.nabble.com/Unexpected-dispatcher-behaviour-tp14252592s16154p14253138.html
Sent from the Zend Framework mailing list archive at Nabble.com.



Re: [fw-general] Unexpected dispatcher behaviour

2007-12-10 Thread Łukasz Wojciechowski
On Dec 10, 2007 3:30 PM, Matthew Weier O'Phinney [EMAIL PROTECTED] wrote:
 For now, if you define __autoload(), it will be an issue; however, if
 you use Zend_Loader::registerAutoload(), which registers with
 spl_autoload(), all works correctly (due to differences in how each
 handles exceptions). So, the quick fix, until the next release, is to
 use Zend_Loader::registerAutoload() if you want to use autoloading.

Oh thanks ;) Didn't notice registerAutoload(). Thnx :)


-- 
Łukasz Wojciechowski