What a mess. In all the years of using Suite Iāve never had an upgrade so totally break a site. I donāt think the CSS file is being loaded. Nothing looks right.
Look at the attached screen shot.
Iāve tried rebuilding and repairing everything⦠no luck.
Javascript does not work.
Canāt get 7.9 theme back.
Does anyone have any ideas what to do?
I saved my previous database dump file. Can I get it to run with a new 7.9 install? How would I do that?
I donāt understand about the cron jobs, but I agree with you in principle. Iāve never had an update to SuiteCRM change permissions. However, this major update did. I logged in via FTP and SSH and saw them myself. Thus, I can only assume that the update has some code in it that issues a āchmodā command for certain files. Given my history of never having a broken update since 2014 when I started with Suite (converting from Sugar) until this update which for sure broke the site (you saw the pix) I can only conclude that it was the update code that did it. I donāt have a better answer.
It would be interesting to āgrepā for a āchmodā line of code in the update files but I donāt have the time to devote to it.
Has anyone else reported a similar problem on this forum?
I might add here that I truly dislike the new theme and would like to have my simple black and white Theme-7 back again. Iād like to know why the Suite engineers decided to delete it. I imagine that they had a good reason⦠perhaps it was no longer maintainable?
Also the new system is a bit slower than the 7.8.x version it replaced. Iāve not looked into why yet. Maybe I have to again disable AJAX as I did in the previous version.
Also, email does not work. There is a small āfromā dropdown box that does not work. When sending I get a pop-up: āError Sending Email. Please contact your administrator for assistance.ā It is not a big deal to me as I rarely used email on Suite. It must be some setup item that got hosed in the update. Iāll have to look at the docs when time permits.
Can you please post the results of this command (run it from the SuiteCRM root folder):
ls -al
This will give me a quick glimpse of your permissions settings. Iāve seen a user start getting problems with permissions because an Apache upgrade (or reconfiguration) had simply changed the web-server user, so his permissions were like they had always been, but nothing was working anymore.
Ok. Iām assuming you xxxād out the username, but that is is always the same user name. This is important, so tell me if you see more than one user name, or if you see files owned by root.
I donāt see suitecrm.log there, maybe you moved it to a better place. Can you tell me the user/group ownership of it?
Then we need to know which user your web server runs under. Do you have a ācron_allowed_usersā entry in your config.php? What does it contain?
Yes the user name is the same although I didnāt delve deeply into all the sub-directories. Is there a command to list everything in all directories? I do not see files own by root or ānobody.ā My server is configured using FastCGI so that Apache runs as me, the user. That usually avoids update issues like this. Note, in fixing the issue I did not issue a chown command, only a chmod.
There is no suitecrm.log because years ago this was a conversion from SugarCRM. I have sugarcrm.log and it owned by me,⦠same as all the files.
I donāt see www-data anywhere in your files, so which is it? Please donāt confuse me by changing user names. If you really feel you need to obfuscate, just change ājoeā to ācharlesā or whatever, but keep it consistent.
Youāre missing a space and a dot at the end of those commands.
So, supposing your web-server user is ājoeā, and he belongs to group called āusersā, you could issue these commands from your SuiteCRM root directory:
And then you need to make sure that your cron jobs are running from Joeās crontab:
crontab -e -u joe
And finally make sure theyāre not running from any other crontab (check crontab -e, and check crontab -e -u root, and other users that you might have used before).
Do a Quick Repair and Rebuild and check if problem is solved.
I donāt know how ājoeā got in there since last time, unless I just overlooked it?
All I know is that everything is running well now. Weāll see what happens at the next update, which I expect to be soon⦠perhaps 7.9.1 is already out there. (I wish SuiteCRM would notify me when there is a new update like Sugar used to do back in the day.