אני לא יודע אנגלית לכן אני כותב בעברית. אני משתמש בפונקצייה הזו באתר שלא שייך לויקימדיה, היום ניסיתי לשמור עריכה והוא התריע לי על התנגשות עריכה עם עריכה שבוצעה לפני יומיים.
About this board
Triggers without an edit conflict
I'm working on a draft page on the English Wikipedia, more specifically a draft for YouTuber JackSucksAtLife. The issue is that it detects an edit conflict, when there was nothing edited for 3 hours. I just opened up the page and edited it, and then it says that there was an edit conflict. I have no more details. Could someone investigate this?
I'm afraid this is a long known issue with the conflict detection in MediaWiki core and nothing that can be fixed in this extension. Sorry.
How did I get here?
Was reporting AIV and got a message about feedback for a Beta feature.
I like this.
Thank you! We're happy to hear it.
Happy new year from the Technical Wishes team!
On my local dev wiki, the (just installed) feature is broken : I choose thanks to the radio buttons which version I want to keep, but when I click save, the page reloads and every conflict paragraph is highlighted in red. None of the options I chose are memorized. If I start over and try to save again, the same thing happens.
Thanks for your swift response.
I trigger myself the conflict resolution thanks to two separate accounts (since it is my dev wiki) on two separate browsers (I tried a bunch, does not seem to be the cause of it).
I run MediaWiki 1.35.6 on a local EasyPHP dev server (Apache 2.4.25 x86 - PHP 7.4.19 x86 - MySQL 5.7.17 x86).
The error happens whether there is more than one paragraph or just one.
It seems that if I choose the newest, not saved yet, revision, the page reloads with a red "alert" background-color on conflicting paragraphs and deletes all choices.
If I choose the already saved revision, the paragraphs that had conflicts just disappear, but the page is still not saved: the interface shows then only the unchanged paragraphs, which is really weird.
I hear you about the PHP version, but every other extension works perfectly, so that would be odd.
Might be linked to my other extension configurations, I'll try on a fresh install and keep you posted.
That sounds really strange. Sorry, I have no idea. I even went back and tested this older version (it's almost 2 years old by now) and it seems to work fine for me. The error sounds like parts (?) of the POST request are lost. Maybe it's an overly aggressive security or spam protection plugin in Apache or PHP?
Unable to figure out how to use feature
Feature showed my addition with a check and an "X". I clicked the check. I then clicked "Show preview" and nothing happened. I then gave up.
we tested the feature on deWiki and it worked. In order to solve your problem, could you please tell me which page you were trying to edit? And if possible also send a link to the diff of the change you were making? We will then try to solve your problem or figure out why it occurs and get back to you.
These both were additions at the same point in the file, so the conflicting change appeared first on the edit conflict page, followed by my change.
thank you for the details and information. We have reconstructed your problem and indeed found that the interface seems to fail scrolling to the preview part when clicking the "Show Preview" button. Many thanks, for your awareness and your comment! We have created a Phabricator ticket to resolve the issue. You can also follow-up the next steps there.
Extension Failed to Work
When I use this extension on my wiki, i got such errorlog:
VM2235:956 Uncaught TypeError: Cannot read properties of undefined (reading '$ui') at RealtimePreview.isScreenWideEnough (<anonymous>:798:893) at <anonymous>:793:1381 at Object.add (<anonymous>:956:537) at realtimepreview/init.js (<anonymous>:793:959) at runScript (load.php?lang=zh&modules=startup&only=scripts&raw=1&skin=citizen:12:268) at Array.<anonymous> (load.php?lang=zh&modules=startup&only=scripts&raw=1&skin=citizen:12:948) at flushCssBuffer (load.php?lang=zh&modules=startup&only=scripts&raw=1&skin=citizen:4:956)
That's an error message from the WikiEditor extension. I can't tell how this is related, sorry. Maybe you need to update that extension first? What was on screen when this error appeared?
Thanks for the reply, but this is the only error I saw when the issue occurred, and nothing seems to be happening on my backend (including the Nginx logs).Besides my wikieditor is already up to date.
Vagueness of Message
The edit conflict interface doesn't indicate whether forcing one's edit through will preserve the edit by the other user or will wipe out the previous edit. Since it doesn't say that the previous edit will be preserved, I have found it best to temporarily save my edit, and back out from it, and apply it again. If the edit conflict interface is meant to preserve the other edit, it should say so. ~~~~
This makes no sense
I've probably commented here before, but I just got another instance of this and felt compelled to talk about it. Every time I'm dropped into the EC tool, I'm totally befuddled as to how to proceed. I'm a software developer, I'm used to merge conflicts. Every merge conflict tool I've ever used has some way to say, "Keep this version", "Keep that version", "Keep both". I don't see any of that here. I see a box which shows "Conflicting comment", and another box which shows "Your comment", and no indication of how I'm supposed to proceed to select which, or both, I want to keep. I'm going to do what I always do; copy my text, abort the edit, and start again from scratch, pasting in my saved text.
I'll add that edit conflict resolution is something people do rarely. That means they don't remember the details of how the tool worked the last time they used it, so it's got to be totally obvious how things work in order to be effective. The developers who wrote the tool use it all the time, so it's hard to step back and ask themselves, "If I knew nothing about how this worked, would I be able to figure it out?"
I agree, and have been annoyed by this often. If it isn't going to give me useful instructions, why doesn't it just say, "Your edit has been aborted. You can copy it and try again"? ~~~~
I agree—I just bull my way through and seem to get random consequences—as if some critical timing issue picks an outcome with no meaningful interaction on my part. (What request initiated this beta offering what were the goals?
Totally confusing and useless.
The places where edit conflicts happen most are on very long talk pages that handle a multitude of different threads, such as for example the VP or ANI. But wouldn't expect the WMF devs to understand that, would you?
As per [[User:Rober McClenon|Robert]], why doesn't it just say, "Your edit has been aborted. You can copy it and try again"?
By the time one has figured out what to - and still left wondering - it's quicker and easier to copy your text, quit the page, reload it and paste your comment in the fresh edit mode display.
When I was editing on Japanese Wikipedia, there was a display saying "I understand." I think you should change this word. It doesn't work as Japanese.