Transcript
Sugar Community Edition Release Notes Version 5.2
Copyright Information
Sugar Community Edition Release Notes Version 5.2, 2008 Copyright © 2004-2008 SugarCRM Inc.
This document is subject to change without notice.
License This work is licensed under the Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 License (“License”). To view a copy of this license, visit http://www.creativecommons.org/licenses/by-nc-nd/3.0/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA.
Disclaimer Your Warranty, Limitations of liability and Indemnity are expressly stated in the License. Please refer to the License for the specific language governing these rights and limitations.
Trademarks All SugarCRM logos in this document are registered trademarks of SugarCRM Inc. See the SugarCRM trademark policies at http://www.sugarcrm.com/crm/open-source/trademark-information.html for more information on how SugarCRM trademarks can be used.
12/16/08
Introduction This document describes the requirements, new features, enhancements, and known limitations in Sugar Community Edition 5.2. You can upgrade from Sugar versions 5.0x, and 5.1 to Sugar version 5.2. The Sugar 5.1 plugins and extensions are compatible with Sugar 5.2. Note: It is strongly recommended that you make a copy of your production system and use it to test 5.2. Please continue providing feedback on this release as we continue to develop Sugar functionality for the upcoming releases. We will continue to work to incorporate your feedback into the development process. 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 Portal which is accessible through http://bugs.sugarcrm.com. Use “5.2.0” to designate new bugs found in this release. You can also update existing bugs with additional information. Check the Bug Portal for known issues prior to submitting bugs. Topics include: z
“Requirements for 5.2” on page 1
z
“New and Enhanced Features” on page 2
z
“Compatibility Matrix” on page 4
z
“Known Issues” on page 5
Requirements for 5.2 Requirements for 5.2 are as follows: z
z
Increase the value of the memory_limit parameter in the php.ini file as follows: |
MySQL Server: 40M or higher
|
MS SQL Server: 40M or higher
To install Sugar 5.2 successfully, ensure that the MB String module is installed in your PHP libraries.
z
If you are using MySQL, you must install version 4.1.2 or higher to use with Sugar 5.2.
z
For Microsoft Exchange, Sugar supports only versions 2000 and higher.
z
z
z
Before upgrading to 5.2, navigate to the php.ini file on your system and change the post_max_size and upload_max_filesize settings to more than 20MB. Restart Apache and then begin the upgrade process. The process of upgrading to 5.2 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. In order to better support multi-byte character storage with Microsoft SQL Server, You can configure Sugar to use FreeTDS driver. see “Installation Prerequisites and Guidelines” in the Sugar Community Edition Installation and Administration Guide. The supporting files are in a zip file, sugarcrm-MB-mssql.zip at http://www.sugarforge.org/frs/
?group_id=6.
New and Enhanced Features Sugar 5.2 offers the following new and enhanced features. Connectors to External Data Sources Sugar provides a connector to LinkedIn. Additional connectors to other data sources can be obtained and installed using Module Loader. Sugar Feed Sugar Feed enables users to be informed as soon as a user creates a new contact, lead, opportunity, or case. Users can add a My Sugar Feed dashlet on their Home page so that when a user performs any of these actions, a message displays in the dashlet on their Home page. Users can also be notified when a lead is converted, when a case is closed, and when an opportunity is closed. Additionally, users can post status updates, external links, images, and YouTube videos for other users to view within the dashlet. My Portal Dashlet Sugar provides a My Portal dashlet that presents product information and news about SugarCRM on your Home page. You can add additional My Portal dashlets to view information from external web sites and applications directly within your Sugar instance.
Enhanced Features When you create or edit a drop-down list, you can now sort the items in ascending or descending order.
2
Sugar Community Edition Release Notes - 5.2
Compatibility Matrix
Compatibility Matrix SUGAR BUILDING BLOCKS PLATFORMS z
Linux
SUPPORTED VERSIONS Red Hat 4.x, 5.x (Advanced Server, Enterprise Server)
COMMENTS Sugar runs on any OS that runs PHP
Oracle Enterprise Linux 5.1 z
Windows
CentOS 4.x, 5.x XP, 2003, Vista
z
Mac
OS X
PHP PHP (MYSQL, SQL Server) DATABASES z MYSQL z MS SQL Server WEB SERVERS z Apache z
IIS
5.1.0 - 5.1.2, 5.1.4, 5.1.6, 5.2.0-5.2.6 4.1.2x, 5.0x 2005 1.3x, 2.0x, 2.2x 5.1, 6.0, 7.0
SUGAR PLUG-INS z
z
z
z
z
Sugar Plug-In for Microsoft Outlook Sugar Plug-In for Thunderbird
Outlook 2003, 2007
Sugar Plug-in for Microsoft Word Sugar Plug-in for Microsoft Excel 5.1 Client (Browser)
Word 2003, 2007, XP
Supports any version that runs PHP Supports any version that runs PHP
Thunderbird 1.5, 2.0
Excel 2007 Firefox 2.0 and 3.0 IE 6.0 and 7.0
MULTIMEDIA z Adobe Flash
Safari 3.0 7 and above
Recommended Stacks Linux Stack z PHP version z Apache z RedHat Enterprise Preferred Databases MySQL SQL Server Windows Stack z Windows z PHP version
Sugar Community Edition Release Notes - 5.2
5.2.6 2.0.59, 2.2.3 Workstation 4 5.0.41 2005 2003 5.2.6
3
z
IIS Preferred Databases MySQL SQL Server
6.0 5.0.41 2005
Notes: 1.
Stict mode is supported for MYSQL.
2.
The PHP setting, MBstring.func_overload =7 is supported.
Known Issues Bug 26820 After upgrading to Sugar 5.2, the “Task ID” and “Duration” fields no longer display in the Project Task Detail View.
Known Limitations z
In the Module Loader, when you install a custom module that you exported as well as published, the “Uninstall” and “Disable” buttons do not display in the published module after the exported module is installed. Therefore, it is recommended that developers publish modules on a different Sugar instance instead of the development instance.
z
Some entry points were changed in Sugar 5.1. Hence, a custom file created in 5.0, unless you manually updated it with the new entry point in 5.1, may fail in 5.2 with the error message “Not a valid entry point”. For example, if you have customized vCard, navigate to custom\modules\ \metadata\detailviewdefs.php and replace
