[00:00:03] [discord] they closed my phabricator ticket asking them to do it saying that it would be happening automatically in 1.39 or something [00:00:07] [discord] which is incorrect [00:00:32] [discord] (I'm getting ready to do some mass edits and it would be annoying to have to do them twice, lol) [00:00:51] [discord] yea i think it's fine [00:01:12] [discord] I just realized I was never verified [00:01:20] [discord] I forgot how I do that [00:05:05] [discord] with the wikinapbot or whatever its called [00:05:08] [discord] ah [00:05:09] [discord] wikiauthbot [00:05:14] [discord] but nicknamed wikinapbot here [00:07:29] [discord] there we go [00:07:56] [discord] I can't believe it took this long for me to notice I'd have expected someone to say something [00:08:25] [discord] lmao its fine [00:08:39] [discord] Bot usually mentions the command whenever someone joins [00:09:51] [discord] should probably stick a more static message somewhere like #server-info or #rules [00:18:26] [discord] ...Well, I can seemingly no longer use autowikibrowser because logging in just fails now [00:18:54] [discord] ah [00:18:58] [discord] must be some kind of you problem [00:19:01] [discord] jk [00:38:34] [discord] this is a problem because a wave of mass edits is needed [00:38:52] [discord] guess what else doesn't work now: the plugin equivalent [00:39:40] [discord] 'Mass edit using regular expressions' doesn't recognize pages as *existing* [00:41:49] [discord] It's working for me. make sure it's valid regex in the Search For box. start and end with a forward slash: /example/ [00:42:25] [discord] and escape any special characters [00:43:25] [discord] https://cdn.discordapp.com/attachments/407537962553966603/1066518413603774505/image.png [00:44:12] [discord] thats from masseditwithregex? [00:46:14] [discord] I was doing a stupid also [00:46:21] [discord] ended up figuring it out [00:47:12] [discord] but it doesn't do null edits unlike autowikibrowser, that's annoying [00:48:08] [discord] oh i see [00:49:11] [discord] (I'm trying to force a cargo table to populate because it doesn't finish on its own normally) [00:49:25] [discord] (always stops about 20% in) [01:00:19] [discord] https://cdn.discordapp.com/attachments/407537962553966603/1066522668754538587/image.png [01:03:30] [discord] well it did make edits [01:47:35] [discord] woohoo miraheze beat fandom to 1.39 [01:48:30] [discord] I had trouble finding info - is autowikibrowser no longer working on this version of mediawiki a known issue? or is it a miraheze issue or [01:55:51] [discord] indeed very good [01:55:55] [discord] im not sure [01:56:06] [discord] currently everything wrong with miraheze will be insisted to not be a miraheze issue [01:56:50] [discord] miraheze refuses to implement support for webp in multimedia viewer because they insist multimedia viewer will automatically get such support in 1.39 [01:56:57] [discord] it has not got such support automatically [01:57:13] [discord] Masseditregex has limitations that are almost as annoying to work around as just null editing a few thousand pages by hand [01:57:14] [discord] Miraheze never said that [01:57:24] [discord] whoever closed the phab ticket did [01:58:19] [discord] They weren't part of Miraheze, it must be some sort of misunderstanding or something from OrangeStar. They help with config, etc..., but don't represent Miraheze. If it still doesn't work, reopen the task. [01:58:35] [discord] alright got it [01:58:38] [discord] i wil [02:02:32] @Rabby And beat to 1.38 [02:02:38] Beating Fandom with MediaWiki versions isn't hard [02:02:45] They used 1.19 up until 2021. I'm not even joking [02:02:59] Hello Guest15! If you have any questions, feel free to ask and someone should answer soon. [02:04:57] [discord] Anyway, is anyone else having awb issues [02:07:00] [discord] Wow a lot of people are joining at once [02:15:21] [discord] yeah it seems they finally can upgrade mediawiki versions on god [02:19:29] Yeah like I said [02:19:36] Only for Fandom is updating MediaWiki a major event [02:20:58] [discord] I mean it can be a major event for anything if something unexpected breaks from it [02:21:18] [discord] Ideally that shouldn't happen though [02:22:27] [discord] (I am ongoingly annoyed at my abrupt post-update autowikibrowser troubles which have turned this into a major event for my wiki \:P) [02:23:54] [discord] Maybe update AWB? [02:24:16] [discord] It's the latest version [02:24:29] [discord] It thinks it needs to update actually but there's no update available [02:24:55] [discord] Because no update has been released since before I downloaded it [02:26:20] [discord] Can You Put The Imagenes Of Lana Loud Shoes Of The Episdioe Of Love Birds? [02:27:07] [discord] more specifically this is what it says [02:27:08] [discord] https://cdn.discordapp.com/attachments/407537962553966603/1066544511469240371/image.png [02:30:32] [discord] . unless I'm stupid and accidentally ran an old-ass installation [02:31:05] [discord] would be really helpful if it told you what version you were running [02:31:19] [discord] turns out I was not in fact running the latest version [02:31:44] [discord] because I had apparently never switched my start menu shortcut to the newer one or deleted the old folder [02:32:11] [discord] so nvm everyone I'm just stupid ¯\_(ツ)_/¯ [02:35:24] I believe fandom is planning a 1.39 upgrade this year [02:35:34] They are currently on 1.35 [02:35:44] (LTS) [02:36:10] They are on 1.37 [02:36:14] They were never on 1.35 [02:37:23] https://community.fandom.com/wiki/User_blog:Brandon_Rhea/Fandom_will_be_upgrading_to_MediaWiki_1.39_in_2023 [02:37:24] [url] User blog:Brandon Rhea/Fandom will be upgrading to MediaWiki 1.39 in 2023 | Community Central | Fandom | community.fandom.com [02:37:29] Yup 1.39 is planned [02:37:39] [discord] what happens if fandom tries to buy miraheze [02:37:59] [discord] since it likes buying competitors so much [02:38:12] [discord] We're not publicly traded in such a way to allow a forced offer. [02:38:37] [discord] *forced acquisition [02:38:42] Who would they even "buy Miraheze" from? [02:39:00] [discord] (A for profit cannot own a non profit under UK legislation anyway) [02:40:23] Also it looks like Fandom stole my wiki creation design idea [02:40:35] [discord] How so) [02:41:16] I had suggested that instead of requesting wikis on Meta, you would request them on a wiki specifically for that [02:41:16] The RequestWiki page exists on every wiki, but you only have permission to use it on Meta [02:41:16] Can transfer there both to be more organized and to allow more control [02:41:25] CosmicAlpha: Agent: can we please add 1.39 news to the meta main page? [02:41:26] Fandom did this with `createnewwiki.fandom.com` [02:41:30] It's already been done [02:41:35] oh [02:41:53] You know, you could have looked at the main page before saying that :p [02:41:57] MacFan4000: I already did. [02:42:16] Heh [02:42:17] [discord] I don’t believe they “stole” your idea, that was necessary because of technical implementations of how Fandom runs things. [02:42:33] It wasn't necessary, it was done via community.fandom.com for many years [02:42:53] I just closed the phab task [02:42:58] [discord] That was before the update to 1.37 [02:43:15] MacFan4000: no I left it open for a reason. not done. [02:43:17] [discord] Just like changing a wiki settings is done on community central not on a per wiki basis. [02:43:31] Actually, it is [02:43:37] (it is on a per wiki basis) [02:44:07] [discord] Im saying that settings aren’t changed on-wiki for a wiki, they’re changed on Community Central. [02:44:13] I am still doing sql patches MacFan4000, and left it open so I can track it on there. [02:44:29] Community central is a wiki [02:44:38] [discord] You’re not understanding what I’m saying. [02:44:39] And again what does that have to do with createnewwiki.fandom.com [02:45:29] [discord] I’m trying to explain that there are technical implications of how Fandoms set up is that mean that there is a central wiki for requesting wikis, which was switched from Community to its own wiki — they didn’t steal your idea. [02:46:04] [discord] Beg pardon. I have an issue with my wiki not allowing me to edit the Common and Cosmos CSS files. :blobnervouspleading: [02:46:35] [discord] Do you have interface-admin perms? [02:46:48] [discord] Yes, it worked before the update. [02:47:02] [discord] Now I get an error. [02:47:10] [discord] What’s the error? [02:47:38] [discord] https://cdn.discordapp.com/attachments/407537962553966603/1066549673541783552/image.png [02:48:28] copy and paste me the request ID (that random hash of characters) [02:49:05] [discord] 1f0ba24107f4cb42f9b734a3 [02:50:27] "LogicException: This ParserOutput contains no text!" well that's an interesting error... [02:50:35] [discord] :o [03:00:47] [discord] I need some help [03:01:02] [discord] does miraheze able to handle template styles [03:01:45] [discord] Yeah, but you'll need to enable the extension under manage extensions > parser hooks [03:02:20] [discord] okay so basically I want to be able to make templates exactly like the original wiki [03:03:11] [discord] so could you help me plz [03:03:20] [discord] I think it could be better if I asked you in dms [03:04:02] [discord] I'm very new to this and have 0 clue what I'm doing [03:06:35] [discord] what is the original wiki..? [03:06:58] [discord] wikipedia [03:07:05] [discord] oh dear [03:07:08] [discord] so on wikipedai [03:07:12] [discord] when exporting [03:07:25] [discord] check the "include templates" box or whatever its called **but** be very careful [03:07:37] [discord] you can end up exporting hundreds of templates by mistake when exporting from wikipedai [03:08:21] [discord] I'm ngl i do know that but I'm wondering if it is possible to include template styles so I can make the infobox template [03:08:51] [discord] use portableinfobox for infoboxes [03:08:58] [discord] its easier and mobile-friendly [03:09:14] [discord] I'm new to this could you explain [03:09:26] [discord] I'm sorry I don't want to be a bother [03:10:12] [discord] portableinfobox is an extension [03:10:36] [discord] that you can enable in managewiki [03:10:38] [discord] under extensions [03:10:42] [discord] parser functions [03:11:51] [discord] what Pasar functions should I enable [03:11:56] [discord] the one named [03:11:58] [discord] portableinfobox [03:12:19] [discord] got it [03:12:23] [discord] There will also be another named template styles, I strongly recommend enabling that one too since so many other templates rely on it [03:13:00] [discord] yeah [03:13:04] [discord] thank you I will see if it works [03:13:07] [discord] kk [03:13:10] [discord] what does this do [03:13:25] [discord] portableinfobox alone wont fix your problem but it makes it easier to make new infoboxes and to import infoboxes from fandom [03:13:37] [discord] wikipedia infoboxes will have to be solved through templatestyles [03:14:10] [discord] okay so my next question. Is it possible to copy a specific section of the wiki [03:16:19] [discord] im not sure what you mean by that [03:16:48] [discord] like pretty much all the modules needed to run a wiki [03:17:49] [discord] Special:Export on the wiki you want to export from [03:18:04] [discord] could you specify what templates you want and where and what for and i could try to figure it out [03:23:06] [discord] like I need modules to run the infobox template and I would like the modules that you are needed to have to run a sports wiki [03:26:12] [discord] can you [03:26:22] [discord] link the module(s) you want to import [03:26:33] [discord] to you [03:26:33] [discord] or [03:27:19] [discord] in this server [03:28:03] [discord] https://cdn.discordapp.com/attachments/407537962553966603/1066559845064523836/rn_image_picker_lib_temp_a9a5ce8e-2b64-4895-a72b-97027c015f2b.jpg [03:28:13] [discord] i said link [03:28:15] [discord] i cant read that at all [03:29:31] [discord] Page Module:Infobox/styles.css must have content model "Sanitized CSS" for TemplateStyles (current model is "plain text"). [03:30:11] [discord] So the errors about those stylesheets are usually indiciative that you might've done the imports before enabling the templatestyles extension (or that the extension hadn't 100% completed setup yet) [03:30:35] [discord] Special:ChangeContentModel [03:30:47] [discord] This can be fixed by navigating to the special page for changing content model and putting in that exact page name (Module:Infobox/styles.css), then changing as suggested to Sanitized CSS [03:37:53] [discord] is it possible to like purge the templates I've made and start over [03:38:32] [discord] I done f'ed up [03:42:46] [discord] You can do a bigdelete yourself via the Special:Nuke page, aiming for the Template namespace [03:43:14] [discord] But if it gets beyond what you can process yourself, you can always file a request on the Stewards' Noticeboard for a total wipe [03:44:11] [discord] well rn I want to run a sports fantasy world and I want the infoboxes for American football teams, biographies, and such [03:44:43] [discord] but I need the modules to run it [03:49:29] [discord] So, a couple routes you can go: [03:49:29] [discord] [03:49:30] [discord] 1. Attempt to create something like the infoboxes you see on Wikipedia but using the Portable Infobox extension. [03:49:31] [discord] [03:49:33] [discord] The downside - it's a very different structure for how to create them so you can't just directly borrow code from wikipedia [03:49:34] [discord] [03:49:35] [discord] the upside: [03:49:37] [discord] - it doesn't have the dependencies you'll find with wikipedia templates so you won't need to chase missing modules, stylesheets and configuration pages [03:49:38] [discord] - it automatically borrows from and follows your wiki's overall theming, no extra CSS required [03:49:39] [discord] [03:49:41] [discord] 2. Borrow Wikipedia's templates and modules for infoboxes exactly. This doesn't require you to write your own code, but it will require a good few days of debugging and importing what's missing to make the templates work as intended. [03:50:09] [discord] If you do decide to switch to the portable infobox route, we have a near-identical version to what fandom uses, which is nice because that means their boxes work here AND their help documentation works too: [03:50:11] [discord] [03:50:12] [discord] PortableInfobox Main Documentation (fandom) - https://portability.fandom.com/wiki/Portable_Infoboxes [03:50:13] [url] Portable Infoboxes | Portability Hub | Fandom | portability.fandom.com [03:50:13] [discord] Generalized Help Page with Examples (fandom) - https://community.fandom.com/wiki/Help:Infoboxes#Examples [03:50:14] [url] Help:Infoboxes | Community Central | Fandom | community.fandom.com [03:50:14] [discord] Additional Implementation Examples (fandom) - https://portability.fandom.com/wiki/Example_communities#Portable_Infoboxes [03:50:15] [url] Example communities | Portability Hub | Fandom | portability.fandom.com [03:52:16] [discord] another upside to portableinfobox is that its easily mobile compatible [03:52:31] [discord] there are more mobile users than desktop users online [03:55:07] [discord] I'll see what I decide [03:55:13] [discord] sorry for bothering yall [03:56:14] [discord] No worries at all, this is exactly why this channel (and the community) exists. Starting up a new wiki is a lot, but it gets easier! [03:56:32] [discord] Feel free to stop by w/ more questions as you get further in. [03:59:18] [discord] I'm trying my best out here [03:59:48] [discord] I mean I will definitely let yall check it out in the end [04:01:54] [discord] So post-upgrade our category list at he bottom of each article looks like this: [04:01:54] [discord] https://cdn.discordapp.com/attachments/407537962553966603/1066568362676731914/image.png [04:02:08] [discord] As if the styling on it has broken completely [04:02:41] [discord] table styling is broken too [04:02:42] [discord] https://cdn.discordapp.com/attachments/407537962553966603/1066568562443038760/image.png [04:02:57] [discord] It seems isolated to us, I've noticed no similar effects on any other wiki [04:08:13] [discord] Does this persist if you use the 'purge' option under 'more' on a page where this shows up? [04:10:43] [discord] Yep [04:11:11] [discord] It seems to me that it could be a skin related issue, no other skin is doing this [04:14:13] [discord] which skin? [04:14:45] [discord] We're on Medik [04:19:01] [discord] I've heard/noticed it happen on Timeless and Vector also. [04:19:20] [discord] I think it is cache related. [04:26:25] [discord]