Theme update boinks WP 4.3.1

  • I updated to theme version 0.1.20151007 as per my Dashboard update. When I did, it boinked my site and made it impossible to preview posts claiming I needed version 4.4 of WordPress in order to view my site. I went to www.ads-software.com to download version 4.4 but it is not available yet. Not good!

    I had to roll back to the previous version of Twenty Sixteen. I don’t know if I will update it if this is what I can expect to happen.

    I absolutely LOVE the theme’s simplicity and ease of creating a child theme (which I’ve done). PLEASE – don’t update the theme to require a version of WordPress that doesn’t exist yet.

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

  • jgbennette,

    This was posted on October 2nd: https://make.www.ads-software.com/core/2015/10/02/update-on-twenty-sixteen/ and within the text is the following quote: “Twenty Sixteen now also will require 4.4-alpha”.

    The only way you can get the current versions of Twenty Sixteen to work properly is to upgrade your website using the WordPress Beta Tester Plugin located here:
    https://www.ads-software.com/plugins/wordpress-beta-tester/. You have to install it, enable it, and then choose option #2 (Bleeding edge nightlies) on its Settings page.

    If you have never done that before, I would very carefully read both the Reviews and Support Tabs for the plugin. Otherwise, you’ll have to wait until WordPress 4.4 comes out in the first week of December to download the finished product of Twenty Sixteen.

    Hope that helps.

    Well, it explains what is going on. But I can’t really say that it helps.

    When Twenty-Sixteen was announced in August I really liked it so I started using it on a number of my sites. It worked fine. Nowhere in the information I read was it mentioned that I would need to stop using it at some point as it would become incompatible with the release version of WordPress.

    So now I’m left with the choice of using an unreleased version of WordPress on production sites (not gonna happen) or changing theme again.

    I guess I have to take the second option, but it leaves a bad taste in the mouth.

    Seriously, can’t you see what a bad idea this is? If you release a theme without marking it as “Beta” or something like that, then people are going to start using it. Taking it away from them again six weeks later is just rude.

    davorg,

    Seriously, can’t you see what a bad idea this is? If you release a theme without marking it as “Beta” or something like that, then people are going to start using it. Taking it away from them again six weeks later is just rude.

    I agree with you that it was poorly planned out, but I’m only an end-user myself and not a Theme Developer. The only reason that I knew what was gong on is that I follow this tab https://make.www.ads-software.com/core/ daily. When I saw that no explanation was being offered here for current users, I decided to do it on my own. I know that it doesn’t provide a good remedy for your dilemma, but it’s all that I can do.

    You might post a comment here https://make.www.ads-software.com/core/2015/10/02/update-on-twenty-sixteen/ to prevent your dilemma from happening to others in the future.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Theme update boinks WP 4.3.1’ is closed to new replies.