Hi,
Solved! Go to Solution.
Views
Replies
Total Likes
The very first part of templates definition, taken from http://dev.day.com/docs/en/cq/current/developing/templates.html : "A Template is used to create a Page"
The content of template is just a plain node hierarchy, that will be copied to the newly created page. There is very loose coupling between instance of template (i.e. page) and template. This binding is defined in the second part of the definition: "defines which components can be used within the selected scope". This is the only dynamic part in the equation.
For the problems like yours, some additional work needs to be done. For bunch of pages, that were created for template with wrong renderer attached it's impossible to change it manually (e.g. using crxde). There are open source tools like Groovy console (https://github.com/Citytechinc/cq-groovy-console) which can invoke the migration code. You can easily find all the pages with given template configured and change sling:resourceType property to the new one you'd like to. Unfortunately, you need to do this operation on every environment affected.
Hope this helps. If any further questions - don't hesitate to ask.
Mateusz
Views
Replies
Total Likes
The very first part of templates definition, taken from http://dev.day.com/docs/en/cq/current/developing/templates.html : "A Template is used to create a Page"
The content of template is just a plain node hierarchy, that will be copied to the newly created page. There is very loose coupling between instance of template (i.e. page) and template. This binding is defined in the second part of the definition: "defines which components can be used within the selected scope". This is the only dynamic part in the equation.
For the problems like yours, some additional work needs to be done. For bunch of pages, that were created for template with wrong renderer attached it's impossible to change it manually (e.g. using crxde). There are open source tools like Groovy console (https://github.com/Citytechinc/cq-groovy-console) which can invoke the migration code. You can easily find all the pages with given template configured and change sling:resourceType property to the new one you'd like to. Unfortunately, you need to do this operation on every environment affected.
Hope this helps. If any further questions - don't hesitate to ask.
Mateusz
Views
Replies
Total Likes
Thanks for the info Mateusz.
Views
Replies
Total Likes