Details
-
Bug
-
Resolution: Fixed
-
High
-
1.10.0, 1.9.1, 1.7.4
-
eZ Studio + Legacy Bridge 1.2.1 + Legacy 5.4.10
Description
After installing eZ Platform EE with Legacy Bridge and Legacy 5.4.10 the blocks "All Drafts Scheduled for Future Publication" and "My Drafts Scheduled for Future Publication" on "My Dashboard" in the Platform UI backend are not working (the spinner won't stop spinning and the contents won't load). The errors "Failed to load list of all scheduled content" and " Failed to load list of content scheduled by the user" are shown to the user. The network tab shows that there are four requests that ended with a 500 response code (two for each block). These requests are:
- http://ezplatform-ee.dev/api/datebasedpublisher/v1/content/schedule/0/10
- http://ezplatform-ee.dev/api/datebasedpublisher/v1/content/schedule/user/0/10
The responses from these requests look as follows:
{
"ErrorMessage": {
"_media-type": "application\/vnd.ez.api.ErrorMessage+json",
"errorCode": 500,
"errorMessage": "Internal Server Error",
"errorDescription": "The API provider 'datebasedpublisher' could not be found.",
"trace": "#0 XXX\\ezplatform-ee\\ezpublish_legacy\\kernel\\private\\rest\\classes\\rest_provider.php(59): ezpRestProvider::createProvider('datebasedpublis...')\n#1 XXX\\ezplatform-ee\\ezpublish_legacy\\kernel\\private\\rest\\classes\\router.php(51): ezpRestProvider::getProvider('datebasedpublis...')\n#2 XXX\\ezplatform-ee\\ezpublish_legacy\\kernel\\private\\rest\\classes\\router.php(38): ezpRestRouter->doCreateRoutes()\n#3 XXX\\ezplatform-ee\\vendor\\zetacomponents\\mvc-tools\\src\\router.php(90): ezpRestRouter->createRoutes()\n#4 XXX\\ezplatform-ee\\ezpublish_legacy\\kernel\\private\\rest\\classes\\dispatcher.php(46): ezcMvcRouter->getRoutingInformation()\n#5 XXX\\ezplatform-ee\\ezpublish_legacy\\kernel\\private\\rest\\classes\\ezpkernelrest.php(188): ezpMvcConfigurableDispatcher->run()\n#6 XXX\\ezplatform-ee\\ezpublish_legacy\\kernel\\private\\classes\\ezpkernel.php(53): ezpKernelRest->run()\n#7 XXX\\ezplatform-ee\\vendor\\ezsystems\\legacy-bridge\\mvc\\Kernel.php(119): ezpKernel->run()\n#8 XXX\\ezplatform-ee\\vendor\\ezsystems\\legacy-bridge\\bundle\\Controller\\LegacyRestController.php(35): eZ\\Publish\\Core\\MVC\\Legacy\\Kernel->run()\n#9 [internal function]: eZ\\Bundle\\EzPublishLegacyBundle\\Controller\\LegacyRestController->restAction()\n#10 XXX\\ezplatform-ee\\vendor\\symfony\\symfony\\src\\Symfony\\Component\\HttpKernel\\HttpKernel.php(144): call_user_func_array(Array, Array)\n#11 XXX\\ezplatform-ee\\vendor\\symfony\\symfony\\src\\Symfony\\Component\\HttpKernel\\HttpKernel.php(64): Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw(Object(Symfony\\Component\\HttpFoundation\\Request), 1)\n#12 XXX\\ezplatform-ee\\vendor\\symfony\\symfony\\src\\Symfony\\Component\\HttpKernel\\DependencyInjection\\ContainerAwareHttpKernel.php(69): Symfony\\Component\\HttpKernel\\HttpKernel->handle(Object(Symfony\\Component\\HttpFoundation\\Request), 1, true)\n#13 XXX\\ezplatform-ee\\vendor\\symfony\\symfony\\src\\Symfony\\Component\\HttpKernel\\Kernel.php(185): Symfony\\Component\\HttpKernel\\DependencyInjection\\ContainerAwareHttpKernel->handle(Object(Symfony\\Component\\HttpFoundation\\Request), 1, true)\n#14 XXX\\ezplatform-ee\\web\\app.php(70): Symfony\\Component\\HttpKernel\\Kernel->handle(Object(Symfony\\Component\\HttpFoundation\\Request))\n#15 {main}",
"file": "XXX\\ezplatform-ee\\ezpublish_legacy\\kernel\\private\\rest\\classes\\rest_provider.php",
"line": 37
}
}
Steps to reproduce
- Setup new eZ Platform EE installation.
- Add the Legacy Bridge using the following instructions: https://github.com/ezsystems/LegacyBridge/blob/master/INSTALL.md.
- During the step Add legacy routes add the routes above _ezpublishDateBasedPublisher in the app/config/routing.yml file.
- Instead of the step to run composer require for the legacy bridge, run the following:
composer require --update-with-dependencies "ezsystems/ezpublish-legacy:5.4.10 as 2017.07.x-dev" "ezsystems/legacy-bridge:^1.0.4"
This will ensure that you have Legacy version 5.4.10 installed and not the 2015.01.3 version (this will be corrected in some way outside the scope of this issue).
- Log in to the PlatformUI backoffice.
- The above error appears.