Drupal Ctools
more_horiz
close

on 30th October 2012 / by webmaster
"CTools CSS Cache. Unable to create The CTools CSS cache directory, ctools/css could not be created due to a misconfigured files directory. Please ensure that the files directory is correctly configured and that the webserver has permission to create directories." If you are getting this error message while inspecting the status reports on your Drupal site then continue reading to get the solution. Drupal Drupal Issues Drupal Ctools Leave a reply Your email address will not be published. Required fields are marker * Anonymous (not verified) access_time 18 Aug 2019 - 19:55 Following post asks to run chown command. I don¨t have SSH access so dont know how to run it.http://theaccidentalcoder.com/content/drupal-and-permissions-avoiding-d… loneranger (not verified) access_time 18 Aug 2019 - 19:55 Hello there, I found your site today after searching for a solution on ctools access denied issue on my drupal backup site after an silly problem on the drupal7 language changes to the earlier site. First of all, I would like to thank you'll for your precise/accurate answers to questions/problems on yout Site! I'm having problem of accessing my site after changing the language. It is deafault drupal german installation but after installation I use it for english language. It worked for a long time untill I changed the language again! I hope, You'll understand the spesific situation here what I'm explaining. At the moment I'm runing an 21 days old backup as my site again! If there is an solutin for this, please kindly let me know it. Best Regards, Anonymous (not verified) access_time 18 Aug 2019 - 19:55 I cannot change the permissions of files/ctools/css "550 Could not change perms on css: Operation not permitted" Anonymous (not verified) access_time 18 Aug 2019 - 19:55 I use a Linux distro so just went into: sites/default/files/ Then create the directly: sudo mkdir ctools and then gave ownership to my web server (www-data): sudo chown www-data:www-data ctools Then I reloaded the Status Report page in Drupal and the error message had gone. Thanks webmaster! Add new comment