Support » Plugin: Jetpack by » [Plugin: Jetpack by] 1.3.2 broke JetPack

  • Resolved shrtstck


    Getting an error hidden up top by the WP admin bar, but when I try to access JetPack settings via wp-admin/admin.php?page=jetpack I now get:

    Warning: array_merge() [function.array-merge]: Argument #2 is not an array in (redacted)/wp-content/plugins/jetpack/jetpack.php on line 1207

    Warning: Invalid argument supplied for foreach() in (redacted)/wp-admin/includes/plugin.php on line 1384

    Warning: Invalid argument supplied for foreach() in (redacted)/wp-admin/includes/plugin.php on line 1384

    You do not have sufficient permissions to access this page.

Viewing 15 replies - 16 through 30 (of 39 total)
  • I’m not seeing it here — which Jetpack options are you all using?

    We’re working on a fix now. Thanks for your patience.

    @supernovia – When i reinstall, i should be the initial/start options, right? Can’t change anything before i’ve connected with So no options!

    @michael Adams – Great! Thanks for the response.

    Everything is working fine on my site and JetPack is still capturing hits to pages for stats so I am not deactivating, it seems the only issues I can tell are the error messages on the dashboard.

    I agree JetPack is super flaky but unfortunately it drives my “Most Popular Posts” widget, which is a good one to have

    @michael – THX! Like I said if there is any info I can provide to assist don’t hesitate to ask. Trying to be helpful here and not a whiner 😉

    Everything working on my site again now. Updated to 1.3.3 via FTP.
    Thanx, Michael!!

    I got an error that an arrey was not an arrey…

    The reason these bugs exist is because we’re trying to do make the Stats page (what most want people look at) what you see when you click on the Jetpack+Stats top level menu.

    There’s a bunch of edge cases, though, so we have to be “clever” in how we do it.

    Apparently, we haven’t found all the edge cases because we don’t yet know all the things to test for. We’ve been releasing like mad to try and fix the bugs you report, but it looks like this experiment is at best half-baked, so we’ll probably revert to the old behavior: When you click the Jetpack top level menu, you’ll see Jetpack, not stats.

    Stay tuned.

    I got the warnings after I updated to the 1.3.2 version. I disabled the plugin. Now I see there is a 1.3.3 update but I don’t get an auto-update message in the wordpress admin backend.

    All good now, thanks for the quick response!

    1.3.3 worked for me!
    checked “update” without the auto-update message – it failed (it said it was up to date)…Then it found the new update. Installed and then refreshed the screen. Lokks okay to me.

    Inspired by @mrtomdaly I forced an update and got the same sequence of reaction, first failed, then offered auto-update. All’s well that ends well. Kudos to the JetPack team for prompt reaction.

    JetPack – amazing response! Thank you

    Sounds like most of the issues here are resolved, but there were a couple other bugs this menu madness caused.

    In 1.3.4, we ended up going back to the old behavior for now: Clicking the top level Jetpack menu takes you to Jetpack (not stats).

    So many releases! 🙂 Thanks very much, everyone, for letting us know about these bugs so we could address them quickly.

Viewing 15 replies - 16 through 30 (of 39 total)
  • The topic ‘[Plugin: Jetpack by] 1.3.2 broke JetPack’ is closed to new replies.