Page MenuHomePhabricator

Saving edits shows preview, next save shows conflict although no recent edit in history
Closed, ResolvedPublic

Description

Author: hardy

Description:
For about the last ten days the following has been happening frequently.

(1) I click on "save page";
(2) It behaves as if I'd click on "Show preview"; it shows the preview and the
editing window;
(3) I click on "save page" again;
(4) It says "Edit conflict";
(5) I hit "back" until I see the page without the edits;
(6) I click on "reload";
(7) I see the page without my edits;
(8) I click on "Page history" and see that no one else has edited the page in
the mean time, so there is no reason to report an edit conflict.

Another sequence has also frequently occurred: after step (6), I see the page
with the edits I entered. That should have appeared after I clicked on "save page".


Version: unspecified
Severity: major
OS: Linux
Platform: PC

Details

Reference
bz1762

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 8:17 PM
bzimport set Reference to bz1762.
bzimport added a subscriber: Unknown Object (MLST).

daniel wrote:

The same happened on my Wiki! I'm running a debian woody system with php 4.1,
mysql 3 and mediawiki 1.4.0. With mw 1.3.11 there was no such problem.

kmp1 wrote:

I had the same problem. The solution found in bug 1819 solved it.

jylee wrote:

I'm getting the same bug on the English Wikipedia right now.

zigger wrote:

(Changed summary to be more specific, based on original report. Restored OS.)

I've been plagued with a version of this bug. When I'm editing in many tabs,
usually doing disambiguation, the saves (alt-s generally) result in previews.
Repeated alt-s or pressing the save button eventually work, but htis is putting
unecessary load on the servers and on me! (This is on Wikipedia BTW). Cheers.
Rich Farmbrough

ajohnston wrote:

Our hosting support at Fatcow sent this, but we still can not save edits when
logged in. Guests can edit and save, but logged in users get the persistent
preview loop.

According to our engineers the php.ini field is left blank. The php.ini looks like:

; Check HTTP Referer to invalidate externally stored URLs containing
ids.
; HTTP_REFERER has to contain this substring for the session to be
; considered as valid.
session.referer_check =

; How many bytes to read from the file.
session.entropy_length = 0

; Specified here to create the session id.
session.entropy_file =

Rich:
Sessions sometimes expire prematurely and the session is reinitialized on the next save attempt.

Adam:

This problem has always been due to incorrect session configuration, usually either:

  • Setting the save path to a directory that didn't exist
  • Setting the save path to a local filesystem on a multiple-server farm
  • Setting some configuration option that caused session data to expire or be ignored

People having this problem are also unable to maintain a login session unless they check the 'remember
password across sessions' checkbox, but for some reason never mention this when reporting the can't-
save symptom.

However if you're not experiencing a problem with edit conflicts, you're on the wrong bug report. :)

bizzaleth wrote:

I'm having the same problem, but no matter what I press it gives me a preview --
I never get the "edit conflict" message.

W wrote:

I am editing en.wikipedia. Has only shown up since last night's software
upgrade. Sometimes requires pressing 'Save' four times. I never get the "edit
conflict" message.

zigger wrote:

See bug 2603 for the 1.5beta "preview instead of save" problem, without the
following conflict originally reported.

ajohnston wrote:

Brion Vibber:
Thanks for the suggestions, but I cant work out how to change the paths. Can
you let me know where the paths are entered?
Thanks,
Adam

(In reply to comment #7)

Rich:
Sessions sometimes expire prematurely and the session is reinitialized on the

next save attempt.

Adam:

This problem has always been due to incorrect session configuration, usually

either:

  • Setting the save path to a directory that didn't exist
  • Setting the save path to a local filesystem on a multiple-server farm
  • Setting some configuration option that caused session data to expire or be

ignored

People having this problem are also unable to maintain a login session unless

they check the 'remember

password across sessions' checkbox, but for some reason never mention this

when reporting the can't-

save symptom.

However if you're not experiencing a problem with edit conflicts, you're on

the wrong bug report. :)

ilyanep wrote:

This appears to have been fixed now, as no such errors show up anymore.

The problem is indeed resolved, a meaningful error message is now given instead
of the described behaviour. There's nothing more we can do about it in
MediaWiki, it's entirely a system administration issue. Closing.