Zend Framework

Bug: 'include(FrontController.php) [function.include]: failed to open stream: No such file or directory' error message

Details

  • Type: Sub-task Sub-task
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.9.2, 1.9.3, 1.9.4, 1.9.5, 1.9.6, 1.9.7, 1.9.8, 1.10.0, 1.10.1, 1.10.2, 1.10.3
  • Fix Version/s: 1.10.5
  • Labels:
    None

Description

Hi,
Even though I saw that this bug fixed,
I still get this error message:

'Warning: include(FrontController.php) [function.include]: failed to open stream: No such file or directory in /xxx/library/Zend/Loader.php on line 83'

The workaround of adding 'false' at class_exists() in BootstrapAbstract.php (line 354) still solves this.

Issue Links

Activity

Hide
David Abdemoulaie added a comment -

The false parameter was removed from the get_class() call in r17801. Simply adding it back causes the test case Zend_Application_Bootstrap_BootstrapAbstractTest::testRequestingPluginsByAutoloadableClassNameShouldNotRaiseFatalErrors.

I'm going to try and see if I can't find out a way for this to work in both cases.

Show
David Abdemoulaie added a comment - The false parameter was removed from the get_class() call in r17801. Simply adding it back causes the test case Zend_Application_Bootstrap_BootstrapAbstractTest::testRequestingPluginsByAutoloadableClassNameShouldNotRaiseFatalErrors. I'm going to try and see if I can't find out a way for this to work in both cases.
Hide
David Abdemoulaie added a comment -

I'm stumped. Any ideas Matthew?

Show
David Abdemoulaie added a comment - I'm stumped. Any ideas Matthew?
Hide
Glen Ainscow added a comment -

I get this error as soon as I enable the fallback autoloader. Any ideas?

Show
Glen Ainscow added a comment - I get this error as soon as I enable the fallback autoloader. Any ideas?
Hide
Miroslav Kubelik added a comment -

Yes, if you want to remove this warning, you need to disable fallback autoloader and rewrite your code for an properly namespace based loading.
Using false in get_class isn't solution, because it produces other problems as Matthew said.

I think module bootstraping need to be deeply revised, but I don't have currenty any idea.

Show
Miroslav Kubelik added a comment - Yes, if you want to remove this warning, you need to disable fallback autoloader and rewrite your code for an properly namespace based loading. Using false in get_class isn't solution, because it produces other problems as Matthew said. I think module bootstraping need to be deeply revised, but I don't have currenty any idea.
Hide
Glen Ainscow added a comment -

What if you're using a library (or application classes) that aren't namespaced?

Show
Glen Ainscow added a comment - What if you're using a library (or application classes) that aren't namespaced?
Hide
David Abdemoulaie added a comment -

I created a patch that prevents this warning from occurring.

http://gist.github.com/353288

It doesn't break any unit tests. However, I tried but couldn't duplicate the warning in a unit test context.

I can duplicate it in an application at will though by doing the following:

1. Enable fallback autoloader
2. Use module bootstraps `resources.modules[] =`

This will result in 1 warning per module bootstrap.

Show
David Abdemoulaie added a comment - I created a patch that prevents this warning from occurring. http://gist.github.com/353288 It doesn't break any unit tests. However, I tried but couldn't duplicate the warning in a unit test context. I can duplicate it in an application at will though by doing the following: 1. Enable fallback autoloader 2. Use module bootstraps `resources.modules[] =` This will result in 1 warning per module bootstrap.
Hide
David Abdemoulaie added a comment -

Fixed in r22124

Show
David Abdemoulaie added a comment - Fixed in r22124

People

Vote (4)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved: