After successfully upgrading from 7.7.9 to 7.8.1 - when trying to search for âaccountsâ or âleadsâ or âopportunitiesâ or âcontactsâ using the drop down menus I got a message that said
An error has occurred:
There was an error processing your request, please try again at a later time. If the error persist, please have your administrator disable Ajax for this module.
So, I disabled Ajax - no help. Now I an unable to enable Ajax. Now when I try to search I get a blank page.
Sorry, we thought we had reported the suite.crm log errors. We did do a hard refresh of the browser cache. We do have customized search view, just with two additional fields. Since we were unable to quickly fix we reverted back to 7.7.9. So, we wonât be able to provide any more useful information. We will wait for the next update and try that. Thanks,
^^^ That file is customised - to what extent I donât know. How I know this is because it is sitting in the custom directory. So there is obviously something in that which is making everything fail.
You will need to speak to the developer whom provided it to you.
If I could get you to go into a bit more detail. The only customization we did was to add some fields and re-arrange some fields in the Accounts, Contacts, and Opportunities modules. However, we have done no customization in years and yet we have been able to update using the wizard. Generally I update each time a new update is noted in the newsletter.
Is there any thing in particular we should be looking for? Any tests we could run to locate the source of the problem? Would removing the customization folder be a good test to see if that is the source of the problem?
The 7.8.x upgrades had a few changes made to how templates are rendered that perhaps is causing the issue with customised views.
From the logs you provided:
Uncaught Error: Call to undefined method ListViewSmarty::ListViewSmarty() in /var/www/html/blah/suitecrm/custom/modules/Accounts/AccountsListViewSmarty.php:8
Stack trace:
^^^ This file is NOT a core file i.e. it was added AFTER a vanilla install not by the system. Now this maybe a case of a very old instance you have upgraded over and over but I would still highly be unlikely as this file is not often in the custom directory until it was specifically changed to be so.
I understand that you say that you have only changed fields in the layouts, but that doesnât change the fact that the error is coming from that file.
What I suggest you do is compare that file to the core file inside of Accounts module to see the differences. If there are then you can try and deleting/renaming that file and allow the system just to use the core file.
My only warning here is that you will need to also check the following file:
I had the same problem, at first with Cases. A quick look at my PHP error log and subsequent code dive told me the override method CasesListViewSmarty in custom/modules/Cases/CasesListViewSmarty.php, was lacking any __construct() function.
Adding the following immediately after the opening bracket of the class definition (class CasesListViewSmarty extends ListViewSmarty) fixed this for me:
function __construct() {
parent::construct();
}
A little more investigation indicated the same is true in Projects, Accounts, Opportunities, Leads, Prospects, Meetings and Contacts. In the above suggestion, simply replace the word âCasesâ with each of these, add the __construct() function to each respective class and you should be good to go.