Sugar Open Source Release Notes Version 4.5.1j

Known Limitations

•	The “Install from Sugar” option in the Module Loader has been removed.

•	On MYSQL, the upgrade process will change the data types of three columns (Description, Description_HTML, and Raw_Source) in the Emails table. Therefore, depending on the size of your Email table and the abilities of your database server the upgrade may take longer than usual.

•	If you share a MySQL database user name between two instances of Sugar applications where one is a pre-4.5.1 Beta version and another is a 4.5.1 Beta version, you may run into periodic collation errors. An example error is:

MySQL error 1267: Illegal mix of collations (utf8_general_ci,COERCIBLE) and (latin1_swedish_ci,IMPLICIT) for operation...

This is caused by sharing of connections between two applications using different collations. Release 4.5.x uses UTF-8 encoding and collation, while prior releases used the default setting.

To correct this problem, please use different user names for accessing the MySQL databases. This is a general issue, therefore the interference could also happen between the Sugar application and another application.

•	If you have created an index in MySQL database with key length of more than 333 characters, the upgrade to Sugar 4.5 will cause an error during the database character set conversion. MySQL displays the following error message:

“Specified key was too long; max key length is 1000 bytes”

This is a MySQL limitation. The 333 characters limit is for the combined length of all fields you specified as key for the index.

You must drop the index and recreate it so the index uses fewer characters from the columns. Internally, MySQL accounts 3 bytes for each character during the UTF-8 conversion.

•

After you upgrade the Upgrade Wizard, the system directs the user to the value specified for the Site URL parameter in the config.php file. Therefore, ensure that this value is set to your test instance instead of your production instance before you begin upgrading the Upgrade Wizard. This will prevent inadvertent changes to your production instance.

•

If you have created an index in MySQL database with key length of more than 333 characters, the upgrade to Sugar 4.5 will have an error during the database character set conversion. The error message “Specified key was too long; max key length is 1000 bytes” comes from MySQL and is a MySQL limitation. The 333 characters limit is for the combined length of all fields you specified as key for the index. You must drop the index and recreate it with fewer characters. Internally MySQL accounts 3 bytes for each character during the UTF-8 conversion.

•	Automated upgrading is not supported for the SugarPortal and for the Forums module. To upgrade, you will need to manually unzip the files and replace the existing files on the system with the new files.