Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do you know why I got this message ? #35

Open
MaraScott opened this issue Sep 21, 2017 · 3 comments
Open

Do you know why I got this message ? #35

MaraScott opened this issue Sep 21, 2017 · 3 comments

Comments

@MaraScott
Copy link

Hi,
Do you know why I got this kind of message ?

Fatal error: require(): Failed opening required 'symfony/lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine/Doctrine/Parser/sfYaml/sfYamlConfigHandler.php' (include_path='.:/usr/share/php') in symfony/lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine/Doctrine/Core.php on line 1118

see original issue qdpm/qdpm#2

@regisnew
Copy link

regisnew commented Oct 2, 2019

It's becouse of autoload.

@regisnew
Copy link

regisnew commented Oct 2, 2019

#34

@alquerci
Copy link

alquerci commented Oct 5, 2019

Hello,

@regisnew Yes, because of autoloading logic that try to load class sfYamlConfigHandler that is not part of Yaml component see: https://github.com/FriendsOfSymfony1/doctrine1/blob/v1.3.6/lib/Doctrine/Core.php#L1135
So the PR #34 is not going to fix it, as it just upgrade Yaml code and fix composer autoloading.

@davask Doctrine1 autoloader is registered on this application.
The reason is because of autoloader precedence order.
Symfony1 autoloader must be register before Doctrine1 to avoid this error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants