• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Do templates need to be updated 4.1 > 4.2?

D

dwightk

Guest
I just upgraded from 4.1 to 4.2. I'd like to figure out if all the templates need to be updated.

I installed the one Ag template as a test and see it's version is 4.0.0, so I assume it has not been updated.

Is there anything different about the 4.2 templates?

For future updates, it would be very helpful to know what template changes are needed in order to have full access to the new features. I have a number of custom templates and would need to update them. I don't recall ever seeing a list of template changes needed....
 
Update to new Sitebuilder version always requires templates update. In this case you need to download all templates from here for example: ftp://download1.swsoft.com/SiteBuilder/templates/4.2.0 and install them all on your 4.2 installation. Some of the templates were updated in this package, some were not, but for compatibility all templates should be updated. Old templates should also work fine with new version but it is strongly suggested to use latest ones.
If template version was not changed after update, it just means that update did not affect this particular template.

As for custom templates for every new version Parallels developers prepare documents like custom template developer's guides which can be found here:
http://swdn.swsoft.com/en/library/. So you can use it for custom templates update if you have any issues with it after update but it should be compatible and should not cause any issues at least in the context of one branch 4.x versions.
 
Back
Top