Title: 2.9 blocking posts
Last modified: August 21, 2016

---

# 2.9 blocking posts

 *  Resolved [galan05](https://wordpress.org/support/users/galan05/)
 * (@galan05)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/29-blocking-posts/)
 * 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/](https://wordpress.org/plugins/jetpack/)

Viewing 2 replies - 31 through 32 (of 32 total)

[←](https://wordpress.org/support/topic/29-blocking-posts/page/2/?output_format=md)
[1](https://wordpress.org/support/topic/29-blocking-posts/?output_format=md) [2](https://wordpress.org/support/topic/29-blocking-posts/page/2/?output_format=md)
3

 *  Plugin Contributor [Andrew Ozz](https://wordpress.org/support/users/azaozz/)
 * (@azaozz)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/29-blocking-posts/page/3/#post-4656580)
 * [@sbscomp](https://wordpress.org/support/users/sbscomp/) seems some plugin (or
   something) is removing `wp.autosave.local`? If that is really really needed, 
   at least should be done in a compatible way. Or if there is a good user case 
   for it, open a core ticket 🙂
 *  [sbscomp](https://wordpress.org/support/users/sbscomp/)
 * (@sbscomp)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/29-blocking-posts/page/3/#post-4656581)
 * Thanks for the follow-up Andrew. Digging into the code, I find in looking at 
   the code in autosave.js, it appears that the autosaveLocal() function which is
   used to initialize the autosave.local property willa return an undefined/null
   value if the checkStorage() method does not return true (for example, if local
   storage is disabled or otherwise not available).
 * The after-the-dark component of jetpack assumes that this object is always available
   and the method therein is always present.
 * From my read, then, either ATD needs to check for that being present (per my 
   proposed patch), or the core autosave module needs to set a flag which indicates
   that the methods should not proceed but rather act as a noop and return. (full
   disclosure: I’m not a JS guru, I’m a server dev by trade, so there may be a third
   option I’m not aware of).

Viewing 2 replies - 31 through 32 (of 32 total)

[←](https://wordpress.org/support/topic/29-blocking-posts/page/2/?output_format=md)
[1](https://wordpress.org/support/topic/29-blocking-posts/?output_format=md) [2](https://wordpress.org/support/topic/29-blocking-posts/page/2/?output_format=md)
3

The topic ‘2.9 blocking posts’ is closed to new replies.

 * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237)
 * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/jetpack/)
 * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/)

 * 32 replies
 * 13 participants
 * Last reply from: [sbscomp](https://wordpress.org/support/users/sbscomp/)
 * Last activity: [11 years, 11 months ago](https://wordpress.org/support/topic/29-blocking-posts/page/3/#post-4656581)
 * Status: resolved