-
Notifications
You must be signed in to change notification settings - Fork 156
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
SF2.7 / SF2.8 + Propel1 / Bad propel init on first call after clear:cache #356
Comments
PropelBundle initializes configuration in boot method in PropelBundle.php which seems to be too late in some scenerio. I ran into the same problem when I use propel query in constructor of service that is passed to twig as global variable. Check this out for more details: http://stackoverflow.com/questions/34298976/does-symfony-2-8-load-bundles-and-services-in-correct-order-during-warmup |
thanks for theses explanations, but as say ryan, "In short: this looks like a quirk of Propel to me, but someone who knows more about Propel might know a way to forcefully "boot" it. Propel is special because of the static context it uses." So, anybody in the Propel core team have advices about this "boot" issue? |
Same problem w. a fresh new project in SF2.8, any help welcome. |
Can you provide an installation with the problem? A PR on https://github.com/havvg/symfony-propel-edition would be awesome :) |
Env:
The first time I call a page or a SF command line after having clear the cache, I've got this error:
If I recall the page or the command line, it works fine.
Someone have ideas?
Thanks.
The text was updated successfully, but these errors were encountered: