Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added info on how to migrate custom tags from ezpublish #869

Merged
merged 11 commits into from
Feb 28, 2020
Merged

Added info on how to migrate custom tags from ezpublish #869

Show file tree
Hide file tree
Changes from 5 commits
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
d5262f9
Added info on how to migrate custom tags from ezpublish
vidarl Nov 14, 2019
521928e
Added anchor on custom link attribute(customtags) and linked to it fr…
vidarl Nov 14, 2019
c453d73
fixup! Added info on how to migrate custom tags from ezpublish
vidarl Nov 14, 2019
5f46281
fixup! Added anchor on custom link attribute(customtags) and linked t…
vidarl Nov 14, 2019
29346e8
Proofing
Nov 15, 2019
8e6cc1c
Merge branch '2.5' into migrate_custom_tag
Feb 19, 2020
211dccb
Fix heading
Feb 24, 2020
3ba86f2
Merge branch '2.5' into migrate_custom_tag
Feb 24, 2020
13ff970
Fix link
Feb 24, 2020
c47848d
Apply suggestions from code review
Feb 25, 2020
b3e695f
Fixes after review
Feb 27, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/guide/extending/extending_online_editor.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ They are configured under the `ezrichtext` key.

If you want to learn how to apply them to your installation follow [Creating a custom tag tutorial](../../tutorials/extending_admin_ui/6_adding_a_custom_tag).

**Example: YouTube tag**
#### Example: YouTube tag

Preparation of the tag always starts with the configuration file that should be added to `app/Resources/config`. This is sample configuration for the YouTube tag, `custom_tags.yml`:

Expand Down Expand Up @@ -108,7 +108,7 @@ ezrichtext.custom_tags.ezyoutube.attributes.width.label: Width
ezrichtext.custom_tags.ezyoutube.attributes.align.label: Align
```

**Example: FactBox tag**
#### Example: FactBox tag

FactBox tag is a good example for showcasing possibilities of `ezcontent` property.
Each custom tag has an `ezcontent` property that contains the tag's main content.
Expand Down Expand Up @@ -179,7 +179,7 @@ ezrichtext.custom_tags.ezfactbox.attributes.style.choices.light.label: Light sty
ezrichtext.custom_tags.ezfactbox.attributes.style.choices.dark.label: Dark style
```

**Example: Link tag**
#### Example: Link tag

You can also configure a custom tag with a `link` attribute that offers a basic UI with text input.
It is useful when migrating from eZ Publish to eZ Platform.
Expand Down
28 changes: 28 additions & 0 deletions docs/migrating/migrating_from_ez_publish_platform.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -362,6 +362,34 @@ When you are ready to migrate your eZ Publish XmlText content to the eZ Platform

`php -d memory_limit=1536M bin/console ezxmltext:convert-to-richtext --export-dir=ezxmltext-export --export-dir-filter=notice,warning,error --concurrency 4 -v`

**Custom tags**
andrerom marked this conversation as resolved.
Show resolved Hide resolved

eZ Platform now supports custom tags, including inline custom tags, and limited use of custom tag attributes.
After migrating to RichText, you need to adapt your custom tag config for eZ Platform and rewrite the custom tags in Twig.
See [Custom tag documentation](../guide/extending/extending_online_editor.md#custom-tags) for more info.

If you configured custom attributes in legacy in OE using [ezoe_attributes.ini](https://github.com/ezsystems/ezpublish-legacy/blob/master/extension/ezoe/settings/ezoe_attributes.ini#L33-L48), note that not all types are supported.

Below is a table of the tags that are currently supported, and their corresponding names in eZ Platform.

| [XmlText](https://github.com/ezsystems/ezpublish-legacy/blob/2019.03/extension/ezoe/settings/ezoe_attributes.ini#L33-L48) | [RichText](https://github.com/ezsystems/ezplatform-richtext/blob/2.5/src/bundle/DependencyInjection/Configuration.php#L17) | Note |
andrerom marked this conversation as resolved.
Show resolved Hide resolved
| ------------- | ------------- | ----- |
| `link` | [`link`](../guide/extending/extending_online_editor.md#example-link-tag) | Treated as a string, no special UI provided by the eZ Platform editor |
alongosz marked this conversation as resolved.
Show resolved Hide resolved
| `number` | `number` | |
| `int` | `number` | |
| `checkbox` | `boolean` | |
| `select` | `choice` | |
| `text` | `string` | |
| `textarea` | Not supported | Use `string` as workaround |
| `email` | Not supported | Use `string` as workaround |
| `hidden` | Not supported | Use `string` as workaround |
| `color` | Not supported | Use `string` as workaround |
| `htmlsize` | Not supported | Use `string` as workaround |
| `csssize` | Not supported | Use `string` as workaround |
| `csssize4` | Not supported | Use `string` as workaround |
| `cssborder` | Not supported | Use `string` as workaround |


###### 3.2.2 Migrate Page field to Page (eZ Enterprise only)

**If** you use Page field (ezflow) and an eZ Enterprise subscription, and are ready to migrate your eZ Publish Flow content to the eZ Enterprise Page format, you can use a script to migrate your old Page content to new Page, to start using a pure eZ Enterprise setup. See [Migrating legacy Page field (ezflow) to new Page (Enterprise)](#migrating-legacy-page-field-ezflow-to-new-page-enterprise) for more information.
Expand Down