Version 3.0 forward .css follows wp_head call

  • Resolved bottle washer

    (@bottle-washer)


    12 years, 9 months ago

    Version 2.6.1 worked for us, but we finally jumped to 3.0.9. Our scripts and styles module .css customizations then failed, because in versions 3.0.1 forward the theme css is inserted AFTER wp_head. Why is that? I thought the standard — expressed right in the header.php file — was not to do that, because it would break modules (it did).

Viewing 2 replies - 1 through 2 (of 2 total)
  • Theme Author wayneconnor

    (@wayneconnor)

    12 years, 5 months ago

    3 was re-designed based on the example Twenty 10/11 etc theme. I think that’s why that changed. It’s a long time ago I can’t remember!

    Thread Starter bottle washer

    (@bottle-washer)

    12 years, 5 months ago

    Well, OK, thanks for the reply, but “resolved”?

    The problem is: doing it that way does indeed break some module behavior, especially when trying to maintain customization compliance by using re-definitions rather than theme modification. As I mentioned, the comments in header.php warn against doing that very thing.

    I fixed it the only way I could: put the calls back into the order they should be in, thus modifying the theme… which I was trying to avoid. Nothing failed after that change, but of course I am only concerned with my own utilization.

    Just thought you should know; it seems to me to violate the standard.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Version 3.0 forward .css follows wp_head call’ is closed to new replies.