Sugar Community Edition 5.2 Documentation
Sugar Community Edition Release Notes
Version 5.2.0h
Fixed Bugs in 5.2.0f
If you associate two or more target lists with a newsletter campaign, subscriptions to the newsletter are not applied correctly.
When importing data that includes a custom Flex Relate field, the system displays an “Undefined Index” warning during the import process.
The string ‘Please Select’ is hard-coded in two locations in the Selector.php file instead of calling a label from a corresponding language file to allow for localization.
When importing records with qualified fields, field values beginning with multi-byte characters are truncated.
Search returns incorrect results if you use a relationship within the same module as a search filter.
The Bug Tracker dashlet displays values for the Priority drop-down list as P1, P2, and P3 instead of Urgent, High and Medium.
In a Newsletter Campaign, users can view all newsletters even if they are not members of the team assigned to the campaign.
Sugar does not display a warning if you delete an email template that is used in an active email campaign.
When you select a field containing a Checkbox value as a search filter, Sugar does not retain the value after returning the search results.
When you create an Alert email template with a non-English language pack, Sugar displays the module name in English.
When you use single quotes or double quotes to perform a global search by full name, the system treats the full name as a last name and returns too many results.
When you attempt to apply an email template to a blank outbound email containing an attached file, Sugar deletes the attachment.
When using a non-English language pack, if you add a new IFrame or Link field in Studio, the “Generate URL” string is not translated.
Apache Web Server users can delete dashlets from the Home page even if the administrator has locked the Home page to prevent such actions.
When you add a custom Checkbox field to a module’s layout in Studio, Sugar does not update existing records with the new field. Hence, searching for records using the new field as a filter produces incomplete search results because only records that were created after the new field was added to the layout are displayed.
If a lead and a contact have the same email address, only the contact’s address is populated in email templates.
Apache Web Server users can circumvent patterns that the .htaccess file uses to prevent access to protected files.
When you add the “Member of” field to the Accounts List View to view parent-child relationships, the List View reverses such relationships and displays the parent account as the child account.
Copyright 2004-2009 SugarCRM Inc.
Community Edition License


| 






