technical migration path to ez platform and ez studio - jan 2016
TRANSCRIPT
www.ez.no
MIGRATING TO EZ PLATFORM AND EZ STUDIO
A GUIDE FOR TRANSITIONING TO EZ’S NEW GENERATION
VERSION 1ar
www.ez.no
Agenda
TODAY: 5.X STACK MANUAL MIGRATION
Look at manual migration and an recent example of that.
SOON: 5.X CONTENT MIGRATION PREVIEW
Look at what migration tools will be available soon in 16.02 and 16.04.
LATER: FULL CONTENT MIGRATION
Overview of missing features before we can call it feature complete.
FUTURE: 3.X / 4.X CONTENT MIGRATION
Some info on how we might be able to cover 3.x/4.x content migration.
INTRODUCTION
Overview of what migration implies.
IntroductionOverview of how migration will work once all migration features are in place.
www.ez.nowww.ez.no
Migration Overview
Solution based on 3rd, 4th or 5th
generation eZ CMS:eZ Publish “legacy”
Solution based on 6th generation
eZ CMS:eZ Platform
and eZ Studio
“Legacy” eZ Platform / eZ Studio
www.ez.nowww.ez.no
Overview of differences
Environment (operating system, web servers
, database server…)
eZ Publish
eZ Publish Customization
eZ Publish Extensions
Content
Environment (operating system, web servers
, database server…)
eZ Platform & Symfony
eZ Platform & Studio Customization
eZ Platform & eZ Studio Bundles
Content
“Legacy” eZ Platform / eZ Studio
www.ez.nowww.ez.no
Re Development
Upgrade
Option A: Direct Upgrade
Environment (operating system, web servers
, database server…)
eZ Publish
eZ Publish Customization
eZ Publish Extensions
Content
Environment (operating system, web servers
, database server…)
eZ Platform & Symfony
eZ Platform & Studio Customization
eZ Platform & eZ Studio Bundles
Content
“Legacy” eZ Platform / eZ Studio
www.ez.nowww.ez.no
Upgrade
Upgrade
Option B: Via 5.x, part 1
Environment (operating system, web servers
, database server…)
eZ Publish
eZ Publish Customization
eZ Publish Extensions
Content
Environment (operating system, web servers
, database server…)
eZ Platform 5.x stack Customization
Symfony Bundles
Content
“Legacy” eZ Publish 5.x “Hybrid”
eZ Publish
eZ Publish Customization
eZ Publish Extensions
eZ Platform 5.x stack & Symfony
www.ez.nowww.ez.no
Upgrade
Upgrade
Option B: Via 5.x, part 2
Environment (operating system, web servers
, database server…)
eZ Platform 5.x stack & Symfony
Content
eZ Publish 5.x “Full stack”
eZ Publish
eZ Publish Customization
eZ Publish Extensions
Environment (operating system, web servers
, database server…)
eZ Platform & Symfony
eZ Platform & Studio Customization
eZ Platform & eZ Studio Bundles
Content
eZ Platform / eZ Studio
eZ Platform 5.x stack Customization
Symfony Bundles
5.X stack manual migrationWith code on 5.x “Full stack”, and with simple content, you can already migrate.
www.ez.nowww.ez.no
FROM EZ 5.X SYMFONY TO EZ PLATFORM & EZ STUDIO
๏ Download eZ Platform or eZ Studio
๏ Move configuration and code over
๏ Add RichText and/or Landing Page field
๏ Manually move content over using UI
www.ez.nowww.ez.no
๏ Installation:
๏ 5.4 installation, all Symfony/5.x “Full stack”
๏ Only light use of XmlText: headings, paragraphs and bullet lists
๏ POC upgrade:
๏ 1 day
๏ 50% on re creating basic content structure, 50% setup & alignment
๏ Content moved by copy paste
๏ Both OE and RichText FieldType cable of handling this content
๏ Limitations: No controls exposed yet on adding new bullets list groups
POC Example: GodFisk.no
Content Migration PreviewWhat tools and guides to expect for 16.02/16.04
www.ez.nowww.ez.no
Content Migration Preview
๏ 5.4 to eZ Platform/eZ Studio Upgrade Guide [planned, eta 16.02]
๏ RichText
๏ Script for upgrading XmlText to RichText [in progress, eta 16.02]
๏ Custom tag guide [planned, eta 16.04]
๏ Custom tag migration guide [planned, eta 16.04]
๏Landing Page
๏ Script for upgrading Flow to Landing Page [planned, eta 16.04]
๏ Content and configuration
๏ Custom block guide [exists]
๏ Custom block migration guide [planned, eta 16.04]
Full Content MigrationOverview of the main missing features in order to enable all migrations.
www.ez.nowww.ez.no
Feature status
✓ Landing Page Field type feature parity, including custom blocks
✓ Rich Text Field type feature parity, including custom tags
‣ OE (Online Editor)
➡ Controls for Bullet lists [eta 16.02]
➡ Broader Embed support [eta 16.02 and 16.04]
➡ Controls for Tables
➡ Custom tags
➡ Custom attributes
➡ Classes (for all tags)
Further info: https://doc.ez.no/display/MAIN/Transitioning+from+eZ+Publish+to+eZ+Platform+and+eZ+Studio%3A+Feature+Comparison
3.x/4.x Content MigrationLook beyond for possible direct content migration for legacy versions.
www.ez.nowww.ez.no
3.x / 4.x content migration
๏ Once we have 5.x upgrades covered
๏ Handle 4.7 and while on it we can go as far back as sensible
๏ Feedback on which versions most installs are on is welcome to identify needs!
Again, further info in regards to features: https://doc.ez.no/display/MAIN/Transitioning+from+eZ+Publish+to+eZ+Platform+and+eZ+Studio%3A+Feature+Comparison
Summary
www.ez.nowww.ez.no
Summary
➡Upgrade Doc from 5.4 - planned, preview eta around 16.02
๏Rich text
✓ eZ XmlText upgrade to eZ Richtext (Docbook) - now in prototype for 16.02
See: https://github.com/ezsystems/ezplatform-xmltext-fieldtype/pull/7
✓ eZ RichText Field Type supports all features XmlText did, incl. custom tags & embeds
➡ But you’ll have to adjust your code for this, code migration guide planned.
➡Known limitations with OE: Tables, Bullets, Custom tags, limited embeds
๏Pages
✓ eZ Flow upgrade to eZ (Studio) Landing Page - planned, eta 16.04
✓ eZ Landing Page Field Type supports all features Flow did, incl. pages, zones & blocks
➡ But you’ll have to re implement your blocks, code migration guide planned.
➡Known limitations: Landing page not updated on content delete
www.ez.nowww.ez.no
Migration Take aways
๏Right now (15.12, & 15.12.1 due next week) best match is new projects
๏Migrations becomes possible increasingly over the course of 2016
๏ Simple sites with simple needs possible starting 16.02 end of February
๏Most sites, even those with simple approval workflows and Flow, by 16.04/16.06
๏Complex sites should ideally go via 5.4 and should rather evolve there until ready, migrations can happen as of Fall 2016
๏After this point we can consider prioritizing direct 4.x content upgrade scenarios
