Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter RAMilewski

    (@ramilewski)

    Ed: I’ve loaded Default 1.7.2 into my WordPress instance and when I preview it I see the problem. It may be that the problem is only triggered with some sidebar configurations.

    Since there’s no telling how many other themes borrowed code from Kubrick and Default over the years, I think the best advice is to strongly encourage people running WordPress blogs to test their sites with a browser that has an HTML5 parser. (e.g. Firefox 4, Chrome 9, Opera 11.5)

    They should do this regardless of which theme they’re using.

    …and if a Forum admin stumbles on this thread, a sticky in the Themes Forum would save a lot of people a lot of heartburn over the next few months.

    Thread Starter RAMilewski

    (@ramilewski)

    Thanks Otto!

    Thread Starter RAMilewski

    (@ramilewski)

    OK… solved it.

    Setting permalinks to “Numeric” and making the tag base archives/tag did the trick.

    Thread Starter RAMilewski

    (@ramilewski)

    WordPress’ refusal to accept the “custom” radio button was caused by my failure to put a closing / on the format.

    Tried:
    /archives/%post_id%/

    WordPress accepts that, but it doesn’t solve the RSS problem.

    Harty,

    If you haven’t already, try posting this over on the Bytes for All Forum. There are some very knowledgeable Atahualpa experts there, and they have been a great help to me in the past.

    Thread Starter RAMilewski

    (@ramilewski)

    Update: I tried setting a custom permalink format of:

    /archives/%post_id%

    …but when I click on the Save Changes button WordPress changes back to the “Numeric” radio button.

    What’s going on?

    Esmi,

    You’re posting the same three steps for this problem everywhere.

    For many of us, they don’t work.

    What’s the procedure when those three steps fail?

    Thanks!

    The problems extend well past Windows/IIS platforms. My Ubuntu/Apache site had been through numerous automatic upgrades dating back to well before 3.0. Even the 2.x to 3.0 auto update went smoothly.

    The 3.1 upgrade splattered it and it’s still down. Attempts at manual upgrades have also failed, and I’ve found nothing in these forums that has been helpful. It was running the latest version of the Atahualpa theme, so it can’t be blamed on an “old” theme.

    I’m about to try a fresh 3.1 install and I guess I’ll rebuild the site by picking all the old articles out of the database backups by hand.

    This is truly ugly, and has severely lowered my confidence in WordPress as a platform. I have another half dozen sites to deal with, but they’re going to stay on 3.0.5 until I’m absolutely sure I understand what’s going so terribly wrong.

    Fixing this appears not to be much less work than moving to a whole new platform. The WordPress folks really should have a tutorial page somewhere with a step-by-step how-to on doing a forensic manual restoration.

    I’ll report back if I learn anything useful doing the rebuild.

    esmi,

    Thanks, but no joy.

    1 – Switching the theme by renaming the current themes folder just results in a blank page, even after trying to force a login.

    2 – Resetting the plugins folder by fiddling the database has no effect. The same No Update Is Necessary page still appears when I try to go to the dashboard.

    3 – Rerunning the upgrade using wp-admin/upgrade.php has the same effect as your second suggestion.

    It appears to be running 3.1 because I can see the new (ugly) admin bar atop the front page. …but it’s pretty useless ’cause there’s no way to add content without being able to get to the dashboard. Choosing anything from the new admin bar just brings up the No Update Necessary page again.

    I ran the auto-update from 3.0.5 to 3.1 and it appeared to work, except that now when I try to log in I get a page that says “No database update is necessary”.

    Any suggestions?

    Thread Starter RAMilewski

    (@ramilewski)

    OK… so the code tag does unexpected formatting here too!

    Form layout should be:

    Label: [---Textbox---]
         [---Submit---]
Viewing 11 replies - 1 through 11 (of 11 total)