Please complete the following fields as applicable:

What version of the DMPRoadmap code are you running? (e.g. v2.2.0)

v3.0.2

Expected behaviour:

• create a template, and publish it
• create a plan based on that template
• manually unpublish it by clicking "unpublish"
• add question (or make any change) to that template
• new version should be created, because there are plans attached to it

Actual behaviour:

• I can freely add changes to that template, without a new version being created. This way the changes are visible in the new plan..

Steps to reproduce:

• create a template, and publish it
• create a plan based on that template
• manually unpublish it by clicking "unpublish"
• add question (or make any change) to that template
• go to your plan: the changes are visible.

B.T.W: the same happens when you publish a new version, and the old published one becomes unpublished again

I guess the problem here is that published=false looks like the first (draft) state of the template,
when no plans can be attached, so the interface has no clue it was used before. Maybe set archived=true?
I thought that archived=true was meant as the last stage in the lifecycle of a template; at least for migrated
templates, from dmponline_v4..