PodPress and WordPress 2.6: A Quick Update

For those of you wondering what is going on with PodPress like I am, so far it doesn’t look like the programmer was able to complete an update to the popular WordPress plugin in the ten days that he assumed it would take.

There are currently many issues with PodPress’ WordPress 2.6 compatibility, and Dan Kuykendall aka Seek3r seems to be taking his time to work on what should be a major release in version 8.9, despite everyone wishing he would push an interim release to fix the current issues.

Over the last few weeks, people have come up with all sorts of ideas on how to make PodPress 8.8 work with WordPress 2.6 as well as making the experimental version of PodPress 8.9 work with WordPress 2.6.

Andrew Ozz was one of the first to get the PodPress 8.9 experimental release working for many people, with a fix that should fix PodPress for those using WordPress 2.6 and having issues due to the post revisions feature that WordPress now includes.

In the comments of the Andrew Ozz post, there is a person named Otto who has instructions on making it work with PodPress 8.8, but not really any confirmation on if it does, in fact, work or not.

There are also people disabling post revisions, which is a great feature, either through plugins or through manually editing core files.

Some people started a small donation drive in order to try to fund development time of the plugin, and not much money was raised, from what I can tell.

It looks like the WordPress community really wants this plugin to work, but aren’t willing to wait for the final release, nor pay for its development. As I have said before, I think the biggest issue is that this is a hobby project for Dan, rather than an Automattic sponsored project. Automattic should be actively participating in the development of important plugins such as PodPress.

Will we see a new release of PodPress in the next week? And if a WordPress 2.6 compatible version of PodPress becomes a month or more away from being released, will people wait, or try to transition to something else?

