MAMP > 5.7.4 RC2 : ConcreteCoreFileStorageLocationStorageLocation.php
Permalink 1 user found helpful
Hi there,
this message pops up after updating (via replacement of the old concrete folder) from 5.7.3.1 to 5.7.4 RC2 at the start page of my site:
Doctrine\Common\Proxy\AbstractProxyFactory::getProxyDefinition(): Failed opening required '/Applications/MAMP/htdocs/concrete5/application/config/doctrine/proxies/__CG__ConcreteCoreFileStorageLocationStorageLocation.php' (include_path='/Applications/MAMP/htdocs/concrete5/concrete/vendor:.:/Applications/MAMP/bin/php/php5.6.7/lib/php')
do i have to make clean new install or can I edit the AbstractProxyFactory.php in
/Applications/MAMP/htdocs/concrete5/concrete/vendor/doctrine/common/lib/Doctrine/Common/Proxy
to get rid of this message (creating the __CG__ConcreteCoreFileStorageLocationStorageLocation.php file ?)
this message pops up after updating (via replacement of the old concrete folder) from 5.7.3.1 to 5.7.4 RC2 at the start page of my site:
Doctrine\Common\Proxy\AbstractProxyFactory::getProxyDefinition(): Failed opening required '/Applications/MAMP/htdocs/concrete5/application/config/doctrine/proxies/__CG__ConcreteCoreFileStorageLocationStorageLocation.php' (include_path='/Applications/MAMP/htdocs/concrete5/concrete/vendor:.:/Applications/MAMP/bin/php/php5.6.7/lib/php')
do i have to make clean new install or can I edit the AbstractProxyFactory.php in
/Applications/MAMP/htdocs/concrete5/concrete/vendor/doctrine/common/lib/Doctrine/Common/Proxy
to get rid of this message (creating the __CG__ConcreteCoreFileStorageLocationStorageLocation.php file ?)
did you visithttp://www.yoursite.com/index.php/ccm/system/upgrade... and run the upgrade script?
@andrew: it kinda worked - it showed me an update message from 5.7.31 to 5.7.4 RC2 but also:
file_put_contents(): Filename cannot be empty
still - the error is gone :D - so it worked :D merci :)
file_put_contents(): Filename cannot be empty
still - the error is gone :D - so it worked :D merci :)
I think you can refresh the doctrine proxies by going to /index.php/dashboard/system/environment/entities and clicking the "Refresh Entities" button though. That might get you past this error if you can get there.