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
{{ message }}
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.
Cloned Sandbox few days ago and played around.
Just to test runned "composer update" today and updated successfully.
After that treebrowser in admin panel turns to this
In webprofile ajax request logs get this exceptions:
Detected the following problem: Hm. No clue what goes wrong. Maybe this is a real 404?
exception 'Puli\Repository\Api\ResourceNotFoundException' with message 'No PHPCR-ODM document could be found at "/false/cms/routes"' in /home/bubuntu/Documents/websites/BleedingEdgeSymfonyCMF/vendor/symfony-cmf/resource/Repository/PhpcrOdmRepository.php:177
Stack trace:
#0 /home/bubuntu/Documents/websites/BleedingEdgeSymfonyCMF/vendor/symfony-cmf/resource/Repository/PhpcrOdmRepository.php(49): Symfony\Cmf\Component\Resource\Repository\PhpcrOdmRepository->getDocument('//false/cms/routes')
#1 /home/bubuntu/Documents/websites/BleedingEdgeSymfonyCMF/vendor/symfony-cmf/resource-rest-bundle/Controller/ResourceController.php(57): Symfony\Cmf\Component\Resource\Repository\PhpcrOdmRepository->get('//false/cms/routes')
#2 [internal function]: Symfony\Cmf\Bundle\ResourceRestBundle\Controller\ResourceController->getResourceAction('default', '/false/cms/routes')
#3 /home/bubuntu/Documents/websites/BleedingEdgeSymfonyCMF/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php(153): call_user_func_array(Array, Array)
#4 /home/bubuntu/Documents/websites/BleedingEdgeSymfonyCMF/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php(68): Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object(Symfony\Component\HttpFoundation\Request), 1)
#5 /home/bubuntu/Documents/websites/BleedingEdgeSymfonyCMF/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(169): Symfony\Component\HttpKernel\HttpKernel->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
#6 /home/bubuntu/Documents/websites/BleedingEdgeSymfonyCMF/web/app_dev.php(39): Symfony\Component\HttpKernel\Kernel->handle(Object(Symfony\Component\HttpFoundation\Request))
#7 {main}
Next exception 'Symfony\Component\HttpKernel\Exception\NotFoundHttpException' with message 'No resource found at path "/false/cms/routes" for repository "default"' in /home/bubuntu/Documents/websites/BleedingEdgeSymfonyCMF/vendor/symfony-cmf/resource-rest-bundle/Controller/ResourceController.php:61
Stack trace:
#0 [internal function]: Symfony\Cmf\Bundle\ResourceRestBundle\Controller\ResourceController->getResourceAction('default', '/false/cms/rout...')
#1 /home/bubuntu/Documents/websites/BleedingEdgeSymfonyCMF/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php(153): call_user_func_array(Array, Array)
#2 /home/bubuntu/Documents/websites/BleedingEdgeSymfonyCMF/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php(68): Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object(Symfony\Component\HttpFoundation\Request), 1)
#3 /home/bubuntu/Documents/websites/BleedingEdgeSymfonyCMF/vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php(169): Symfony\Component\HttpKernel\HttpKernel->handle(Object(Symfony\Component\HttpFoundation\Request), 1, true)
#4 /home/bubuntu/Documents/websites/BleedingEdgeSymfonyCMF/web/app_dev.php(39): Symfony\Component\HttpKernel\Kernel->handle(Object(Symfony\Component\HttpFoundation\Request))
#5 {main}
The text was updated successfully, but these errors were encountered:
Dont run composer update. It seems some updated bundle cause this issue. Use sandbox's composer.json, composer.lock and rollback by running "composer install".
Cloned Sandbox few days ago and played around.
Just to test runned "composer update" today and updated successfully.
After that treebrowser in admin panel turns to this
In webprofile ajax request logs get this exceptions:
The text was updated successfully, but these errors were encountered: