You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a bug with PHP/libxml where simplexml_load_file (used by doctrine mapping XML driver) will fail even when loading xml with no external entities if libxml_disable_entity_loader is set to true. This bug still exists with latest PHP5.6 and latestt PHP7 (didn't check PHP5.5 but expect to be affected too). See https://bugs.php.net/bug.php?id=62577&edit=1 and http://www.serverphorums.com/read.php?7,1262794 (discussion on making libxml_disable_entity_loader setting default to true for PHP7 or 7.1).
This bug causes error in reading FosUser's orm mapping in XML. See #1062
Change FosUser doctrine mapping to use YML instead of XML hence avoiding this bug
The text was updated successfully, but these errors were encountered:
layanto
changed the title
Use Yaml doctrine mapping instead of XML due to issue with XML driver and libxml_disable_enttitty_loader
Use Yaml doctrine mapping instead of XML due to issue with XML driver and libxml_disable_entity_loader
Dec 23, 2015
There is a bug with PHP/libxml where simplexml_load_file (used by doctrine mapping XML driver) will fail even when loading xml with no external entities if libxml_disable_entity_loader is set to true. This bug still exists with latest PHP5.6 and latestt PHP7 (didn't check PHP5.5 but expect to be affected too). See https://bugs.php.net/bug.php?id=62577&edit=1 and http://www.serverphorums.com/read.php?7,1262794 (discussion on making libxml_disable_entity_loader setting default to true for PHP7 or 7.1).
This bug causes error in reading FosUser's orm mapping in XML. See #1062
I have raised this with doctrine project too. See doctrine/orm#3788 and https://groups.google.com/forum/m/#!topic/doctrine-user/vAb_3zcz6vU
The PHP bug was reported back in 2012 and is still not fixed. My suggestions (in order of preference):
The text was updated successfully, but these errors were encountered: