-
Notifications
You must be signed in to change notification settings - Fork 25
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
[Semantical Error] The annotation "@Gedmo\Mapping\Annotation\Timestampable" #24
Comments
Is DoctrineServiceProvider registered before the ExtensionsServiceProvider? |
I've tried them both ways round, currently as below
Really strange as it was working fine :S |
Here's my config file if it's of help.
|
Extensions must be defined after DoctrineSP. |
Yeah, I'm on there now.. |
Nevermind, other problem :) |
Finally worked it out and in hindsight I don't know why I didn't try this sooner! My App service provider had a custom validation method... which used the Auth facade, which is running off Doctrine! Moving the Doctrine service provider above the App service provider solved it.
Sometimes a day off gives your mind a bit of clarity! Thanks again Patrick for your help the other day. |
In case anyone else runs into this issue, I had experienced it due to adding custom Doctrine Types in a |
@jwondrusch yes, never call any services in register() as the service might not been registered yet. For custom doctrine types we have a config setting: https://github.com/laravel-doctrine/orm/blob/1.1/config/doctrine.php#L113 |
Having done a recent composer update I'm now getting the following error. I've tried rolling back to previous versions of Laravel-Doctrine, the extensions and also Gedmo, but nothing appears to help.
I'm not really sure where to look, it was working 100% before the composer update.
My composer settings are
Are you able to help?
The text was updated successfully, but these errors were encountered: