eddierebel

Thank you moshu, you have solved everything apparently ?? I took out the old css and inserted the calendar section from yours. Now I will just tinker with yours until it fits in with this theme a little better. Keep up the good work!

I have tried changing the font sizes for all #wp-calendar references in the default, classic, and journalized-winter (the theme I am currently using) folders and so far nothing has changed. Any other suggestions? Does anyone have some code for this I could try inserting into my .css to see if it changes? Thanks for all the help — You guys rock!

That’s what I was afraid of. In the style.css there are alot of references to .b2calendar — I have changed all of the font sizes and it has yet to change anything on my webpage. Here is what it says right now, if anyone has a suggestion on how to make this look like a normal, standard calendar I would appreciate it:

.b2calendartable {
background: #bfc4cb;
border: 1px solid #5f7797;
}

.b2calendarmonth {
font: 7px georgia;
}

.b2calendarrow {
}

.b2calendarheadercell {
background: #5f7797;
color: #e9f2fc;
font: 7px georgia;
}

.b2calendarcell {
color: #333333;
font: 7px georgia;
}

.b2calendartoday {
color: #ff0000;
}

.b2calendaremptycell {
}

.b2calendarlinkpost {
color: #354463;
text-decoration: none;
}

So wouldn’t you know that I got everything working until I hit the 2.0 upgrade — everything went smoothly until I reran upgrade.php and that generated this error:

N clo
Warning: Cannot modify header information – headers already sent by (output started at /home/xxxxxx/public_html/moist/wp-config.php:1) in /home/xxxxxx/public_html/moist/wp-admin/upgrade.php on line 10

and now when I go to my blog I see N clo at the top of the page.. any suggestions?

***

Nevermind, I’m an idiot. I did a search for the error, found the problem. My config file had the N clo crap at the beginning of it. Problem solved. Thanks again guys.

Hey guys, thanks for all of the advice. I just now finally got up to WP1.0.2 after finally removing the SQL command DROP TABLE wp_settings; — there was no table with that name and that’s where it kept erroring out at.

Thanks for the link to the previous versions as well, I searched around for a long time and could not find those. ??

Keep up the good work!