Hello again,
I am thoroughly impressed with the progress Iâve made with SuiteCRMâs implementation within my company, but there is one bug in particular that is totally confusing me.
The problem is this: After logging in, and redirecting to the dashboard, the page is entirely white. Refreshing the page will properly load everything. Hereâs what Iâve found:
- This does not apply to âSystem Administratorâ users. However, a regular user with all roles still has this problem.
- This applies to both LDAP and standard users.
- Firebug for Firefox reports a â500 Internal Server Errorâ after login, but otherwise displays nothing else. After a refresh, that message is gone.
- Inspection of the source using Chromeâs âInspectâ feature shows that a lot of Javascript does not appear to load after login. After a refresh, much more code loads.
- Disabling âActivity Streamsâ globally will completely fix the issue.
- Inspection of âSugarCRM.logâ seems to show that SecuritySuite is not firing properly at the first login. I see absolutely no references to this plugin until after I refresh the page.
- Changing the default module after login does not have any problems. Security is properly applied.
- My web server (IIS) is not reporting any strange issues. If I turn on PHP debugging, nothing is displayed on this white page.
Any ideas about what else I can try? The dashboard is one of the most important features of SuiteCRM, Iâd hate to not be able to load it automatically for users upon login. I have attached a copy of my SugarCRM.log file, Debug-level, including the first login and one refresh.
Thanks for any help.
Same issue here. Not sure what to look for. Disabling the Activity Stream is not really a workaround, since it is a useful functionalityâŚ
Seems to be related to the twitter connector, even having it disabled. With display errors to âonâ I get the message
Fatal error: Cannot redeclare class OAuthToken in custom\include\social\twitter\twitter_auth\twitteroauth\OAuth.php on line 27
I do not need this connector, so I tried renaming that function to OAuthtoken2 and it seemed to do the trick.
So, in line 27 change
class OAuthToken {
to
class OAuthToken2 {
Obviously, this is not a solution, but a workaround. Someone more knowledgeable should find the true fixâŚ
1 Like
Thank you! That worked for me.
Given that itâs in the custom folder, too, hopefully this will persist through upgrades.
Well, although it is in the custom folder, I believe it is there because it is an addition to the default sugarcrm, but it is a core to the suitecrm package, so I guess it will not persist through updates.
Anyway, I do not know it it is related but I was experiencing very slow login times. This perfomance problem was only perceived at login and not through the normal operation of the application. Our server does not have direct access to the internet. Increasing the logs up to debug level, we were able to identify an aprox 1 minute gap just after SELECT * FROM config
where name = âmodule_twitterâ and value = 1;
We guessed there might be some code that tried to access the internet, so we went to the table âconfigâ and we set the value of the âmodule_twitterâ entry to 0. That worked like a charm and the login performance issues were gone. Since we do not use that connector, hopefully it will not have any side-effectsâŚ