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.
I've gone through all the CSS files looking for the light colored text and changing them to dark colors, but no matter what I do, most of the labels in the wizard are white on almost white, and near impossible to read. Can anyone direct me to the exact CSS to change this? I've attached a screenshot showing what I mean, the labels above the text fields are almost invisible.
I'm using the default theme for Asset, Bluelagoon was almost unusable due to placement of items being scattered all over the place.
Comment | File | Size | Author |
---|---|---|---|
AssetSample.jpg | 26.09 KB | Steel Rat |
Comments
Comment #1
zroger CreditAttribution: zroger commentedmost likely, this color is coming in from the stylesheet of your site's theme. to override, use a declaration like
Comment #2
Steel Rat CreditAttribution: Steel Rat commentedThanks! That helped the form items, but there are other areas, mainly descriptive text.
One section after choosing Upload, at the bottom of the form which starts with the text "Select the permissions for this asset" are still coming up white. The page source says the div has a class of "description", but I don't find that class in any of the asset CSS files, either in the main asset folder or the themes folders.
Comment #3
nevets CreditAttribution: nevets commentedIf you use firefox I suggest trying out the firebug extenstion. It has an inspect feature that speeds up finding the css rule(s) that are responsible for the styling you see.
Comment #4
wmostrey CreditAttribution: wmostrey commentedComment #5
Steel Rat CreditAttribution: Steel Rat commentedI think this misses the issue. The wizard is using CSS from the drupal theme, but only some of it, and therefore the display gets abused. Why should I have to go through and try and apply fixes for every potential theme I may want to use? The wizard should use its own distinct CSS and not inherit from Drupal.
Comment #6
1kenthomas CreditAttribution: 1kenthomas commentedI suspect what is being looked for is more like:
Without this asset picks up the li a.active (white) definition from system.css (not a theme!) and displays it on a white background (in most themes).
I'll second that this should perhaps be addressed at the module level.
This is also fairly hard to address as FFox web developer will not invoke in the wizard (no CTRL-Y), FireBug (F12) has problems, and IE7 web dev toolbar... well, does trace it correctly, but...
Comment #7
1kenthomas CreditAttribution: 1kenthomas commentedAlso
Also, gently changing this to "minor, alpha3, UI" and "active..."
Comment #8
1kenthomas CreditAttribution: 1kenthomas commentedOK, next issue: the asset wizard popup in fact does not load any stylesheets from the current theme (aha!). Therefore it is not possible to theme from the theme folder at all (for those who give our themers access to that and not to the rest of our installs).
This is why the white-on-white is picked up from system.css; else the default theme would likely not define...
Hacking around it here now... upping priority to "normal..."
K
Comment #9
1kenthomas CreditAttribution: 1kenthomas commentedI added
to l.923 of asset_wizard.inc.
Comment #10
wmostrey CreditAttribution: wmostrey commentedMy preferred fix for this issue would just be to add
drupal_add_css(path_to_theme() ."/style.css");
so people can overwrite css from within their theme. I'll check this with the default themes and come back with a small rapport. Thanks for your work Kenneth, it is highly appreciated.Comment #11
wmostrey CreditAttribution: wmostrey commentedI won't add this. For instance in the Garland theme this completely screws the wizard's lay-out. If people want to do this, they can always plug in theme_asset_popup.
Comment #12
Steel Rat CreditAttribution: Steel Rat commentedSo, what's the fix apart from trying to fix all the possible problems manually?
Frankly I've stopped using Asset in favor of IMCE, for the reported reason and the ability to manage uploaded images (resize, delete, etc.) I would have liked to use Asset because it looked nice and was easier for non-techie users, but if the text isn't readable without jumping through hoops...