Looking for a Date?

I want pussy

When I changed the appearance of this blog back in January, there were a number of little bugs that I had yet to fix. I haven’t had the time or energy to fix any of them. I already spend too much time on this blog; any time spent fixing means less time writing.

One of the smallest problems, yet one of the most annoying, was the tendency for long titles to overrun the date, making it hard to read either. I “fixed” this by making shorter titles. It finally wore me down, so I spent some time today mucking with the CSS and trying to move the date somewhere else.

Thanks mostly to a comment that ParrotLover left back in January, I was able to move the date to its new home, right under the title.

Let me know if it doesn’t look right in a modern browser, or if I broke something else.

4 Responses to “Looking for a Date?”

  1. Bart v.d. M. Says:

    I don’t see the change… You didn’t change it back already did you? On my screen, your ‘Darwin was wrong #1′ post is still displaying the error that you describe here, although it doesn’t matter that much because only the ‘n’ of ‘vacation’ overlaps.

    BTW I use FF 3.5.5 for a browser.

  2. Bart v.d. M. Says:

    Ignore the above, I just reloaded the page and it did work out as you described here. Weird, ’cause I could see the post after this one, so it can’t have been my cache that needed updating…

  3. Ron Britton Says:

    Bart:

    When I tested it in FF 3.5.5, it looked fine. I have received another report just like yours. I think the browser only fetches what is new. It already had the (old) CSS cached, so it didn’t download it again. When you reloaded, that forced it to grab everything.

  4. Parrotlover77 Says:

    Glad I could be of help!

    CSS caching display issues are very common during a transition. One way to work around this issue is to rename the CSS file when you make significant changes like that. Not sure if you can do that in WP. If it’s a new name, the browser doesn’t know it can use a cached version.