This user is a MediaWiki enthusiast and third-party wiki system administrator.
Languages: de-N, en-3, fr-1
Based in Berlin, Germany: UTC+1 (CET) / UTC+2 (CEST)
The profile picture is licensed CC BY-NC-ND DE 3.0, my contributions here are licensed CC BY-SA 4.0, and my code contributions are licensed according to the software's license or ISC if the software provides no explicit license information.
How can I find out which skins support this responsive mode? Pretty sure Medik does not, which is why I set the following in the "LocalSettings.php" file:
$wgDefaultUserOptions['skin-responsive'] = 0; $wgHiddenPrefs[] = 'skin-responsive';
This assumes that no skin supporting this mode is installed for the wiki.
Thanks a lot for fixing the issue. My wiki logs are silent now.
MariaDB [DB99093932820210211]> show create table searchindex; +-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Table | Create Table | +-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | searchindex | CREATE TABLE `searchindex` ( `si_page` int(10) unsigned NOT NULL, `si_title` varchar(255) NOT NULL DEFAULT '', `si_text` mediumtext NOT NULL, UNIQUE KEY `si_page` (`si_page`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci | +-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 1 row in set (0.000 sec)
I looked for the offending page in the database with SELECT * FROM page WHERE page_id = 3380;and got the following result:
I also observe this error on 1.40.1. I’m not completely sure, but it seems to appear when the (default?) skin in not Vector
I suggest to revert the change. This issue is spamming my logs day by day.
I think that arraymap and arraymaptemplate will never make it to ParserFunctions. I suggest moving them to the Arrays extension.
I got the same issue when I was on REL1_39 for Mobile Frontend—some version of February or April 2023. After updating to the latest revision on REL1_39, everything is working as expected again.
Was "rebuildLocalisationCache.php" running for a specific language or all?
Is this issue persistent?
Fantaxtic! Thanks for both resolving the issue and making the changes available in the supported branches. I really appreciate your efforts.
@Ammarpad It appears that nobody detected your patch set yet. Do you happen to know how is working on email integrations to MediaWiki? Probably that person will be able to check your patch set.
I was just about to report this, too.
Awesome! Thanks a lot!!
Cool, thanks a bunch. I will give this a shot by going to the page table. Hopefully, it is just this one page.
Thanks a lot! Perfect!
This is still an issue for the extension's version (REL1_35), which is meant to work with MediaWiki 1.35.x. I have not tested 1.39.x yet.
Is there any way to figure out which page is / which pages are causing the issue?
@Ammarpad Thanks for your insight and for providing a patch for the issue. This is much appreciated. I am puzzled that I seem to be the first to experience the issue. I would have thought this is likely to happen more or less frequently. Well, sometimes ... :)
It could be that there is also a misconfiguration or a too-aggressive configuration of the relaying server at play. I cannot tell, though.
@Tgr Thank you for extending the release notes and for your tip about web editing with Gerrit. I was not aware at all that this is possible. I was a bit in a hurry yesterday which is why I was not able to continue getting the patch done. :|
Somehow I get many errors when submitting the patch to add a note about this extension to the release notes. It would be cool if someone on this task could do it. Thanks.
Self answering. I just downloaded the 1.40.0 zip, and it is there. I updated the docu and will create a pull request to add this info to the release notes.
Hmm, is this extension bundled or not? On its page on mediawiki.org is still marked as a beta with no information about it being bundled. Moreover, the release notes of MW 1.40, this part got me asking here, do not mention it: https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/REL1_40/RELEASE-NOTES-1.40#35
When it comes to the open tasks for the extension, they should probably be relabeled as Core tasks.
Documented that this extension is in Core starting with MW 1.4.0: https://www.mediawiki.org/w/index.php?title=Extension%3ARenameuser&diff=6014662&oldid=5986186
Still happening on
Ships with version 2.0.0 Thanks @cicalese for the fix!
@Harej Thank you for your effort and for promoting my account to admin. However, as expected, this does not help at all.
The extension Purge was forked an updated in the meantime. The code is at https://github.com/AlPha5130/mediawiki-extensions-Purge/ When searching for SkinTemplateNavigation no result was shown. @Jdlrobson Will be nice if you could do a second check to confirm. However, marking this one as done already.
No idea. Have not seen it in a while. We can still reopen if it continues to happen.
I believe the rationale for closing this task should end up as a comment. Not sure why the task description was changed. PS Nothing against closing this one.
Thanks a bunch for the feedback. I assume this issue can be closed now.
I cannot tell. Not sure which wiki I reported this for. Let's close for now. It can still be reopened.
@Aklapper It would be fantastic if you could get somebody from the database team just to comment if such a check already exists in newer versions of MediaWiki. If not, it will also be nice to get an assessment if it is feasible to have the check, thus making this a feature request. Thanks a ton.
Three years later, Google finally also pointed to this issue.
FYI This is still an issue with MW 1.35.x, but I found a solution for Strato users. See the linked thread from the task description. :)
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/40
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/39
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/38
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/37
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/36
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/35
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/34
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/33
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/32
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/31
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/30
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/29
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/28
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/27
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/26
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/25
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/24
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/23
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/22
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/21
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/20
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/19
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/18
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/17
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/16
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/15
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/14
Transferred to GitHub: https://github.com/SemanticMediaWiki/SemanticDrilldown/issues/13