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

Plesk 7.5 Reloaded and MySQL 4.1

Re: MySQL 4.1 Upgrade for Plesk

If you are running osCommerce, then you have real problem, since osCommerce yet doesnt support 4.1.xx.
[/B]

This is so untrue. Please don't distribute this false information in order to promote your business. I'm currently running the included osCommerce with MySQL v4.1.12 on Plesk 7.5.4 and RHEL3.

If someone needs to run osCommerce on MYSLQ v4.1.1 or higher, there is a very easy way to do it. Just add old_password on the my.cnf file and restart mysql.

-D
 
Re: Re: MySQL 4.1 Upgrade for Plesk

Originally posted by dennysp
This is so untrue. Please don't distribute this false information in order to promote your business. I'm currently running the included osCommerce with MySQL v4.1.12 on Plesk 7.5.4 and RHEL3.

If someone needs to run osCommerce on MYSLQ v4.1.1 or higher, there is a very easy way to do it. Just add old_password on the my.cnf file and restart mysql.

-D

can the migration be painful ? any chances to break my databases ?

what is that old_password thingy ?
 
There's always a CHANCE it can break, so make a backup first. The old_password thing is just a compatability feature that allows MySQL3-style authentication for scripts, required for osCommerce I believe.

Out of interest, have you noticed any problems with any scripts on MySQL4.1, or are they quite happy with old_password switched on?
 
Back
Top