WordPress.org

Ready to get started?Download WordPress

Forums

Jetpack by WordPress.com
[resolved] 2.9 blocking posts (33 posts)

  1. galan05
    Member
    Posted 6 months ago #

    When I try to publish, the post merely shifts back and forth between "edit text" and "proofread" modes. Won't publish under any circumstance. Unlike others, my text doesn't disappear when I deactivate the plugin. Once Jetpack is deactivated, the post publishes as per normal. I love Jetpack, but I can't use it anymore until this bug is fixed.

    https://wordpress.org/plugins/jetpack/

  2. wolverineguy7575
    Member
    Posted 6 months ago #

    Hi Galan05,
    I was having the same issue today, I was searching and didn't find anything online. I was trying to schedule while I was in the Text tab. I decided to switch to the Visual tab and was able to schedule the post.

    Hope that works for you as well,
    Scott aka Wolverineguy7575

  3. galan05
    Member
    Posted 6 months ago #

    Hi Scott--

    Tried that, no joy. The only thing that works here so far is deactivating the plugin completely.

  4. conservativeread
    Member
    Posted 6 months ago #

    publicize is broken in 2.9 and I tried to go back to 2.8 and it still don't work and no support either they dropped vers. 2.9 and now we can get any support on these issues. sad

  5. wolverineguy7575
    Member
    Posted 6 months ago #

    I had another issue, I was updating a page not a post and it wasn't allowing me to save in the text screen, but would in the visual but then some of my code wasn't saving so the page didn't look right. I went into Jetpack setting and deactivated the Spelling and Grammar piece and then I could save and update from the text view

  6. conservativeread
    Member
    Posted 6 months ago #

    for me this has been an issue since wp 3.8 I told them but they don't listen there are times when I cant switch between the two tabs there stuck makes it hard to use wp for posting kinda ironic.

  7. galan05
    Member
    Posted 6 months ago #

    Well, when enough users delete Jetpack altogether, maybe they'll listen to that.

  8. geig3r
    Member
    Posted 6 months ago #

    I had this problem and fixed it by unchecking the automatic proofread settings in Users > Edit your settings. Automatic proofread when...

    I didn't have to nuke jetpack.

  9. Brandon Kraft
    Happiness Engineer
    Plugin Author

    Posted 6 months ago #

    Howdy y'all,

    We're tracking this issue and working to isolate the cause and fix.

    In the meantime, you can work around it two ways:
    * Switch to the Visual Editor before publishing or
    * Via Users->My Profile, deselect the option to proofread before publishing/updating (as noted by @geig3r above).

    Thanks for your patience. It isn't happening for everyone (only one of my sites, personally, is seeing this) and seems to be inconsistent across browsers, so thanks again.

    Cheers!

  10. galan05
    Member
    Posted 6 months ago #

    Switching to the Visual Editor before publishing did nothing to help me. Deselecting the proofread option in Edit My Profile did the trick, for now. Prior to that, I encountered this problem on Firefox, Safari and Google Chrome. I don't use Internet Exploder, so I can't speak to that.

  11. geig3r
    Member
    Posted 6 months ago #

    Glad it worked for you galan. Who doesn't hate that sinking feeling of updating and having important stuff stop working.

  12. asiaout
    Member
    Posted 6 months ago #

    My "publish" button does not work after the update

  13. Hussam Al-Tayeb
    Member
    Posted 6 months ago #

    firefox web console says
    TypeError: window.wp.autosave.local.suspend is not a function
    upon failure to update a post.
    Disabling proofread makes updating posts work again.

  14. Brandon Kraft
    Happiness Engineer
    Plugin Author

    Posted 6 months ago #

    Thanks all for your patience.

    We have a fix that we're finishing testing on and look to release an update very soon.

  15. Just so everyone is updated, a patch has gone into Jetpack to fix the issue and there will likely be a point release after some further testing.

    https://github.com/Automattic/jetpack/commit/7cdc9e10580631ca640ed872fcda2f666eb39bcd

    Until the update is released, I recommend disabling After The Deadline to automatically proofread posts before they are published.

  16. Hussam Al-Tayeb
    Member
    Posted 6 months ago #

    I applied the patch to my jetpack 2.9 installation. it fixes the bug. thank you.

  17. Hussam Al-Tayeb
    Member
    Posted 5 months ago #

    I found another problem. this still breaks posts. publishing won't show the current draft.
    Again, disabling proofreading fixes it.

  18. Richard Archambault
    Happiness Engineer
    Plugin Author

    Posted 5 months ago #

    Hussam:

    Did the problem still happen even after you applied the patch?

  19. Hussam Al-Tayeb
    Member
    Posted 5 months ago #

    yes, after applying the patch. It keeps saying there is a stored draft and publishes that instead.

  20. Brandon Kraft
    Happiness Engineer
    Plugin Author

    Posted 5 months ago #

    Thanks, Hussam.

    I'm working on confirming. If you could provide any additional details on how this occurred, please do let me know (editing an existing published post, editing a draft, etc).

    EDIT: I haven't been able to confirm this yet. By "Stored Draft", do you mean the autosave? I've seen the autosave message upon re-editing a published post, but updating works as expected. Still testing.

  21. Hussam Al-Tayeb
    Member
    Posted 5 months ago #

    yes, autosave. sorry.
    And it was a new post. I was writing and pressing publish submit a autosaved draft instead of what I submit.
    I restarted firefox, and it worked on second trial.

  22. Brandon Kraft
    Happiness Engineer
    Plugin Author

    Posted 5 months ago #

    Hussam: I can't duplicate it. My hunch is that since there wasn't a version bump when the patch applied, the browser cache may have been playing some tricks on us.

    Since restarting Firefox resolved it for you, a "natural" update with a version number bump should work as well.

    Going to consider this bug as resolved.

    For everyone waiting, the update should be in the next couple of days.

  23. Hussam Al-Tayeb
    Member
    Posted 5 months ago #

    Ok, thank you very much :)

  24. Brandon Kraft
    Happiness Engineer
    Plugin Author

    Posted 5 months ago #

    Howdy again,

    My apologies for the delay and the trouble with version 2.9. We are uploading version 2.9.1 to the servers now, so you should see an update notice in your WordPress dashboard relatively soon.

  25. soleiltan
    Member
    Posted 5 months ago #

    So with this Jetpack 2.9.1, do I deactivate the old version and delete it and then upload the new version?

  26. Brandon Kraft
    Happiness Engineer
    Plugin Author

    Posted 5 months ago #

    In your WordPress Dashboard, visit the Dashboard->Updates page. You can click the "Check Again" button if the update doesn't appear there.

    You won't need to do anything special regarding deactivating, etc.

    Cheers!

  27. grwinscott
    Member
    Posted 5 months ago #

    Jetpack2.9.1 It has stopped my being able to share my post on Faccebook and prohibits me from viewing my post. I went to another browser and styped in my URL and nothing came up. If I deactivate Jetpack I can view my post, but still no ability to place my post on Facebook with its excerpt. Everything was great last week and then the updates have stressed me out. For 2 days no one could get on my site.

  28. grwinscott
    Member
    Posted 5 months ago #

    Now new readers cannot subscribe with their emails because I had to deactivate Jetpack. It used to be great, please stop updating. Sorry, you can tell I'm stressed to the max

  29. grwinscott
    Member
    Posted 5 months ago #

    Thank you for the fix. I downloaded 2.9.2 this morning. What a relief.

  30. sbscomp
    Member
    Posted 2 months ago #

    I discovered on one of my client sites this evening that the patch above does not completely solve the issue. If the autosave.local object is null, but autosave.server is not, you will still get an exception.

Reply »

You must log in to post.

About this Plugin

About this Topic

Tags

No tags yet.