This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit ezplatform.com

eZ Community » Forums » eZ Publish 5 Platform » Legacy extension in ez5
expandshrink

Legacy extension in ez5

Legacy extension in ez5

Monday 12 August 2013 10:05:31 am - 3 replies

Just a couple weeks ago I asked here about how to rewrite the custom datatype and custom fetch function into brand new FieldType and Twig extension. Now, after vacation, I'm back to topic and need your help again.

Just imagine that I have a bit complex legacy extension which works perfectly () in admin panel in latest eZ community version. Obviously, what I need to do is make it working on front-side of the project. You have me the instructions (http://share.ez.no/forums/ez-publish-5-platform/custom-datatype-migrationhttp://share.ez.no/forums/ez-publish-5-platform/custom-fetch-functions-in-ez5.x) for some points, but still - I'm wondering how to start? happy.gif Emoticon

Should I start from creating a new Bundle or should I rewrite the code in legacy extension? What should be the next steps? In case I need to create the Bundle, where to place *.tpl files (because as far as I know, I don't need to rewrite them on twig)?

Have anyone already rewrited legacy extension on ez5? It would be helpful for me to check out such code.

Monday 12 August 2013 11:02:17 am

Hi Piotr, hope you had a nice vacation happy.gif Emoticon

You should defiantly write it as a bundle, and very good source of inspiration is the eZ Tags Bundle given 1. eztags is fairly advance 2. It seem to comply with all best practice in regards layers of unit / integration testing blunk.gif Emoticon

Monday 12 August 2013 11:13:59 am

I had a look on new eZ Tags Bundle and I can't see any templates there (admin panel for instance). Is that mean I need to have two extensions (legacy and bundle) installed to make it work?

Monday 12 August 2013 2:22:50 pm

Yes, the two kernels are not made to integrate on this level, would be difficult to do as they differ so much in field type handling. So as long as your in a need to use both kernels, some features, most prominently field types, needs to be maintained in two variants.

Modified on Monday 12 August 2013 2:24:53 pm by André R

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from