Messed up CSS after clean install?

[gtilflm]

I'm trying to install version 6.3.0 beta1 and I did a completely clean install (as I have never used sugar before).

After installation, it's like all of the CSS links are broken because the display is all messed up. See the attached screenshot.


Thoughts?

[sts]

Please have a look at this blog post: Angel's Blog: SugarCRM Troubleshooting: Formatting Woes

[gtilflm]

Yeah, I ended up finding something after I posted that led me to that solution.

New problem though. Sometimes there are "undefined" messages in certain places. Again, chmodding helped to reduce that, but it's still there. Any ideas?

Thanks.

[rafael.q.g@hotmail.com]

As a workaround try to access admin area (even with t)his broken layout) and change your theme preferences. Maybe another theme could works.

[sts]

In version 6 community edition there is only ONE theme ...

In > 90% of those errors it's a problem with file access permissions.

[Blake Peterson]

Yes this is a permissions issue (99% sure).

Check your config.php file. I had this problem until i used the following settings

   'default_permissions' => 
  array (
    'dir_mode' => 1533,
    'file_mode' => 509,
    'user' => '',
    'group' => '',
  ), 
  

Thanks

Blake

[Chris_C]

I'm trying to install version 6.3.0 beta1 and I did a completely clean install (as I have never used sugar before).

After installation, it's like all of the CSS links are broken because the display is all messed up. See the attached screenshot.


Thoughts?

OMG. Same bug when I installed 6.3.0 beta 2 today, brand new install into an empty folder. It looked like a disaster.

C'mon Sugar team !

I took a closer look at the broken link for the company logo graphic, just to see what was going on....

The graphic, my custom PNG file, showed a 403 error in the browser - access denied, but when I look at the file on the linux server, the image file was set to a perfectly acceptable permission...?!

So I ran a php script that sets all file permissions to 644 and folder permissions to 755.

Now the sugar login screen looks perfect.

I don't know if this is a full complete solution for all screens and all functions. So I will try it out and see if any more 403 errors show up...

[Chris_C]

I just posted a reply to this with a solution.

What happened to my post ?

[sts]

Hi Chris,

since you have less than 10 posts now all your posts (until you reach your 10th post) will be checked for spam, advertising, etc. before putting them into the forum. This takes some time so your post came a bit later into the forum.
(for details see here: SugarCRM Forums - Announcements in Forum : Announcements)

Regards
Stefan

[Chris_C]

Thanks Stefan.

Here is a script I adapted, to reset permissions so that Sugar can run on typical shared hosting.

The challenge this code overcomes is that the apache user is different from the shared hosting user's account, so permissions need to be looser for Sugar webserver and php interpreter (running as the apache username) to have permission to read the Sugar PHP source code files, CSS/javascript, and graphic image files (which belong to the customer's shared hosting account username).

Note: This code resets all the SugarCRM PHP source code, CSS, Javascript, and image files, located inside selected SugarCRM subdirectories, according to the recommendation of Clint on this thread: http://www.sugarcrm.com/forums/f3/in...89/index2.html

You can save this PHP code file to the top folder of your SugarCRM installation.

For example: for company.com with a SugarCRM instance located at: www . company . com / crm (remove spaces), you would upload this PHP code file to the location on your shared server account with the pathname being something like: "/home/(share hosting account username)/public_html/crm/fix-permissions.php".

Once uploaded, to run the PHP script, just go in your browser to the link http : // www . company . com / crm / fix-permissions.php (once again...remove spaces)

The Script will run, and as it runs, it will display a list the files and directories it's fixing the permissions of.