For now conversion works for these layouts:
- Webapp Datasource Property (webapp item id in the value will be replaced with the id of custom module item that was transferred by the app earlier).
- Webapp item description (modules)
- Webapp List and Detail Layouts (modules, entire tags and liquid tag output)
- Menu Layouts (modules, entire tags and liquid tag output)
- Pages (modules, splitting page content to Content property (part inside <body> html tag) and to SEO - <HEAD> section property (part inside <head> html tag))
- Page Templates (modules, entire tags)
- ContentHolders (modules)
- Any include inside any layout above will be parsed and converted using the same rules as for the layout where the include was found.
- For example if the webapp list layout contains {% include “/somepath/someinclude.inc” %}
and content of the include is {tag_description} than conversion engine will modify the content of the include in a scope of webapp list layout so {tag_description} will be replaced to {{this[‘Description’]}}.
Note it will work only for includes that has static path.
The only exception is using {{this.params.moduleTemplateGroup}} inside include path that is placed inside menu layouts
Modules and liquid that will be converted are:
- System and Custom modules:
- module_contentholder
- module_menu
-
module_webapps
- If the webapp used some template="/somepath/custom.tpl" than conversion will create additional list layout named like _somepath_custom_tpl and attach it to the result component type="module ".
Also that layout will be added to conversion queue and also will be parsed by conversion engine like webapp list layout.
- General modules:
- module_pagename
- module_isloggedin
- module_goback
- module_closewindow
- module_today
-
| date:"" liquid filter will be replaced by | format_date:"" because the bc date format used in liquid fully corresponds the date format in format_date liquid filter instead of date filter.
-
{{globals}} usage (~ means any subproperty):
- *{{globals.get.~}}
- *{{globals.cookie.~}}
- *{{globals.site.host}}
- *{{globals.site.datenow}}
- *{{globals.visitor.deviceclass}}
- *{{globals.visitor.ip}}
- *{{globals.visitor.useragent}}
- *{{globals.visitor.referrer}}
- *{{globals.user.entityid}}
- *{{globals.user.firstname}}
- *{{globals.user.lastname}}
- *{{globals.user.username}}
- *{{globals.user.email}}
- *{{globals.user.isloggedin}}
PS: By the way, note that the transfer engine stopped forcing replacement of content of custom module layouts if the content doesn’t correspond to default custom module list and detail layout.
It should help if you repeat the transfer of the same webapp in order to let it migrate additional webapp items and not affect the custom module layouts edited by the admin user.
Hope it makes sense. If you have any additional questions please don’t hesitate to ask me here.
