[00:22:08] [1/2] what are the class names for this so I can stylize it, keeps going away too quickly [00:22:08] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543415486681710754/image.png?ex=6a94c92f&is=6a9377af&hm=110843e0f3b2487b07607d2339eea2e80cd587cb7853aebd176fe35a62d1d471& [00:23:41] nvm [00:26:41] How do i reset my wiki [00:27:17] I was listening to a friend on what to do and now i have a bunch of imported wiki templates that dont work properly [00:40:38] [1/2] did a bit more tweaking, nice (this means basically nothing I just like high numbers) [00:40:38] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543420141302194277/image.png?ex=6a94cd85&is=6a937c05&hm=86f807481fa0765f190afa419a893866b376853eb7219c72a75444a041cb9265& [01:18:40] oml THANK YOU NOTARACHAM!!!! [01:25:31] [1/2] having absolutely no syntax is scary [01:25:32] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543431442015715440/image.png?ex=6a94d80b&is=6a93868b&hm=7e80da456ded0a0166003f2ac99c480cbfb19cfd10d67c609c866b6574a68b14& [01:35:26] how did people back then do it??? [01:37:48] Glad to be of help, good luck with rest of wiki cleanup and expansion. [01:38:11] They didn’t [01:38:18] Sintaxe looks so much cooler than syntax [01:38:25] what....... [01:38:50] It’s a mystery how the early coders coded [01:39:13] Punchcards and far too much hand math [01:39:18] omg thank you so much [01:39:20] they were doing random shit and praying they worked [01:39:52] [1/2] Every time I read about early video game development [01:39:53] [2/2] I sweat nervously [01:40:09] Making graphics through code sounds especially obnoxious [01:41:08] they sacrificed their sanity to make progamming much easier for future developers [01:46:01] wait say more [01:46:03] i'm interested [01:46:55] Iunno the exact process. Early pixel graphics had to be created via assigning colored pixels to a grid through code and not a graphic design program [01:47:37] [1/2] When I say old games I mean like this [01:47:37] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543437001460551680/IMG_6269.jpg?ex=6a94dd38&is=6a938bb8&hm=a212fe50b28385eefcc65b77c58719f549d9d30806d0c23df2009e4633a2b197& [01:48:56] wow that sounds painful [01:58:03] had to do that shit in assembly too prob [01:58:08] sounds fun [01:58:43] actually no sometimes I forget how old C is [02:28:34] smallam how long would you last coding without syntax [02:28:48] this is still readable [02:29:08] it's readable but gets confusing fast imo [04:19:47] am i just cooked [04:23:29] You have two routes: manual deletion of the templates or a [[phorge]] ticket for tech team assistance [04:23:30] [04:28:25] Okay! thanks [05:02:23] hi there. [05:04:45] i hope you all be alright. i want to make an zim file out of a wiki that is hosted on miraheze, how can i do that without anubis stopping the progress? [06:59:15] what about already approved, existing wikis with same scope? [06:59:41] [1/3] i noticed these: [06:59:41] [2/3] https://meta.miraheze.org/wiki/Special:RequestWikiQueue/34180 [06:59:42] [3/3] https://meta.miraheze.org/wiki/Special:RequestWikiQueue/63875 [07:02:20] [1/3] both are in use: [07:02:20] [2/3] https://cnmusic.miraheze.org/wiki/Special:Statistics?uselang=en [07:02:20] [3/3] https://cpop.miraheze.org/wiki/Special:Statistics?uselang=en [07:06:08] oh, according to [[CP#Forks]] one of them has to be closed? [07:06:09] [07:12:45] oh sorry i think i misread it. CP says `Nor does it apply to wikis that are in different languages from one another.` one wiki is `Chinese` the other is `Chinese (China)` so ig it doesn't apply [07:17:17] chara: we don't run Anubis. Are you getting an error? [08:32:01] the favored approach is reconciliation, sometimes they have been left alone if there isn't really conflict [08:33:07] although the latter is more of a time prioritization choice than a true lack of basis to reconcile [08:35:27] so global volunteers won't deal with such cases proactively? [08:40:39] Global volunteers have limited time, it's probably better to focus on things that are actively creating issues. [08:41:32] effectively they are dealt with as backlog reports [08:42:03] the priority is indeed low because the actual problem is usually low although wikis that actively create friction or are pretty trivial reconciliations tend to resolve quicker [08:42:55] i see [08:43:11] btw is it possible to make createwiki ai recognize potentially repeated wiki requests? [08:43:33] the two do overlap a lot if you look into it [08:43:36] it is reasonable to make a [[SR/WR]] entry anyway, indeed encouraged in the case of established overlapping wikis because unless it is something as immediate as a just approved wiki that has an obvious conflict, it is probably not an instant reconcillation [08:43:37] [08:45:15] A preferred approach at a glance because the two wikis are well underway is to make them aware of each other and recommend the existence of the other to both [08:46:27] making the ai aware of existing wikis or duplicated requests has been an idea a few times and I forget why it was not feasible enough to bake in, but I recall it would at least involve special work to make it aware of something in a way that isn't trivial by default [08:47:01] although I would still think something like a raw list where hm, there is already a doors wiki, read that request would result in very obvious cases like the doors wiki being reconciled [08:47:23] without necessarily having the ai websearch all live wikis or something similarly intensive [08:48:24] the idea from my primitive understanding would be something like a vector db glued on that can refer to the broader queue which would at least catch more things although there are wildcards like when wikis are changed via sr and phorge with no reflection on the request, but this can trip up stewards as well [08:49:54] I do agree it would be very optimal to hit this at the actual requesting level, and recent changes have made the ai itself more affordable in operation with little slip in quality, so perhaps we have a little room if this is something available to our arrangement. cc @cosmicalpha for thoughts and if maybe a phorge task to this effect would make sense [08:50:06] be it vector db or another approach [08:51:01] I imagine some sort of comprehensive list of wikis and scope could also be helpful for human reviewers too. [08:51:16] But would probably be a nightmare to compile. [08:59:36] maybe it's good maintain a requestwiki form but reflects the wiki's current staatus [09:00:15] including dbname change, scope change, etc [09:27:20] RhinosF1: hm, no, havent tried but thought i have saw anubis somewhere. [09:27:23] i will try [09:27:50] Please try [09:28:12] If you do get blocked by the firewall, PM me with your user agent and ip after a few attempts and I'll look [09:28:18] We can exempt you if you're blocked [09:28:25] thanks a lot. [09:55:53] can we filter recent changes to not show the endless stream of "user creation log"? [10:07:50] One day some kind individual will make a GUI version of PyWikiBot [10:10:56] autowikibrowser? [10:11:48] Something that works on Linux without Winr [10:12:06] And no don't say JWB [10:12:26] Actual hell [10:12:54] I mean [10:12:56] you could just [10:12:58] make it yourself lmao [10:13:11] I was wondering what it would take [10:13:17] jwb is better than nothing [10:13:23] i sometimes have to use it on mobile [10:13:34] Wow [10:13:36] well [10:13:40] depends how far you want to go [10:13:45] JWB is fine for 99% of things [10:13:58] It's just clunky, that's all [10:14:06] And a massive eyesore [10:14:15] the fact AWB uses subversion is enough to put me off [11:01:11] [1/2] I'm trying to get the Disambig part to not be read by the preview but I can't find anything for it in the stuff on text extract [11:01:11] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543576310922748017/image.png?ex=6a955ef6&is=6a940d76&hm=f8abfdc95c155fda0bd7414edc4bfebf70fce160c27c7aa745e2e859a6bb5e41& [11:52:18] syntax is a feature of all languages. "syntax highlighting" is the term you're looking for [11:52:47] also I never use syntax highlighting, although that's a bit of a cheat since I do have vscode [11:53:37] yeah that [11:53:48] why don't you use it thou [11:53:54] performance [11:54:03] also iirc it messes with ctrl+f [11:54:14] what does ctrl+f do [11:55:42] wwr also known as google [13:40:15] wikitext vscode? [13:40:26] is that something one could just enable [13:47:52] [1/2] [[dev:jswikibot]] is an imitation of pywikibot. [13:47:53] [2/2] The whole reason I wrote it was because I really liked pwb generators and filters but there aren't anything like it that can be conveniently run in the browser. [13:47:53] [13:48:27] Very interesting [13:50:01] [13:51:55] oh you mean just editing wikitext in vscode [13:52:34] thought it was something else [13:52:55] there's also some integration with the actual wiki but I don't bother with that [13:53:48] thats cool [13:54:39] maybe it would be helpful for automatically pulling wiki modules [13:55:14] yeah [14:19:02] [1/5] hi! does anyone else experience any ERR_TIMED_OUT when on a wiki? [14:19:02] [2/5] > Loads for a while and then it just gives me an error, doesn't happen with any other site so I don't think it's my WiFi [14:19:02] [3/5] > Same thing happens on my PC [14:19:02] [4/5] - from one of my users [14:19:03] [5/5] https://cdn.discordapp.com/attachments/407537962553966603/1543626100461019156/HQ-dAOIWAAAhE8g.png?ex=6a958d55&is=6a943bd5&hm=eac8e49086e63956ffe3782caed6bec80473a99035149ee4dc912d77d3f3242d& [14:21:34] nope [15:01:41] We can't do this in either this AI or the old AI really, we will be able to when we finish our in house AI though probably. [15:04:05] I feel like if it's ERR_TIMED_OUT it's not directly caused by mh [15:04:16] if it was a timeout between cloudflare -> mh servers cloudflare would show some interstitial page [15:06:41] Can you do a trace route pls [15:21:55] [1/2] hello minerva please center your fucking search bar thank you [15:21:55] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543641927898103858/image.png?ex=6a959c13&is=6a944a93&hm=a9d06011d496fcd674044a4f3d5663f2fc4c658b5d1354abf769a6591789d76b& [15:22:28] > minerva [15:23:10] minerva was never meant to be a serious skin, it was meant to be used on Wikipedia with MobileFrontend [15:23:48] [1/2] yeah I'm aware, I don't care how it looks at larger screen sizes but like [15:23:48] [2/2] cmon you couldnt've at least centered the search bar? [15:30:01] minerva is useless [15:30:05] it's actively missing features [15:30:12] like the settings menu is really dodgy [15:32:02] and this is why you should submit to our citizen overlords [15:32:12] why do you think I made citizen the default skin on WO [15:32:17] out of the box citizen just looks nice [15:32:26] you don't need to customise it really and it is still nice [15:32:42] plus citizen is the only skin I can think of that has really good mobile support [15:33:21] vector 2022 is fine for desktop and I prefer it to vector 2010 but it's pretty poor on mobile [15:33:28] I haven’t really had any issue wit timeless mobile so far [15:33:36] what about responsive mode vector 2022 [15:33:46] I mean vector works but [15:33:48] citizen is nicer [15:33:53] it has that floating thingy at the bottom with all the tools [15:34:02] it's just fiddly to use on mobile [15:35:14] it totally depends on icons on mobile [15:36:26] on mobile citizen you must rely on your muscle memory on pages with non-icon actions such as managewiki and abusefilter [15:36:49] wdym? [15:37:11] tbf abusefilter is pretty poor on mobile in general [15:37:49] in general abusefilter has some pretty poor UX though lol [15:38:07] oh I see what you mean [15:38:14] https://cdn.discordapp.com/attachments/407537962553966603/1543646032213319740/image.png?ex=6a959fe5&is=6a944e65&hm=a858758e612bf90e2178369c89dc4a1a53a6a82195256338614907d32e39697a& [15:38:46] [1/2] you have to remember which is extension and which is namespace [15:38:47] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543646169270587412/image.png?ex=6a95a006&is=6a944e86&hm=987106fd55834e8a6028f567f2b37087009b29aa7c13a5b4c52fa7ee53c8f4e2& [15:38:53] yes i mean that [15:39:00] same to abusefilter and managewiki [15:39:30] I would go patch it but I don't like submitting wmf patches [15:39:32] gerrit is scary [15:39:35] and really confusing [15:40:21] [1/2] minerva shows the tab names [15:40:21] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543646565858811935/image.png?ex=6a95a064&is=6a944ee4&hm=c0ff640d637c0281986aeeed19bc097b4d9be1d98b5cca119b653281e6d5d0ed& [15:40:41] I think it's because citizen is going for the icons first approach [15:40:48] which would work if developers added icons to their actions [15:41:02] [1/2] so is vector-2022 [15:41:02] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543646738311676084/image.png?ex=6a95a08d&is=6a944f0d&hm=cc97ad4c1470a7786e5fb265f0176dbcf0facaf510144d8f2929c77517eb88ff& [15:41:34] maybe managewiki is fine owned by mh. i don't think abusefilter tabs would get icons [15:41:48] and citizen only uses icons from codex afaik [15:42:13] it's not easy to find icons that fit each tab of abusefilter/managewiki either [15:42:40] abusefilter tabs wouldn't get icons because the wmf don't really give that many shits about people downstream unless they patch it themselves [15:42:47] but theoretically it could be patched just to detect citizen mobile [15:47:46] maybe citizen should show beginning few characters as fallback for actions without icons, i just guess [15:48:29] that would probably be more confusing [15:50:39] [1/2] this would be much more understanable than blank buttons [15:50:39] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543649157095497839/image.png?ex=6a95a2ce&is=6a94514e&hm=fa4e9b5068f2356387a62e75677b7616f00102908e9c8282bc8fee307716d94f& [15:57:41] [1/2] implemented for my wiki :alive: [15:57:42] [2/2] Also had to fix one bug with it, if one sorts by new and upvotes/downvotes a comment, commentstreams would still change comment position on the loaded page [16:01:22] i wonder why userprofilev2 doesn't implement a static url for avatars based on userid [16:02:40] it's either avatar_{uid}.png or .jpg (or .jpeg and more?) now. if a static url returns the avatar it would save many requests [16:03:11] adding official avatars support across profilesv2 and commentstreams is like 30 minute work for the extension devs [16:03:12] (requests to try extension names or requests to queryuserprofilev2) [16:04:10] maybe? we're also waiting for a new comment extension to be reviewed by miraheze [16:04:20] which one [16:04:31] https://issue-tracker.miraheze.org/T14569 [16:04:56] it already includes native upv2 avatars [16:05:41] i plan to switch to it from commentstreams as soon as it's approved and deployed [16:06:11] looks very promising [16:16:37] https://github.com/miraheze/ManageWiki/pull/807 should be fixed if this is merged [16:16:47] the icons are limited by citizen but [16:17:16] [1/2] this still looks a whole lot better [16:17:16] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543655855256502442/image.png?ex=6a95a90b&is=6a94578b&hm=bf7ddd8e2c00cc9ffd04ccd3e3b67e1677af8b79dc8a7cca7e79e2a20fe0ec37& [16:17:21] although maybe not the best choice of the flask for core but [16:17:24] I couldn't think of anything better [16:17:33] impressively speedy [16:18:30] do they appear on citizen only on mobile or also on desktop? i like the designs [16:18:34] desktop [16:18:52] I couldn't be bothered to figure out a way to stop it showing on desktop and tbh I think it fits with citizen in a way [16:19:00] yeah [16:19:42] idk if there are other skins affected but [16:19:52] citizen is the main one that I think is used so heavily [16:23:38] only abusefilter is not invited by citizen now [16:23:56] abusefilter is weird [16:26:57] and wikilove is halfly invited (they didn't include the heart icon but it can be fixed with easy css) [16:27:22] [1/3] default vs css fix [16:27:23] [2/3] https://cdn.discordapp.com/attachments/407537962553966603/1543658400548917359/image.png?ex=6a95ab6a&is=6a9459ea&hm=380b36bb9181f4fdfee15df1d4df52d1a965e5a240b43d0a2d6f1f56ca9cdac7& [16:27:23] [3/3] https://cdn.discordapp.com/attachments/407537962553966603/1543658400926277662/image.png?ex=6a95ab6a&is=6a9459ea&hm=e6d0f4500eec360e786cd1c3f491d6a7d8884727535c582e4d7dc768d886853a& [16:27:36] I imagine that's because citizen doesn't load the heart icon [16:27:59] yeah it doesn't [16:29:06] https://github.com/StarCitizenTools/mediawiki-skins-Citizen/issues/1180#issuecomment-3567377204 i mentioned it here [16:29:24] oh i didn't notice this is already closed [16:30:04] citizen is very move fast and break thingsy [16:30:13] I like the skin but it's not the most compatible with some things [16:31:19] Hopefully we can get some feedback from Zippy's users since WO already deploys it. [16:31:30] IBW started using it [16:31:38] not sure if that's a blessing or a curse [16:31:46] it seems fairly stable though [16:31:52] does it have a non js mode? [16:32:14] I get grumpy because it does move many buttons I need to press as steward. [16:32:15] I think you need the v4 token mode for the fix to be applied, and we don't have that yet because of all the compat stuff (which should be dropped at this point now that the parser cache is cleared). [16:32:39] But setting that aside, it's a great skin for newcomers with limited styling experience [16:32:55] isn't there a url param or what to enable it? [16:32:55] If I do get any feedback from them I will try to use my best judgement. [16:33:16] it's the skin for people who don't like normal mediawiki styling [16:33:32] I don't think so. The whole thing is lazily loaded when the user scrolls near the bottom of the page and JS is probably required for that behavior. [16:33:49] I prefer citizen in most cases but tbh I am swinging back to vector '22 now because it's a bit easier to use if you know where stuff is [16:34:00] citizen buries things in extra button presses that are beginning to annoy me more and more [16:35:23] [1/2] seems not [16:35:24] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543660415567794268/image.png?ex=6a95ad4a&is=6a945bca&hm=2d61ced822e7aa294b61d887aa1cc669d6bedf7fe1e5be55a3a846f87dc8a98d& [16:35:45] citizen is still missing the heart icon lol [16:36:03] but good news is the cross-wiki notifications is fixed [16:36:33] btw my wiki does break a lot in citizenpreview=4. good news is i don't need to rush to fix them [16:37:35] tbh I have no idea where icons even are in citizen [16:37:57] vector 22 was awkward on launch but I like it now, at the very least it improves on the limitations of the original vector like being shit on mobile [16:38:17] vector 22 does look cleaner [16:38:21] my comment here shows where the icons were at that time [16:38:29] old vector feels a bit [16:38:32] .com bubble era [16:38:40] yeah but adding it to that json array doesn't change it it seem [16:39:01] oh i thought they definitely have reconstructed them after that [16:39:11] Oh I guess it was closed since the original issues were resolved, not wikilove [16:39:30] once I get my pull of citizen connected to my dev env I will open a pull to fix wikilove [16:39:31] i'm surprised that array exists to now [16:39:47] I need to symlink it in and then fix whatever version incompatibility it causes [16:41:29] speaking of wikilove, its interface seems even older than .com bubble [16:41:55] oh wikilove is so dated [16:41:57] it's like pagetriage [16:41:59] but probably worse [16:42:44] global monobook safemode for you [16:42:56] we do have many ancient things within mediawiki [16:42:58] global vector is becoming really tempting [16:43:05] damn it does an even better job of being shit on mobile [16:43:10] twinkle may be another ancient thing [16:43:18] twinkle needs bringing up to date [16:43:29] on wmf projects I use redwarn or uv instead most of the time [16:43:32] wmf needs to step up their skin game [16:43:33] but for tagging there's still nothing better [16:43:38] citizen is outmogging vector [16:43:38] you DO NOT want a non-js mode [16:43:44] that's how you get outages [16:43:53] how do you get outages from non js modes 😭 [16:44:09] on the other hand, i recently found an amazing gadget on wmf wikis that requires mw1.46 so i can't steal it now [16:44:09] I only add non js modes to things I know raidarr might use [16:44:41] (it can be ported to 1.45 but i prefer to load it instead of fork it) [16:44:44] commentstreams gets embedded into the page HTML, and that's caused numerous outages [16:44:47] [1/6] To expand on raidarr's original comments, forking doesn't always automatically result in closure of one wiki - we assess on a case-by-case basis, some of the criteria we look at to decide on next steps: [16:44:47] [2/6] * Were both wikis created in good faith or is one a spite-fork? [16:44:47] [3/6] * How long have both been operating? Are they both still receiving updates? [16:44:47] [4/6] * How developed is each project? [16:44:48] [5/6] * Is there a case to be made that theyr'e tackling the same project but from different angles? [16:44:48] [6/6] * Is one of the administrators absolutely unwilling to work with the other? [16:44:52] and makes many pages on bc wiki awful to load [16:44:59] commentstreams is not very nice tbh [16:45:00] lazy-loading is so much better [16:46:59] since when did 1.46 require some weird opensearch plugins btw [16:47:00] If you are smart about the parser cache (e.g. cache the entire comment section and invalidate it only when a new comment gets added) it should be fine. Just another cache read. No idea how CommentStreams approaches it though. [16:47:07] 1.45 doesn't need the wmf's weird opensearch plugins [16:47:08] but 1.46 does [16:47:10] so weird [16:47:19] badly! [16:47:34] how about we use the tag extension instead [16:47:52] that way we can all just add on pages where we want comments [16:47:56] and then forget and have to AWB it in later [16:48:08] I will forgive that extension because it's probably 2 decades old [16:49:25] [1/6] i think i can answer some of them. [16:49:25] [2/6] - both are separately created in good faith. the later one just didn't search thoroughly if there's already a wiki [16:49:26] [3/6] - first since aug 2023, second since aug 2025 [16:49:26] [4/6] - first has 56 articles and 6k edits; second has 160 articles and 1.7k edits [16:49:26] [5/6] - no. they both focus on pop chinese music, which is clear from both wiki requests and wiki content. a notable difference is one uses `zh` language the other uses `zh-CN` language [16:49:26] [6/6] - i'm an administrator of the second wiki (not crat or creator). neither our crat nor i am unwilling to work together, but we're afraid they don't even realize the wikis overlapping [16:49:35] [1/2] what is the point of it knowing I meant --all but not running it [16:49:35] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543663987005067334/image.png?ex=6a95b09e&is=6a945f1e&hm=3a911708fb8a936a561ae72c8d68b3f720f916025e2b31b0b6ddb2436c1859a8& [16:49:42] it's not like there was any other thing I could've been running [16:50:50] I'd rather mild inconvenience than programs running commands that I didn't type [16:51:24] Good context. I don't have time to dive in deep, but from first glance at the highlights, as both are substantially developed (albeit the one you're operating to a much larger degree), we'd be most likely to let both wikis continue on their way and notify of existence in the case they want to join forces. [16:51:27] the gadget i mention doesn't even rely on that. it replies on an attribute that was changed in 1.46 bc of parsoid [16:51:36] it was clear I added -all intending to run --all [16:51:43] I couldn't have been intending to run anything else [16:52:05] thank you for your reply! [16:52:20] clear to you, the human running the command [16:52:25] the program itself can only guess [16:52:45] I know but like [16:52:47] it's pretty clear cut [16:52:54] it wasn't a typo it was a missing dash [16:53:18] this is the gadget i want that relies on mw1.46: https://meta.wikimedia.org/wiki/User:Dragoniez/ConfirmLogout [16:53:40] I feel like mediawiki already does that sometimes [16:54:08] click logout [16:54:15] and you'll be logged out [16:54:27] yeah but I've had it before where it goes are you sure you want to log out [16:54:32] I forgot where [16:54:56] enwiki has it that's it [16:54:56] maybe on a wiki with such gadget enabled by default [16:56:01] oh wait I have a script on enwiki in my common.js [16:56:04] that would explain it lmfao [16:56:16] https://en.wikipedia.org/wiki/User:Fred_Gandt/confirmLogout.js seems to be it [16:56:32] not sure why it needs 1.46 because that script has existed since 2014 [16:56:59] this version has a better interface [16:57:47] how can you need a better interface for a button lmao [16:58:09] oh actually I see [16:58:14] [1/2] like this [16:58:14] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543666162984820896/image.png?ex=6a95b2a5&is=6a946125&hm=dacc74a891dab7d8d703686a94c9f1a92619903e98332ea0e95dc0f29b96432c& [16:58:37] [1/2] but you have to remove these to make it work in 1.45 [16:58:37] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543666261760938095/image.png?ex=6a95b2bc&is=6a94613c&hm=d86906cbcd4571b6f3ebf0f2ade2dd68874d8050528c3e7116b349a93367f69d& [16:58:54] i prefer loading to forking so i'm waiting until we update to 1.46 [17:04:21] fair enough [17:04:47] forking stuff isn't really that useful unless you very specifically want one feature that upstream don't have [17:10:17] still would use over the god awful tag [17:10:29] give me better and I will evangelize it [17:10:44] use Yappin lmfao [17:10:50] where is it in managewiki [17:10:51] it is so much better [17:10:55] on WO [17:10:55] not mh [17:11:00] square one [17:11:07] but if it has matured on oasis, good to know [17:11:08] I figured move fast and break things while doing some free bug testing for petra [17:11:14] I forget why but there was some reason we weren't jumping on Yappin [17:11:25] if comments can import into it, even better [17:11:26] it did have a pretty dodgy XSS at one point [17:11:44] I trust WG will get it ship-shape in time, yes. [17:11:53] petra's fork is better than the WG version [17:12:00] the WG version has no import stuff [17:12:11] I'd probably be willing to test it live on the reception wikis right now if the old comments can convert ove [17:12:25] on oasis [17:12:30] I haven't tested importing them [17:12:33] but theoretically it should work [17:12:39] Not qualified to make an assessment, but sounds like it's just very very new, so there's more tires to kick and QoL features to add before we can make the jump here. [17:12:44] that's generally a point of friction that keeps worse extensions alive well beyond their time [17:12:49] For better or worse, MH is definitely more risk-averse. [17:13:00] WO is the bleeding edge [17:13:17] in terms of the actual infra it's probably more reliable than mh because the database doesn't shit itself weekly but the code is very dodgy [17:13:23] in places [17:13:31] which makes it funny how involved I am because I'm usually violently allergic to that edge in software [17:13:40] I don't have the bandwidth to look after all 300 extensions [17:13:48] or at least not as intensely as people do here [17:13:56] I am trying to slowly deprecate useless ones [17:14:03] so that tag one is on its way out [17:14:12] and commentstreams will also be leaving at some point [17:14:23] if it can convert and yappin would hold up I say kill it [17:14:23] SMW is supposed to be dead already and cargo is probably slated for replacement in due course [17:14:36] I prefer yappin over it in terms of UX [17:14:50] if yappin can replace both, works for me [17:15:29] for now on miraheze I am sticking to CS because it is what is available [17:15:37] if yappin becomes available that would likely change quickly [17:16:29] I'm not super familiar with CS but does it have any comment control stuff like yappin [17:16:40] I mean I can delete comments and edit and stuff [17:17:05] can you set per wiki overrides for enabled vs read only vs not enabled [17:17:30] and if deleting comments then child comments aren't pointlessly glued to the last comment posted which is one reason I evangelize over the tag one [17:17:44] if by that you mean not let people comment as a permissions thing then that is a thing [17:18:52] is it per page though? [17:18:57] [1/2] I'd kill or at least throw some money for two extensions to exist in particular though, something that overhauls talk pages to be not a clunky disaster and for better or worse flow was simply a better formula for talk pages, and an extension that streamlines what we do with the SR into a single special-page backed approach where structural patrolling or heaps of template, module, JS [17:18:58] [2/2] glue are not required to have the effect of rfx helper, archiving and so on, and is basically plug, configure, and play for wikis to have a nice usable administrator noticeboard [17:19:02] I know you can probably revoke comments rights globally [17:19:06] CS is managed per namespace and iirc can be disabled per page [17:19:17] It does and is done through a tag on the page, which is easier to automate but impossible to gate with permissions. [17:20:21] by no means do I figure cs is perfect but would I use it over , every time [17:20:22] CS also doesn't have a readonly mode IIRC. The readonly thing was why I did not convert Yappin from the comment control special page to native MediaWiki page protections. [17:20:38] I quite like the read only [17:21:05] I've simply neither used or looked at yappin so if its better in most ways or every way, neat [17:21:28] it's different [17:21:34] but to me it does seem better [17:21:52] I think it has a few features missing and a few better [17:22:26] to me then the difference is if its overall put together different but more sanely in which case I'd see no reason to really recommend cs, or if it approaches differently in ways end wikis have a legitimate interest preferring one over the other in which case I'd advocate case by case and both existing including on oasis [17:23:18] the sole justification I see for is legacy support including its tie to blogpage and socialprofile stuff [17:23:39] both of which at a personal level I'd rather replace with their alternatives anyway [17:24:06] socialprofile is disgusting [17:24:08] [1/2] I think the only problem is that Yappin has way too many LoC for a human review. Claude has done that which uncovered a sec vulnerability. For a human to put in the effort of reading 5k+ LoC would be a huge ask. [17:24:08] [2/2] It's still less than half as much code as CS but still. [17:24:13] it should be wiped off the face of the earth [17:24:37] fellow claude user finding XSS vulnerabilities in Yappin I see [17:26:19] MH should make many more extensions restricted imo. Still waiting for https://github.com/miraheze/ManageWiki/pull/789 though. Maybe I should just implement the popup myself. Idk how CA wants the implementation to be like code-wise though. [17:27:13] [1/3] there are 2 issues I have with SocialProfile tbh [17:27:13] [2/3] number 1 is that it's a wiki not a social network [17:27:14] [3/3] number 2 is that it is so old and shitty that it's not really fit for purpose [17:28:11] do we still have displaytitle, the extension that doesn't do what most people who turn it on hope it does and just confuses things [17:28:24] idk what DisplayTitle does tbh [17:28:43] it like masks names in a way that makes the origin page hard to determine and has only ever been a mess for me [17:28:58] sounds like shit [17:29:11] can't you just use that thing to make the display title on the page [17:29:14] like normal people do [17:29:17] I've always ever turned it off when I had it in a scope where it was appropriate to do so [17:29:18] without having a parser functionf or it [17:29:28] yeah displaytitle as a magic word thing is already built in and what people tend to want [17:29:31] it seems overly complex [17:29:35] but I've seen it just enabled because oo displaytitle [17:29:37] I hate it [17:29:53] if you really want to make your links look proper just do [[Link|with whatever capitalisation you want]] [17:30:08] well iirc it was doing that on stuff like recent changes [17:30:18] you might see my frustration with that [17:30:52] that seems messy [17:31:13] to completely change the title of a page displayed everywhere except the record of the page internally [17:31:23] I can also imagine that messes with a bunch of API access [17:31:53] We do and it's also causing performance problems. [17:32:02] oh good yet another reason [17:32:26] I think with a quick skim of who's actually using it you can probably fast track have it wiped off the map [17:32:38] the fact it obscures pages in a way that is really weird and not very useful is enough of a reason to put me off it [17:32:53] I don't entirely understand the point of it other than to fuck with people trying to find the page [17:33:09] and the description in managewiki is horrible and lends to its confusion [17:41:17] if i select everything in the import log and make the target and parameters hidden does that delete them? thats what it seems like the website is saying but I'm not sure [17:47:28] The page title says delete the log at the bottom says delete and the edit reasons button says delete but the actual options say "hide" [17:47:28] I believe that hides the record of the import rather than deleting the imported page [17:47:41] how do i delete them :< [17:48:18] Visit template page >> delete option on the page itself. 🙁 [17:49:34] [1/2] For a few dozen imports it's not so bad, but if it's in the hundreds, then tech assistance is the way to go as we discussed before. [17:49:34] [2/2] Sorry, imports are a real pain to mass delete [17:57:46] ugh whatever man 😭 [18:49:36] [1/2] would be nice if someone can handle https://meta.miraheze.org/wiki/Steward_requests/Restricted_changes?oldid=560625 [18:49:36] [2/2] i didn't notice that the sr backlog was stacking up... [18:59:17] It was at 36 yesterday, I brought it down to 3. It's not particularly stacking up [19:00:17] iirc [[dev:jswikibot]] has an option for that [19:00:18] [19:01:14] honestly in favour of total undeployment just due to the extension name [19:02:25] Let's bring it to the community via RfF to gather legitimate uses (if they have some), and if there is none, we can undeploy it. [19:02:36] im just trying to figure out how to format tables without ripping from wikipedia [19:03:22] oh our wiki has been using displaytitle [19:04:10] it formats things liketitles including italic substring [19:04:47] [[help:CSS]] [19:04:58] [19:05:23] thank you qwq [19:05:34] [1/3] usages [19:05:35] [2/3] https://cdn.discordapp.com/attachments/407537962553966603/1543698211162824704/image.png?ex=6a95d07e&is=6a947efe&hm=cdb44cd9cafbf2bfd161812802e1f24e4f987d7e1a1da9664bb2d5cad1c9f919& [19:05:35] [3/3] https://cdn.discordapp.com/attachments/407537962553966603/1543698211540308008/image.png?ex=6a95d07e&is=6a947efe&hm=c7d00c4af0484d6794fad93c180efc6c69545b2b72c14ceb30b9b872937660d5& [19:06:50] i'd not depend on this if we don't have the extension from the very beginning but i've done much work on it [19:08:08] hmm how about instead make it restricted, and turn it off for all wikis that use it. then we can reenable it for xyy [19:10:15] As far as I know the big thing we use it for is that links to translated pages display the translated title [19:11:06] well i think it's possible to make workarounds by getting displaytitle with js, but i'm not sure which is worse in performance, compared to the ext [19:11:07] 4th on the entire farm [19:12:54] js means checking almost every single link on a page i think? idk how the ext works [19:13:15] yeah that's basically what the extension does iirc [19:13:38] but if you use `maxage` and `smaxage` it could maybe be more efficient [19:14:07] so maybe disabling the ext also makes wikis with the requirements implement it in another way that also brings fouc [19:14:51] i think the ext also caches [19:15:18] yeah but does it cache between parses [19:15:24] no [19:15:34] sometimes it expires and display plain title [19:15:45] when i have to purge to see correct displaytitle [19:16:26] tbh we removed all manual italic marks for links sitewide after we discovered this ext after we moved from fandom to miraheze, i thought it's a good thing at that time [19:16:39] if someone told me at that time i would not have enabled it either [19:17:34] I think other wikis use templates to properly format stuff. but yeah if that's what your wiki has entirely relied on for years then restricting it is probably the better option than undeploying. It's not like it's got security issues (that we know of), it's just that because nearly 2000 wikis have it its inefficiencies add up [19:18:25] you can't format titles in categories and dplforums with templates [19:18:38] that's what's in my screenshots above [19:19:01] (for other usages, we can simply perform a sitewide replace again) [19:19:41] but it seems dplforums is not optimistic in ext tests recently? [19:20:13] Fart [19:20:19] if i had known this i really would told the myself of one year ago don't use those exts [19:20:46] what do you mean by "this"? [19:21:23] can I crash out about opensearch [19:21:27] that displaytitle may bring performance and other concerns, and dplforum is actually an outdated choice [19:21:34] sure [19:21:38] turns out it doesn't like having 3000 shards on a tiny cluster [19:21:49] well none of us knew, not your fault for not being omniscient [19:21:51] no matter what it will just freeze up and die when I restart the node lmfao [19:22:25] Let's have this be the first and last of this, please. [19:22:28] and then it trips breakers and idk [19:22:32] in general I hate java [19:22:55] I might just leave it and see how it turns out after an hour [19:23:44] oh and ArticleRatings too.. it's thrilling to see all our community's choices turn to break on newer mw [19:24:02] [1/2] the only reason I suggested undeployment was because I thought it was likely that the majority of people enabling it thought it made `{{displaytitle}}` work, or forgot that it was enabled [19:24:03] [2/2] is my experience with displaytitle lmao [19:24:37] you should try being the most active CommentStreams wiki [19:25:18] yeah i also thought it's required for that magic word originally. but after we made it clear we decided to keep it [19:25:27] displaytitle is pretty weird [19:25:44] [1/2] (I do wonder how much we use it on the Rain World wiki actually because what it allows is for any link like ``[[Regions/fr]]`` to display as ``Régions`` but factually most links are actually just ``[[Regions/fr|Régions]]`` and don't need it at all. However many templates rely on ``PAGENAME`` which may only give the expected title with DisplayTitle on. Very unsure, the intrica [19:25:44] [2/2] cies of our translated templates have been too complex for me to keep track of haha) [19:26:10] btw we do have a template for formatting italic links before, but i've been requiring it must be subst-ed since we were on fandom, to avoid template parsing counts [19:26:52] and you know, `[[xxxxx]]` is much easier than both`{{subst:aa|xx}}` and `''[[xxxxx]]''` [19:27:22] that's why we decided to keep displaytitle [19:27:23] glad that the first time I tried translation I saw the mutilated wiki code and immediately went no [19:27:25] ugh im not sure this is what i am looking for [19:27:37] and we expanded its use to things like categories later [19:27:41] css is how you change the look of things [19:29:31] [1/4] Two links I'll recommend depending on what you're trying to do: [19:29:32] [2/4] * https://www.mediawiki.org/wiki/Help:Tables [19:29:32] [3/4] * https://en.wikipedia.org/wiki/Help:Advanced_table_formatting [19:29:32] [4/4] Visual editor can be handy (surprisingly) in quickly generating a table and adding columns/formatting so you don't have to type out the code by hand, too. [19:29:41] VE is great for tables [19:29:56] the table syntax is so poor that VE makes it actually nice [19:30:17] yeah tables and templates with TemplateData are the two things I'd say VE is better than source [19:30:29] If you're still having difficulties, a more specific question towards what you're trying to accomplish will help us better guide you, and if it's complicated, a #support thread is probably the way to go to make sure it doesn't get lost in general chat [19:32:44] i suppose displaytitle is needed for this usage of `{{PAGENAME}}` [19:33:47] maybe they should add a magic word that outputs a page's display title [19:36:41] speaking of magic words i recently got screwed over by `{{#contentmodel}}` which is newly added in mw1.45. i found `{{#switch:{{#contentmodel}}|CSS|JavaScript=xx}}` is not a reliable method for detecting a page's content model when i test in `?uselang=ko`, but the magic word returns content model name in user language. i wonder why they added such a new magic word [19:39:39] oh. i didn't notice it has a param to return canonical content model name when i read the doc again just now😭 [19:40:11] so `{{#contentmodel}}` returns local cm name by default i remember now [19:41:56] infobox [19:42:00] Rosettte [19:42:11] Sorry... [19:44:38] Im trying to search out if any answers have come to my topic. Still not quite about this classic infobox and the code Im using [19:47:26] You can ask @abaddriverlol for the reason for that design decision, though most of us only think about the English use case since we all mainly work on English wikis. [19:51:54] it's alright. i tried to reproduce it just now but failed. maybe it's just the server was unhappy then [19:56:50] (otherwise it combines complicated message localizations that can't be reproduced normally in non-mediawiki ns; anyway i'm not reproducing it now) [19:59:31] actually we only have less than 10 comments now 😂 [19:59:51] i've got more from fandom waiting for yappin to import tho [20:00:51] btw your allcomments script is still working very fine on our wiki, displaying all our comments bc it's too few [20:07:42] This helps thank you qwq [20:09:27] I'm getting confused trying to find templates to replicate and being unable to [20:10:34] [1/2] I'm trying to make an infobox like this and the portable infobox help page says to install a file and put it in a folder (an neither of those things seem applicable at all) [20:10:35] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543714569585692803/image.png?ex=6a95dfba&is=6a948e3a&hm=e2cbd25977221952addcc5cbd10d71c2ec94e92bf846dc06e16c323e0a41f08c& [20:11:52] go to Special:ManageWiki/extensions [20:11:53] originally i tried installing a bunch of wikipedia templates because that is what my friend told me to do but it didn't work so i deleted them all [20:12:36] oh i see what happened [20:12:52] I tried going to infobox builder etc but didn't include special: [20:21:31] The main use case that was presented in the task back then was e.g. editing `MediaWiki:Editinginterface` and showing a message like "You're editing a page" [20:31:16] Yeah, unfortunately it's a common first error to the point that we have an essay about it [20:31:47] https://meta.miraheze.org/wiki/User:Raidarr/Don%27t_import_Wikipedia [20:31:48] it worked really well for my friend [20:31:57] yeah i read it [20:32:59] For simple use cases it can absolutely work, but it can also be a lot of navigating dependency hell [20:43:49] I also think that if you're copying stuff from Wikipedia you are limiting the amount of help you can get from people when things break [20:44:10] I don't speak for everyone but if someone's asking for help with a template and it's copied from Wikipedia there's no way I'm diving into that [20:48:41] if your friend was willing to do all that was necessary to glue things together and maintain it that is one thing, and he would have been more responsible taking a more direct role in setting that stuff up for you because he has screwed you for fairly typical support [20:49:10] the wikipedia template system being pretty much optimized for an omnipresent vast base that actually gets that stuff which was never meant to be very parsable to one person [20:59:19] Maybe i should open a support thread but i dont understand how to implement css style changes with the templates in XML [21:00:16] iirc fandom had a preset template called “character”, does miraheze have the same thing to import? or is that completely different [21:00:36] Mine were just recently transferred over and kept their formatting from a character infobox [21:00:59] from Fandom -> Miraheze (idk if it was reformatted so its kinda a question for that too) [21:05:02] where is the css page for the wiki [21:06:04] Someone in here was helping me figure out my infobox display (classic infobox using wikitext and maybe some Lua). I created an infobox in a Template, and then created a page in my Miraheze wiki to pull in that infobox Template and then declare values. Seems like I dont have errors coming up on my Wiki page that is calling that infobox. So, that is fixed. However, look at the display of that page: https://www. [21:06:04] pasteboard.co/nUp8tiv1wB8n.png ---- is the light grey box (on the right) normal? I ask because nothing contained in that light grey box has to do with the pulled in parameters of that infobox. [21:06:22] The infobox reference text there (located in the source) is : {{Infobox Item Simple|itemifalwaysconsumable=Yes|itemifrenewable=Yes}} [21:15:59] MediaWiki:Common.css, though that takes several minutes to start showing up. [21:16:32] For testing, I recommend putting css changes into your preferences > appearance > custom css location [21:16:44] As that is near-instant [21:25:21] I understand why people just copy wikipedia now ;-; [21:26:45] Is there any way to add categories to image file pages at all? [21:28:05] Yeah, you just edit the page like any other [21:33:04] [1/2] sorry this has probably been asked before but i cant find it, a wiki is normally deleted if it isnt edited in.. a year or so? [21:33:04] [2/2] but if its a wiki for a game for example that's pretty much completed and the game is old and/or will not get updates again, is there a way to request an exception to that rule [21:42:14] I am legitimately so mad rn [21:42:15] Yes, it's possible to request a dormancy policy exemption on [[SR/RC]] [21:42:16] [21:42:49] ooohhh saving that, thank you!! [21:43:31] [1/2] Okay so ive figured out how to use the xml template and css styling but [21:43:31] [2/2] how would i style things like background color on an element on a case by case basis [21:57:17] is this in a template? If so, what does the template look like currently? [22:00:12] [1/5] 1) Preview 2) Code 3) Template 4) css [22:00:13] [2/5] https://cdn.discordapp.com/attachments/407537962553966603/1543742158186610748/image.png?ex=6a95f96b&is=6a94a7eb&hm=7287575951254754fbf9b4990332bda0512a6cc1bfd00cb987b214041dfeb7a2& [22:00:13] [3/5] https://cdn.discordapp.com/attachments/407537962553966603/1543742158467637408/image.png?ex=6a95f96b&is=6a94a7eb&hm=dd3affd8ab8229304bba5f78ef7627d97fd26272162fbed1b4601cb842264c7a& [22:00:13] [4/5] https://cdn.discordapp.com/attachments/407537962553966603/1543742158732009492/image.png?ex=6a95f96b&is=6a94a7eb&hm=368cde7243da8028a7928e15ecf12d707a4332d74cae46e6578450242a0c5c4a& [22:00:13] [5/5] https://cdn.discordapp.com/attachments/407537962553966603/1543742159054704640/image.png?ex=6a95f96c&is=6a94a7ec&hm=ba07d69b257388fc86f9b11f7c914e7505d1251e471a99d0d3cdbe87cdee38da& [22:00:44] and the text-align: center; is doing nothing just ignore that i forgot that was there [22:01:23] currently i was trying to get the header to display the text "description" [22:01:34] but it's showing up as the empty grey rectangle [22:22:24] [1/2] Header doesn't use `data-source`, it is meant to be a static field like `
Information/header` [22:22:24] [2/2] [22:25:32] @/RosetteH Really hard to tell what's going on without knowing what your template is doing but that page doesn't seem to be invoking the template properly [22:27:53] Then how would you edit it as a template [22:28:47] i dont understand :( [22:31:17] If the header is always supposed to read "Description" then put `
Description/header` there [22:31:49] You don't use header as a parameter [22:34:07] okay i see [22:46:28] [1/2] … [22:46:28] [2/2] How does one invoke something in .css to have a background image for light mode and one for dark mode?… [22:49:05] @janebuzjane : Here is the template where Im trying to set up the infobox fields in the first place: https://voxelibre.miraheze.org/wiki/Template:Infobox_Item_Simple [22:50:41] and then here is the page that Im trying to test that page out to call the Infobox Item Simple into things, declare the parameters for those datapoints. https://voxelibre.miraheze.org/wiki/Sandbox_Page I stuck to just posting 2 datapoints to keep things simple until I can progress further. [22:59:42] [1/2] background-image: light-dark(light image, dark image) [22:59:42] [2/2] maybe [23:02:41] Ah, got it [23:02:44] Let me try that [23:04:48] [1/8] if that doesnt work, you can do your light image and then followe it with [23:04:48] [2/8] ``` [23:04:48] [3/8] @media (prefers-color-scheme: dark) { [23:04:49] [4/8] .selector { [23:04:49] [5/8] background-image: dark imaage; [23:04:49] [6/8] } [23:04:50] [7/8] } [23:04:50] [8/8] ``` [23:05:06] In Common.css? [23:05:45] well wherever you're putting this css. if you're just testing i would recommend your user css page or templatestyles if it's for a template [23:06:00] It’s for my Common.css [23:06:02] Or Citizen.css [23:06:18] then just your user css page [23:06:43] it loads instantly rather than waiting however long for common.css/citizen.css takes to load [23:08:10] Ah, got it [23:10:03] well this would only work based on browser preferences [23:10:43] skins like vector 2022 and citizen will have selectors like `:root.skin-theme-clientpref-day`, `...-night`, and `...-os` [23:10:50] a yesyes [23:21:27] Unfortunately, didnt work [23:22:27] which one? [23:24:35] https://cdn.discordapp.com/attachments/407537962553966603/1543763394140573858/IMG_9366.jpg?ex=6a960d32&is=6a94bbb2&hm=59f967dd6d75cc6868e77eede4bb8ae3de6ef96cc58bb3a9a8240301eded1553& [23:24:46] I tried this to @thewwrnerdguy’s suggestions [23:25:07] i think you did :root, rahter than :root. [23:25:17] [1/2] … [23:25:17] [2/2] Oh wait… [23:25:35] Huh [23:25:39] Still doesn’t work? [23:25:47] oh [23:25:54] what are you trying to set the background of [23:26:04] The wiki [23:26:26] @/RosetteH tbh I'm not sure what this module is doing or what the Infobox row template is doing - is this based off of something from wikipedia? Miraheze's dev's Infobox template/module is better: [23:26:48] try `:root.skin-theme-clientpref-day ~ body` [23:26:52] doesnt work like that. root is for variables like setting up `--this` [23:27:15] Oh [23:27:27] you could try `.skin-theme-clientpref-day body` & `.skin-theme-clientpref-night body` [23:27:33] Alright [23:27:35] If you say so [23:27:54] wouldnt you need the sibling selector [23:28:23] Oh wait I did it [23:28:28] But the background sort of broke [23:28:41] ? no [23:28:42] ignore me [23:28:51] https://suppression.miraheze.org/wiki/User:Pale_Zenith/BMC [23:29:07] i recommend using the preview button before saving css [23:31:13] Still broken [23:31:18] The images repeat [23:33:00] Not from Wikipedia. The infobox I was using as a guide can be seen here: https://minecraft.wiki/w/Template:Infobox_item?action=edit [23:34:20] it does [23:34:31] `:root` does the same thing as `html` [23:34:51] tgats surprising [23:34:57] it would be `>`, not `~` [23:35:36] ;-; [23:35:39] [1/4] add 'fixed' after your url [23:35:39] [2/4] then [23:35:40] [3/4] background-repeat: no-repeat; [23:35:40] [4/4] background-size: cover; [23:35:52] [1/2] Uhhh [23:35:52] [2/2] In what order? [23:36:40] [1/3] background: url(...) fixed; [23:36:41] [2/3] background-repeat: no-repeat; [23:36:41] [3/3] background-size: cover; [23:36:57] Ah, I see [23:37:35] [1/2] alternatively [23:37:36] [2/2] background: url(...) center / cover no-repeat fixed; would do it in 1 line, but it's slightly less semantic [23:38:27] --- if you look at how its displayed there you will notice that, on each line, that there are 3 instances of a pipe character being used about 5-6 times. Last night, in this IRC room, it was suggested that the first pipe should be left alone and that maybe the second pipe and on should be replaced by {{!}} . That didnt seem to help, as I still got errors. [23:38:55] i know, somehow i tricked myself into thinking html, head, and body were siblings [23:40:58] Quick question [23:41:09] [1/2] YES IT WORKED [23:41:10] [2/2] GRACIAS MES AMIGAS [23:41:12] [1/2] this image was originally uploaded as a png but its still got a box arouns it I dont want [23:41:13] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543767577732583454/image.png?ex=6a961118&is=6a94bf98&hm=2588e96f09575f1085c5f022935a1108dc3486f724998ac2df3ae26a90aaccbb& [23:41:26] is there a way to fix it? [23:42:05] [1/2] https://cdn.discordapp.com/attachments/407537962553966603/1543767797673238548/image.png?ex=6a96114c&is=6a94bfcc&hm=76935da557857441473d2ccd32fa61bf9ecb167dccf1e2197a9aa827eb9f03bf& [23:42:05] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543767797996322847/image.png?ex=6a96114c&is=6a94bfcc&hm=90edf74e146646c0139c9330c66e9f390bfd9430b126763953dd3d977f234229& [23:42:17] it shows the squares that theres no background too [23:42:36] what's the page [23:43:01] https://officialbetrayed.miraheze.org/wiki/Official_Betrayed_Wiki#Welcome_to_the_Official_Betrayed [23:43:02] this one ^ [23:43:15] even that has no background LOL [23:43:53] [1/2] do you want it to be more like this? [23:43:53] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543768252188991589/image.png?ex=6a9611b9&is=6a94c039&hm=7003b8d933a06587806f77196b8253ca4ecf9e3ed59cb45c9babd23aeaea6f4e& [23:44:10] I just set `background: transparent;` on the `img` element [23:44:24] Ideally yea, id like no background on it [23:44:27] tyvm! [23:45:09] [1/2] this is if you also set transparent background on the `figure` element [23:45:09] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543768567164571689/image.png?ex=6a961204&is=6a94c084&hm=4ff24ff009789f9e6437dbbed6f9e8c3995c0ebededc4b4c521c71a56d9d4222& [23:45:14] how do I make sure its like that for all png images? [23:45:34] oh this is perfect, id just need the border not to be there [23:45:47] you could probably get away with just doing this in common.css [23:46:08] inch-resting [23:46:19] which border [23:46:25] or are you talking about both of them [23:46:34] the box around the image here ^ [23:46:40] that background is pefect [23:46:44] imo they help to separate the image from the caption from the rest of the page [23:47:03] I especially need it fully transparent because I might change some default colors around [23:47:31] [1/2] like this kinda layout ^ [23:47:31] [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1543769167004565554/image.png?ex=6a961293&is=6a94c113&hm=560636dcfc81ef17e1dbee4bf8521ce5f814c2a2dcccf8287e92bf8a194871c8& [23:47:38] anyway, with css you can inspect element and mess around until you get what you want :3 [23:47:54] oh good to know! [23:48:04] I mean at that point don't use `|thumb` [23:48:13] ah gotcha [23:48:16] or `|center` or whatever it is that's causing the caption [23:48:33] I forgot about that icl, but ikwym [23:48:52] [1/2] Hi, can someone help me with this? [23:48:52] [2/2] I'm trying to create a custom tab o edit one. I imported this https://dev.miraheze.org/wiki/Template:Tab, but I don't know what to do now. I tried the "Basic usage", but I got message: "Script error: No such module "Tab"." [23:48:52] Also is this something you can do from here too? [23:48:53] https://cdn.discordapp.com/attachments/407537962553966603/1543769508827766954/image.png?ex=6a9612e4&is=6a94c164&hm=295e331a11bba4fbc452c4ddacba5a9d5bbca1e21924d620a27ca9a304b8a7eb& [23:49:06] or do I gotta do every single one individually based on where it is on the page [23:49:33] I'm not sur ewhat you mean [23:49:48] you can make css that targets all images with captions [23:50:13] gotcha [23:52:48] You already have a support thread open for this; if someone can provide direct help they'll likely do so in your thread [23:53:10] which i just did