Hi HLopes - I definitely think we should figure this out.
I'm not in favor of adding specific changes to support specific modules.
In Drupal 6, the rules from CSS Injector get loaded in the module-loading time (before themes) according to the module weight of the module. So it's possible to fiddle with module weights to change it.
In Drupal 7, the rules from CSS Injector get added last, after themes and everything.
It's not so normal in CSS to rely on *not* adding a rule, it's generally the more specific rule or the one that's added last that controls behavior.
to use a rule when a node is converted - for instance, if i want to convert a profile from content profile, and change role accordingly.
I don't think that it should be a problem, as long as it's wrapped in module_exists(). Don't know about drupal 7, as i work mainly with drupal 6 (for now).
Well, the issue is open, lets see if anyone else finds this approach interesting.
Comments
Comment #1
rfayHi HLopes - I definitely think we should figure this out.
I'm not in favor of adding specific changes to support specific modules.
In Drupal 6, the rules from CSS Injector get loaded in the module-loading time (before themes) according to the module weight of the module. So it's possible to fiddle with module weights to change it.
In Drupal 7, the rules from CSS Injector get added last, after themes and everything.
It's not so normal in CSS to rely on *not* adding a rule, it's generally the more specific rule or the one that's added last that controls behavior.
If you want to proceed on this line, please provide a patch, http://drupal.org/patch.
Comment #2
hlopes commentedI understand your point, but think that there is no problem in doing so.
I have done that on a couple of modules, for example Node Convert
http://drupal.org/node/839614
to use a rule when a node is converted - for instance, if i want to convert a profile from content profile, and change role accordingly.
I don't think that it should be a problem, as long as it's wrapped in module_exists(). Don't know about drupal 7, as i work mainly with drupal 6 (for now).
Well, the issue is open, lets see if anyone else finds this approach interesting.
cheers
Comment #3
klonosNW or NR makes the issue show up in the 'View pending patches' section, but there is no patch provided, so setting to 'active'.
Comment #4
francewhoaIt seems this is fixed in the latest versions of Context and CSS Injector. Details at https://www.drupal.org/node/909962#comment-9977185