Version 6.0.1

Introduction

This document describes the requirements, new features, enhancements, and known limitations in Sugar Community Edition 6.0.1.

Please continue to provide feedback on this release as we continue to develop Sugar functionality. The SugarCRM Development Team is closely monitoring your feedback and is making every effort to fold it into upcoming releases.

For more information on a bug or to provide feedback, use the SugarCRM Bug Tracker which is accessible through http://bugs.sugarcrm.com. Check the Bug Tracker for known issues prior to submitting bugs. When creating a bug for a new issue, use “6.0.1” to designate new bugs found in this release. You can also update existing bugs with additional information.

Topics include:

•	Requirements

•	Upgrade Guidelines

•	Compatibility Matrix

•	Fixed Bugs in 6.0.1

Requirements

Requirements for 6.0.1 are as follows:

•	Increase the value of the memory_limit parameter in the php.ini file as follows:

•	MySQL Server: 96M or higher

•	MS SQL Server: 96M or higher

•	To install Sugar 6.0.1 successfully, ensure that the Multibyte String (mbstring) module is installed in your PHP libraries.

•	If you are using MySQL, install version 5.0 or higher to use with Sugar 6.0.1.

•	If you are using Microsoft Exchange, use versions 2000 and higher.

•	To successfully upload the Upgrade zip file, before upgrading, navigate to the php.ini file on your system and change the post_max_size and upload_max_filesize settings to at least 60MB. Restart Apache and then begin the upgrade process.

Upgrade Guidelines

You can upgrade from Sugar versions 5.5.x and 6.0 to Sugar 6.0.1. To upgrade from 5.5.1, 5.5.2, 5.5.3 and 5.5.4, use the same upgrade package: SugarCE-Upgrade-5.5.1-to-6.0.1.zip. To upgrade from 6.0.0, use SugarCE-Upgrade-6.0.0-to-6.0.1.zip

Note:

It is strongly recommended that you test 6.0.1 on a copy of your production system before you upgrade it.

Guidelines are as follows:

•	The process of upgrading can take up to an hour. If you are using the IIS Web server, you need to ensure that the CGI application does not time out. To do this, on IIS, set the CGI script timeout to more than 300 seconds, which is the default value.

•	If op-code caching is enabled in the PHP configuration file, you will need to disable it before upgrading your Sugar installation. You can enable it after the upgrade process is complete.

Compatibility Matrix

SUGAR BUILDING BLOCKS	SUPPORTED VERSIONS	COMMENTS
PLATFORMS		Sugar runs on any OS that runs PHP
• Linux	Red Hat 4.x, 5.x (Advanced Server, Enterprise Server) Oracle Enterprise Linux 5.1 CentOS 4.x, 5.x
• Windows	Windows 7, XP, 2003, 2008, and Vista
• Mac	OS X
PHP
PHP	5.2.1- 5.2.6, 5.2.8 - 5.2.13, 5.3.0-5.3.3	The PHP setting, MBstring.func_overload =7 is supported
DATABASES
• MYSQL	5.0x, 5.1	Strict mode is supported for MYSQL
• MS  SQL Server	2005, 2008
WEB SERVERS
•    Apache	1.3x, 2.0x, 2.2x	Supports any version that runs PHP
•    IIS	6.0, 7.0
MAIL SERVERS • Exchange
• QMail
• GMail
• Yahoo
• Client (Browser)	Firefox 2.0, 3.0, 3.5, 3.6 IE 7.0, 8.0 Safari 4.0
MULTIMEDIA
• Adobe Flash	7.0 and above
RECOMMENDED STACKS
Linux Stack
• PHP version	5.2.8
• Apache	2.0.63, 2.2.4
• RedHat Enterprise	Workstation 4
Preferred Databases
MySQL	5.1
SQL Server	2005
Windows Stack
• Windows	2003
• PHP version	5.2.8
• IIS	6.0
Preferred Databases
MySQL	5.1
SQL Server	2005

Fixed Bugs in 6.0.1

Bug 25256

The value used for the “Reply-to” field in an email campaign is the one entered for the “From” field of the email instead of the value specified in the Campaign Wizard.

Bug 37241

Account name is null in imported opportunity records.

Bug 37663

Merging duplicate records strips down carriage returns from the address field.

Bug 37883

Sugar API deactivates sessions when a request contains multiple IP addresses.

Bug 38109

Datetime fields in Studio ignore user's time format preference.

Bug 38381

Users cannot define Thousands Separator in the User Login Wizard.

Bug 38488

When using MySQL version 5.0x, a SQL error prevents subpanels from displaying in a record’s Detail View.

Bug 38504

When a user is logged out of Sugar due to session timeout, Sugar does not display a timeout notification.

Bug 38563

Field names are truncated in the Detail View of custom modules.

Bug 38569

If a language pack is installed, upgrading to Sugar 6.0 results in breaking the Home page tab.

Bug 38597

The Mass Update panel in no longer available on the Email Queue page.

Bug 38652

The History sub-panel does not display the full contact name.

Bug 38679

Clicking on Global Search popup window’s scroll bar causes Search window to move.

Bug 38721

Custom Date fields regress to previous day when records are saved.

Bug 38841

Attempts to import account records fails with a fatal error message.

Bug 38990

SOAP commands that do not contain parameters fail to run successfully.

Bug 39059

The Silent Upgrader does not run successfully if you are using a custom viewdefs.php file that is not well formatted.