Odin is pleased to introduce the new Micro-Update #11 for the 12.5.30 version of Plesk.
The 12.5.30 MU#11 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, Odin strongly recommends keeping your operating system and PP software up-to-date.
The following issues were resolved:
[-] (On Linux) After upgrading from Plesk 12.0 to Plesk 12.5, webspaces with chrooted shell and one or more additional domains could not be renamed. (PPPM-3517)
[-] (On Linux) After adding a custom firewall rule allowing all connecntions from a particular IP address, connections from other sources to all services became blocked. (PPPM-3499)
[-] (On Linux) A confusing error message was displayed when upgrading Plesk from 11.0.9 to 12.5.30. (PPPM-3537)
[-] (On Linux) Changes to the mailbox size limit on the service plan level were not applied to existing mailboxes. (PPPM-3502)
[-] (On Windows) After Plesk cloning, the MailEnable servers list was not reset. (PPPM-3497)
[-] (On Windows) After the default PrivateTemp directory of Plesk was changed via the system registry to another directory, the temporary files were still generated in the original PrivateTemp directory. (PPPM-3524)
[-] The "-admin_info_not_required true" option of the "init_conf utility" did not not work. (PPPM-3529)
[-] When a PHP version 5.3 or later was used for a domain, the "allow_url_fopen" and "file_uploads" settings became unavailable. (PPPM-3459)
[-] The list of databases for a domain in the Active mode displayed only the first 25 databases. (PPPM-3498)
[-] Changes to the individual PHP handlers' php.ini files were not validated, which could lead to the handler becoming inoperable. (PPPM-3510)
[-] For domains created in Power User view, the File Manager URL failed to open in the Classic List mode. (PPPM-3503)
[+] If a dump for some domain is invalid during migration, all correct domains will be imported and a clear error message will be reported for an invalid domain, explaining what is wrong with this dump.
[+] It is possible to customize the path for the "authorized_keys" file that is used by Plesk Migrator for automatic configuration of ssh between source and target servers by setting the AuthorizedKeysFile parameter in the "/etc/ssh/sshd_config" file.
[-] The instruction about manual installstion of transfer agent displayed in the log on Windows was missing a step about renaming the 'C:\panel_migrator\panel-transfer-agent\python\python.exe' file to 'C:\panel_migrator\panel-transfer-agent\python\panel-migrator-python.exe'. (PMT-2340)
[-] When a conflict between customer logins took place during migration, there was no clear error message explaining the reason of the conflict. (PMT-2337)
[-] After migration was completed, the hint near the Search button displayed variable names instead of text. (PMT-2333)
[-] Migration stopped if a domain with a domain alias was assigned as the default domain to some IP address. (PMT-2332)
[-] Migration failed if branding was configured on the source server. (PMT-2331)
[-] Migration from cPanel servers failed if there was a reseller on the source server owning both one or more domains and one or more customers. (PMT-2328)
[-] If there were an invalid XML data in the WebServerSettingsParameters table of Plesk database, generation of the source dump failed. (PMT-2325)
[-] Migration to Plesk without working DNS service was impossible. (PMT-2319)
[-] Migration from Plesk on Linux with mod_security enabled was impossible. (PMT-2318)
[-] When a domain on a source server was associated with several IPs of the same type, the migration list was not generated and an unclear error message was displayed. (PMT-2105)
[-] During migration from Plesk 9.x or earlier, domain administrator accounts created on the source server failed to migrate. (PMT-2073)
[+] - Added
[-] - Fixed
[*] - Improved