empty
| 
Sugar Community Edition 5.2 Documentation
Sugar Community Edition Release Notes
Version 5.2.0k
|
|
Introduction
This document describes the requirements, new features, enhancements, and known limitations in Sugar Community Edition 5.2.0k.
You can upgrade from Sugar versions 5.0.0x, and 5.1.0 to Sugar version 5.2.0k. All Sugar 5.1.0 plug-ins and extensions are compatible with Sugar 5.2.0k.
|
Note:
|
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.0k” to designate new bugs found in this release. You can also update existing bugs with additional information.
|
Note:
|
If you are running PHP 5.2.9, and you are upgrading from Sugar 5.2.0c or earlier versions, turn off PHP notices in php.ini before upgrading to Sugar 5.2.0k to ensure that the Upgrade Wizard does not fail. If you are planning to upgrade to PHP 5.2.9, it is recommended that you do so after you upgrade to Sugar 5.2.0k.
|
|
•
|
|
•
|
|
•
|
Before upgrading to 5.2.0, 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.0 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.
|
|
•
|
In order to better support multi-byte character storage with Microsoft SQL Server, you can configure Sugar to use FreeTDS driver. For more information, 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.
|
Connector to External Data Sources.
Sugar providesa connector to LinkedIn. Additional connectors to other data sources can be obtained and installed using Module Loader
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.
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.
When you create or edit a drop-down list, you can now sort items in ascending or descending order.
|
•
|
Due to a limitation of Apache 1.3x for Windows, Sugar cannot, for security purposes, restrict access to the sugarcrm.log file using the .htaccess file. It is strongly recommended that you use one of the following options to address this concern:
|
|
•
|
Move the log file out of the webroot, and add the following configuration setting to the config_override.php file specifying the new path to sugarcrm.log:
|
|
•
|
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\<modulename>\metadata\detailviewdefs.php and replace <name="vcard" action="vCard.php>"
<name="vcard" action="index.php">
|
•
|
If you had renamed module tabs prior to Sugar 5.2.0g, and then used the Silent Upgrader to upgrade to Sugar 5.2.0g, your changes will be lost during the upgrade. After upgrading to 5.2.0h, you will have to rename your module tabs again.
|
|
Sugar runs on any OS that runs PHP
|
||||
|
Red Hat 4.x, 5.x (Advanced Server, Enterprise Server)
|
|||
|
||||
|
||||
|
5.1.0 - 5.1.2, 5.1.4, 5.1.6, 5.2.1-5.2.6, 5.2.8 - 5.2.11
|
||||
|
||||
|
||||
|
Supports any version that runs PHP
|
||||
|
Supports any version that runs PHP
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Creating a web-to-lead with a redirect URL that points to a static page hosted on an IIS web server results in an error message when a campaign target attempts to submit the form.
Sugar does not correctly decode emails that contain “Content-transfer-encoding: quoted-printable” in the message header.
On the Outbound Email Queue Management page, you cannot view emails sent or attempted for a specific email marketing message of a newsletter campaign because Sugar displays records for all the marketing messages.
Alternate database configuration does not work with MS SQL if the main database and the alternate database are on the same host machine.
Solution: Specify different users for the two databases.
|
|
|
Copyright 2004-2009 SugarCRM Inc.
Community Edition License
