WP 4.1 Autosave

Hi!

I don’t reproduce this problem with v4.1.

Hi!

I have the Polylang ‘autosave’ problem, too. New to WP, so can’t tell about versions before WP4.1. Clean WP 4.1 install with 3 noticeable changes from ‘default’ install:
(1) WP is installed on a subdomain -> testsite.mainsite.com; there is a different WP instance running on the main site (different WP directory)
(2) I have the SEO plugin “WordPress SEO by Yoast” installed.
(3) In polylang settings, I have changed the Sync-Settings to include:
page template, published date, page order, comment status, post format, featured image, ping status and page parent.

All the rest should be pretty much standard.

When editing pages or posts, flipping back and forth between translations (after proper save/publish) creates an autosave-version despite the proper manual save.

In the pages list/overview for each page there are 2 page entries one with English ‘checked’ and German ‘pencil’ (for the english page) – the German page respectively shows English ‘pencil’ and German ‘checked’. (I guess that is how it’s designed to be, but not sure since I couldn’t find a screenshot in the online help/blog).

Help much appreciated!

Template is twenty fourteen I forgot to mention above.

I did a “compare revision” of the autosave vs. the manual version. – On my WP system, the difference appear to be <p>-HTML tags.

<p>[gallery ids="94,95,96"]</p>

Just for the info, I noticed the issue, too. (WP 4.1, Twenty Fifteen theme)

I did a “compare revision” of the autosave vs. the manual version. – On my WP system, the difference appear to be <p>-HTML tags.

<p>[gallery ids="94,95,96"]</p>

Adding automatically paragraphs is something done by WordPress (not Polylang) for a while

@chouby thanks for double-checking!
However, I have the following thought: If WP created the ‘autosave’ challenge, then the problem would be present even without the Polylang plugin.

— To test the hypothesis, I deactivated the Polylang plugin, and the autosave problem was gone completely. I reactivated Polylang and the problem was there again.

So WP ‘alone’ doesn’t seem to have that challenge (or at least it’s not surfaced). It’s when Polylang is activated, when the autosave-bug becomes active, too.

Is there any information I could provide which would help to triage the cause of the problem?

Meanwhile, I installed Polylang on a completely different site (different hoster, different initial install etc.). Same problem.

I initially misunderstood the issue. Now I am able to reproduce. This is a tricky and not major bug, so will wait for v1.7 to fix it.

@chouby – great! Thank you!

You can test the 1.7beta if you want.
See: https://www.ads-software.com/support/topic/you-can-test-the-beta-version-of-polylang-17