How to update VB template using product xml file?

[vbboarder]

I'm writing a product xml file and want to update a default VB template with the one I've included in the xml file. If I just give my template the same name as the VB template, then my template will become the default and the VB template will be deleted. How do you prevent the VB template from being deleted?
Also, how do you prevent the new template from being the active one without the user's confirmation (similar to when you update VB and the updated templates are saved but not set to active if the old template has been modified)? Much appreciated for any help

[Opserty]

Don't update a default template. Either include installation instructions with the changes or edit the template through a plugin when the page is executed.

Maybe helpful: [How-To] Using Plugins for Automatic Template Edits

[vbboarder]

Originally Posted by Opserty

Don't update a default template. Either include installation instructions with the changes or edit the template through a plugin when the page is executed.

Maybe helpful: [How-To] Using Plugins for Automatic Template Edits

Thanks for the link. I'm aware of how to edit a template via a plugin, but was hoping to update a default template similar to how a new VB version updates its templates.

[Marco van Herwaarden]

Distributing (modified version of) default vB templates with a modification is an absolute No-No.

[vbboarder]

Originally Posted by Marco van Herwaarden

Distributing (modified version of) default vB templates with a modification is an absolute No-No.

Actually, I'm not looking to modify a default VB template, but replace it with another one and NOT have the default VB template deleted. Anyways, I know what you mean...., what I want to do is probably a legal no-no too..... I guess I'll just use the "edit template via a plugin" technique.

[Marco van Herwaarden]

What i mean is that overwriting default templates with any version (modified/rewritten) is an absolute NoNo, as it will destroy the original template and it will be a lot of work to reinstall the original at a later stage (for example when uninstalling the modification).

[vbboarder]

Originally Posted by Marco van Herwaarden

What i mean is that overwriting default templates with any version (modified/rewritten) is an absolute NoNo, as it will destroy the original template and it will be a lot of work to reinstall the original at a later stage (for example when uninstalling the modification).

I'm aware of that - that's why I asked this question in my first post:

How do you prevent the VB template from being deleted?

[Opserty]

The vB template won't be deleted. But the users customised template may lose its customisations, that is where the problem lies. I haven't seen it done before with a modification, hence why it is difficult to offer help. Just stick to the tried and tested method of telling the user or using Plugins.

[Marco van Herwaarden]

Originally Posted by vbboarder

I'm aware of that - that's why I asked this question in my first post:

And my post was an (second) answer to that question.

To avoid confusion, i don't think Opserty's answer is correct on your question (if i understand correctly).

Bottomline is that you should never touch the default templates in the master style (and including it in a product will always place the templates included in the product into the master style). So don't ever distribute versions of default templates in your modifications.