Doubling entries

[ddeimeke]

Unfortunately, I have no clue how to reproduce the behaviour. Sometimes I write an article and save (and publish) it, after a few moments I edit something in the article that I forgot and I end up with two (published) articles.

This happens either with drafts and with published ones.

Any idea where this comes from? Autosave?

Serendipity 2.1-alpha1, PHP 5.4.16

[ddeimeke]

I can reproduce it exactly the way described before.

Write an article, save it, keep the edit window open, do some changes and save it again.

[onli]

That should be caused by a javascript error after saving the entry that prevents the id to be set, this code:

Serendipity/templates/2k11/preview_iframe.tpl

Line 58 in c786d45

<script type="text/javascript">$(document).ready(function() {

Next time this happens, could you check your browser js console for errors?

[ddeimeke]

I will try to remember. The problem is, that I only find out about duplicate entries once I click on "edit entries".

[yellowled]

@ddeimeke This has been open for almost two months now – did you remember to reproduce what @onli suggested?

[ddeimeke]

Yes, I tried to, but I never saw the duplicate entry directly after I saved an article. I only recognized them after publishing. In my opinion, the combination of autosave and preview create this issue.

[yellowled]

Xmas issue cleanup – this issue has been open, but without interaction for a while now. Is it still an issue? Has anyone tested or reproduced it? Should/can we close it?

[ddeimeke]

I did not see this behavior for a while now. Maybe you close the issue and I open a new one, once it occurs.

[yellowled]

Makes perfect sense. 👍

[onli]

It occurred again.

I still can't reproduce it in my blog, test or otherwise, but we found a plan how to solve this: The moment the "Create new entry" is generated create a new entry with a proper id. The new part of this is that we could get rid of the javascript which sets the id of the newly generated into the entry editor id. But it is potentially complicated codewise. Investigate.

[yellowled]

@onli Shouldn't this be fixed by the recent changes we made to the backend preview or is this unrelated to the preview?

[onli]

Not unrelated, as it is caused by the JS in the save iframe not working properly. Removing the backend JS could help to reduce this, but fully solved it would only be if we follow the plan described in #340 (comment), or if we find a better solution.

[garvinhicking]

(Should hopefully be fixed)