- Plesk 12.5 for Linux
- Plesk 12.5 for Windows
Plesk is pleased to introduce the new Micro-Update #39 for the 12.5.30 version of Plesk.
The 12.5.30 MU#39 update is recommended for all Plesk users and includes general functionality fixes that improve the stability, compatibility, and security of your Plesk server.
To ensure optimal server reliability and security, we strongly recommend keeping your operating system and Plesk software up-to-date.
[*] PHP 5.5 was updated to version 5.5.37.
[*] PHP 5.6 was updated to version 5.6.23.
[*] PHP 7.0 was updated to version 7.0.8.
The following issues were resolved:
[-] (on Windows) Using the init_conf.exe utility with the -hostname-not-required option resulted in an error (PPPM-4643).
[-] (on Windows) When creating a subscription based on a service plan with the disk space quota of 1 MB, physical hosting could not be created if the subscription name was longer than 16 symbols (PPPM-4648).
[+] Microsoft SQL database migration improvements: now the dump of the source server is created by means of Microsoft SQL and the interaction with the database server is performed from the source server, thus solving the problem of connection from the remote servers.
[+] Improvements of mail content migration on Windows: copying of mail content is now faster, the content is synchronized during the repeated migration so that only new emails are copied.
[+] Migration of subscription permissions on Windows was optimized for better performance in case of large amount of directories.
[+] Hosting description samples were added to the Plesk Migrator extension. (PMT-2732)Plesk Migrator user interface could become unavailable in case of problems of migration session directory. (PMT-2953)
[-] Migration failed if a subscription contained additional users with passwords in wrong Base64 encoding. (PMT-2933)
[-] Confusing error messages were displayed after removing of the Plesk Migrator extension (PMT-2912)
[-] Migration of Microsoft SQL database failed in case when Microsoft SQL server was running under a custom user. (PMT-2888)
[-] Migration from Confixx was blocked in case when some binary data was present in database fields on the source server. (PMT-2884)
[-] Error reporting was unclear in case of Plesk migration for some non-English Windows localizations. (PMT-2877)
[-] Migration from custom hosting: Post-migration checks were applied for all subscriptions and not only for those that were selected for migration. (PMT-2876)
[-] The check-infrastructure command in CLI failed if it was run before the check command. (PMT-2874)
[-] After migration from Plesk on Windows some temporary data remained on the source server. (PMT-2873)
[-] If business model for a domain was not converted after upgrade from Plesk 9.5 to Plesk 10.1 on a source server, such a domain was not included into a migration list. (PMT-2867)
[-] Migration from custom hosting: Plesk Migrator tried to add the “www” prefix to a domain with wildcard in name when this option was not allowed by Plesk. (PMT-2865)
[-] In case database is switched from source to target without actual data transfer (DB assimilation), no any messages about this were included into the info.log file during migration. (PMT-2860)
[-] In some cases additional users of subscription could get wrong email address after migration. (PMT-2859)
[-] Migration on Linux failed if the “root” user’s home directory pointed not to /root. (PMT-2856)
[-] Migration from Confixx failed if a domain contained several subdomains with forwarding from one to another by chain. (PMT-2852)
[-] Migration list generation is blocked if a subscription is associated with absent add-on service plan or if add-on service plan belongs to another owner. (PMT-2837)
[-] Migration failed for a subscription with dublicated DNS records. (PMT-2829)
[-] Migration of a protected directory from Confixx failed if the directory name contained spaces (PMT-2826)
[-] Every next call of the dump agent cleared the logs of a previous call of dump agent in the migration session directory. (PMT-2822)
[-] In case DNS service was turned off on the source server Plesk Migrator still verified if it is enabled on the target server. (PMT-2821)
[-] Migration on Windows failed if the Windows dump agent output contained some garbage caused by third-party DLLs. (PMT-2799)
[-] Migration on Windows failed when IPv6 was used for connection to a target Plesk server. (PMT-2794)
[+] - Added
[-] - Fixed
[*] - Improved