Since Fields seems to insist on giving me an "N/A" option for a boolean field, I want to take it out in the CSS, but I don't want it going away every time there's a system upgrade. Is there some easy way to give Seven (the admin theme) another CSS file (or setting to it) that it won't overlay on upgrades?
Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
Ms. Nancy Wichmann wrote:
Since Fields seems to insist on giving me an "N/A" option for a boolean field, I want to take it out in the CSS, but I don't want it going away every time there's a system upgrade. Is there some easy way to give Seven (the admin theme) another CSS file (or setting to it) that it won't overlay on upgrades?
Have you considered adding the CSS changes to a module? How about changes to the CSS for the theme itself?
If I change the Seven theme files, when Drupal 7.5, and all releases above it, come, I will have to do them all over again - if I, or who ever takes over after me, remember. A module with nothing but a hook_init() would work, but seems overkill. Maybe the best thing is to just not use an admin theme.
Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
From: Earnie Boyd
Is there some easy way to give Seven (the admin theme) another CSS file (or setting to it) that it won't overlay on upgrades?
Have you considered adding the CSS changes to a module? How about changes to the CSS for the theme itself?
Thanks, Ted. That looks like a good possibility. Is there a lot of overhead? I would allow pretty much everything to be inherited and just add a new CSS file. I guess the "theme" would just be an .info file.
Nancy E. Wichmann, PMP (781) 697-6344 Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
From: Ted ted-drupalists@webfirst.com
To: support@drupal.org Sent: Monday, July 18, 2011 9:10 AM Subject: Re: [support] Admin CSS
Why not create a sub-theme? http://drupal.org/node/225125
Ted
On 7/18/2011 9:04 AM, Ms. Nancy Wichmann wrote: If I change the Seven theme files, when Drupal 7.5, and all releases above it, come, I will have to do them all over again - if I, or who ever takes over after me, remember. A module with nothing but a hook_init() would work, but seems overkill. Maybe the best thing is to just not use an admin theme.
Nancy
Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
From: Earnie Boyd
Is there some easy way to give Seven (the admin theme) another CSS file (or setting to it) that it won't overlay on upgrades?
Have you considered adding the CSS changes to a module? How about changes to the CSS for the theme itself?
-- [ Drupal support list | http://lists.drupal.org/ ]
Fabulous! It works perfectly (after flushing the theme registry).
Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
From: Ted
I think the overhead is pretty low. Here's a discussion of that: http://groups.drupal.org/node/161029
Why not create a sub-theme? http://drupal.org/node/225125
-
Earnie Boyd -
Ms. Nancy Wichmann -
Ted