my hosting provider is relaxing some permissions relating includes, file writing permissions, etc.
Y also have executed the infamous âfix-permissions.phpâ script in order to correct some permission issues and finally I will perform a new repair and rebuild.
so far, I can asert that browser cache has nothing to do with this. Maybe sugarâs remote one could. I will enable developer mode if necessary.
Same problem here with Add Dashbord Page
No problem to add Dashlet.
fresh 7.1.1
local Windows 7 + PHP 5.3.8 + apache 2
form for adding page appear OK,
after submit (if ânot clearâ FireBug log option) - see in red POST SUGAR_ROOT_FOLDER/index.php?module=Home&action=AddDashboardPages
after that home page is refreshing and no added Page⌠- just âSuite Dashboardâ tab
Hello Will,
Yes. Actually testing on few PC which are on LAN but same problem.
At the time of installation i had notice like: Invalid argument supplied for foreach() in D:\xampp\htdocs\wms-crm\modules\AOR_Reports\AOR_Report.php
and also had below notice once after installation:
Notice: Undefined variable: dashletData in DashletGeneric.php on line 304
I hope above notice has nothing to do with dashlet error
well, I have tested with two different installations of suitecrm and yes, the problem is with the browsers.
internet explorer is totally able to add tabs and widgets, while firefox and chrome donât
Problem with add tap and add dashlets is related to the response time and js order execution, I only faced the problem when accessing SuiteCRM thru a VPN.
To fix the isseu I have inclued the following code lines on custom/Home/AddDashboardPages.php after line 89:
Dear mikebruns99 and mjpires,
Thank you for addressing the issue. Yes Mike, somehow it appears client issue but earlier version was smooth for adding dashlet. I even found work around that if i use chrome and first add dummy tab and then try to add dashlet to main tab then it works.
Dr Mjpires, thank you for taking efforts and also attaching file. I replaced file and appended code as you mentioned but in my case it did not solve the problem so now going with above solutions i have mentioned. :cheer:
Regards,
Harsh Patel
seems that some js code is prone to load failure, load order failure or something like that, depending on browsers and net conditions.
recent changes in last version of suitecrm triggered this issue.
well, so why donât we take a look to the git commits of last release, so we know what has changed and we find something to trace?