• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Updates

OK, but the link above is where the web-based updater downloads files. And that's the only file on that link that's marked the 27th, so that's got to be it :)

Look here for the FreeBSD 5.3 updater config file. This is what the updater reads to decide what is available. And as you can see (the lines with file= are the actual update file lists), there are 3 files in the list - the "core" Plesk 7.5.3 file, the hotfix from the other day, and now there is the sitebuilder update in that list.

-J
 
It's just a new build, could be anything changed but it's pretty much always a positive change. I wouldn't worry about it if your 7.5.3 is working, otherwise you might as well upgrade. It's probably one of the changes in the release notes which didn't work in the first build, so they published a second build which does incorporate the changes in the release notes.

Just speculating ... but if your server has bugs you might as well upgrade, if not, don't.
 
I have had a bad response since the last update, there is no way to make httpd to respond with the ioncube loaders.... it gave me a lot of errors.

I deactivated it, and works (httpd).

I will investigate further on my box to see what else is failing. and update here with the result and the solution (if find any LOL)

regards,
 
for CentOS 3.3+

Welp... for having CentOS 3.3 support it sure refused to run the autoinstaller from the control panel. *scratches head* Anyway, the easy way to deal with all this is to make sure you have CentOS completely updated then temporarily changing /etc/redhat-release to state:
"Redhat release 3 (Final)"

This will allow the automated updater to run properly. just change it back afterwards.
 
Back
Top