I upgraded to 7.2.1 and since then I canāt get to the email screen. I get the top menu and thatās it.
When I click on an accountās email address I get a pop up saying āundefinedā.
I have tried to reset the permissions on /cache/jsLanguage/en_us.js to 777 but that did nothing.
There HAS to be a fix for this.
Anyone?
Please?
This sounds like permissions.
You would need to update all files in the instance and update the config.php dir section also. there are a number of posts on the forum which explains how this is done and what to set them to.
if that doesnt fix it then be worth looking at the sugarcrm.log and the error log for the server to find out what is causing the issue you are seeing.
Ian.
Yes it was permissionsā¦ but it was on two obscure filesā¦ see:
https://suitecrm.com/forum/bug-tracker/2478-undefined-message-on-pop-up?start=15#17898
I also trashed the .htaccess file and let Suite write me a new one via the Repair module.
There are more problems with permissions and .htaccess on this board and with Suite than anything else. The Suite developers would be well-advised to put these issues as their number one priority and fix this part of the system before making any other changes or additions.
There was a time yesterday when I thought to myself āLooks like Suite is just a ākludgeā of Sugarā¦ and neither of the systems really fit together. I canāt deal with this mess every time there is an updateā¦ maybe itās time to scrap it all and go to a brand new āmodernā codebase like X2 Engine or pay for Salesforce or some other CRM.ā
I really came close yesterday to leaving seven years of Sugar and about two years of Suite and moving on. But Iām glad I figured this out (with help from the community) and I hope that financial support for Suite will grow so as to enable SalesAgility to afford to bring in more developers and āhelperā resourcesā¦ but seeing the dismal results of the recent Kickstart campaign, I have some doubts.
Hi,
There is alot of permissions issues but these can normally be over come by just resetting the permissions for the full instance to what the default is ment to be. as long as you have set up the permissions correctly and updated the config.php file to contain these then when a repair and rebuild is requested the issue should not re-appear and you shouldnt have this problem.
most of the problems which are seen by users the permissions have not been set correctly in the config file so when the system does a repair and rebuild the files it updates/creates then has different perrmissions which then makes all these problems appear.
Im glad you have got this sorted at your end. 
Ian.
There is a lot of confusion about what should be coded in the config file. Can you tell us what you recommend.
(And one of the reasons for confusion is that Sugar used octal for ādirā and āfileā mode.)
array (
'dir_mode' => 1528,
'file_mode' => 432,
'user' => '',
'group' => '',
),Agreed that this can be improved on. however it partly depends on the server set up. the following is what we have been recommending
array (
ādir_modeā => 1517,
āfile_modeā => 420,
āuserā => āā,
āgroupā => āā,
),
Ian.
This may be of assistance to some folks:
I donāt know why Suite suggests different values but there must be a reason. Anyway, I use the Sugar recommendationsā¦ but maybe I shouldnāt? (Itās working now so Iām not messing with it!!)