Can someone transwiki the page metawikimedia:Help:Transwiki to Help:Transwiki and any other helpful pages discussing the Wikimedia transwiki protocol to the MediaWiki wiki? Thanks! Please move this post to an appropriate discussion page if necessary, I was not sure where to post it on the MediaWiki site. Nicole Sharp (talk) 02:19, 14 October 2015 (UTC)
User talk:Quiddity (WMF)
I've added a softredirect to that meta page. AFAIK, a single location is preferred, so that translators don't have to do the work twice, and to prevent slow content-divergences. Also, the meta location is preferred for most wikimedia-specific documentation, whereas Mediawiki.org is for documentation that applies to all re-users of the MediaWiki software. (Though inconsistently, because there are ambiguous areas and edge-cases, plus not everyone agrees. There are various proposals/ideas for fixing (or at least improving) this situation in the long-term.)
Also, just in case, you might also be looking for M:Help:Import.
I wanted to thank you for adding a 'Discussion moving to' summary link to the closed discussion. It is greatly appreciated.
P.S. I ran into a Unable to parse content due to a Parsoid failure while writing to you. I then started testing to replicate the problem, and I accidentally clicked save on a test post. Flow won't let me actually delete my botched save (I pointed out the no-delete design flaw before). So I edited this undeleteable post, and edited the "test" title, to turn it back into my original message.
I spent quite a while testing, but I couldn't figure out exactly what I did to trigger the Unable to parse content due to a Parsoid failure error. I'll give you as much of a report as I can. It started out with this text:
I wanted to thank you for adding a 'Discussion moving to' summary link to the closed discussion. It is ''greatly appreciated.
Note the '' before the word greatly, where I tried to add italics in visual mode. I then switched to Wiki mode, and I thought it odd that Flow put the nowiki tag starting at the apostrophy before the word Discussion. So I made a randomish edit... no clear plan in mind.... I don't recall exactly what I did.... it's possible I left an un-paired nowiki tag. I just wanted to see what Flow would do when I flipped back and forth between Visual and Wiki modes. Each time I flipped to visual and back, Flow re-wrote it differently each time. Flow was applying an unstable round-trip transformation. After about 4 round trips it crapped out with Unable to parse content due to a Parsoid failure.
It's a serious design flaw that Flow constantly translates and translates the content, with no underlying "fixed reality". This is why it keeps mangling stuff. With Talk pages, wikitext is the fixed reality, and it simply gets rendered.
Thanks for these notes, and the new topic at Talk:Collaboration/Workflows. I'm going to be away for the next few days, but will get back to it a.s.a.p.
- Hello, I cannot add a hyperlink to my homepage or my homewiki on my MediaWiki userpage. I receive an error message stating to contact an administrator or my account will be blocked :-o. ~~~~
- Accidental duplicate convo at [user talk:Jasper Deng]. ~~~~
Ah, it looks like Jasper left the note on your talkpage, 2 years ago. You should be fine, given that you're not a spambot!
I'm not sure what error you're encountering, exactly, but it might just be "warning" you, and not actually "stopping" you. Please try to save the edit twice. If that doesn't work (i.e. if the filter is actually "stopping" you from saving the edit), come back here and paste what you'd like added, without the "http" s, and I'll add it for you.
I would also strongly recommend removing the direct email link, that you've currently got there (and at English Wikipedia). You've already got it in your Special:Preferences, hence any editor will be able to use the "Email this user" link in the sidebar, to contact you (that link only appears when editors have a verified email address in their preferences). Otherwise, if you leave it as plaintext, spammers are likely to eventually find the plaintext version and add it to their lists.
Hope that helps.
p.s. this new type of discussion page (an extension named Flow) doesn't require signatures. Let me know if you have any feedback about it - it's part of what I'm working on improving. :-)
I was very confused on the editing format, yes. Very sorry to tell you, but my feedback is that I absolutely hate it. It is confusing, awkward, and next-to-impossible for me to use, sorry :-(. It makes it extremely difficult to copy and paste text from outside sources/wikis and jars my thinking since I like to edit everything in plaintext. ~~~~
I didn't see the date on Jasper's comment. The antispambot must still be preventing users from adding homepage links then. I just tried it again, and it worked this time, no warning, thanks. My e-mail address is already public as plaintext on ICANN WHOIS to spammers so it doesn't really matter where I post it online. Also, I like to have the e-mail link public so if a user is having technical problems or doesn't have a Wikimedia account, they can still e-mail me without needing the MediaWiki interface. ~~~~
Detailed feedback is always helpful, thank you again. :-)
I should add that it is aggravating enough that if it was implemented on all Wikimedia sites, I probably would avoid posting on talkpages altogether.... It should be an option on/off in preferences, with default option off. The beauty of wikimarkup is that it is very easy to archive and crosspost between wikis and it improves the information flow of hypertext (and thus new avenues of thought), whereas rich text defeats that and undermines the purpose of wikitext. ~~~~
If you click the
[] icon in the bottom corner of the text box, it will change into wikimarkup mode, for us people who prefer that. :-) It will also remember the last edit-mode (wikimarkup, or visual editor) that you used to change any text.
Being able to cross-post topics between pages (currently possible with transclusion, but awkwardly), and between wikis (not possible with standard wiki pages), is part of the plan.
There are many things that need to be added/improved/tweaked, and it will hopefully change a lot over time.
Hope that helps, and thanks again.
Flow opt-in questions
- Rollback support needs to be added. This feature request is phab:T93494
- It is not possible to see multiple diffs at once. As Trizek wrote in our other discussion, this is difficult because each post is stored separately.
- How much do you think the task in #3 would solve this? Can Q-bit array give an example use-case where diffs would be needed instead?
- I think this is the feature request at phab:T108407 per our other discussion.
- This bug is phab:T113702
- (script/gadgets and bots)
- For bots that use Pywikibot, there are details at Manual:Pywikibot/Flow about how to easily update.
- For bots using other frameworks, there are comments in this email to mediawiki-api which might help.
Thank you, as always. :-)
phab:T108407 says simply "equivalent, Compare selected revisions" but does not say how it would be. So it's hard to say it will be able to to solve or not.
I've updated the description in phab:T108407 with a detailed explanation of the one suggestion solution. Does that help?
Yes, now more clear. Here are some examples from him:
1) standard function Watchlist "updated since my last visit." They are very convenient for quick viewing of all new posts in the entire page/forum (not only in one topic). - We see all the new and minimum of old. View all at once the discussion / forum is the only way to quickly get acquainted with the situation after a couple of days break. Maybe not so many editors do it, but so do useful active editors.
2) diffs for a few edits are essential as evidence in resolving conflicts. - Users often make 2-5 edits per message, and this message may be done on one or more posts. There is still need to remember that you can hide the Flow posts that probably will not add to the convenience for this case.
your message at test.wikipedia.org
Hi! I noticed [https://test.wikipedia.org/wiki/User_talk:%D7%9C%D7%A2%D7%A8%D7%99_%D7%A8%D7%99%D7%99%D7%A0%D7%94%D7%90%D7%A8%D7%98#An_important_message_about_renaming_users] yesterday and hope you might give me a hand.<br />
[https://test.wikipedia.org/wiki/File:2152085cab.png] shows some buggy red links. I suppose a bug report should be opened on this. Please note that
File:2152085cab.png looks fine
Hi, I'm slightly confused because I think the first link you pasted might be wrong? (It points to a usertalkpage post, from almost 1 year ago)
(Re: this Flow talkpage: To switch between Wikitext and VisualEditor here, click the "</>" icon in the bottom corner.)
Hi! Thanks for enabling Flow at Latvian Wikipedia. Will have feedback later (probably at WT:Flow), but now I have some error. When I try to add description for this page, I get an error "Previous revision identifier is missing". OK, I understand why I could get it (because it is the first version of it), but this should be fixed.
Thanks! Also noticed, that when I try to edit my post (at lvwiki), the "loading" is too long. I waited some 2 minutes, then pressed "Cancel" :(
Re: loading time, Is that a consistently-reproducible bug? (i.e. does it occur every-time) - I've tried just now and it loaded after approximately 1 second.
Perhaps try a hard-refresh (ctrl-F5 in most browsers - or en:Wikipedia:Bypass your cache for details).
Yes, it is consistent. Note: it happens only in Monobook, in Vector it loaded after some 1-2 seconds. Tested with (latest) Firefox, both on Win XP and Win7.
Logged-in with my testing account, I got such errors, but they probably aren't related to this problem.
Use of "addOnloadHook" is deprecated. Use jQuery instead. load.php:156:550 Exception in module-execute in module site: load.php:178:1 TypeError: document.attachEvent is not a function TypeError: document.attachEvent is not a function Stack trace: @https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb line 4 > eval:48:664 .globalEval/<@https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb:4:666 .globalEval@https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb:4:632 runScript/<@https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb:163:126 jQuery.Callbacks/fire@https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb:45:104 jQuery.Callbacks/self.add@https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb:45:656 .Deferred/promise.always@https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb:46:865 runScript@https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb:162:724 execute/</checkCssHandles@https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb:163:638 execute/</cssHandle/<@https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb:163:768 jQuery.Callbacks/fire@https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb:45:104 jQuery.Callbacks/self.fireWith@https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb:46:431 jQuery.Callbacks/self.fire@https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb:46:474 fireCallbacks@https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb:158:1 addEmbeddedCSS@https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb:158:754 addEmbeddedCSS/<@https://lv.wikipedia.org/w/load.php?debug=false&lang=lv&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=3vxc1Hwb:158:191 load.php:178:39 Use of "wgCanonicalNamespace" is deprecated. Use mw.config instead.
I get that error on all pages (e.g. main page) if I use monobook: https://lv.wikipedia.org/wiki/Sākumlapa?useskin=monobook
I asked around a bit, and put some details at W:lv:MediaWiki diskusija:Monobook.js
The last post was mine.
Oh, it looks like, that I can edit posts here. Even in Monobook.
There are some errors happening more at Latvian Wikipedia. Like, when I (in Wikitext mode) try to preview, I got error "Error: One or more dependencies failed to load". So I suppose we (lvwiki and other projects) don't get stable version, but some testing version?
I'm only getting that error on Lvwp (e.g. this works fine: https://ca.wikipedia.org/wiki/Viquip%C3%A8dia_Discussi%C3%B3:Flow/proves?useskin=monobook ) I think it might be related to the error you mentioned above? Let's try again, once that monobook error is fixed. (All wikimedia wikis get the same "master" version, which is always the latest version, following the standard mediawiki weekly release schedule (Wikitech:Deployments/One week) plus any other rapid fixes that need to be deployed during the week)
OK, now it seems fine. Removed this code. Thanks, I also found one more error, that I was looking for, so double thanks :) Would like to "hire" some dev to inspect the code for w:lv:mediawiki:Common.js and skin-specific files. We most probably have some old, unneeded code there. We don't have so tecnical community :)
OK, the last thing, that annoys me. "12 hours ago". At lvwiki, when page is loading, it shows "pirms 12 stundām", which is completely OK. When the page is loaded, it shows "12 stundas agrāk" (not so OK). But I can't find the corresponding Mediawiki message (using uselang=qqx).