• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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