Hi Markus,

yes there is. same way we roughly intend to solve it for next 5.x release.

Setup Symfony to take over the url  ( content/versionview/{ObjectID}/{EditVersion}/{LanguageCode}/{FromLanguage} ) and redirect it to a controller similar to the stock content controller in 5.x stack with the difference being selecting a specific version instead, given legacy admin interface uses iframe to front end this should theoretically work.

In reality there probably is a couple of more edge cases and things to take care of then that, but this should already be a big step towards solving the problem without having to change legacy.

Best,

André

Hi André, thanks for your reply.

I gave it a try, but it seems that I'm missing something...

There are two issues that I'm fighting at the moment:

* Though the custom route works in my user siteaccess, the admin backend just ignores the symfony2 route and still uses the legacy viewcontroller.

* My custom controller is basically a copy of the eZ\Publish\Core\MVC\Symfony\Controller\Content\ViewController class. This class expects injection of a ViewManager object. I've tried adding this to my services.yml:

    my.controller.preview:
        class: My\CustomBundle\Controller\PreviewController
        arguments: [@ezpublish.view_manager]
        parent: ezpublish.controller.base
        scope: request

But (in the user siteaccess) I always get an exception: "Catchable Fatal Error: Argument 1 passed to My\CustomBundle\Controller\PreviewController::__construct() must be an instance of eZ\Publish\Core\MVC\Symfony\View\Manager, none given"

Could you please give me a hint what I'm missing here?

Another approach is to call subrequests into symfony from the legacy stack. We've created a legacy template operator for this: 

https://github.com/blendinteractive/blendsubrequest

From an architectural standpoint, this isn't a good solution, but it works well and provides an easy solution until more of the admin is moved to the Symfony stack.

Very nice Joe ! Definitely valuable for migration / Forward compatibility!

I think it deserves a blog post

Hi Joe,

this looks pretty good - I'll try this tomorrow. Thank you very much!

Hi Joe,

I've added your extension, but unfortunately I get a "Operator 'render_controller' is not registered" warning. I regenerated the autoloads array, and the operator class is listed there. Is there anything else I need to do?

Modified on Tuesday 03 December 2013 12:58:59 am by Markus Mahner

Hi Markus

Did you activate the extension in settings/override/site.ini.append.php ?

Hi Jérôme,

yes, I did. I even tried moving the entry around (top/bottom of ActiveExtensions[] list), just in case this would change anything. And of course I cleared the caches every now and then.

Hi Markus, 

I took another look at the code, I'm not sure why it won't work for you. Sounds like you've tried most of this, but as a troubleshooting checklist:

• The root of the code from the repo should be at ezpublish_legacy/extension/blendsubrequest in your project
• The ActiveExtensions list in ezpublish_legacy/settings/override/site.ini.append.php should contain ActiveExtensions[]=blendsubrequest
• Autoloads should be refreshed. From your ezpublish_legacy folder, 'bin/php/ezpgenerateautoloads.php'
• The legacy cache should be cleared. From your ezpublish_legacy folder, 'bin/php/ezcache.php --clear-all --purge -s <correct siteaccess>'
• If it's still not showing up, you might try checking the config for typos, and clearing the cache manually by deleting everything in ezpublish_legacy/var/cache/* and ezpublish_legacy/var/<your siteaccess>/cache/*

I hope that helps.

@Joe: You should add a composer.json and an entry in Packagist for this extension

Check this out!