GenerateProxiesCommand getConfiguration()->getProxyDir() is undefined #6269

Open
opened 2026-01-22 15:29:55 +01:00 by admin · 2 comments
Owner

Originally created by @Musiksammler on GitHub (Jul 5, 2019).

Bug Report

Q A
BC Break no
Version 3.0.x-dev

Summary

I just started to use the doctrine console. With a simple "php vendor/bin/doctrine orm:generate-proxies" it fails with the following message: "Call to undefined method Doctrine\ORM\Configuration::getProxyDir() in .../vendor/doctrine/orm/lib/Doctrine/ORM/Tools/Console/Command/GenerateProxiesCommand.php on line 57"

Current behavior

Command failes when to proxies directory is given as an argument.

Use the doctrine console with following call:

"php vendor/bin/doctrine orm:generate-proxies"

Expected behavior

That the command generates the proxy classes even without giving an explicit directory.

Originally created by @Musiksammler on GitHub (Jul 5, 2019). ### Bug Report | Q | A |------------ | ------ | BC Break | no | Version | 3.0.x-dev #### Summary I just started to use the doctrine console. With a simple "php vendor/bin/doctrine orm:generate-proxies" it fails with the following message: "Call to undefined method Doctrine\ORM\Configuration::getProxyDir() in .../vendor/doctrine/orm/lib/Doctrine/ORM/Tools/Console/Command/GenerateProxiesCommand.php on line 57" #### Current behavior Command failes when to proxies directory is given as an argument. Use the doctrine console with following call: "php vendor/bin/doctrine orm:generate-proxies" #### Expected behavior That the command generates the proxy classes even without giving an explicit directory.
admin added the Bug label 2026-01-22 15:29:55 +01:00
Author
Owner

@greg0ire commented on GitHub (Sep 28, 2019):

Where should the proxy classes be generated?

@greg0ire commented on GitHub (Sep 28, 2019): Where should the proxy classes be generated?
Author
Owner

@Ocramius commented on GitHub (Oct 2, 2019):

Note: https://github.com/doctrine/orm/pull/7770#issuecomment-537401418

In theory, we can solve this by just "instantiating" a proxy for every metadata type: the ProxyManager component will already perform disk writes, if configured in such way.

getProxyDir() should no longer be used. /cc @alirezameskin (if you want to give this another try)

@Ocramius commented on GitHub (Oct 2, 2019): Note: https://github.com/doctrine/orm/pull/7770#issuecomment-537401418 In theory, we can solve this by just "instantiating" a proxy for every metadata type: the ProxyManager component will already perform disk writes, if configured in such way. `getProxyDir()` should no longer be used. /cc @alirezameskin (if you want to give this another try)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#6269