Postponed (maintainer needs more info)
Project:
CSS Injector
Version:
7.x-1.4
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
13 Jan 2011 at 18:02 UTC
Updated:
18 Feb 2013 at 17:21 UTC
Jump to comment: Most recent file
Comments
Comment #2
rfayThanks for the patch.
Use git diff --no-prefix to generate your patch and it won't have the extra a/ and b/ that made this fail.
I didn't know that the public files directory could be outside the drupal directory. Under what circumstances would you do that?
Comment #3
mukhsim commentedPublic files folder could be on a network share or separate file system for performance/security reasons.
Imagine having a dozen websites under multisite configuration. You might want to point files folder for each domain to a mount point which is both read and write, but keep everything else on a read-only partition.
A patch generated with --no-prefix is attached.
BTW, how do I get rid of "\ No newline at end of file" message in the patch file? Or is it supposed to be there?
Thanks,
Mukhsim.
Comment #4
rfayThanks!
I wouldn't worry about the "no newline at end of file" thing.
Comment #5
mukhsim commentedUpdated patch, checked out from CVS.
Comment #6
rfayI suspect that #1044670-12: Fix file handling resulting in Incorrect path to css file on Windows is a better solution for you. Could you please test it?
Comment #7
windmaomao commentedhaven't try the patch yet, but after i migrate to multisite, css_injector is not working properly.
it just complains that the folder is not writable, but i wonder which folder it's asking right now. And i guess i have name conflict as well, since both sites has css_injector_1, and i don't think they have the same content right now. most likely one of the css_injector_1 is missing, which is understandable.
i wonder, css_injector probably can do something similar to cTools import/export, so that we don't need to worry too much about migration in the future. Sorry if i'm asking too much. This module rocks btw.
Comment #8
rfay@windmaomao, please try 7.x-1.8 and see if it resolves your problem. The complaint in the status report was bogus and was fixed long, long ago, but never got into a release. But I just created 7.x-1.8.