When trying to confirm email, I get [1ce279ecfbfd6b7d87c8ff30] 2023-06-07 16:26:48: Fatal exception of type "Wikimedia\Rdbms\DBQueryError"
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Yesterday
Fri, May 26
I also can not create an account myself.
I created an account on beta.betaheze back then, do I still need to create another on test. ?
Why can't I assess beta. ?
Wed, May 24
Yep, that's true.
Tue, May 23
Using visual editor in the Template: namespace?
You shouldn't be using the visual editor in the template namespace.
Wed, May 17
Rhar's exactly what I said earlier. The "Page views in the past 30 days" parameter in the "Page information" page is powered by the Pageviews Analysis, which only works on Wikpedias.
Pageviews analysis is a Wikipedia tool that can’t be implemented on Miraheze.
Wed, May 10
Tue, May 9
May 2 2023
May 1 2023
It's the one with mention, although "echo-subscriptions-web-mention" needs to be set to true first before those will work. It is supposed to be by default though.
Apr 29 2023
You can enable VisualEditor, and do some other cool stuff at Special:ManageWiki/extensions, Special:ManageWiki/settings, etc.
It opens for me and I use Microsoft Edge too. Or maybe, what exactly do you mean by configuration panel?
In T10755#217484, @Agent_Isai wrote:purgeExpiredUserrights.php removes users who are in temporary groups, it does not remove user rights which are no longer registered with MediaWiki.
In T10755#217462, @OrangeStar wrote:@Ugochimobi Sorry, what maintenance script are you talking about?
Apr 19 2023
SRE please run the maintenance script for this. We've seen this in the past and the maintenance script did the job.
Apr 18 2023
TemplateStyles and over 300 other extensions is available for use via ManageWiki
Apr 17 2023
Closing as invalid as it required no SRE intervention.
You can do this on-wiki; https://assurworldbuilding.miraheze.org/wiki/Special:ManageWiki/settings#mw-section-editing and on $wmgWikiLicense select Creative Commons BY-SA-NC 4.0.
Since the wiki's inception, are you the only user with activity?
You can't have a group name be 'tech' and have the MediaWiki message be 'editblacklisted'.
So, @C.Syde65 after the PR has been merged. You can do every other thing on-wiki.
You will create the User group, with the name 'tech' and give it the editblacklisted user right; then create the various MediaWiki interface messages as you stated above, then go to the various namespaces that you want to restrict to this group and on the $wgNamespaceProtection put editblacklisted and save.
This should do what you want.
Apr 14 2023
Apr 12 2023
Apr 10 2023
As long as it's a VALID ISO code, then it should work (I hope I guess right).
I'd suggest you look through this table and check for languages that you think would not be applicable to your wiki, you can borrow their codes and use them for your requested language.
Otherwise, we'll have to remove the ones that aren't working from the config.
In T10714#216047, @Gui7814 wrote:does this mean that it is not possible to add new ISO codes instead of replacing them?
Pretty clear. I think the reason the other four didn't work is that they aren't valid ISO 639-1 language codes.
Previous task: T10711
Expectable behaviour though. According to our Table of all possible two letter language codes only 'et' is assigned to a language, which is Estonian, in simpler words, only 'et' is a valid ISO 639-1 language code.
So, can you check, if the 'et' language code shows you 'Entertidés Lettíno' (your requested replacement) or Estonian (the default)?
Are you using them as Interlanguage links?
Apr 7 2023
In T10704#215874, @BrandonWM wrote:Please enter into ManageWiki/core, and change the site language to Chinese. Also, for future reference, probably better to direct these questions to Discord/IRC as they're not technical issues. If you need any more help though, of course am happy to assist.
You'd have to manually do it from here https://citizenwiki.cn/wiki/Special:ManageWiki/namespaces
Choose the namespace and change the name from English to the preferred language.
Apr 3 2023
Kindly link to the PR, @BrandonWM
Mar 27 2023
It's set to false by default because that's the default from the extension originally, not because it shouldn't be set to true.
Mar 23 2023
I'm closing this as invalid because there was no SRE intervention. Plus, the fact that this was the wrong venue.
Mar 21 2023
Per comments here. T10633#214324
Kindly use the Special:RequestImportDump page on the meta-wiki after you get the XML file from the export wiki.
Per OrangeStar, you can request such an import via the above-linked page in metawiki. Unless it's a considerable dump import, then this task becomes superfluous.
I am closing it as invalid.
I won't advise adding this to ManageWiki; it would complicate things. There's nothing wrong with doing it at the request of users.
Let's not add to the existing workload when we can dodge it now.
In my humble opines tho.
Mar 16 2023
Have you tried enabling Maps from ManageWiki?
Mar 10 2023
Mar 8 2023
You can do this already by going to https://rtp.miraheze.org/wiki/Special:ManageWiki/settings on your wiki >> head to Notiifcation tab >> there you will find a box to input your discord channel webhook. When done you will be notified of all changes that happen on your wiki.
In spite of that, I actioned your request. But please, per BrandonWM, do well to visit the community noticeboard with requests like this.
Mar 6 2023
I actioned this in my GIWA capacity.
Feb 23 2023
As a matter of fact, it looks like the remaining templates that are not appearing in the lists of transclusion for that template are not existing, whereas they are.
SRE: I think the refreshLinks.php needs to be run on the wiki because, after a manual dummy edit to one of the templates the Twinkle_Standard_Installation template is transcluded in, the lists of transcluded pages for that template immediately updated with the template I dummy-edited.
So yeah, maybe refreshLinks.php or something similar would fix it.
Yeah, It was as a result of the rename.
I've done a PR moving all configs for your former name (famepediatechwiki) to become configs for this new name (infopediawiki).
Feb 20 2023
you can enable at Special:ManageWiki/extensions on your wiki.
Feb 17 2023
SRE, I think all this needs is a maintenance script run for the wiki, I remember facing the same issues on my wiki once upon a time.
Feb 14 2023
Oh, right. Then, @Junikea you can enable at the Special:ManageWiki/extensions page in your wiki.
Tooltip is an unmaintained extension and therefore I'm not sure we can install it, although there's an alternative Simple tooltip extension which is currently maintained by Universal Omega and he can probably install that. Check it out: https://m.mediawiki.org/wiki/Extension:SimpleTooltip_(Universal-Omega)
Feb 13 2023
Yeah, it was obviously fixed along the way, probably on maintenance or something.
Feb 10 2023
Feb 8 2023
This error started after making gpcommonswiki the Global File Usage wiki of all my wikis, it literally happens on all three wikis gpcommonswiki, gratisdatawiki, gratispaideiawiki.
This is still very much pending... Any luck @Reception123
R123 always faster :)
Feb 7 2023
Feb 6 2023
Feb 5 2023
Actually, setting `wgMFSiteStylesRenderBlocking` to true would make styles inside MediaWiki:Mobile.css become render-blocking, according to docs.
And unless I am wrong, a render-blocking resource is a portion of code in website files, usually CSS and JavaScript, that prevent a web page from loading quickly.
So I am not sure it does what you want.
Also, this is intended for situations where the TemplateStyles extension cannot be used. If it is enabled, it may increase the time it takes for the mobile site to render, depending on how large MediaWiki:Mobile.css is for your wiki.
This PR https://github.com/miraheze/mw-config/pull/5109 should fix it, after merge.
Feb 4 2023
In T10430#210222, @danielg28 wrote:OK thank you. When will the changes take effect?
I refreshed the browser, cleared the cache. No effects so far.
In T10430#210208, @OrangeStar wrote:True is the default value, yes. This task, however is asking for the value to be set to false in order to use Kartographer's markers instead of OSM's (https://phabricator.miraheze.org/T10430#210082). This is achieved by setting that variable to false. Per settings.js at Kartographer:
// Disable hosted marker functionality if ( !mw.config.get( 'wgKartographerSimpleStyleMarkers' ) ) { L.Icon.Default.imagePath = mw.config.get( 'wgExtensionAssetsPath' ) + '/Kartographer/lib/external/mapbox/images/'; L.icon = function () { return new L.Icon.Default(); }; }This is checking if the variable is set to false.
Feb 3 2023
The latter is wrong, it's supposed to be true, per https://github.com/wikimedia/mediawiki-extensions-Kartographer/blob/7437afb535f20d77a1b1b3f581c4d3c72dfc08eb/extension.json#L585
In T10430#210082, @danielg28 wrote:Sorry, there was an error in my post.
Please add only this line: $wgKartographerSimpleStyleMarkers = '';
The value should be empty . This should display the marker built into Kartographer and not the one from openstreetmaps.
I prefer it when a system administrator assigns it to me :)
Hi there, you didn't give any values, anyway, these configurations are set on our LS.php file already, but we definitely need to update the default values, when this is done, everything should work fine.
Jan 31 2023
It happens miraheze-wide actually. Although I can't vouch for that but, I'm sure of my wikis and many other wikis I've tried it on.
Jan 29 2023
Welp, expect funny behaviour for private wikis.
Jan 28 2023
Oops, it's private, so I can't really access or investigate.
You can do this by yourself. Simple visit https://lustdollplus.miraheze.org/wiki/Special:ManageWiki/settings#mw-section-media and find File Extensions ($wgFileExtensions), click on the box and scroll to find your desired file extension, add them one after the other and save your changes.
Jan 27 2023
In T10378#208994, @Universal_Omega wrote:Swift. T10280
Oh... Why doesn't it?
You mean dump for media files on the wiki? If yes, then you're good to go with using Special:DataDump page too. You can literally generate for pages, files, and managewiki json.
It's way more easier and faster.