search

ekino / EkinoWordpressBundle

Integrate Symfony with WordPress and WordPress with Symfony
GNU General Public License v2.0
312 stars 79 forks source link

fixes issue with doctrine auto mapping #97

Closed ghost closed 8 years ago

eko commented 8 years ago

Hi @pneidig,

Thank you for this fix, have you tested it with Doctrine auto-mapping?

ghost commented 8 years ago

hi @eko,

yes, i have tested it with symfony/symfony 3.0.0 with doctrine auto mapping enabled. i guess it's really a problem with doctrine/orm >= 2.5. doctrine throws a mapping exception on all database operations if the wordpress bundle is enabled:

[Doctrine\Common\Persistence\Mapping\MappingException]                  
Class 'Ekino\WordpressBundle\Entity\model\TermTaxonomy' does not exist

when i was still using symfony 2.x, i was able to solve this problem by downgrading doctrine/orm, but symfony 3.x depends on doctrine 2.5, so this is not a viable solution any more.

see also: https://github.com/FriendsOfSymfony/FOSUserBundle/issues/1790

eko commented 8 years ago

I agree with this fix, I just would like to be sure that this fix is working correctly.

Thank you, this is a good job!