Can't navigate to Opportunities List View

[rickcrites]

Whenever I click the Opportunities Tab, or try to navigate to the Opportunities List View from any supanel, I get this message:

Fatal error: Call to a member function encode() on a non-object in /home/elgrep5/public_html/sugar45d/modules/Opportunities/OpportunityFormBase.php on line 394

It has worked previously. I don't know when it stopped working. I have an opportunity listed that should show in the home page dashlet, but doesn't.

Can anyone shed any light on this for me?

Thanks.

[rickcrites]

Whenever I click the Opportunities Tab, or try to navigate to the Opportunities List View from any supanel, I get this message:



It has worked previously. I don't know when it stopped working. I have an opportunity listed that should show in the home page dashlet, but doesn't.

Can anyone shed any light on this for me?

Thanks.

For the benefit of anyone else that might have the same problem, I find I can "solve" this problem by commenting out the following line in the OpportunityFormBase.php file:

//$quicksearch_js .= '<script type="text/javascript" language="javascript">sqs_objects = ' . $json->encode($sqs_objects) . '</script>';

But, I don't know yet what other problems or issues might result from removing this line. At least I can get to the Opportunities List View screen now.

Can anyone spot the error in the above line? I am running JSON 1.1.1, and this error did start appearing after I installed the JSON module. Encode is obviously a JSON command. Could it be just a syntax error or typo? Any help would be appreciated.

Best,

[chrisky]

For the benefit of anyone else that might have the same problem, I find I can "solve" this problem by commenting out the following line in the OpportunityFormBase.php file:

But, I don't know yet what other problems or issues might result from removing this line. At least I can get to the Opportunities List View screen now.

Can anyone spot the error in the above line? I am running JSON 1.1.1, and this error did start appearing after I installed the JSON module. Encode is obviously a JSON command. Could it be just a syntax error or typo? Any help would be appreciated.

Best,

Rick, the error in the line you of code you posted is the period before the equal sign,
remove that period as it should NOT be there, that is an syntaxual error.

[chrisky]

OMG

I just took a look at that file...

Wow!

And everyone wonders why Sugar's such broken with more bugs in each release..

That file & code examplifies what is apparently a problem inside the sugarTeam.

Any programmer will see what I mean, everything from the syntax errors, to the devlopers code (I can soo relate to that... referring to things like lines commented out throughout devloping and experimenting...)

A file with code like that should never be in a public release..

[rickcrites]

Rick, the error in the line you of code you posted is the period before the equal sign,
remove that period as it should NOT be there, that is an syntaxual error.

Thank you very much for your help with this.

There seems to be something else wrong with the line than just the period before the equal sign. I removed that and the exact same error still came up. Any other ideas? The error message says it is calling the function on a "non-object."

Any other ideas?

Thanks again.

[chrisky]

Thank you very much for your help with this.

There seems to be something else wrong with the line than just the period before the equal sign. I removed that and the exact same error still came up. Any other ideas? The error message says it is calling the function on a "non-object."

Any other ideas?

Thanks again.

Yep, I do have more ideas.. after having looked at the file for curiosity..
And it needs major help..

Just the mere line you referenced Rick, examplifies just how amazed I am and my opinion above..

$quicksearch_js = $qsd->getQSScripts();
$quicksearch_js .= '<script type="text/javascript" language="javascript">sqs_objects = ' . $json->encode($sqs_objects) . '</script>';

Any coder would see this and sratch their head, as the second would replace the quicksearch_js variable, thus the monkey head sratching....

Innnyyy, minnnnie, mineeeeeeee, moeeeeee

Which one is it? Is it either?

Between that and all the other problems in this file, combined together, amount to a "project" to say the least.

Sorry for the bad news Rick, but you're not going to get this working by yourself..

Sugarteam, maybe, maybe myself eventually, etc. will have to tackle that..
Frankly, it'd be quickest and easiest to follow by the Sugarteam with one or more of them having written it.
I have way better things to do than spend an eternity trying to familiarize myself with that code and how it opporates, in order to adequately being to modify and/or work with it.

[rickcrites]

Yep, I do have more ideas.. after having looked at the file for curiosity..
And it needs major help..

Just the mere line you referenced Rick, examplifies just how amazed I am and my opinion above..

$quicksearch_js = $qsd->getQSScripts();
$quicksearch_js .= '<script type="text/javascript" language="javascript">sqs_objects = ' . $json->encode($sqs_objects) . '</script>';

Any coder would see this and sratch their head, as the second would replace the quicksearch_js variable, thus the monkey head sratching....

Innnyyy, minnnnie, mineeeeeeee, moeeeeee

Which one is it? Is it either?

Between that and all the other problems in this file, combined together, amount to a "project" to say the least.

Sorry for the bad news Rick, but you're not going to get this working by yourself..

Sugarteam, maybe, maybe myself eventually, etc. will have to tackle that..
Frankly, it'd be quickest and easiest to follow by the Sugarteam with one or more of them having written it.
I have way better things to do than spend an eternity trying to familiarize myself with that code and how it opporates, in order to adequately being to modify and/or work with it.

OK. I get the picture.

I will just leave it commented out and file a bug report. Let's let Sugar sort it out when they get around to it. It seems to work OK without that line anyway (so far...).

I appreciate you looking into it.

[chrisky]

First, I was able to reproduce the problem...
That is, we had it too..

After working on that file, I believe that I've corrected it; however, only time will telll..
I'm also wise enough to assume the opposit, I know better than to think 'Sug' is fixed..
You just replace one problem with two new & different problems..

rofl though true..

I'm not gonna throw a copy of the file out there and add to the chaos of [possible] problems.
Espoecially considering that I really have no clue, let alone confident that it's all fixed and everything will work perfect..

But this is what I've gotten so far..

[rickcrites]

First, I was able to reproduce the problem...
That is, we had it too..

After working on that file, I believe that I've corrected it; however, only time will telll..
I'm also wise enough to assume the opposit, I know better than to think 'Sug' is fixed..
You just replace one problem with two new & different problems..

rofl though true..

I'm not gonna throw a copy of the file out there and add to the chaos of [possible] problems.
Espoecially considering that I really have no clue, let alone confident that it's all fixed and everything will work perfect..

But this is what I've gotten so far..

Thanks.

I have filed a BUG report.

Best,

[chrisky]

Bugger..

All links are correct and functioning (detail views of the account, the contact, the edit view of the opportunity, etc..) that are on each row of the listview.

I've got the select button working as well, but the create button is still broken and I'm done for now, moving onto other things on my todays list..

I just knew that it's never over till the fat monkey sings..