Title: ed.2010's Replies | WordPress.org

---

# ed.2010

  [  ](https://wordpress.org/support/users/ed2010/)

 *   [Profile](https://wordpress.org/support/users/ed2010/)
 *   [Topics Started](https://wordpress.org/support/users/ed2010/topics/)
 *   [Replies Created](https://wordpress.org/support/users/ed2010/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/ed2010/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/ed2010/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/ed2010/engagements/)
 *   [Favorites](https://wordpress.org/support/users/ed2010/favorites/)

 Search replies:

## Forum Replies Created

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

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WP-Cumulus] [Plugin: WP-Cumulus] Tags are no longer clickable](https://wordpress.org/support/topic/plugin-wp-cumulus-tags-are-no-longer-clickable/)
 *  Thread Starter [ed.2010](https://wordpress.org/support/users/ed2010/)
 * (@ed2010)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/plugin-wp-cumulus-tags-are-no-longer-clickable/#post-2523479)
 * Hi Roy
 * Thanks for that – I validated the markup a month or two ago – and looks like 
   since then:
    a) The <head> tag was accidentally removed from header.php during
   an unrelated edit (*facepalm*) b) The html_type row in wp_options was missing,
   causing my theme’s header.php to output: <meta http-equiv=”Content-Type” content
   =”; charset=UTF-8″ /> …rather than: <meta http-equiv=”Content-Type” content=”
   text/html; charset=UTF-8″ /> …as well as WordPress to send the wrong HTTP response
   Content-Type.
 * Now that those have been fixed, the page validates and WP Cumulus works again.
 * Cheers! 🙂
 * Ed
 *   Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/)
   
   In reply to: [Default and Kubrick Based Themes Fail on New Browsers](https://wordpress.org/support/topic/default-and-kubrick-based-themes-fail-on-new-browsers/)
 *  [ed.2010](https://wordpress.org/support/users/ed2010/)
 * (@ed2010)
 * [15 years, 2 months ago](https://wordpress.org/support/topic/default-and-kubrick-based-themes-fail-on-new-browsers/#post-1956898)
 * RAMilewski: Yes sorry, appears I spoke too soon – this issue effects even the
   current version of Default. I’m not able to edit my post above now though 🙁
 *   Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/)
   
   In reply to: [Default and Kubrick Based Themes Fail on New Browsers](https://wordpress.org/support/topic/default-and-kubrick-based-themes-fail-on-new-browsers/)
 *  [ed.2010](https://wordpress.org/support/users/ed2010/)
 * (@ed2010)
 * [15 years, 2 months ago](https://wordpress.org/support/topic/default-and-kubrick-based-themes-fail-on-new-browsers/#post-1956846)
 * Yes and has been replaced by TwentyTen, I’m aware of that.
 * People still use old themes and will come to the support forum asking why they
   are broken.
 * Giving fellow triagers/front line support volunteers a heads up as to the imminent
   browser changes (so they are prepared for a potential influx in the next 2-3 
   weeks) seemed like a prudent course of action.
 * Make of it what you will…
 *   Forum: [Themes and Templates](https://wordpress.org/support/forum/themes-and-templates/)
   
   In reply to: [Default and Kubrick Based Themes Fail on New Browsers](https://wordpress.org/support/topic/default-and-kubrick-based-themes-fail-on-new-browsers/)
 *  [ed.2010](https://wordpress.org/support/users/ed2010/)
 * (@ed2010)
 * [15 years, 2 months ago](https://wordpress.org/support/topic/default-and-kubrick-based-themes-fail-on-new-browsers/#post-1956841)
 * The point of this thread is more to act as an advance warning/heads up, explaining
   problems people may be having with their theme – given that Firefox 4 and IE 
   9 (both of which are affected) will be released in ~2 weeks – and so might result
   in an influx of support threads here.
 * I’ve checked the latest version of default using the preview here:
    [http://wp-themes.com/default/?TB_iframe=true&width=1585&height=900](http://wp-themes.com/default/?TB_iframe=true&width=1585&height=900)…
   and it seems to have had the issue fixed.
 * So presumably as long as people are using default and keeping it up to date, 
   then they won’t be affected.
 * However, for the **many** sites that use a custom theme based on Default/Kubrick,
   who haven’t incorporated newer Kubrick/Default changes, then they may be affected.
 * eg like this user’s custom theme based on Kubrick:
    [http://www.buzzmachine.com/](http://www.buzzmachine.com/)
 * **tl;dr…**
    – Fault is only in older versions of the theme – So agree it’s the
   responsibility of the blog owner to update/change to a non-broken theme – This
   thread is just attempting to give advance warning to those who offer support/
   triage, given that Firefox 4/IE 9 are going to be released in <2 weeks
 * Sticky/known issues list perhaps?

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