I created a small Package with just 1) a new Template (for an existing Document type) and 2) a new Content page that uses that template. Then I installed this package on another PC.
The issue is that after installation, the template isn't applied on new content pages on the destination site.
Looking at the umbraco DB, figured that, after installation the 'xml' field in cmsContentXml table is giving an incorrect template id. (It chose the default template id for the linked document type, i.e. chose MyTemplate1 instead of MyTemplate3).
Note: I've alraedy tried AllowTemplateForDoctype Package action. However, it just enables the template on the document type, but doesn't auto select the same template for the content page.
Given the problem is stated clear enough, is there any solution to this?
What version of Umbraco did you experience this on?
The above descriptions sounds like it could be a bug - therefore I suggest you report the above in the issue tracker here: issues.umbraco.org/issues/U4
Installing Package missed out Content->Template link
To test and describe the problem clearly:
I created a small Package with just 1) a new Template (for an existing Document type) and 2) a new Content page that uses that template. Then I installed this package on another PC.
The issue is that after installation, the template isn't applied on new content pages on the destination site.
i.e. Document type: MyDocType
Templates : MyTemplate1, MyTemplate2, MyTemplate3 (new)
Content: Content3 (new)
Looking at the umbraco DB, figured that, after installation the 'xml' field in cmsContentXml table is giving an incorrect template id. (It chose the default template id for the linked document type, i.e. chose MyTemplate1 instead of MyTemplate3).
Note: I've alraedy tried AllowTemplateForDoctype Package action. However, it just enables the template on the document type, but doesn't auto select the same template for the content page.
Given the problem is stated clear enough, is there any solution to this?
Hi M
What version of Umbraco did you experience this on?
The above descriptions sounds like it could be a bug - therefore I suggest you report the above in the issue tracker here: issues.umbraco.org/issues/U4
/Jan
We've seen it on 4.7.1 and 4.7.2 versions.
Thanks - posted as an issue on http://issues.umbraco.org/issue/U4-1548
is working on a reply...