[DoctrineBundle] The proxy file ... does not exist issue

[mschneid]

With the new RC 4 I receive several "The proxy file "%s" does not exist. If you still ..." exceptions. If I remove the boot function in Symfony\Bundle\DoctrineBundle\DoctrineBundle everything works fine. It seems to me that the new doctrine autoloader mechanism isn't compatible with this code.

[akloboucnik]

Mya I ask why this is closed? I'm still having this issue, even with current HEAD...

[stof]

Could you provide a way to reproduce your issue ? I don't have it.

[mschneid]

The problem only occurs if you use an entity with associations as security provider (Entity implements the AdvancedUserInterface). If you clear the cache while your login session is still running, symfony will not be able to create the proxy files at the next request.

By now I found two solutions for this problem:

• Create an empty file (e.g. with touch ../cache/AcmeIssueBundleEntityCategoryProxy.php)
  or
• Remove the boot function in Symfony\Bundle\DoctrineBundle\DoctrineBundle

What do you think, is the boot function in the DoctrineBundle class still necessary (with the new doctrine autoloader mechanism)? For me everything works perfectly without these lines.

[stof]

if you remove the boot function, The proxy cannot be autoloaded when unserializing the token, which makes your application fail when you have a proxy object as user interface (or as a related entity if you serialize them too).

The new Doctrine autoloader mechanism is for annotations. It has nothing to do with proxies.
Doctrine does not register an autoloader for its proxies. It requires the cached file when the class does not exist yet. So Doctrine itself does not need to autoload the proxies. But this is needed when you unserialize a proxy as you don't call Doctrine before.

If you have a serialized proxy object in your token and don't have the proxy class, there is no way to make it work properly. Your case may work when removing the method if the proxy is not your User class but a related entity as the main object has its class. But the related object is created as a __PHP_Incomplete_Class__ which means your object is in a broken state and the methods using the related object will fail.
To clear your cache, use the CLI command which warms up the proxies. This way you don't have this issue about non-existant proxies.

[akloboucnik]

Ok, thanks for the help - updating Doctrine stuff to 2.1.0 and adding new annotation loading mechanism to autoload.php made it work, so thanks for the explanation and sorry for bothering.

[Adamamont]

Hmm, I still have this bug with using cache:clear.

[pogotc]

I'm still having this issue using cache:clear as well, that's with the final 2.0 release.

[mschneid]

Clear your PHP Session by hand:

rm /var/lib/php5/*

[Adamamont]

I suppose, that it isn't good solution for production.

[Adamamont]

This issue only for developer environment. In production everything is OK.

[fabpot]

fixed in #1968

[juanmaia]

I see that it is closed, but im still getting this bug.
Basically im not using mysql at all, just mongodb and it seems to be looking for the wrong files as the message i get is:

The proxy file "/home/caderno/Symfony/app/cache/dev/doctrine/orm/Proxies/CadernoCadernaoBundleDocumentRoleProxy.php" does not exist. If you still have objects serialized in the session, you need to clear the session manually.

I think its looking just in the orm path..
I have also generated the proxies with doctrine:mongodb:generate:proxies

For the authentication i created my own service and my config.yml goes like

providers:
        default:
            id: caderno_security_provider

Any ideas?