Project:Support desk

Welcome to the MediaWiki Support desk, where you can ask MediaWiki questions!

(Read this message in a different language)

See also

Other places to ask for help:

• Chat rooms
  • Wikimedia Chat (Mattermost)
  • MediaWiki unofficial (Discord)
  • Outreachy chat (Zulip)
  • Hackathon chat - (Telegram @wmhack group)
• Email groups
• StackOverflow (third-party)
• Unofficial MWUsers forum (third-party)

Before you post

• Check the basic How does MediaWiki work? guide.
• Check the FAQ and Errors and symptoms .
• If your question is about a specific feature, check the relevant technical manual , end-user help or extension page and consider asking on its talk page .
• For issues about the mediawiki.org website, report to Current issues instead.
• For trying out wiki editing, use the Sandbox instead.

Post a new question

1. To help us answer your questions, please indicate which versions you are using, as found on your wiki's Special:Version page:
   • MediaWiki version
   • PHP version
   • Database type and version
2. Please include the web address (URL) to your wiki if possible. It's often easier for us to identify the source of the problem if we can see the error directly.
3. To start a new thread, click "Start a new topic".

Hi,

I´m migrating a v1.15.3 MW to another Server with v1.35

I copied the database an the update.php gives the following error:

...batch conversion of user_options: Wikimedia\Rdbms\DBQueryError from line 1699 of /var/www/wiki/includes/libs/rdbms/database/Database.php: Error 1146: Table 'wiki.mw_revision_comment_temp' doesn't exist (127.0.0.1)

Function: MediaWiki\Revision\RevisionStore::fetchRevisionRowFromConds

Any hints for me?

The Table 'wiki.mw_revision_comment_temp' indeed does not exist in the DB.

I only have 'wiki.mw_revision'

I did some research and generated the db tables manually; four tables were missing:

mw_revision_comment_temp

mw_comment

mw_revision_actor_temp

mw_actor

now I get another error from the update.php:

Beginning migration of revision.rev_user and revision.rev_user_text to revision_actor_temp.revactor_actor

Wikimedia\Rdbms\DBQueryError from line 1699 of /var/www/wiki/includes/libs/rdbms/database/Database.php: Error 1242: Subquery returns more than 1 row (127.0.0.1)

Function: MigrateActors::migrateToTemp

I´m still messing around with the problem :/

does anybody have a hint for me to fix this?

Maybe start from scratch but move to a different version, eg 1.31? I know what you're doing is supposed to work but...

I need help with my wiki.. I recently import some templates from wikipedia.. And some of the imported page has link from wikipedia. example below Wikipedia:How to post, Is there a way i can access all of them so i can update it to mine.

There's an "allpages" special page you could use, if I understand the question correctly.

I have been facing issue and some limitation using Shared hosting and i am about to upgrade my plan to VPS .. Which Web Panels do you think i should go for...

interworx OR cpanel

I've only used cpanel, and found it fine (although that was probably five years ago). But surely one of the points of a VPS is that you get full shell access to do whatever you want, and so the web control panel is less important?

I second that. I suppose I was spoiled as on my shared host I had shell access. But just get a basic unmanaged VPS. You won't look back. I don't even know whether mine has a control panel. I assume not :-)

My wikipage has recently been changed to the timeless skin in order to make it more responsive. After this, description/definition lists are no longer displayed as before. Before:

item

description

now:

item (in another font, Times New Roman?)

description

While I am really happy with the rest of timeless, I would like to change this. I have tried different things in the mediawiki:common.css and in the mediawiki:timeless.css pages, but nothing appears to affect the font of "item". Is there any way to change this?

You could overwrite the "font-family" definition for .mw-body dt in MediaWiki:Common.css

Thank you for your reply. Unfortunately, this does not seem to work. I can change the font colour, but not the font itself...

Can you include what CSS you actually used?

Why not?

I don't know...

If you cannot describe which exact (!) steps you performed, and what happens, and what you expected to happen, then nobody else can help I am afraid.

I have placed

