Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
Sitebuilder templates from v.3 are supported by new version 4. But it is strongly suggested to upgrade templates together with rest Sitebuilder packages as there were made a lot of corrections.
So if we upgrade the templates will the old ones be lost and will clients need to pick a new one? Or can both v3 and v4 templates exist on the same server? Or can we keep a select number of the old templates?
Originally posted by Jllynch So if we upgrade the templates will the old ones be lost and will clients need to pick a new one? Or can both v3 and v4 templates exist on the same server? Or can we keep a select number of the old templates?
During upgrade old templates will be rewritten with new ones. So both versions of templates could not exists on the same server. You can keep some of the old templates but we can not guarantee that it will work correctly, as new templates released for new version with some bugfixes. So in this case it is better to upgrade. To keep old templates you can move them to some different named directory, for example, /usr/local/sitebuilder/htdocs/templates/night_club-001/ to /usr/local/sitebuilder/htdocs/templates/night_club-111/
and correct <template id="night_club-001" in info.xml file, so Sitebuilder should recognize this templates as different one.