Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • It’s not working for me either. Please let us know when you have a fix for the issues posted by Julia and John_NYC. I’d love to use this plug in. Thanks for developing it!

    Thread Starter helzerman

    (@helzerman)

    Thanks Ryan, I tried that. Didn’t work for me, but I understand it does work for others.

    I understand the mod’s point that any number of things can cause an upgrade to go wonky –and I agree. Also agree that problems can be avoided with by doing things without auto installers.

    After spending more time than I wanted to, I decided to go back to the old version, which was good enough for me.

    I still say, it’s something WP should think about. For example, when I checked last, Google came up with over 23,000 returns for the error. Now, let’s say most of those are just discussions. So maybe only 3,000 blogs have that error. Still a lot, right?

    Now, each could have it for a different reason, but isn’t it odd that so many blogs have the same error? And why aren’t the tables being updated?

    I’m not complaining about wordpress, which I quite like, only saying that enough people are having this one particular error (for whatever reasons) that it’s probably worth it for the developers to look into it ahead of the next release.

    In any event –many thanks to everyone for taking the time to help.

    See you all in the next version.

    Thread Starter helzerman

    (@helzerman)

    I’m rolling back to the old version. I’ve already done the upgrade SEVERAL TIMES and you do not get ANY errors. There is no sign anything is wrong until you look at your blog and/or the db tables.

    Not to be cheeky, but if this was just something I happened to do wrong (and I’ve updated a lot of php programs, although I don’t pretend to be an expert) do you think you’d see 20,000+ google results when you search for this error?

    I’m sorry…. but I think that whilst there are still tons of messed-up blogs out there, it is reasonable to suggest that there might be something amiss.

    Thread Starter helzerman

    (@helzerman)

    That’s the thing… I did the upgrade (which “said” it was successful) and then had the errors. Then I tried the force upgrade of the db so that I could make WP run the upgrade script again (otherwise you get the message that the upgrade already ran fine).

    No matter what I do — WP tells me everything went fine yet the appropriate tables do not show up on my database when I check it in phpmyadmin.

    Has anyone come up with a fix for this? Judging by the amount of blogs out there with these errors on the page, I think this would make for a good step-by-step sticky.

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