How have to solve this ....
[d2ebbb87bf232eac27bb8e1c] 2024-09-21 19:23:16: Fatal exception of type "Wikimedia\Rdbms\DBQueryError"
Please, anyone help us.
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.
|
How have to solve this ....
[d2ebbb87bf232eac27bb8e1c] 2024-09-21 19:23:16: Fatal exception of type "Wikimedia\Rdbms\DBQueryError"
Please, anyone help us.
Please enable $wgShowExceptionDetails to get detailed error message. See Manual:How to debug for additional information.
No me permite iniciar sesión y no me mandan los mensajes en el correo
Cannot remove "index.php" from URLs on v.1.39.8
I have 2 wiki installs v.1.38.1, have used tool at shorturls.redwerks.org for new v.1.39.8 wiki install as I did for 2 older ones, but code the tool generates doesn't work for v.1.39.8.
Also, Common.css font-size for tagline is not applying in v.1.39.8 like it does in v.1.38.1
See — https://dstall.com/REF/index.php/Main_Page, https://dstall.com/REF/index.php/MediaWiki:Common.css
@DStallTX: It looks like your $wgArticlePath is set to /REF/index.php/$1
. Try changing it to /REF/$1
. But also, what do the relevant bits of your web server configuration look like?
Doesn't work revised without index.php. (Actually had omitted that line of code, but added it per your revision.) I'm on shared hosting. Don't know about web server config.
@DStallTX: Without being able to change the web server's rewrite rules you might not be able to do short URLs. There might be somewhere in your control panel or whatever, where you can change things. What provider is it?
AsuraHosting.com Short URLs work fine with v.1.38.1, so why don't they work with v.1.39.8?
Hmm good point! And nothing else has changed? Doesn't work revised without index.php What is the actual error? You get a 404? Is the error coming from MediaWiki or is it a generic server error?
URL does not shorten - still includes index.php
Font-Size does not change in Tagline, regardless of how I size font (em, px, pt, %, etc.)
URL does not shorten - still includes index.php It looks like https://dstall.com/REF/Main_Page is currently redirecting to https://dstall.com/REF/index.php/Main_Page — have you changed $wgArticlePath? If you change it, what error do you get?
Nothing happens when I make that change - URLs don't shorten, still include index.php.
Currently, I do not have $wgArticlePath? in LocalSettings. I only have $wgScriptPath bc I only have that in LocalSettings for the other 2 wikis and URLs shorten just fine there with only $wgScriptPath.
I do have all the code in .htaccess that the tool generates for that file. Per instructions, I have to use code generated by the tool bc my sites are on shared hosting.
@DStallTX: Nothing happens when I make that change - URLs don't shorten, still include index.php. That sounds like maybe it's being overwritten later in LocalSettings.php maybe, or is not being set correctly, because it shouldn't be ignoring it like that. What if you set it to an obviously wrong value (e.g. $wgArticlePath='/WRONG/$1';
) does that value show in the links when you open a wiki page?
Since the only page passing both dev=y
and admin=y
in {{Hubs}} is Manual:Maintenance scripts, I personally think it would be good to place it near that.
I have set up a private wiki for a group of authorized people to use. Is it possible to create a separate landing page for non-authorized users only?
I need this page to be visible without logging in. After logging in, they would be taken to the Main Page. Would that be possible?
You can make "Main Page" public and say whatever you want to say on that page, and a different "Home Page" which would be the "true" main page for authorised users. An example can be seen on any private WMF wiki, such as https://steward.wikimedia.org/.
Can you show the steps how to set the login use use :Home Page" as the landing page instead of Main Page ?
What do you mean by "login use"? You mean authorised users? I don't think there's an easy way to "block" Main Page, but authorised users just need to click a link.
Specifically, index 'el_from' cannot be dropped from `externallinks` because it does not exist in this table. This is a bug in [maintenance/archives/patch-externallinks-el_to_path.sql]. Please help! Will this be resolved in the next updated?
on page https://www.mediawiki.org/wiki/Manual:Using_custom_namespaces#For_extension_developers we use last link as : {{ll|Extension namespace registration}} but the title (of ns Main) remains in english on the translated page . Why ?
Where can I edit Site Subtitle? Currently, subtitle is only pulling name of wiki, e.g. From MyWiki. I want to add colon with extra description of wiki to the subtitle.
I know the subtitle can be styled in Common.css, but I want to edit text of subtitle - Manual:Tagline (Site Subtitle). I also know there's a CustomSubtitle extension, but I've been able to add text to subtile before, just can't remember how I did that. Is there a way to do it in Vector skin? Can it also be done in MobileFrontend so it shows in Mobile view as well as Desktop?
Hello,
I have MW 1.26.2 but my old custom skin doesn't load the javascript for sortable tables.
My custom skin was created in older versions of MW and I think it doesn't have the latest updates.
What is the javascript needed for sortable table ? where can I find it, and how to add it in the skin ? plz
Many thx
Alex
You should look over the skinning tutorial: Manual:Skinning Part 1
There is a Skin->getDefaultModules() which needs to be called so that the mediawiki.page.ready resource is loaded which handles sortable tables.
You may also find the ResourceLoader/Migration guide (users) helpful.
Used API.
I need to update some extension code to work with MW1.39. I believe the problem is because it relies on Manual:$wgParser.
The code is from https://stackoverflow.com/questions/18379992/how-to-use-the-mediawiki-parser-to-get-html-from-wikitext
$text = "Your [[wikitext]]";
$title = $skin->getTitle(); // Get the title object from somewhere or use $wgTitle
$parser = new Parser;
$parserOptions = new ParserOptions;
$parserOutput = $parser->parse( $text, $title, $parserOptions );
$html = $parserOutput->getText();
echo $html;
I think the replacement for the $parser =
line is $parser = \MediaWiki\MediaWikiServices::getInstance()->getParser();
But now $parserOptions = new ParserOptions
needs a UserIdentity object and I'm stuck there.
Any pointers would be gratefully received.
What is proper to do here depends on the context of where this code is running from. Where is this code running? What is it trying to do?
The code you posted doesn't even use $wgParser.
That said, ParserOptions::newFromAnon() may be what you are looking for.
It's an extension I updated years ago based on the old "Bulletfeed" extension. When used with "action=bullet_feed" it turns HTML bullet points into an RSS feed. So basically the best way of getting the HTML content of the page is what I need. The little I knew is now very rusty, as you were able to tell already... The extension isn't exactly the same as the code above (e.g. it doesn't just echo $html at the end).
Basically I can get the page wikitext all right, but would like to parse it to HTML. The reason is that the wikitext calls a template. If I had unlimited time I would probably rewrite it from scratch. But if I could find out how to convert wikitext to HTML, including expanding templates, then that sticking plaster would be good enough for now!
In the end I used the API, based on the PHP code here: API:Parsing_wikitext#PHP. For some reason, "http_build_query" didn't work, so I just created $url by hand.
wikimedia 1.35 on linux debian, php 7.3
what possibly could give a client side ERR_CONNECTION_RESET editing a sub section, no apparent errors server side, editing the entire page works properly, I intentionally disabled https, plain http is enough inside a secure lan
thanks for any hints whatsoever where to look possibly
Did you look at your webserver error logs (apache error logs, php-fpm process logs...)? A connection reset may indicate the webserver or (more commonly) the php engine crashed while processing the request (usually with a SIGSEV signal, or "segmentation fault"). If that's the case, this may happen due to a buggy php extension installed, sometimes related to php caching.
I have this at the beginning of LocalSettings.php :
error_reporting( E_ALL );
ini_set( 'display_errors', 1 );
and at the end :
$wgShowError = true;
$wgShowErrors = true;
$wgShowSQLError = true;
$wgShowSQLErrors = true;
$wgShowException = true;
$wgShowExceptions = true;
$wgShowExceptionDetails = true;
$wgDebugComments = true;
$wgDebugLogFile = "/var/log/mediawiki/logfile.log";
no errors in /var/log/apache2/error.log
[Tue Sep 17 21:07:31.966640 2024] [mpm_prefork:notice] [pid 1487] AH00163: Apache/2.4.38 (Debian) configured -- resuming normal operations
[Tue Sep 17 21:07:31.966765 2024] [core:notice] [pid 1487] AH00094: Command line: '/usr/sbin/apache2'
in /var/log/mediawiki/logfile.log
I can't find any "error" or "segmentation" what should I look for say "timeout" ?
/var/log/syslog also nothing apparent :
Sep 17 21:07:31 mediawiki1 systemd[1]: Started The Apache HTTP Server.
Sep 17 21:09:00 mediawiki1 systemd[1]: Starting Clean php session files...
Sep 17 21:09:00 mediawiki1 systemd[1]: phpsessionclean.service: Succeeded.
Sep 17 21:09:00 mediawiki1 systemd[1]: Started Clean php session files.
Sep 17 21:09:01 mediawiki1 CRON[1558]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Sep 17 21:22:01 mediawiki1 CRON[1566]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Sep 17 21:39:00 mediawiki1 systemd[1]: Starting Clean php session files...
Sep 17 21:39:00 mediawiki1 systemd[1]: phpsessionclean.service: Succeeded.
it is php 7.3, how to configure php-fpm ?
If you are using apache, you're using apache-mod-php and not php-fpm.
Looks like you can discard a segmentation fault at this point. It may be an intermediate firewall or proxy (mis)detecting some weird thing and resetting the connection. Only you know the different devices/software between your browser and the server to know what could be. A network inspecting tool like Wireshark or tcpdump can be used by an expert to check on both server and client from where the connection reset originates.
if possible to delete previous message, it should be :
from wireshark on client side, after the POST there is a red RST, connection dropped I suspect from server side, the strange thing is that editing the entire page works
You may run the same analysis from the server side using the tcpdump command line utility (restrict to http port and optionally by IP to not get flooded). If you get the same results, this would confirm it's the server dropping the connection somehow. If not, there's an intermediate network equipment interfering.