body { color: #5a7425; font-size: 15px; font-family: "Verdana"; }

td { color: #5a7425; font-size: 15px; font-family: "Verdana"; }

div.mw-parser-output { color: #5a7425; font-size: 15px; font-family: "Verdana"; }

div#mw-parser-output { color: #5a7425; font-size: 15px; font-family: "Verdana"; }

div.mw-content { color: #5a7425; font-size: 15px; font-family: "Verdana"; }

.mw-body dt {font-family: "Verdana";}

in mediawiki:commons.css. This changes the colour of the font, but not the font type. As described above, I want my definition lists to look as they did with the vector skin (bold term, defined by the ; before the word, regular, indented text under, defined by the :) . I am rather new at this, and am still looking to find my way around. The site in question uses version 1.31.12, timeless version 0.8.1.

You shouldn't have just one font in the font-family, you should offer a selection in case the device doesn't have that single font; in which case the device will use its default font. Possibly unlikely not to have Verdana, but better to offer a choice anyway.

There's no need to use quote marks around the font-name unless the font-name has a space in it.

These comments don't really address your issue!

Removed the Extension:TitleKey.

Howdy,

I have recently upgraded our test wiki from 1.31 to 1.35.4 (PHP 7.4.24, MySQL 5.7.35). It is just a test environment, so the question is not urgent but I would appreciate if s.o. could give me a hint someday.

We are using the default search without any extensions (no CirrusSearch, ...), it has always been sufficient for us. The default behaviour is: When beginning to type, a small dropdown box opens, showing up to 10 matches. This feature has always been active for the main namespace (and continues working after the upgrade). Additionally, one could have typed <namespace>:<searchstring> and then the dropdown shows the matches within the given namespace. Which does not work any longer.

For comparison, check www.perrypedia.de vs. test.perrypedia.de and try searching "Hilfe:" or "Mediawiki:" - works fine in live wiki, doesn't find anything in test. Is this change intended or did I do something wrong? Kind regards, K.

is your skin the correct version, and are there errors in the web browser's developer console?

You could try using the opensearch api module manually Api:Opensearch and see if it gives any errors.

Currently I am using Vector, which was part of the Mediawiki 1.35 bundle, but I have also tested other skins and the behaviour (missing search suggestions) is the same in any skin.

No errors in the developer console.

No errors in the Apache error log. (lots of PHP warnings that don't matter: deprecated hooks)

No errors when using the opensearch api. It works but I notice the opensearch api slightly differs from the search suggestions in the way it searches namespaces ...:

The documentation states I could supply the namespace within the URL, like "api.php?action=opensearch & search=N & namespace=12" *) This parameter seems to be ignored, the search result shows articles of the main namespace.

On the other hand I can supply the namespace as part of the search string "api.php?action=opensearch & search=Hilfe%3aN" *) The search results are then limited to the "Hilfe" namespace but shows all articles containing an "n", i.e. a fulltext search - in contrast to the search suggestions dropdown, where I expect to see all articles beginning with "n".

*)the editor rejects the full url (spam filter)

Found and fixed! The trouble resulted from Extension:TitleKey. Removed the extension, now the namespace search works as before.

(Even without TitleKey, the search is case insensitive so I dont know a reason why to have it installed.)

I want to limit a certain user account only to fix typos and add symbols such as (CONTENT), [URL LINK_TEXT] [[INTERNAL_LINK]], {{TEMPLATE_CALL}} and so forth.

I assume that in my particular website, limiting the that user account up until 500 characters per edit would be enough.

Is there any way to do so without installing any extension and without any JavaScript limitations?

Is this question different from Topic:Wil0u07fcqbxi336?

when i go to special pages and listed the new files all will show but not the of my user.

even when i write my user name into the selection textbox nothing will found.

did someone had a idea?

regards Jan

Please see "Post a new question" in the sidebar. Also, which exact page? What does not show mean? No entry? A broken thumbnail? Something else? Does the autocomplete in the textbox work? Does it work for other usernames?

The third edition of the m:Coolest Tool Award is looking for nominations!

Tools play an essential role for the Wikimedia projects, and so do the many volunteer developers who experiment with new ideas and develop and maintain local and global solutions to support the Wikimedia communities. The Coolest Tool Award aims to recognize and celebrate the coolest tools in a variety of categories.

The awarded projects will be announced and showcased in a virtual ceremony in December. Deadline to submit nominations is October 27. More information: m:Coolest Tool Award. Thanks for your recommendations! -- SSethi (WMF) for the 2021 Coolest Tool Academy team 05:57, 19 October 2021 (UTC)

I'm attempting to deploy MediaWiki 1.35 on Namecheap shared hosting, I was under the impression that the merge of Parsoid into the MediaWiki core would allow this so I apologise if I have misinterpreted.

I have decompressed the tarball into my site folder and installed it using MySQL and largely default installation options to try get something up and running. My plan is to have two sites so that I may familiarise myself with MediaWiki on one, test things out and fine tune prior to deploying to the actual site; one private, one authenticated edits only.

I have reinstalled the software several times now, including deleting the database used to ensure it's not culprit and I am still no closer to figuring out how to correctly setup Visual Editor. I am constantly met with the error "Error contacting the Parsoid/RESTBase server (HTTP 403)" and I cannot figure out for the life of me what is causing it.

I have attempted to invoke "/rest.php/{domain}/v3/page/wikitext/Main Page" substituting my domain in which works as expected. I have tried to enable cookie forwarding with no luck. I have tried explicitly declaring the Parsoid instance. I have tried manually loading the Parsoid extension from vendor/wikimedia/parsoid/extension.json, I'm running out of things to try.

I would have thought that the software would work out of the box, but I read up on it anyway to make myself aware of any "gotchas" and I am still struggling to understand the root cause of the issue, any input would be greatly appreciated.

JSON response received upon saving changes

Hi. Were you able to solve this? It seems like a bunch of people have complained about this at least at Extension talk:VisualEditor and phab:T263928, but no one really confirmed that the issue/bug exists.

I am putting this out more widely as an answer to this issue as I had a LOT of trouble resolving it. Basically, on some (cPanel) hosted sites the Parsoid/RESTBase Server API communications are blocked by several (PHP) ModSecurity rules. My host does not allow you to disable ModSecurity using .htaccess so I had to contact my hosting tech support and get them to whitelist rules for my wiki one or two at a time, while generating new ModSecurity rule errors by attempting to edit using VisualEditor, until we had found all the rules which were resulting in this error.

NB: At some point during this process a few pages might start working - not throwing a 403 - but then test a few more pages as they might still trigger ModSecurity.

I had the same problem with a very popular web hosting provider (the one similar to a crocodile). At first, it looked like @Nghtchld's suggestions were the root. There were ModSecurity issues for sure - their logs confirmed this. However, modification of the rules didn't solve the issue. It turns out that for some reason, the visual editor can call resources from other than the local hosting server. Since I didn't have allow statements specifically permitting those, they were all denied. The hosting service added all the IPs that could possibly be used for this to my .htaccess (there were over 60), and now it works just fine.

It took A LOT of badgering to get them to fix this. They kept telling me my .htaccess wasn't granting permission to my own client. It was super frustrating. But it was all worth it. I like working with markup code, but when it comes to just pounding out some text content, the visual editor is much better.

I've recently started using an RSS bot in our wiki's Discord server to log recent changes to a channel, but ran into an issue where some filters specified in Recent Changes don't affect the feed. Despite hidenewpages=1 and hidelog=1 functioning as intended on the Recent Changes page, they don't remove new pages and move/deletion/block logs from the raw feed. I am aware of extensions that add more dedicated activity feeds to a server, but I do not have control over what extensions get installed so they aren't an option.

Currently I've had to specify filters on the bot's side, but since it's filtering by what's in the <description> tags, as that's the best I can do, an edit summary containing the filtered phrases will prevent that change from being posted by the bot, which is obviously not desirable.

For the record, the namespace filter does affect the feed, so surely other filters not doing so is unintentional behaviour, right? This can be observed on any wiki's Recent Changes page, including this one.