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

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 Village Pump 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".

I recently noticed that the default signature on Commons includes localized text for the talk page link, e.g. [[User:CalendulaAsteraceae|CalendulaAsteraceae]] ([[User talk:CalendulaAsteraceae|<span class="signature-talk">{{int:Talkpagelinktext}}</span>]]), which I think is a great feature for a multilingual wiki.

Based on this discussion, it looks like this has been the case since 2021, and, as was brought up at the time, the fact that all parser functions in signatures are automatically SUBSTed means users cannot both customize their signatures and have their talk page link localized.

For example, I would like my signature to also include a link to my contributions page, like so: —[[User:CalendulaAsteraceae|CalendulaAsteraceae]] ([[User talk:CalendulaAsteraceae|<span class="signature-talk">{{int:talkpagelinktext}}</span>]] • [[Special:Contributions/CalendulaAsteraceae|{{int:contribslink}}]]), and the automatic substitution means that the text of my signature is only available in English: —[[User:CalendulaAsteraceae|CalendulaAsteraceae]] ([[User talk:CalendulaAsteraceae|<span class="signature-talk">talk</span>]] • [[Special:Contributions/CalendulaAsteraceae|contribs]]).

I completely agree that i18n must not be an afterthought, and if the software itself is interfering with localization, that's a problem. How feasible would it be to add an exception for localized text to the automatic SUBSTing of parser functions, and what is the appropriate way to propose this?

Easiest would probably be to set $wgCleanSignatures which would allow all templates. I dont know if templates were disabled for performance reasons or just because enwiki didnt like it. If its the latter then all that is needed to change on commons is community consensus.

Only allowing int: might be harder, require more dev effort.

You might want to reach out to someone on the editing team as they have worked on signature validation in the past.

2023_Техн_Проблеми_12.05.png

When editing the wiki usik64wiki.miraheze.org/. I encountered the following problems: 1./ The logo and favicon do not load, although I downloaded the corresponding files for the project. 2./ When opening the editing page, characters are not inserted using the paired tag ’. MediaWiki:Copyrightwarning What to do? Who can I turn to for a solution? https://usik64wiki.miraheze.org/

Native language is Ukrainian. I use a translator here. Sorry for mistakes. Дякую, Usik64 (talk) 11:58, 5 December 2023 (UTC)

