Posted by johnjanney on December 23, 2007 at 11:31pm
Jump to:
| Project: | Event |
| Version: | 5.x-1.0 |
| Component: | User interface |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I'm trying to change the font color for the Start, End and Timezone (when someone clicks on an event to view more details). I have a dark background and the font is black (so this does not work). When I change color to #fff in ".event-calendar .start" inside the event.css nothing happens. I tried in several other places, but nothing seems to work.
Here is an example of the problem:
http://www.ustacademy.com/07-11-28-usta-tournament-2007
Could someone point me in the right direction?
Thanks,
John
Comments
#1
.event-calendar .start is only for the actual calendars, not the individual entries.
Try
.event-nodeapi .event-start {
color: #fff;
}
#2
No, that didn't seem to work...
#3
When editing the css, I think the advice is to make the changes in your theme files instead of in the module files themselves. The theme files are the last css files to be read in as a page loads and so overide previous declarations.(Also if you upgrade your module then you don't lose the css changes - a few more instructions about this here: http://drupal.org/node/11774)
Gerhard's suggestion seems to make sense, but each of your problem items are '.event-start', '.event-end', '.event.tz', so each of these needs declaring. I would try it without the .event-calendar, so:
div.event-start, div.event-end, div.event-tz {
color:#ffffff;
}
But just make sure you put it at the end of your css (usually in your theme's style.css, or in this case /themes/bealestreet/css/suckerfish_blue.css), so that it's not getting accidentally overidden by a declaration elsewhere.
Also to turn the labels white:
div.event-start label{
color:#ffffff;
}
I've checked this out using the firefox webdeveloper extension and it seems to work for me.
#4
That seemed to work.... yeah! Thank you!
#5
You are a genius!
We've been chasing this same issue for 6 months now, and I could never find the right phrase to search for until today. This worked for us as well.
#6
Marking "fixed" based on reporter feedback.
#7
Automatically closed -- issue fixed for 2 weeks with no activity.