Ezplatform Xmltext Fieldtype Laravel Package

Product Decisions This Supports

• Unblocks the platform upgrade decision. The core value of v2.0.0 is not new functionality — the feature set is identical to v1.9.2 — it is that the package now runs on eZ Platform v3. This directly supports a "can we move off legacy eZ Publish 4.x/5.x and onto v3" decision, which is often gated on whether historical content can be carried forward intact.
• Content migration strategy (XmlText → RichText). This package exists to convert legacy XmlText fields into RichText. It is a migration instrument, not a runtime feature. Treat it as a line item in a content-migration workstream rather than as a product capability.
• Build vs. buy, resolved toward adopt. The scope is narrow, well-defined, and tedious: deprecated field type tags, class parameters, Symfony 5 exit-status codes, v3.0 stable compatibility. Rebuilding this in-house is a multi-week engineering cost with no differentiation. Adopt.
• Roadmap sequencing input. Because 2.x is explicitly scoped to migration use only, it should not be placed on a product roadmap as a shipped capability. It belongs on the upgrade roadmap, with a defined start and, critically, a defined end (removal once migration completes).
• Risk reduction for a legacy-to-current jump. The release specifically enables migrating directly from eZ Publish 4.x/5.x to eZ Platform v3, skipping intermediate hops. That shortens migration timelines and reduces the number of intermediate platform states the team must support.

When to Consider This Package

Consider adoption when:

• You hold legacy eZ Publish 4.x/5.x content with XmlText fields and are targeting eZ Platform v3.
• You are planning a content migration and need a validated, community-reviewed converter rather than a bespoke script.
• Your migration environment can be isolated from production runtime dependencies — this is the right deployment pattern for a migration-only field type.

Look elsewhere when:

• You are greenfield, or your content is already RichText. There is no migration to perform and the package adds nothing.
• You are on eZ Platform v2.x or earlier — pin to the 1.x line, since 2.x targets v3.
• You are targeting Ibexa DXP v4+. The release notes speak specifically to eZ Platform v3 (v3.0 stable); do not assume forward compatibility with the post-rebrand v4 line without a spike.
• You need a runtime content field type. The maintainers state plainly that 2.x is for migration only — using it as a production dependency would be an inappropriate coupling.

Adoption criteria to confirm before committing: a defined migration window and exit plan, a rollback path for converted content, and confirmation that the Symfony 5 exit-status changes do not conflict with any custom migration commands in your own tooling.

How to Pitch It (Stakeholders)

For executives: This is a small, targeted dependency that clears a blocker on our platform upgrade. It lets us bring historical content forward from legacy eZ Publish directly onto eZ Platform v3, instead of rebuilding that conversion ourselves or maintaining an intermediate platform. Cost is minimal; the alternative — bespoke migration tooling — is engineering time we would rather spend on the product. It is deliberately scoped as migration-only and will be retired once the migration completes.

For engineering: v2.0.0 is a compatibility release, not a feature release — same capabilities as v1.9.2, now working on eZ Platform v3.0 stable, with the expected Symfony 5 and deprecation cleanups done (field type tags, class parameters, command exit codes). Two things to note: 2.x is supported only for XmlText → RichText migration, so keep it out of production runtime dependencies and scope it to the migration environment; and it targets v3 specifically, so treat v4/Ibexa DXP as unvalidated until we spike it.