For questions and problems with the CMS core. This board is NOT for any 3rd party modules, addons, PHP scripts or anything NOT distributed with the CMS made simple package itself.
tmp folder and its children have permission set to 755. I found combined_stylesheet from cache folder has permission set to 644. What will be the safest case?
Edit:
Setting tmp and cache folder to 777, combined_stylesheet refused to generate and admin log report the same message: "Plugin: cms_stylesheet Smarty Compile process failed, unable to write cache file".
Edit:
Added attachment
Attachments
[The extension txt has been deactivated and can no longer be displayed.]
phpversion: 5.3.21
md5_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 0
E_DEPRECATED: 8192
memory_limit: 64M
max_execution_time: 30
output_buffering: On
safe_mode: Off (False)
file_uploads: On (True)
post_max_size: 33M
upload_max_filesize: 32M
session_save_path: /var/chroot/home/content/31/9985931/tmp (0705)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)
Server Information:
Server Api: cgi-fcgi
Server Db Type: MySQL (mysqli)
Server Db Version: 5.0.96
Server Db Grants: Could not find a suitable "GRANT ALL" permission. This may mean you could have problems installing or removing modules. Or even adding and deleting items, including pages
How did you install it, did you unpack the tar.gz in server file manager or FTP folders/files to site, might be an 'owner' problem, is this a windows server..?
I locally unpacked the tar.gz before uploading the folders through Filezilla. The server is based on CentOS 6 hosted by GoDaddy. Edit:
After several reinstalls and disassociated the css, it turned out the bug is related to smartys themselves I used inside the stylesheet hence above error message.
Attachments
[The extension txt has been deactivated and can no longer be displayed.]
which fixed the stylesheet error. Can anyone reproduce the problem related to the use of root_url inside background tag? If that happened, I guess I found a bug.