Hi,you need to ask at Miraheze ( https://meta.miraheze.org/wiki/Community_noticeboard ). Both of these are things that only miraheze operators can fix.

Hi I keep getting error when saving saving an edit to a table.

Error contacting the Parsoid/RESTBase server: http-bad-status

If i edit the table in edit source it seems to save fine?

Any help or advice would be appriciated?

Many Thanks

Extension:VisualEditor#Troubleshooting

seemed transitional behaviour.

Hi all, new translations messages this morning seem no longer to be applied 'immediatly' on the translated pages; (existing modified messages are correctly displayed on these same pages) Any changes done in the cache management this night ? Thanks. --Christian 🇫🇷 FR (talk) 10:39, 5 December 2023 (UTC)

ok , seems returned to its normal behaviour. --Christian 🇫🇷 FR (talk) 12:08, 5 December 2023 (UTC)

Hi. I am struggling to get my wiki installed. The setup fails.

I have added echo statements into:

mw-config\index.php

includes\WebStart.php

includes\Setup.php

and the fault seems to lie in Setup.php with the lines

$wgHooks = new FauxGlobalHookArray(

MediaWikiServices::getInstance()->getHookContainer(),

$wgHooks

);

I have tried filling in a LocalSettings.php file, but I am not confident on the answers that I have supplied. Some examples of this file would be helpful to know the type of answers that I should be giving.

Please provide a step by step explanation what you changed with full and clear file names, and which exact "statements" you added to which file and why, and your exact MediaWiki version.

What does fails mean? Do you encounter an error? At what step do you have the issue?

To Malyacko & Bawolff,

I downloaded the latest MediaWiki zip file, uncompressed it, copied it up to a 'w' folder on my server with FileZilla. I have now commented out all the echo statements that I had inserted.

I run w/index.php

That shows...

"MediaWiki 1.40.1

LocalSettings.php not found.

Please set up the wiki first."

Go to w/mw-config/index.php and get

"This page isn’t working

www.coacto.co.uk is currently unable to handle this request.

HTTP ERROR 500"

Thanks in advance for your help.

Can you check if your webserver error logs have any errors in them?

I do get webserver errors such as this...

"[Wed Nov 29 06:09:54.659233 2023] [autoindex:error] [pid 775501:tid 140426910287616] [client 173.239.211.221:19887] AH01276: Cannot serve directory /home/ggdb0pvh8m86/public_html/wp-admin/css/colors/coffee/: No matching DirectoryIndex (index.cgi,index.php) found, and server-generated directory index forbidden by Options directive, referer: http://coacto.co.uk//wp-admin/css/colors/coffee/index.php"

This is the latest error that happened at six o'clock in the morning when I am not attempting to run any wiki files.

My wiki folder 'w' sits next door to WordPress folders as the URL was primarily designed for a WP site.

I could find no errors relating to my wiki folder '/w/'.

Do you have a separate log file for php errors (sometimes that is different than webserver errors).

See also How to debug (only sone parts of that page are applicable if you havent installed yet)

To Bawolff,

I have cPanel that only shows Errors not just PHP errors.

I looked at Manual:How to debug and made use of some of the Boolean debug tools so that my LocalSettings.php file now has...

# debugging and testing

$wgResourceLoaderDebug = true; // MM addition

$wgEnableJavaScriptTest = true;

$wgShowExceptionDetails = true;

$wgDebugToolbar = true; // MM addition

$wgShowDebug = true; // MM addition

$wgDebugDumpSql = true;

$wgDebugLogFile = "/tmp/sql.txt";

$wgDevelopmentWarnings = true; // MM addition

Copying that up to my server does not appear to have any effect.

The tmp/sql.txt file is not changed. I get the same error as before.

Hi - i just downloaded 1.40.1 and run on php 8.1. First launch and i had 500 error. I enabled error reporting and got fatal error relatet to some composer libraries:

Fatal error: Class 'Liuggio\StatsdClient\Factory\StatsdDataFactory' not found in (path)/includes/libs/stats/BufferingStatsdDataFactory.php on line 35

I googled for it and found a solution:

https://phabricator.wikimedia.org/T166969

I had to manually download vendor/liuggio/statsd-php-client/src/Liuggio/StatsdClient from github and replace original directory. Now it works. It seems that archive have some coruupt files.

It's some trivial bug that most of ppl will solve themselves but its iritating that such a big project has such bugs :/ Maybe ppl solve this and do not report so i will do that.

You need to extract the tar file that supports posix tar file formats, otherwise long filenames can become corrupted.

In 1.40.1 You have typo in a file name. There is:

AbuseFilterGenerateVarsForRecentChangeHook.ph

And should be:

AbuseFilterGenerateVarsForRecentChangeHook.php

Where exactly did you see the typo?

extension is ph, not php. I had also problems with different files (js files) I see there is some problem with extracting tar.gz. I dowonloaded tar.gz under debian and extracted by mc extractor. Under wnidows files are ok.

It's the first time such a problems occur for me. How to properly extract under linux?

Ok. I got it. Problem was extraction. I work on linux for 20 years and the first time i got this problem! Extracting under mc (midnight commander) resulted in corrupt files and filenames. When extracted in command by "tar xf filename" everything went ok.

U should solve this. There is something broken with this archives :/

There are multiple types of tar files, and they each handle long filenames differently. Maybe midnight commander doesn't support posix tar file

I encountered an error while using an image in the .webp file format. The images are correctly stored in the filesystem, and I have manually created two directories in my mediawiki installation: /images/thumb and /images/tmp. Both of these directories have the file permissions set to drwxr-xr-x. I came across a similar support topic, but there were conflicting responses on how to resolve the issue. I attempted to fix it by adjusting the variables $wgUseFileCache and $wgFileCacheDirectory, but it didn't solve the problem. Can anyone provide guidance on how to resolve this issue? Thank you!

I am able to suppress the error by using

$wgIgnoreImageErrors = true;

However, this only allows me to display full size images and doesn't allow thumbnailing

I ran into this previous topic which led me to put

putenv('TMPDIR=/var/www/html/images/tmp');

into my LocalSettings.php, however I was unable to edit the TempFSFile.php because it no longer had the line of code:

$newFileHandle = fopen( $path, 'x' );

I even tried giving file permissions to all users with

chmod ugo+rwx tmp

However it still wouldn't generate the thumbnails

Please include exact error messages.

> $wgUseFileCache and $wgFileCacheDirectory

These config settings are unrelated to your issue or file handling.

> I was unable to edit the TempFSFile.php

we strongly reccomend you do not edit any mediawiki core files.

The apache log doesn't present any errors at loglevel error, didn't see anything else at loglevel info but I could've missed something, I tried enabling the mediawiki log according the these directions however it wasn't writing to the file provided even though the file permission were 755. The following error shows within the image box as a textbox: "Error creating thumbnail: Unable to save thumbnail to destination". @Bawolff Is there any additional debug information that I should add?

Figured out the error, I had to chmod 777 the tmp directory because it has 775 permissions which weren't enough...

Its important to remember that mediawiki runs as a different user than you probably do. If you are doing 755 permissions, you also need to chown to the user mediawiki is running as (often, but not always www-data)

If you use Special:PasswordReset more than once for the same username/e-mail address, then https://www.mediawiki.org/wiki/Manual:$wgPasswordReminderResendTime dictates you’ll get "A password reset email has already been sent, within the last 24 hours. To prevent abuse, only one password reset email will be sent per 24 hours."

But that user lost their message and I need to let them regenerate it.

How can I reset the count, probably through the database?

Technically its the user_newpass_time field of the user table in the database. We don't really reccomend mucking about in the database. Have you considered just temporarily changing $wgPasswordReminderResendTime, send the reset, then change it back?

I was just trying to figure out what I need to do to have the donation page not pop up anymore, lol. I donated the very first time I saw it, and I do believe I did a recurring donation of $10 a mth. And it verbally states I believe either at the bottom of the blue background request or it was stated after I donated, that once you did, my cookies should have saved it within the archives or files on my tablet for the wiki sites. Could I have messed up my donation somehow? Bc tbh? If it can be messed up, I am FOREVER unknowingly messing ezpz stuff up with a quickness, lolol.

Thank you ahead of time for Any & ALL Help

RoxStar3333 aka Roxanne

@RoxStar3333 Hi, what is your question, and about which website is it? Please see the sidebar - thanks a lot!

Note: questions about donations to wikimedia foundation are better made by email to donate@wikimedia.org

Oh, I think I figured it out not long after I messaged 3 mths ago. My problem was that EVERYTIME I would go look something up on Wikipedia I would have the request for donations page, w/a green background. And it stated that once I donated (I opted for $10/per mth) that it wouldn’t pop up all the time. But it unfortunately was still popping up. But, as I stated in the 1st line I believe I figured out how to Not have it popping up all the time. I didn’t know that I was able to login to a Wikipedia/Wikimedia account. So I figured, Well what the hay! I’ll see if it lets me login, & PRESTO! It allowed me to login, which then in turn it stopped the green background requests.

I also wanted to make sure that I thank you guys at ANY of The Wiki’s because of you guys creating all of the different Wiki’s I can learn about damn close to anything I so choose. I totally wish that Wikipedia was around when I was in school, lol. 😂 I had to do my reports going to Library and praying I was the 1st one there so I could get the necessary encyclopedia volume BEFORE ANYONE ELSE IN MY CLASS could. It kinda reminds me of a type of Library/Encyclopedia THUNDER DOME lol.

Anyways, Thank You ALL, EVERY SINGLE ONE OF YOU that work for The Entirety Of The Wiki Worlld

Usually the donation message does not appear when you log in as a registered user.