RT template upgrading - unsafe for customizations
-
-
- williamconifer
- Rocketeer
- Posts: 91
- Thanks: 1
-
Greetings,
We have been running into problems upgrading RT templates (mostly Acacia) to ver 1.9. We are finding that customizations we make to Rocksproket and RocNavMenu as overrides get overwritten when we upgrade the template. We follow the steps you have documented for overriding RS layouts, and while this keeps our customizations safe when upgarding RS it isn't safe when upgrading the template.
Is there any best practice you recommend in upgrading a template of yours?
Will this situation improve with the new Gantry 5 templates your are publishing?
Thanks
Jack - Last Edit: 9 years 11 months ago by williamconifer.
- Jack Hughes
-
-
-
- DanG
- Preeminent Rocketeer
- Posts: 36750
- Thanks: 3229
- Custom work done
-
williamconifer wrote:
Is there any best practice you recommend in upgrading a template of yours?
At some point the developer has to assume at least some responsibility for their decisions. The RokSprocket folder in our template is an override for the layouts in the Component folder. So there is no method I know of to create an override for an override.
Your process of saving the RokSprocket folder before updating is the recommended policy, in fact backups before ANY kind of update are always a recommendation we make to our members.
In Gantry 5 the situation will be the same, if you modify a file in it's original location as it can't be copied out as an override in a custom folder, then you're responsible for it's safety when updating.
The devs are exploring options of more RokSprocket-esque functionality within G5, but that is still a work in progress.
-
Time to create page: 0.059 seconds