User talk:Universal Omega

Temp Interface Admin, deletion privileges, & one extension

Hi User:Universal Omega!

Is it possible to:

• Please get interface admin privileges for a while so I can create (and fix) some of the CSS styles for syntaxhighlighter in Vector's dark mode (I need to fix CSS for nav templates, code boxes, parameter box templates, etc.)?
• Please enable the CharInsert extension? (faster page editing for examples and pages that don't have the nav boxes with copy/paste code).
• Have the ability to delete test pages and empty categories used for testing and setup.

Cheers, and advanced thanks! :)

FrozenPlum (talk) 19:11, 8 September 2025 (UTC)

Darn, I just noticed I'd also need the ability to edit the MediaWiki namespace for a while too, which lets me specify MediaWiki:Edittools values for CharInsert definition, and update the sidebar, etc. FrozenPlum (talk) 19:14, 8 September 2025 (UTC)

Hello, I enabled CharInsert and went ahead and granted you full administrator rights on this wiki. If you need additional rights please let me know. Thank you! Universal Omega (talk) 06:05, 9 September 2025 (UTC)

Awesome, thanks! And yw! FrozenPlum (talk) 06:17, 9 September 2025 (UTC)

Apologies for being a pest, I think to edit MediaWiki:Common.css I do need interface admin rights (editinterface, as it doesn't allow editing of that with the current admin config, nor assigning myself needed rights aside from patrolling etc. My aim is to migrate most styles out of Common.css into templatestyles). The only exceptions may be cross-skin things that can't be put in TemplateStyles, such as color variable declarations for reuse. For now, I'm working in templatestyles mainly, though am encountering clashing declarations that need migrated there. Thanks! FrozenPlum (talk) 00:15, 10 September 2025 (UTC)

This has now been done. I apologize I thought sysop had those rights also but seems not (could have added it to sysop, but just gave you interface admin instead) Universal Omega (talk) 00:52, 10 September 2025 (UTC)

Oh gosh, no worries (so did I)! Thanks! FrozenPlum (talk) 01:05, 10 September 2025 (UTC)

Some thoughts

In principle, a wiki could have a custom namespace called "Main", right? In that case, would namespace=Main include pages from ns:0, or ns:Main? To me, it seems that this is a potential issue with setting "Main" as an alias for ns:0 in DPL, especially since you've marked the "empty string approach" as deprecated. Am I making sense, or am I off base?

I have another question for you, unrelated from the first: I've been trying to write some DPL that, when used on a talk page, will generate a list of archives of that talk page. Here's what I've come up with:

{{#dpl:
|namespace={{NAMESPACE}}
|titlematch={{#titleparts:{{PAGENAME}}}}/Archive %
|format=,\n* [[%PAGE%|{{SUBPAGENAME:%PAGE%}}]]
}}

This selects all the right pages, but the problem is that, in the format parameter, {{SUBPAGENAME:%PAGE%}} gets evaluated before %PAGE% is expanded, so it winds up showing the full titles instead of the subpage names. When I try it with tag syntax instead (<dpl>), the output formatting works properly, but the selection criteria no longer work (I assume they're taken as strings instead of being evaluated as wikitext). Can you think of a workaround? If not, it would be nice if DPL could be updated to include a way to achieve this relatively simple use case.

Thanks for taking the time to read this, and thanks for your ongoing efforts to improve DPL; it's a truly great tool for wikis. :) Mr. Starfleet Command (talk) 04:10, 9 February 2026 (UTC)

Regarding your first point, this was brought in some conversations to me during the development of DPL4 as I had not yet considered it. To handle it I decided that if a namespace actually called Main exists, it does not act as an alias to the main namespace and instead uses its actual namespace.

As for your second question, that is a good point, at the very moment I can't think of a simple workaround for it. I will see what I can do about updating DPL to support it or finding a workaround.

Thank you for the message! Universal Omega (talk) 04:51, 9 February 2026 (UTC)

Regarding the empty string approach being deprecated, that likely won't happen now with this new consideration until or unless I find a reasonable alternative. Universal Omega (talk) 04:55, 9 February 2026 (UTC)