restricted.tpl (no backup)

[mrgtb]

I've just noticed a template highlighted in red in my template list.

It's seems in the latest patch pack for download. You have included a new template called "restricted.tpl" in the system folder. Thing is though, this template was not there in the Vivvo 4.0 original download. This means there is no backup template for it. As in the latest Update Pack. You only included that one template file to be uploaded, and not a second "restricted.tpl.original" template. Just thought I would mention it in-case this was overlooked by accident.

Out of curiosity also, All the other templates you upload that have fixes in them in the patch pack that you upload. Well, it the same in a way with them. You really should have created a backup of them to be uploaded also. Otherwise, if a person makes changes to them templates and then reverts them back. They will be reverting back to the Vivvo 4 original templates, and not the new updated ones with fixes they have uploaded from the new patch pack. If you get my drift. There really should have been duplates of them as ".original" templates to overwrite the old ones too. So if they revert back, they are reverting back to the ones that are patched - and not the original Vivvo 4 templates without fixes in them

[shketuljko]

Thank you for your suggestion.
We will consider it in our next Vivvo patch.

[mrgtb]

Well I think it would make sense with all new templates included in the patched folder, to also include a "tpl.original" of it as well to be uploaded. For reasons I posted above.

A prime example would be. Lets say a person installs the latest patch, then later on he modifies a template (that was replaced in the latest patch). And then decides to revert it back. It would get reverted back to the original template that came with Vivvo and not the patched one he uploaded. Because the patched template uploaded, did not also include a ".tpl.original" version of it as well to be uploaded.

He then might start coming here posting a support ticket because a problem as popped-up that was fixed in the patched template he's no longer using, because he reverted back to the original Vivvo one which was not over-written with the new patched original version.

In the long-run, this will save a lot of problems regarding support issues. By simply also including a ".tpl.original" of the new patched templates to be uploaded and overwrite, in-case a person modifies a new patched template he's uploaded and want to revert back to it again - instead of him reverting back to the original Vivvo one without realizing he's doing it.