I figured out what was the cause of this problem, it was the opcode cacher was using, eAcclerator on Windows. It wasn't playing well with Doctrine - I got rid of it, replaced it with APC and all's fine now!
Thanks On Jul 16, 6:30 pm, AMailer <[email protected]> wrote: > Hey, > > Any idea why I would be getting this error? It only occurs when the > cache is loaded. > If I clear the cache, it works fine. > ---------------------- > 500 Internal Server Error - Doctrine\ORM\Mapping\MappingException > Class Application\MyBundle\Entities\User\Account is not a valid entity > or mapped super class. > ---------------------- > > That's what the error looks like. I'm loading this by using: > $this->getEntityManager('user')->getRepository('Application\MyBundle > \Entities\User\Account') > > It works if I clear the cache but then when I refresh (cache is > created) it gives me that error. > > Any ideas? > > Thanks! -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
