• I’ve updated to 3.5, as have my clients.
    The list so far of issues (with all plugins disabled) is:
    widgets don’t work (dropdowns/widgets don’t work as they should re:drag and drop)
    can’t update posts – issues with blank screens and editors
    menus not expanding in the admin.
    Everything in the front end appears to work for now, though one client is also reporting that her ajax commenting system isn’t working. Doesn’t matter which theme is running, and twentytwelve isn’t working on either server. Switching to 2011, updating fresh (manually) with everything switched off and running 2011 makes no difference.
    Adding the debug line makes no difference.
    As one of the blogs is a bare wordpress install, I’m wondering what’s wrong with the update perhaps?
    Anyone else seeing this behaviour?

Viewing 15 replies - 1 through 15 (of 26 total)
  • Thread Starter Kaiberie

    (@kaiberie)

    And now we’re adding ‘plugins can’t be selected en masse from the tick box at the top’

    Try:
    – switching to the Twenty Eleven theme by renaming your current theme’s folder inside wp-content/themes and adding “-old” to the end of the folder name using FTP or whatever file management application your host provides.

    resetting the plugins folder by FTP or phpMyAdmin.

    – re-uploading all files & folders – except the wp-content folder – from a fresh download of WordPress. Make sure that you delete the old copies of files & folder before uploading the new ones.

    – running the upgrade manually via wp-admin/upgrade.php

    Thread Starter Kaiberie

    (@kaiberie)

    Hi Esmi – done all that – been trying to work though all of the troubleshooting I use to track down holes when hacking too. I’ve even imported a site to clean install and it’s having fits. And this is over two up to date, different servers, both running PHP5.
    The error console is giving me this:
    Uncaught TypeError: Object [object Object] has no method ‘on’ – common.js:167

    Looks like something is wrong with my Javascript on the install?

    Did you try any of the steps I suggested above?

    Thread Starter Kaiberie

    (@kaiberie)

    Yes. I compeltely wiped my themes file, my plugins file, uploaded a clean version of twentyeleven, then wiped everything back to the wp-content and wp-config file and uploaded it all.
    The only bit I didn’t do was the upgrade, because I tried that first when I thought perhaps the upgrade was wrong.
    It’s still giving me that as an error on two of them, even when uploading.

    Kai

    Thread Starter Kaiberie

    (@kaiberie)

    One, we’ve resolved by adding the debug line because she used Bulletproof security IN THE PAST. It’s the oddest thing, and I’m still getting reports in that it’s happening on upgrade – so much so in fact, I’ve told everyone on my server that haven’t to hang fire on upgrading. I trust WordPress implicity, but if it’s producing 20/30/40 tech support tickets for me and I’m a one man hosting company, I’m sure it’s causing a nightmare for lots of people.
    And before anyone suggests it’s my server – it’s spread over several servers at three different data centres. I don’t think any of them are configured exactly the same πŸ™‚

    Kai

    Did you reset the plugins folder using PHPmyadmin?

    Thread Starter Kaiberie

    (@kaiberie)

    No. Because I never enabled plugins on this site. I’d just put it up a couple of days ago. No plugins enabled (but I did delete the contents of the plugin folder).
    Thanks for the suggestions, I’m still poking it.

    That error is still there though, after deleting and copying everything back.

    Kai

    So did you restore another db .sql file to this new install?

    Thread Starter Kaiberie

    (@kaiberie)

    esmi – I’ve ran out of time. I’m going to roll this back until I see a solution to this.
    I can’t afford for my sites to be uneditable, and neither can my clients.

    Thanks for the suggestions, but I’ve gone through just about every variation I can think of to fix this, including doing a clean install and moving my wp-config file. It’s stupid – but that javascript error is still throwing itself up.

    Anyway, thanks. I’ll roll back, i I can, and watch the forums.

    Kai

    Interesting, why would you delete my post when it was just as valid as the many other posts you’ll be reading today regarding the screwy update?

    @lcerura: It is impolite to interrupt another poster’s ongoing thread with a question of your own and it causes significant problems for the forum’s volunteers. Please post your own topic.

    Thread Starter Kaiberie

    (@kaiberie)

    Also, I’m not throwing in the towel to be a pain in the butt and I appreciate all the time you’ve put in, but it’s just something I can’t keep messing with right now. If I turn up anything on my travels, I’ll come back and let peeps know, but otherwise, thank you esmi, and I hope that error might help with people finding what’s going wrong.

    Kai

    Apologies to Kaiberie. Never meant to ‘intrude’ I thought my post was relevant.

    @kaiberie: If you do decide to revisit it, it might be worth poking about in an .sql backup file. My best guess is that Bulletproof security (or another plugin) may have left something in one or more of the tables.

Viewing 15 replies - 1 through 15 (of 26 total)
  • The topic ‘After the update to 3.5….problems’ is closed to new replies.