Hi!
I'm using your nice module to theme my private and future production site, but there is one inconvenience at this time. I can't save my changes, instead the save button shows '...' and that's it. At the moment i use your module to see live what changes are doing and save them into an external file, loading it up via ftp.
Because of lack of knowledge i couldn't find a clue. I work with debian and got the same issue on two different machines, although with the same configuration. Permissions and Path seem to be ok, since any tests about them didn't work anything out...
Ideas?
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | FireBug Net Console.png | 213.97 KB | pmol123 |
Comments
Comment #1
guybedford commentedHi, yes sure there should be more debugging information with this in future releases as it is the primary component of the setup.
If using chrome (or firebug), check the network panel to see the save request go through. If you check the response, it returns the filename its attempted to save to. The first thing to check is that this is the correct filename on your server.
Secondly, you need to ensure that php has the write access... so whatever user php runs as (usually www-data), should have write access to the file (ie either the owner with 6** permissions, or the group with *6* permissions).
Comment #2
guybedford commentedI've just added a new release which will inform you what the file is that failed loading as the server path. You should then be able to check if this is a permissions or path issue.
If it's a path issue, let me know and I'll see if we can sort it.
Comment #3
2oland commentedHi,
i checked it with chrome browser and it says:
Not Found404 Not Found
The requested URL /drupal7theming/css/save was not found on this server.
I installed your module via drush and use a zen subtheme with css classes in sites/all/themes/subtheme/css/
and i dont have a css folder in my drupal root.
The path in the dropdown of your module is correct, thus the classes are shown properly.
Since i knew it isnt a permissions problem we actually do have a path problem here (what else ;)
Comment #4
guybedford commentedArgh, yeah these are always annoying. Are you using clean urls on your site? The path should basically just be your drupal site root with the /css/save part. It may just be as simple as adding a "?q=", or we may need to check if it's a subpath issue.
Comment #5
2oland commentedHi guy,
i enabled clean urls and now its working as it is supposed to work. Could it be something about the web server's configuration as well? I had to configure apache before i could enable clean urls and i think there are another features like private files which depends on appropriate apache configuration.
Just another guess.
But for now thanks for pointing me in the right direction.
Comment #6
guybedford commentedI've added the functionality to allow saving css with clean urls turned off. Thanks for reporting the issue.
Comment #6.0
guybedford commentedspell check
Comment #7
pmol123 commentedHi,
CLEAN URLS:
I tried it with 'Clean URLS" both ON and OFF. Same Result
PERMISSIONS:
Does not seem to be permissions as it finds all the files.
I went as fas as setting permissions to 777 from css folder down to all files within.
NOTE:
I am using a Varnish reverse proxy:
I have tried it both ways: 1) thru Varnish and 2) using port 8080 to go around Varnish
I also:
1) turned off the Google Page Speed and restarted Apache.
2) turned off the CSS files caching and aggregation on dev/performance
3) I flushed the CSS cache with DRUSH
I attached the NET console from firebug.
Thank you.
Respectfully,
Patrick O'Leary
Comment #8
deryck.henson commentedDo me a favor and create a new issue with a title relating to your specific error and mention 'Varnish'. This is an isolated issue related to your situation and this issue was originally made using a completely different release (1.7 vs 2.12). I just need to keep the issues separate and distinguishable.
You can just copy + paste what you put here into the new one.
Comment #9
deryck.henson commented