Layout/Appearance

[outwestlondon]

Hi, I've recently installed Sugar and seem to be having trouble.

For a start, the layout is not how I thought it would be - all the options are in a long list down the side of the page and the various boxes etc are looking very VERY old school! (screenshot attached).

Also, my company logo does not appear (just the words 'Company Logo') and the settings do not seem to be saving.

This happens in both Firefox and IE

I know I've posted a few problems here and apologies for doing so, but any help would be gratefully appreciated!


Cheers

Dan

[andopes]

This is due to file permission issue in cache folder.
You need to make sure web server user has read and write access to whole sugarcrm folder.

Cheers

[outwestlondon]

Thanks - is it just a case of changing the CHMOD for the whole directory?

[outwestlondon]

Still no joy - all folders have been set to 777 in CHMOD.

[roblaus]

Yes, chmod the entire Sugar directory to the Apache user/group recursively. Additionally it's not a bad idea to chown/chgrp the whole thing to 755. The documentation is not very clear about this but this method is tried and working without any security issues (or I have yet to find any...)

[Angel]

Per everyone else's comments, it is a security issue. This post has more background on the matter and the solution that's been discussed:

Angel's Blog: SugarCRM Troubleshooting: Formatting Woes

[roblaus]

In addition to Angel's blog post see below the official Sugar statement about permissions and owner. The reason behind all that is simple: Sugar does not only read and execute but also writes a lot. For instance cache/jslanguage and cache/modules is rebuilt from /modules each time you run a quick repair. Whenever you create a custom field or a new layout in studio Sugar (amongst other actions) reads the respective layout file in /modules/MODULE/metadata and puts a copy with your changes into /custom/...

In short words: Sugar's enormous flexibility and ease of customization comes at a price which is sometimes trouble with permissions.


4.
Set permissions on the Sugar files. The following directories, all subdirectories, and files must be writable by your web server user:
¢
cache
¢
custom
¢
modules
¢
config.php
¢
config_override.php
¢
sugarcrm.log
Note:
Typically, there are multiple versions of the log file, such as sugarcrm.log, sugarcrm.log.1, sugarcrm.log.2, and so on.
For example:
chgrp ApacheUser.ApacheGroup <SugarInstallRoot> -R recursively sets ownership for root directory to Apache user and group.
chmod 755 <SugarInstallRoot> -R recursively sets permissions to Read/Write, Execute for the owner, and Read/Execute for everyone else.
The system user that your web server uses to access files in your webroot varies depending on your operating system configuration. Common web server users include:
¢
apache (Linux/Apache)
¢
nobody (Linux/Apache)
¢
IUSR_computerName (Windows/IIS)
Consult your system administrator if you are unsure of your web server user.
5.
Ensure that file permissions are set for Read/Execute to includes directory and sugar root directory (in addition to the already existing list of directories/files) before you view Sugar on your browser.