[03:02:12] why don't copy/pasted hyperlinks in articles automatically become clickable [03:02:22] I gotta go through 100s of these to manually do what every other website does on earth [03:02:38] Where are you pasting them? [03:03:06] Like do you mean you are pasting them into some other non-mediawiki program? [03:03:28] pasting them into a new page [03:03:30] on mediawiki [03:03:40] i have copy transferring over to a new page [03:03:46] but it pastes as plaintext and i gotta redo every hyperlink [03:03:59] If you are using the wikitext editor, they wouldn't be clickable in the edit box because its just a textarea, but would be clickable on save [03:04:04] I have no idea what visual editor does [03:04:37] it does not do that [03:04:42] but the native editor sucks [03:05:02] Which editor is the "native editor" [03:05:13] whatever it is unmodded on a fresh install [03:05:21] i'm using VE now [03:05:27] they both have things that are missing tbh [03:12:06] VE doesn't support copy-pasting from read today because 1) it's using a different parser than generates read view, and 2) it needs more information out of read view than the old one provides [03:12:28] let me find the task if you want to follow it [03:12:42] otherwise, you should copy-paste wikitext almost always [03:13:25] T54091 [03:13:25] T54091: The read HTML should have hinting to allow full DOM copying (as opposed to just rich copying) from read mode into VE surfaces - https://phabricator.wikimedia.org/T54091 [03:13:34] I think, anyway [03:14:49] software is hard, and software built in Javascript the project for which started 13 years ago is harder [03:44:30] Oh hmm, kind of sad that Special:expandtemplates doesn't show a parse profile [03:44:58] like the kind that show up on most pages at the bottom of the HTML // sometimes in other places? [03:46:34] yeah [03:46:50] Be useful when trying to optimize a template for a wiki you don't have write access to [03:48:45] lmao [03:48:52] I understand that feeling. [05:15:36] software is hard, and software built in Javascript the project for which started 13 years ago is harder <-- are you talking about [[commons:MediaWiki:Gadget-ImageAnnotator.js]] by any chance? :D [05:15:45] wait, that [05:15:50] 's even older <.< [05:16:05] :') [05:16:17] no, I was talking about Twinkle clearly [05:16:21] :D [05:17:05] I'm having a bit of an issue getting CentralAuth to work again after moving servers. I have... (full message at ) [05:18:17] If I comment out wgCentralAuthCookieDomain it logs me in but not across wikis. [05:18:27] Orig, should probably tend toward posting a codedump link instead in the future, that long message did not play well with Matrix or IRC [05:18:57] noted — forgot formatting doesn't carry across. my bad! [05:19:02] no, not even that [05:19:15] give me a sec to paste because this keyboard has forgotten what pasting means [05:19:42] oh I can't paste in this chat lmao, same reason of course [05:19:57] this is what showed up on the IRC side: I'm having a bit of an issue getting CentralAuth to work again after moving servers. I have... (full message at ) [05:20:19] crikey [05:20:21] which if you click on it isn't so bad [05:35:39] interestingly if 'wgCentralAuthSessionCacheType' is set to CACHE_DB then it also logs me in but only on the wiki I log in on (which I assume is to be expected) [05:45:42] OriginalAuthorit: IIRC CACHE_DB is local to the current database so it only logs you into that wiki. You need a shared cache across both wikis, typically memcache or APCu [05:46:12] legoktm (@_discord_367157114965327882:t2bot.io) — I believe that's what I was doing in the original message? but that didn't work either [05:47:10] I've done a bit of tinkering and the error now seems to be "No active login attempt is in progress for your session." [05:47:51] my guess is that the wikis aren't talking via the same cache [05:49:32] I just changed 'wgSessionCacheType' => CACHE_ACCEL, [05:49:32] and wgMainCacheType' => CACHE_ACCEL and got the same result hmm [05:55:39] are your wikis hosted from the same server/PHP instance? (aka do they share APCu) [05:57:25] Yeah [06:49:03] Thanks for help earlier , I have setup development environment [06:49:03] I would like to work on this issue : https://phabricator.wikimedia.org/T326905 [08:31:11] Also, Is the wikimedia foundation looking forward to participate in GSoC 2023? [08:31:47] Nikhil61: https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/BYHSBZGGBGZ7S75HU7MQVI34RLMMQ7ER/ [08:33:42] Great!! [08:33:43] Thanks [19:06:33] OriginalAuthorit: did you upgrade MW at the same time or is it only a server move? [19:39:11] مرحبا [19:39:26] هل يمكن تنزيل مقال عن نفسي وتوثيقة [19:39:46] هل تتحدث العربية :) [20:58:28] Did MonoBook have JavaScript search suggestions pre-Vector? [20:59:48] pre-Vector? [21:00:02] Vector didn't even have search suggestions at roll out [21:00:14] IIRC [21:01:49] According to https://web.archive.org/web/20191219002747/https://blog.wikimedia.org/2010/06/15/usability-why-did-we-move-the-search-box/ it did [21:02:01] let's see [21:02:43] because the explicit "Search" button was eliminated and instead you could click the last item in the dropdown to do a full search [21:03:35] I'll let you know what I think of the IA page if it ever loads >____> [21:03:52] but there was https://www.mediawiki.org/wiki/Manual:$wgAjaxSearch which was an "optional" thingy and IIRC never enabled on WMF prod [21:03:53] (btw the second comment on that old blog post is someone asking for fixed width 13 years ago, and then someone replying to them "can you imagine the reaction of the (above) users if they chose to limit the measure of the pages") [21:04:07] legoktm, :D [21:04:23] <3 fresh ideas [21:05:48] > The connection has timed out [21:05:48] > The server at web.archive.org is taking too long to respond. [21:05:53] mildly annoying <.< [21:06:03] heh