• 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.

Feedback from hosts using SiteBuilder

Z

ZeroSixty

Guest
Hello,

To those of you who offer SiteBuilder to your clients:

How have your clients responded to it? Is it well liked? Have your clients had anything good/bad to say about it's ease of use? Do you get a lot of support requests related to the SiteBuilder?

Another question: Once a site has been published to a domain, is there something to prevent the user downloading the site (via FTP) and re-uploading to another domain? Can they then edit the original in SiteBuilder to something completely different (choose another template)? Basically, can you prevent users from creating several different sites with a single published site?

TIA
 
Can anyone answer any of these questions? SWsoft will not respond to my questions :mad:
 
SiteBuilder generates a static web site with a nice design, and provides some basic tools for editing that site. Once the site has been published to a server, there is nothing that would prevent a user from downloading a copy of that site (via FTP) to their local machine and editing it.

The integration between SiteBuilder and PWSE is non-existent, which is too bad. Right about the time that users "outgrow" SiteBuilder, they would be ready for PWSE. Unfortunately, PWSE will quite happily overwrite a SiteBuilder web site without warning, and unlike SiteBuilder there isn't any documentation about PWSE to speak of.
 
Back
Top