• 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 not working

flosoft

Basic Pleskian
Hey,

I have upgraded from Plesk 7.5 to 8.01. I use PHP5 and Debian Sarge.
Now when I go to sitebuilder.domain.com it gives me:
Site error: the file /usr/local/sitebuilder/include/autoprp.php requires the ionCube PHP Loader ioncube_loader_lin_5.0.so to be installed by the site administrator.

If I locate ioncube, I see that it is in the php5 folder :S
What do I need to do?
 
Unfortunately, the version of sitebuilder you have is unsupported by the ionCube loader you have. I had the same problem with mine while I was trying to "test" to see what SiteBuilder was like. I ended up downgrading to the March release to see if I could get the "daily cron messages" to go away. Once they went away, I tested the sitebuilder system. It was nice, it had a lot of features, but it was a demo, and I don't have the loot to throw at it...so it was a waste of a few hours of finding why stuff was broke for me...

What I did..

download current version of Sitebuilder from SW-Soft
rpm -Uvh SiteBuilder*.rpm --force (yes, I had to force it, it'll tell you you have a newer version installed otherwise, a june version, when the version included is a march version, unless they've updated since I had my issues)...

then try to do what you were doing before...
 
Back
Top