Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.2k
Unified autoloading in Sf2 <> Sf1 article#2867
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
wouterj commentedJul 30, 2013
| Q | A |
|---|---|
| Doc fix? | yes |
| New docs? | no |
| Applies to | 2.1+ |
| Fixed tickets | #2331 |
| If the file did *not* live at this exact location, you'd receive a | ||
| ``Class "Sensio\Bundle\FrameworkExtraBundle\SensioFrameworkExtraBundle" does not exist.`` | ||
| error. In Symfony2, a "class does not exist" means that the suspect class | ||
| namespace and physical location do not match. Basically, Symfony2 is looking | ||
| error. In Symfony2, a "class does not exist" error means that the namespace of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
In Symfony2 seems weird here as it is not specific to Symfony2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
ah sorry, this is the chapter comparing to symfony1 so it actually make sense
Unified autoloading in Sf2 <> Sf1 article
Thanks Wouter! |