Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
diff -wBNru css_injector/css_injector.install modules/css_injector/css_injector.install
--- css_injector/css_injector.install 2011-02-24 21:08:11.000000000 -0500
+++ modules/css_injector/css_injector.install 2011-08-13 15:47:34.000000000 -0400
@@ -85,7 +85,7 @@
'title' => t('CSS Injector directory writable'),
'description' => $status == REQUIREMENT_OK ? t('CSS Injector Directory %dir is writable', array('%dir' => $dir)) : t('Directory %dir is not writable', array('%dir' => $dir)),
'severity' => $status,
- 'value' => t('Not writable'),
+ 'value' => $status == REQUIREMENT_OK ? t('Writable') : t('Not writable'),
),
);
return $requirements;
Comment | File | Size | Author |
---|---|---|---|
#2 | css_injector-requirement-should-check-status-1248514-2.patch | 1004 bytes | makangus |
Comments
Comment #1
rfayYou'll need to give a better description than this to get something worked on (and patches are welcome - it looks like you're capable of making one... - maybe you just intended to attach instead of pasting something in?). Please give a complete description of your issue. Please take a look at http://drupal.org/node/73179 and http://drupal.org/node/1155816
I can confirm what I think is your complaint though. Looking forward to a better description and a patch. Thanks for your contribution.
Comment #2
makangus CreditAttribution: makangus commentedI was bored so I decided to roll a patch. I think the bug report from fizk is about "CSS Injector directory writable" is always showing "Not writable" on the status report page. Attached is the patch against the 7.x-1.x branch that checks the status and put it either "Writable" or "Not writable". The code was provided by fizk.
Comment #3
rfayLooks good to me. Thanks!
Committed: http://drupalcode.org/project/css_injector.git/commitdiff/9ef40e6
Comment #5
dimmech CreditAttribution: dimmech commentedMeant to post this answer here, but may apply in the issue it links to as well.
https://drupal.org/comment/8363903#comment-8363903