Sugar 5.0.0 Patch C - shipped on April 10, 2008

[clint]

Sugar 5.0.0 patch B has been out now for about two weeks. Our next 5.0.0 patch release is codenamed Colombia.

Assuming nothing happens that causes us to immediately release a patch (such as a reported security vulernability), the 5.0.0 Colombia patch will be released as patch C.

You can review all bugs that have been assigned to the 5.0.0 Colombia patch here.

As of March 4th, we have 170 bugs targeted for being fixed in the 5.0.0.Colombia patch. That's just about a full load. We likely will not add any more bug fixes to this patch and may in fact need to defer some out.

So what are the most critical bugs in your mind that must be fixed in the 5.0.0 Colombia patch release?

------------
Update on Patch C Plans - 14 March

Due to the fact that there are some more urgent bugs that need to be addressed in the near term, we are pulling out the top 20 bugs from the 5.0.0 Columbia patch release and creating the 5.0.0 Chile patch release. The Chile release will be 5.0.0c and Colombia will most likely be 5.0.0d.

Chile is targeted for release in mid April. We haven't set a new date for Colombia, but it will likely be around July.

You can see the list of bugs planned to be fixed in the 5.0.0 Chile release here.

[dpatech]

I think bug 19924 is pretty critical. This bug was introduced in version 5.0b and makes it nearly impossible to uninstall custom modules cleanly.

http://www.sugarcrm.com/crm/?option=...7-47bad68b380a

The new option on the Admin -> Repiar-> Clear Vardefs Data Cache to "Clear All Cache Files" erases the custom module zip files and manifest files in cache/upload/upgrades/module thereby making it impossible to uninstall any custom modules.

[clint]

Here is my list of bugs which I have passed on to the dev team as "must-fixes" for 5.0.0.

• 19444 - Studio Customisation in any non-english language
• 18988 - Cannot Filter Leads Reports by Account Name
• 19888 - Account name does not show up when creating Alert template for Leads
• 19116 - remove account_name from the leads module and retrieve based on the id
• 19293 - Global Search Does Not Query leads.account_name
• 19529 - Custom relate field always a required field
• 19373 - Tab order not saved

[lougaou]

Any idea about the release date?

[DragonflyMaster]

Here is my list of bugs which I have passed on to the dev team as "must-fixes" for 5.0.0.

• 19444 - Studio Customisation in any non-english language
• 18988 - Cannot Filter Leads Reports by Account Name
• 19888 - Account name does not show up when creating Alert template for Leads
• 19116 - remove account_name from the leads module and retrieve based on the id
• 19293 - Global Search Does Not Query leads.account_name
• 19529 - Custom relate field always a required field
• 19373 - Tab order not saved

Hi Clint,
here is my list:

• 19444 - Studio Customisation in any non-english language
• 19884 - Unable to Edit Drop Downs in Other Language
• 19912 - New drop down list set not saved when created through module builder
• 19924 - Admin Repair function break Module Uninstall

I guess the first and the second bugs are pretty much the same, and the third is something very close to that.
I've found the fourth pretty annoying too.
Nevertheless, may I say you guys are doing a damn good job?

[svaish]

For and I think I speak for many, the campaign module has too many bugs. Fixing these bugs will help us use the campaign module more efficiently.

Thanks Sach

[clint]

For and I think I speak for many, the campaign module has too many bugs. Fixing these bugs will help us use the campaign module more efficiently.

Specific bug numbers?

[seanAUS]

I think that the following bugs need inclusion in Columbia - the first one especially as it is blocking key functionality:

18773 -

** I tried using the relate field to relate a custom field to Contacts and got this error:
-------------------------------------------------
Notice: Undefined index: inv_invoice in X:xxxxxxxxxxxxxxxxxincludeSubPanelSubPanelDef initions.php on line 429

Warning: aSubPanel::require(modules//metadata/subpanels/.php) [function.aSubPanel-require]: failed to open stream: No such file or directory in X:xxxxxxxxxxxxxxxxxincludeSubPanelSubPanelDefiniti ons.php on line 87

Fatal error: aSubPanel::require() [function.require]: Failed opening required 'modules//metadata/subpanels/.php' (include_path='X:xxxxxxxxxxxxxxxxxinclude/..;.;Chp5pear') in X:xxxxxxxxxxxxxxxxxincludeSubPanelSubPanelDefiniti ons.php on line 87

and

19118 -

Scenario: Clean install of 5.0 no other data.

- Create Lead "Bing Lee"
- Change Global and Local date format to: dd/mm/YYYY and time to hh:mm am/pm
- Go to lead - create a call in activities
- Create Contact of same name to cause conflict
- Convert Lead
- Select existing contact
- Error
----------------------------------------------------------------------------
Leads: Convert Lead

Query Failed:INSERT into calls set id='6ec41fef-db19-70ca-a8c9-4782bbbce2e9', name='Bingy Baby', date_entered='08/01/2008 10:53am', date_modified='2008-01-07 23:55:38', modified_user_id='1', created_by='1', description=null, deleted='0', assigned_user_id='1', duration_hours=0, duration_minutes=15, date_start='2008-01-23 00:00:00', date_end='2008-01-23', parent_type='Contacts', status='Planned', direction='Outbound', parent_id='5b0416fe-6763-320d-cb6b-4782bb63d84c', reminder_time=-1, outlook_id=null::MySQL error 1292: Incorrect datetime value: '08/01/2008 10:53am' for column 'date_entered' at row 1
-------------------------------------------------------------------------------------
- Change date format to YYYY/mm/dd and repeat - OK!

[marcstedman]

When should we expect the patch to go out? I am very interested in bug that prevents the global search to query accounts in the leads table. Also, I had a question about the global search. It looks like there is some sort of wildcard implementation bu only after the search term, ie: mysearchterm% and not before and after: %mysearchterm%. So if you're looking for an account named "the best business", you will get a match if you type: "the best" and not "best buisness"

Is this normal?

Also, I don't understand how the account name relates in a Lead. If you go to the Advanced search in Leads, you get to select accounts from the "accounts" table. This would mean the account a lead is associated with comes from this table. But in the Leads creation page, the account name is just a freeform field, meaning it must not be associated with the accounts table. Any clarification on how the account name in a lead work?

Thanks.

[chuangk]

Sugar 5.0.0 patch B has been out now for about two weeks. Our next 5.0.0 patch release is codenamed Colombia.

Assuming nothing happens that causes us to immediately release a patch (such as a reported security vulernability), the 5.0.0 Colombia patch will be released as patch C.

You can review all bugs that have been assigned to the 5.0.0 Colombia patch here.

As of March 4th, we have 170 bugs targeted for being fixed in the 5.0.0.Colombia patch. That's just about a full load. We likely will not add any more bug fixes to this patch and may in fact need to defer some out.

So what are the most critical bugs in your mind that must be fixed in the 5.0.0 Colombia patch release?

Hi Clint, do you know when a fix for bug 18802 (Add Account functionality not working in Opportunities QuickCreate pop-up) will be available? It was entered back in December. Thanks!