• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

SiteBuilder v3 backward compatible with v2

E

ewong

Guest
Hi All,

We have been using Sitebuilder v2 for a long time and has many customers building websites using it. If I upgrade sitebuilder to version3, would all my existing v2 customers continue to work on their existing v2 templates?

Best regards,
Edward
 
As I know situation is the following:

In old version 2.x there are more than 200 templates available. In new version there are almost 500 templates. If we have, for example, in old Sitebuilder templates with name 'aa-02' and in new version we have templates with the same name. In this situation old template won't be migrated and new one will be used instead, as we think that newer templates should be used instead of old one. But there should not be any significant changes in new version of old templates.
Anyway, if you are going to accomplish upgrade and migration I strongly suggest to create full Sitebuilder backup. In this case you can always turn back to old version.
 
Back
Top