Please provide a patch for bug 9291

**Proware** · 2006-10-04, 11:39 PM

Please help! Help! HELP!

Bug #9291 is really causing us serious grief and making our Sugar system unusable.

We have 20 field agents who are screaming at us because of this bug!!

Can anyone or the Sugar team please Please PLEASE provide a patch for this bug urgently.

It is only marked as a Medium priority bug but it is HIGH HIGH HIGH priority for us.

**stevec** · 2006-10-05, 09:18 AM

I concur - just noticed it too - we cannot roll out 4.5 with this present. It also affects a contact's quickcreate for calls too.

The previous versions defaulted with the account set as the parent - with contacts being linked via the calls_contacts relationship. I'll see if I can track this down myself and I'll lean on our re-seller to push this too.

**stevec** · 2006-10-05, 09:30 AM

For info - in EditView.php - it seems that the default application string for the parent type that it should default to is being set as Accounts. However, it is being overridden by the variable "$_REQUEST['parent_type']" which could be getting set in the detail view or maybe the quickcreate script.

**stevec** · 2006-10-05, 10:15 AM

Hi,

I've got a fix for it - it's the form created for the quickcreate ajax form setting the parent type and id as the contact (via the return module definition). You can set this to be the account by setting it to the parent type and id proper.

Edit the two files:
modules/Calls/tpls/QuickCreate.tpl and
modules/Meetings/tpls/QuickCreate.tpl
and find the sections in both:

Code:

<input type="hidden" name="parent_id" value="{$REQUEST.return_id}">
<input type="hidden" name="parent_type" value="{$REQUEST.return_module}">

and replace with:

Code:

<input type="hidden" name="parent_id" value="{$REQUEST.parent_id}">
<input type="hidden" name="parent_type" value="{$REQUEST.parent_type}">

PLEASE TEST THIS!

By changing the definition for the Calls and Meetings quickcreate - it also effects creating calls and meetings against other possible types. E.g. creating calls against leads and bugs etc. I've tested against the situations we might use and it appears to work OK. HOWEVER, get it tested in your environment to make sure it doesn't set the parent incorrectly. If it does, then it might be simpler to set the two $_REQUEST variables within the appropriate EditView.php files within various conditions to make sure it only occurs when creating calls and meetings for contacts.

**Proware** · 2006-10-05, 12:12 PM

You are a true champion.

As we no longer use leads or targets or other modules since they do not work the way we want them to, working fine for contacts is fine for me!!

My team of sales representatives and demanding sales manager thank you over and over.

There is a god!!

**clint** · 2006-10-05, 08:52 PM

Looking in the bug tracker, I see that this bug is marked as fixed. I'm going to check with the engineer right now and see if his fix is more extensive than what SteveC posted. If so, I'll get a hot fix posted here in this thread.

Clint

**stevec** · 2006-10-09, 02:19 PM

Hi..
Good news and bad news.

The Sugar guys fixed bug 9291 for calls - the fix looks like the one I did + additional changes for a 'meridian' issue.

However, they forgot to do the same for meetings too.

Until that's addressed, you'll need to do the above patch by hand for the meetings quick create code.