25 thoughts on “PodPress and WordPress 2.6: A Quick Update

  1. Jeffro2pt0

    I agree. I think PodPress has reached a point where it would be a good idea on behalf of Automattic to pick this project up or sponsor Dan’s work with the project. I know there is a Podcast plugin for WordPress which was a Google Summer Of Code project but apparently, it is nothing compared to PodPress.

    I’ve actually decided to do a Jeffro2pt0 uncensored type of podcast and I wanted to use PodPress as my distribution and for management. Looks like I’ll have to put that on old.

  2. Matt

    We published and sent in a fix for the problem. I’m not sure what else we can do besides just committing the code directly without Dan’s permission.

  3. Jeffro2pt0

    Well, under no circumstances without the permission of the plugin author should the team take it upon themselves to fix the problem. It is great to know that you guys have stepped up and provided a fix for this widely used plugin. I guess it becomes a waiting game yet again.

  4. Matt

    Dan is a really talented developer, there’s probably just something come up in his day-to-day life that has taken priority over PodPress for now. It’s not the end of the world. 🙂

  5. David Peralty Post author

    Ack! How can you say it’s not the end of the world? Have you seen how many people are outraged at this plugin not working? The biggest issues is that there are no alternatives that do all of the things PodPress does, the way PodPress does it. :$

    I guess for me, I just wish someone would release an interim release that fixed the 2.6 compatibility issues with Post Revisions. That’s all… nothing too crazy. 🙂

  6. Atlantic Wave Radio

    Disasterous, I am now in a position I cannot add anything, I am on 2.5.1 and podpress 8.8 still doesnt want to work. I cant get any help. Just a total mess and I don’t blame Dan at all. I blame WordPress and at the moment it wont take much to make me dump it for good. Which I would prefer not to do but any more major screwups like not testing with major plug-ins and I will drop it like a rock.

  7. Jason

    My feed has been busted for about a month now. My ranking has dropped in iTunes off the top 100, and any hopes of taking my podcast “to the next level” are rapidly diminishing as time ticks away. The biggest problem lies in the fact that WordPress is continually pushing updates too often without much in the way of testing with the most popular plugins. Podpress is huge! how could they have released 2.6 without seeing if one of the most popular plugins will work? To me the fault lies in WordPress updating too soon. As I am on a hosted install of WordPress, I can’t roll back, so now I am stuck. From now on, I will clearly be waiting at least two months before pushing any hosted updates of anything WordPress related! What a PITA!

  8. Pingback: Stop Blaming The WordPress Team »   Weblog Tools Collection » Blog Archive

  9. Michael

    “WordPress is continually pushing updates too often without much in the way of testing with the most popular plugins”

    It isn’t Automattic’s responsibility to test the compatibility of the plugins. It’s their responsibility to test WordPress itself. They already went above and beyond in that they developed the fix and sent the code to the plugin author.
    Testing for compatibility with plugins is the responsibility of the plugin author, and to a lesser degree the community.

    As a WordPress user, it would make sense to wait to upgrade until you’ve confirmed on the forums, plugin pages, etc that all of your plugins will work.

  10. Jason

    I’m not much of a coder, I am a systems admin, know a little bit of html and Windows scripting, and I shoot photography for a hobby. My blog has been a combination of those collective skills and interests. Asking me to take more time to search nout forums for early adopters to see if they’ve had problems with a particular plugin before updating takes away from my already limited time. Since I use only highly popular plugins, there would be a general sense that WordPress (or AUtomaticc I guess, whoever they are) would consider the ramifications of their updates on at least the top 10 3rd party plugins. I don’t have raw numbers, but would guess that podpress is in that list.

    The equivalent would be to say that Microsft bears no responsibiity to ensure updates to their operating systems are compatible with say Linksys routers, Intel processors, or Nvidia graphics cards. Technically, sure that may be right, but from Microsofts perspective, it’s in their best interests (and that of their user base) to at least consider it (and they do!) when pushing out updates. And if it breaks something, it would be helpful to at least acknowledge it, and possibly provide help and/or assistance with workarounds or hotfixes (which they do).

    The reason it’s in their interests? If they started pushing updates that break everything for the user base, guess what happens to that user base – it goes away. Microsofts user base actually has gone away in substantial fashion, partly for this type of mentality. Rest assured, if Automaticc or the WordPress developers continue on this course, some other open sourced venue will step up that fixes these compatibility issues, and ten years from now people will say “Remember WordPress? Wasn’t that a funny abberation of an open sourced community!”

  11. Otto

    The fix for PodPress 8.8 that I posted in the comments on Ozz’s blog does, in fact, work fine. I’ve since tested it myself and it remedied the issue. Many others have also used it successfully.

  12. Michael


    Your analogy of comparing the responsibility of one company making sure their software works with certain popular plugins with that of another company making sure their OS works with certain common hardware is not at all accurate.
    The difference is, WordPress is the primary object, with it’s plugins secondary and completely dependent on it, whereas Windows OS is secondary and dependent to the hardware on which it runs.
    Plugins authors make their plugins to work with WordPress, and Microsoft makes their OS to work with certain hardware, not the other way around for either (and yes I know there are exceptions for both, but that is the general rule).

  13. Jason

    I understand that WP is the core that plugins are, well, plugged into. THat is not in question. Microsoft is a core too, whether you like the OS or not. As such, the core is not required to test its own updates against 3rd party elements whether it’s a plugin for wordpress or a driver for a graphics card. Nevertheless, the premise remains that there are entirely too many updates on the wordpress core – so much that average users cannot keep up to speed with which plugins are compatible and which aren’t.

    IF wordpress wants to issue a cutting edge version every 3 months, fine. Just maintain a stable version. I am not alone in this either, despite your preconceived notions to the contrary, so please spare me the diatribe.

  14. Michael

    Your analogy is still flawed.
    The only practical similarity between WP and Windows should be that you shouldn’t always upgrade right away, without a)paying someone to determine if you’re upgrade-ready and then doing it, b)testing the plugins yourself on a development version, and/or c)check out forums for what others report of their experiences. As a sys admin, you should be well aware that you test out a new platform before implementing it. If the OS your company uses releases a new version that has issues with hardware/software you use, then you either don’t upgrade, develop a fix, or contact the vendor of the hardware/software for a fix.
    Frequent releases are a good thing. Windows is criticized because they don’t release (important and useful) updates often enough. Some people prefer Linux, etc because important (read: security/compatibility) issues are address very quickly, just like with WordPress.
    Check out the stats released by Automattic, the average user doesn’t upgrade right away. Most people don’t have the latest version soon after it’s released. Just like it’s the responsibility of Linksys to make their routers work with Windows, it’s the responsibility of plugin developers to make their plugins work with WP, not the other way around.
    As a software developer, I can tell you that when Microsoft releases a new version of Windows, I have to make sure my code is still compatible with the new platform. If it isn’t, I have to fix it. Microsoft has never contacted me to find out what they can do to make their OS compatible for me.

  15. Jason

    With all due respect to your software development skills, (and I am sure they are just scary awesome), when Windows, Mac, or any major player is planning an update to their OS that is major (or a new OS completely), they give developers betas of the stuff to run through tests so the developers can have updates available for when it is released. I see no indication that WordPress did so with podpress despite its enormous popularity.

    Furthermore, why are you lashing out at me? What did I do to break podpress? Absolutely nothing! I am simply pointing out that perhaps WordPress developers might be a little more cognizant that they are not the only fishes in the pond, and in a sea of open sourced goodness, someone else is likely to come along offering developers of plugins advance notice of updates and patches so as to ensure that not only the core (wordpress) but the peripherals (plugins) have both a stable and development version. WordPress does no such thing.

    Now, for those who are keeping score, he says my analogy is flawed…let me spell it out in simple terms:

    WordPress = Windows
    podpress = Linksys

    If you believe for one minute that Windows (Microsoft) does not give Linksys advance copies of their OS for development testing, you are srely mistaken. Even one look at Adobe and their beta programs for Photoshop, Flash, CS3, CS4, and the entire suite of programs – they have betas we don’t know about, but insiders of the industry have. Then they have Public betas, and then finally a shipped version.

    Then, after all that, about a month or so after the shipped version hits, a last update is made x.1 or x.0.1 or whatever to flesh out the last of the glitches.

    Seriously, look at PS, LR, Flash, and virtually every other incarnation of any software, whether it be a CMS, program, or source kernel, this same pattern can be seen industry-wide. Simple acknowledgement from WP develoeprs that they may want to slow down future releases to let plugin developers catch up would be all that’s needed here, not defensive ego slams. Don’t lecture me on how and when I upgrade – be happy you have early adopters – it’s us that allow the glitches to flesh themselves out. Without the early adopters you would have no user base.

    ‘Nuff said – hopefully the analogy is clearer now…

  16. David Peralty Post author

    I think the biggest issue you are both skipping over is that everyone had advanced beta copies of the WordPress release for nearly a month before it was finalized. Now we are more than a month into the 2.6 code base, and still no update.

    Even worse, Matt Mullenweg himself said they had a fix for 2.6 users and that it hasn’t been committed yet.

  17. Jason

    Really? I didn’t know that plugin developers had an advanced copy, nor that the WP had a fix that had not been committed yet. This significantly changes my perspective on the root problem analysis.

  18. Michael


    WordPress did give them an advance copy.

    If a plugin developer doesn’t take advantage of that, it’s not their fault. Does Windows release early versions for Beta testers as well as for hardware/software developers? Of course. I had Vista many many months before it was released. Not that I write any Windows software that is vital to the Windows community, but still, had I not made sure my software were up to date, Microsoft would neither have held my hand nor received blame for any incompatibilities.

    Many people download the latest development version of WordPress. Some for testing their plugins, some for Beta testing WordPress, some just to live on the edge. You can also keep up with Trac to know what changes have been made and potential changes are being suggested.

    So should Matt hold the hand of plugin developers who are too busy with their professional (paying) lives to always be 100% available for their plugin maintenance? Maybe when 2.7 comes out if All in One SEO Pack doesn’t work I’ll let Matt remind me to fix it. Since obviously it will be Automattic’s fault if I don’t update it.

  19. Jason

    Agreed – as I have since discovered that advance copies were provided and that WP even went so far as to provide a fix for the plugin developer, which I will grant is way above and beyond. I do agree that the onus for the update falls on the plugin developer and not WP – what I was unaware of though was that WP provides an advance copy to these developers. As stated above, this does completely change the context, so my previous comments are mitigated by this information.

  20. David Peralty Post author

    For me, the biggest issue with everything is that the WordPress team provided a fix for PodPress, but it wasn’t committed and released as an interim release because the guy that writes PodPress wants to expand its support for other publishing platforms (Drupal, I think).

    So not only can plugin developers try out nightly versions of new releases, but also beta was out a month before the final version. So there was TONS of time for an 8.8.1 release that works with WordPress 2.6. I think its actually quite shameful that we haven’t seen a release, and I wish that the community would step in, get the fix from Automattic and release an 8.8.1 outside of the normal Mightyseek releases.

  21. Michael

    Well it’s not just that WP provides an advanced copy to developers. Anyone can get it. Many non-developers want to be able to test their site or plugins they use prior to the official release coming out. Some people just like playing with the latest version.
    If a plugin developer doesn’t, that’s on them.
    The fact that Matt and Co. developed the fix for a particular plugin shows just how much they care about the WordPress and Open Source community.

  22. Sahdow

    As one of the people who made a pledge, I think we could get more support if people knew how to get to that page, it’s pretty burried. If it weren’t for the fact I can’t get any of the fixes to work on a couple of installations – I probably wouldn’t have found it.

  23. Carl Thomas

    Can’t someone who knows how to do it just fix the code and fork the project? If the podpress folks decide to fix it the fork could die.

    Also, is there consensus on which fix the average user should use? Is no revisions the answer? I have not upgraded because I cant risk being down.

Leave a Reply

Your email address will not be published. Required fields are marked *