You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Map Content also linked the source and destination page templates.
However, when the page was actually imported, the page was generated with the default page template for the page type instead of the specified page template.
In the example above, the page was actually generated in the "right_sidebar" template when it was intended to be imported in the "full" template.
Even though all page templates were allowed on the page type side, the page was always generated with the default page template.
This is very inconvenient if one page type allows multiple page templates!
The text was updated successfully, but these errors were encountered:
Pages were imported using the Migration Tool.
At this time, a page template is specified for the page to be imported on the xml file side.
Example: xml
<page name="PageTitle" path="/blog/abc" public-date="2019-01-01 18:00:00" filename="" pagetype="blog_entry" template="full" user="admin" description="" package="" theme=""><attributes>
Example: Page Type(Basic Details)
Map Content also linked the source and destination page templates.
However, when the page was actually imported, the page was generated with the default page template for the page type instead of the specified page template.
In the example above, the page was actually generated in the "right_sidebar" template when it was intended to be imported in the "full" template.
Even though all page templates were allowed on the page type side, the page was always generated with the default page template.
This is very inconvenient if one page type allows multiple page templates!
The text was updated successfully, but these errors were encountered: