On import, i'm getting
Wrong option: Namespace "(Main)" of the root page does not allow subpages.
How to fix?
Welcome to the MediaWiki Support desk. This is a place where you can ask any questions you have about installing, using or administrating the MediaWiki software.
(Read this message in a different language)
$wgShowExceptionDetails = true;error_reporting( -1 );ini_set( 'display_errors', 1 );
to LocalSettings.php in order to make MediaWiki show more detailed error messages.
|
On import, i'm getting
Wrong option: Namespace "(Main)" of the root page does not allow subpages.
How to fix?
Where shall I place my css modifications for the new Vector (2022) skin? I've tried MediaWiki:Vector-2022.css
but it has no effect.
It may take some time to take effect, usually 20 minutes at most. Otherwise, a syntax error in that page may render the entire CSS or from one point to the end unusable. For example, if you forgot to open or close curly braces. You may want to check if the CSS of that page is valid running it through an online CSS validator.
Sorry, no, there must be another reason. The same css code works fine as "User:MyUser/vector-2022.css" and does not work as "MediaWiki:Vector-2022.css"
Any other ideas? It is Mediawiki 1.39.6
Mediawiki 1.39.6, PHP 7.4.3, MySQL 8.0.36
wfLoadExtension( 'MobileDetect' ); wfLoadExtension( 'MobileFrontend' ); wfLoadSkin( 'MinervaNeue' ); $wgMFDefaultSkinClass = 'SkinMinerva'; $wgDefaultMobileSkin = 'MinervaNeue'; $wgMinervaEnableSiteNotice = true; $wgMFAutodetectMobileView = true; $wgMFEditorOptions = array( 'anonymousEditing' => false, 'skipPreview' => false );
Till 1.35 we used to have MinervaNeue as mobile skin. With 1.39, this doesn't work anymore. Mobile devices apparently use the vector skin. What will i have to do to make the mobile skin work?
The mediawiki logfile is full of thousands of lines which don't say nothing to me, by filtering "mobile" i found one interesting line:
[resourceloader] Module "ext.MobileDetect.mobileonly" not loadable on target "mobile".
???
Is there any list of hidden special pages, such as Special:MyPage hidden from Special:SpecialPages?
There is this list in SpecialPageFactory.php:
// Unlisted / redirects 'Blankpage' => 'SpecialBlankpage', 'Blockme' => 'SpecialBlockme', 'Emailuser' => 'SpecialEmailUser', 'Movepage' => 'MovePageForm', 'Mycontributions' => 'SpecialMycontributions', 'Mypage' => 'SpecialMypage', 'Mytalk' => 'SpecialMytalk', 'Myuploads' => 'SpecialMyuploads', 'PermanentLink' => 'SpecialPermanentLink', 'Redirect' => 'SpecialRedirect', 'Revisiondelete' => 'SpecialRevisionDelete', 'Specialpages' => 'SpecialSpecialpages', 'Userlogout' => 'SpecialUserlogout',
Howdy,
I'm trying to delete some duplicated images, but keep getting the following error:
Error deleting file: An unknown error occurred in storage backend "local-backend".
The images in question all have previous versions that, for one reason or another, show "No thumbnail" as their first version (despite those thumbnails existing previously, prior to new versions being uploaded). Images that don't have "No thumbnail" as their first record can be deleted without issue.
My biggest question is, is there a way to bypass this error and delete the files? Less importantly, what can cause the "No thumbnail" issue to happen? The wiki I'm working on has lost a lot of prior versions of images over the years and no one can pinpoint why, or how to prevent it from happening in the future.
Most often this is due to permissions on the filesystem being incorrect. the webserver deamon and the permissions of the directory have to be compatible.
Hi,
Can you help me debug some mediawiki + S3 compatible service errors ? ( image resize / uploads )
It's an error i have on my server but not locally, but i haven't found any obvious difference between the setup yet
I'm using the following :
- mediawiki 1.39.6 ( a canasta image : canasta:1.39.6-20240104-346 )
- AWS extension 0.12.0
- minio
My FileOperation log :
2024-05-03 15:57:57 9de13bf397d2 mediawiki: S3FileBackend: found backend with S3 buckets: mediawiki, mediawiki/thumb, mediawiki/deleted, mediawiki/temp.
2024-05-03 15:57:57 9de13bf397d2 mediawiki: S3FileBackend: doPrepareInternal: S3 bucket mediawiki, dir=temp/4/42, params=noAccess, noListing, dir
2024-05-03 15:57:57 9de13bf397d2 mediawiki: S3FileBackend: doSecureInternal: creating temp/.htsecure in S3 bucket mediawiki
2024-05-03 15:57:57 9de13bf397d2 mediawiki: S3FileBackend: exception [Null] in doSecureInternal from PutObject ({"Bucket":"mediawiki","Key":"temp/.htsecure","Body":"","@http":[],"@context":[]}): Error executing "PutObject" on "xxxx:9000/mediawiki/temp/.htsecure"; AWS HTTP error: Client error: `PUT xxxx:9000/mediawiki/temp/.htsecure` resulted in a `404 Not Found` response:
<HTML><HEAD>
<TITLE>Network Error</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></ (truncated...)
Unable to parse error information from response - Error parsing XML: String could not be parsed as XML
2024-05-03 15:57:57 9de13bf397d2 mediawiki: S3FileBackend: doCreateInternal(): saving temp/4/42/20240503155757!phpp5WIrX.jpg in S3 bucket mediawiki (sha1 of the original file: jlb3z7ca9kw98dqons8c4pfh0sgo92m, Content-Type: image/jpeg)
2024-05-03 15:57:58 9de13bf397d2 mediawiki: S3FileBackend: exception [Null] in createOrStore from PutObject (false): Error executing "PutObject" on "xxxx:9000/mediawiki/temp/4/42/20240503155757%21phpp5WIrX.jpg"; AWS HTTP error: Client error: `PUT xxxx:9000/mediawiki/temp/4/42/20240503155757%21phpp5WIrX.jpg` resulted in a `404 Not Found` response:
<HTML><HEAD>
<TITLE>Network Error</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></ (truncated...)
Unable to parse error information from response - Error parsing XML: String could not be parsed as XML
2024-05-03 15:57:58 9de13bf397d2 mediawiki: S3FileBackend: Performance: 0.127 second spent on: uploading temp/4/42/20240503155757!phpp5WIrX.jpg to S3
2024-05-03 15:57:58 9de13bf397d2 mediawiki: StoreFileOp failed: {"src":"/tmp/phpp5WIrX","dst":"mwstore://AmazonS3/local-temp/4/42/20240503155757!phpp5WIrX.jpg","overwrite":true,"headers":[],"failedAction":"attempt"}
The 404 responses make me wonder if the domain/port for the s3 bucket is set correctly.
I am sorry for all the stupid questions - I see on the main page it shows how to configure etc even if you are not an admin - how can you change that and have the pages / topics created show on the main page?
If by pages / topics you mean actual pages, you can transclude Special:NewPages as {{Special:NewPages/25}}
Alternatively, use a proper forum software instead of MediaWiki.
Use %0A instead.
How can I wrap lines when I fill the text parameter when using api.php?action=upload
? According to the Documentations, the text parameter should be in the query string, but I need to write something like this...
=={{int:filedesc}}== {{Information}} =={{int:license-header}}== {{self|cc-by-sa-4.0}}
It need to wrap lines, but how?
Thanks!
I recently had to install TorBlock, LoginNotify and CheckUser extensions. Tables were created successfully for Checkuser extension but during testing only localhost adress 127.0.0.1 showed in Special:CheckUser for a user access. I guess IP gets replaced during the process somewhere incorrectly but I need to find out where to fix it. It might be due to caching but in webserver logs and cache logs IPs are correct. I wonder if TorBlock and LoginNotify extensions may be influenced by this issue.
Did you set $wgCdnServersNoPurge correctly?
Its unlikely that TorBlock or LoginNotify affect this.
How is your web server setup. Do you have load balancers, caching proxies, etc in front of your web server. If so, do they set X-Forward-For headers properly?
$wgCdnServersNoPurge was left at default value, that is []. There is varnish cache set up as recommended in Manual:Varnish caching, this setting works
$wgUseCdn = true;$wgCdnServers = array(); $wgCdnServers[] = "ip address:port"; http.X-Forwarded-For is set up with received client IP address.