I'm trying to edit layout.css is my theme. I can see the changes live and the changes appear to save until I perform a page refresh which downloads the original .css file without my changes. The directions say to

Check that php has write access to the necessary css files.

How exactly do I do this? Changing the files to 666 and the directory to 777 didn't work.

Comments

guybedford’s picture

Are you running Drupal in a subdirectory?

If you are, you'll need to download the latest dev version for this fix (or 6.x-1.4 which will be available shortly).

Otherwise, setting the permissions to 661 should do the trick.

pixelgarden-1’s picture

Assigned: Unassigned » pixelgarden-1

Same question, but don't know what the numbers mentioned mean. Where is this setting located?

guybedford’s picture

In the same way that Drupal needs access to the sites/default/files folder, you will now need to apply the same permissions to your theme folder or to specific css files.

If you're using an FTP browser, you can right click on a file and set its permissions. Typically, you should ensure that both 'user' (or 'owner') and 'group' both have read and write access to the file. If using ssh, you can simply type 'chmod 661 filename.css'.

To be sure it's not a path bug in the system, do update to the latest version of the module released today as well.

paulgemini’s picture

Same question but with drupal 7. I'm guessing there isn't a bug in drupal 7.

Sorry for repeating the question, but I want to be methodical about security here. Should I set the theme directory to 661? Or just the theme files I want to edit to 661?

Paul

benlotter’s picture

Yes, I'm running Drupal in a subdirectory. I'll try the dev version when I get a chance to look at this again.

paulgemini’s picture

I'm still having problems with this. A ton of CSS files from modules are showing up, but none of the theme ones are. Using drupal 7 - latest verison of LiveCSS.

I even tried changing my files and theme directory to 777 (*NOT* a good practice, but something that I did in order to see if permission settings were the problem) and then I flushed the cache.

UPDATE: NEVERMIND! FIGURED IT OUT!!!

guybedford’s picture

Hi Paul,

Glad you sorted it - can you share what the fix was in case other people have this issue?

For future reference, you can typically view the request in firebug or chrome and see the error message on the save ajax call.

Additionally if you need to hide the module files, there is a setting for this in the Live CSS admin page.

Guy

guybedford’s picture

Status: Active » Closed (cannot reproduce)

No further information provided...