• Resolved kegill

    (@kegill)


    Two different sites — wiredpen.com and wegetdiets.com — are having issues today with saving post drafts. Neither have had a problem until today. Both were updated to 4.1 weeks ago.

    Google yields no forum discussions of a problem with saving drafts on the www.ads-software.com forums for this version of WordPress.

    In both instances, after “save draft” prior to “post preview” the post reverted to an earlier (possibly initial?) state. This behavior also suggests that auto-save is not working. NOTE: the draft and publish buttons are enabled.

    Different themes. Different plug-ins. Both worked until this afternoon. Only common denominators (besides me) is WP 4.1 and SiteGround as the host.

    The tech I spoke to on chat at SiteGround thinks this is a WP problem. I think the problem has to do with writing to the database. Given that nothing in the configuration of either site has changed since both sites were working (most recent post/edit a few days ago on both), the weak link appears to be SiteGround.

    I have sent a tweet to @wordpress. But I’m not convinced that my WP installation is at issue. I don’t see how WP could spontaneously develop a bug.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter kegill

    (@kegill)

    Argh. ??

    Only common denominators (besides me) are WP 4.1 and SiteGround as the host.

    Thread Starter kegill

    (@kegill)

    On a whim, I deleted the Twitter embed code that was the lede for the article in WiredPen. Suddenly, “save draft” works.

    This is the Twitter code:

    <blockquote class="twitter-tweet" lang="en">Someone get me an invite to <a href="https://twitter.com/THISdotcm">@THISdotcm</a> already ????????
    
    — Jessica Reed (@GuardianJessica) <a href="https://twitter.com/GuardianJessica/status/533397678864883712">November 14, 2014</a></blockquote>
    <script src="//platform.twitter.com/widgets.js" async="" charset="utf-8"></script>
    Thread Starter kegill

    (@kegill)

    On a whim, I removed the Twitter embed code that was the lede for the WiredPen article.

    Save draft now works on that installation. The other one didn’t have Twitter code that might lead to a javascript conflict.

    Thread Starter kegill

    (@kegill)

    THIS IS ONE BUG.

    the tweet contained emoji.

    ????????

    When I deleted the emoji from the text of the tweet, all worked.

    This has been reported as a bug with various Twitter plugins. I have not seen a report relating emoji characters with breaking the WordPress “save” feature.

    One down. One to go. But now I know they weren’t related!

    Hi there!

    This bug has been fixed for WordPress 4.2. (See this ticket.)

    Some parts of it will potentially be backported to a 4.1.x release (though it won’t be in 4.1.1). We don’t have a release schedule for that at the moment.

    Thread Starter kegill

    (@kegill)

    Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘WP 4.1 : save draft / auto-save failure’ is closed to new replies.