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
Warning: DOMDocument::loadXML(): AttValue: " or ' expected in Entity, line: 1
500 Internal Server Error - ContextErrorException
Stack Trace
in /var/www/joiz.lo/vendor/jackalope/jackalope-jackrabbit/src/Jackalope/Transport/Jackrabbit/Request.php at line 685 -
// create new DOMDocument and load the response text.
$dom = new DOMDocument();
$dom->loadXML($xml);
return $dom;
ok - you can blame the angular developers and make them fix their code - but i think it would be also a good idea to add some logic which regcognises a path which will most likely produce a error in jackrabbit route lookup and return straight a 404 instread of bothering the jackrabbit first
The text was updated successfully, but these errors were encountered:
this is fixed in newer versions of phpcr-odm. i debugged the situtation with the current https://github.com/symfony-cmf/cmf-sandbox and was not able to reproduce the issue. the RoutingBundle\Doctrine\Phpcr\RouteProvider::getRouteCollectionForRequest sees /cms/routes/[[dsfdsfdfsd]] as a candidate, but after $routes = $dm->findMany($this->className, $candidates);, the $routes only contain /cms/routes and /cms/simple. this leads to a regular 404 which is the expected behaviour.
i would of course try it out first, but i guess it should work, yes.
there are a few more strict checks in 1.3, so maybe you will see some
error messages in places. just open phpcr-odm tickets when you see
something.
requesting a cmf url of the form http://joiz.lo/main_dev.php/[[dsfdsfsdfsd]] leads to the error message
Warning: DOMDocument::loadXML(): AttValue: " or ' expected in Entity, line: 1
500 Internal Server Error - ContextErrorException
Stack Trace
in /var/www/joiz.lo/vendor/jackalope/jackalope-jackrabbit/src/Jackalope/Transport/Jackrabbit/Request.php at line 685 -
// create new DOMDocument and load the response text.
$dom = new DOMDocument();
$dom->loadXML($xml);
return $dom;
ok - you can blame the angular developers and make them fix their code - but i think it would be also a good idea to add some logic which regcognises a path which will most likely produce a error in jackrabbit route lookup and return straight a 404 instread of bothering the jackrabbit first
The text was updated successfully, but these errors were encountered: