Project:Support desk

v • d • e   Welcome to MediaWiki.org's Support desk, where you can ask MediaWiki questions!

There are also other places where to askCommunication: IRCCommunication#Chat, mailing listsMailing lists, Q&A etc.

Before you post

• Make sure you have read our fundamental introduction.
• Please carefully check our FAQManual:FAQ and Errors and Symptoms pages.
• Project:Current issues is where you should discuss issues about the mediawiki.org website itself.
• If your question is about a specific function, please read the relevant technical manualManual:Contents, end-user helpHelp:Contents or extension page and consider asking on its talk pageHelp:Talk pages.
• Test wiki editing at the Project:Sandbox.

Post a new question

1. To help us answer your questions, please always indicate which versions you are using (reported by your wiki's Special:Version page):
   • MediaWiki
   • PHP
   • Database
2. Please include the URL of your wiki unless you absolutely can't. It's often a lot easier for us to identify the source of the problem if we can look for ourselves.
3. To start a new thread, click "Start a new topic".

Discussions here were converted to another system (2015).

Previous page history was archived for backup purposes at Project:Support desk/LQT Archive 1 on 2015-07-30.

Here

Hello,

Is there a way to translate a page on the fly? I know there is the Translate extension, but what I'm looking for is a solution without having to set each translatable page manually. The text to translate would be words and short phrases, not prose.

I have in mind the selectors that can be found at the top of the pages on zhwiki, hiwiki and hywiki. What is the name of these extensions/features?

Thank you in advance.

Do you mean Extension:ContentTranslation ?

Can the ContentTranslation extension be used to translate and directly display translated text of content pages, without any particular intervention?

I will try to be more explicit. Suppose there is the heading "References" in thousands of pages. If the user changes the display language via the Universal Language Selector, e.g. in Hungarian, the heading would be automatically translated as "Források".

There is a solution with the {{int:x}} magic word, but I would be interested in a simpler approach.

When I start typing use my wiki's search bar, articles that match what I'm typing start to appear. Is there a way to remove certain pages from being listed? I have a page that is a redirect which I would like to exclude from the search suggestions. I placed __NOINDEX__ on the page but it looks like that only affects how other search engines view the page.

According to this, it should get excluded from search suggestions. 

Maybe there are some jobs left which are causing this delay. To see number of remaining jibs, browse to your Wiki's: https://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&siprop=statistics&format=jsonfm

Suddenly my search box stopped working. Previously, it would return previews of all matches. Now, no matter what you type, it displays a spinning wheel and then returns "No match was found"

Thinking I would fix the problem, I went to the trouble of installing the Extension:SphinxSearch, which requires also installing and configuring Sphinx. The search now returns all sorts of stuff, but I still get the No match was found and spinning wheel, making it appear that the search isn't working.

What do I look for to resolve this problem? I'm not seeing any errors in the console.

Site: wiki.vvfh.org

OS: FreeBSD 10.3

MediaWiki 1.29.1, PHP 7.1.10, MySQL 5.6.37

Resolved by myself )

Hello, I have following wiki website:

MediaWiki: 1.29.1
PHP:5.6.30 (cgi-fcgi)
MySQL: 5.6.35-81.0

So I have downloaded Flow, add extension to my LocalSettings.php file, run the update.php. And when I go to discussion page flow appears but when I add a topic it cannot be posted to discussion page, instead of it I see see this (when I click post message):

Could someone tell me how can I fix it? Thank you

Is something related shown in the Console and/or Network tab of your browser's developer tools? Have you checked the log of your webserver if there are some errors? Also see https://www.mediawiki.org/wiki/Manual:How_to_debug

So I have found out the error occurs during the posting, it says:

<br />
<b>Fatal error</b>:  Class 'ApiErrorFormatter_BackCompat' not found in <b>/var/www/u0402490/data/www/wikireshebnik.ru/includes/api/ApiMain.php</b> on line <b>283</b><br />

Any ideas how to resolve the problem?

The problem is resolved by reuploading core MW files to the server

I'm running on FreeBSD 10.3, php 7.1 and Mediawiki 1.29.

I studied the Extension:WikiEditor/Toolbar customization/Library and wrote a widget to add an icon to the toolbar. It allows you to highlight some text with your mouse, then click on the icon to enclose the text in the following code: <span background-color: yellow>Your text here</span>. Then all the editor has to do is change the color.

The problem is, the icon sometimes doesn't show up, and you have to reload the edit page repeatedly to get it to appear. What would cause this apparently random behavior? I'm not seeing any errors in console. But I am seeing these notices:

[Warning] This page is using the deprecated ResourceLoader module "jquery.ui.widget".

[Warning] This page is using the deprecated ResourceLoader module "jquery.ui.position".

[Warning] This page is using the deprecated ResourceLoader module "jquery.ui.core".

Please use "mediawiki.ui.button" or "oojs-ui" instead.

[Warning] Use of "wgServer" is deprecated. Use mw.config instead. (load.php, line 153)

[Warning] Use of "wgArticlePath" is deprecated. Use mw.config instead. (load.php, line 153)

[Warning] Use of "wgScriptPath" is deprecated. Use mw.config instead. (load.php, line 153)

[Warning] Use of "wgCurRevisionId" is deprecated. Use mw.config instead. (load.php, line 153)

[Warning] Use of "wgPageName" is deprecated. Use mw.config instead. (load.php, line 153)

Here's the code, basically stolen from that page and modified:

var customizeToolbar = function() {
    /* Your code goes here */
    $('#wpTextbox1').wikiEditor('addToToolbar', {
        section: 'advanced',
        group: 'format',
        tools: {
            "highlight": {
                label: 'Highlight',
                type: 'button',
                icon: 'images/highlight.png',
                action: {
                    type: 'encapsulate',
                    options: {
                        pre: "<span style=\"background-color: yellow\">",
                        post: "</span>"
                    }
                }
            }
        }
    });
};
/* Check if view is in edit mode and that the required modules are available. Then, customize the toolbar … */
if ($.inArray(mw.config.get('wgAction'), ['edit', 'submit']) !== -1) {
    mw.loader.using('user.options').then(function() {
        // This can be the string "0" if the user disabled the preference
        if (mw.user.options.get('usebetatoolbar') == 1) {
            $.when(
                mw.loader.using('ext.wikiEditor.toolbar'), $.ready
            ).then(customizeToolbar);
        }
    });
}

No one has an answer for this?

I did some greps to see where these things show up.

 1 # grep -r "jquery.ui.widget" Sites/wiki.vvfh.org/*
 2 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.widget',
 3 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.widget',
 4 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.widget',
 5 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.widget',
 6 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.widget',
 7 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.widget',
 8 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.widget',
 9 Sites/wiki.vvfh.org/resources/Resources.php:		'dependencies' => 'jquery.ui.widget',
10 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.widget',
11 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.widget',
12 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.widget',
13 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.widget',
14 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.widget',
15 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.widget',
16 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.widget',
17 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.widget',
18 Sites/wiki.vvfh.org/resources/Resources.php:	'jquery.ui.widget' => [
19 Sites/wiki.vvfh.org/resources/Resources.php:		'scripts' => 'resources/lib/jquery.ui/jquery.ui.widget.js',
20 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.sortable.js: *	jquery.ui.widget.js
21 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.droppable.js: *	jquery.ui.widget.js
22 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.selectable.js: *	jquery.ui.widget.js
23 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.tabs.js: *	jquery.ui.widget.js
24 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.spinner.js: *  jquery.ui.widget.js
25 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.accordion.js: *	jquery.ui.widget.js
26 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.progressbar.js: *   jquery.ui.widget.js
27 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.autocomplete.js: *	jquery.ui.widget.js
28 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.dialog.js: *	jquery.ui.widget.js
29 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.button.js: *	jquery.ui.widget.js
30 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.mouse.js: *	jquery.ui.widget.js
31 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.slider.js: *	jquery.ui.widget.js
32 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.menu.js: *	jquery.ui.widget.js
33 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.tooltip.js: *	jquery.ui.widget.js
34 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.draggable.js: *	jquery.ui.widget.js
35 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.resizable.js: *	jquery.ui.widget.js
36 
37 [root@colo11 # grep -r "jquery.ui.position" Sites/wiki.vvfh.org/*
38 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.position',
39 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.position',
40 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.position',
41 Sites/wiki.vvfh.org/resources/Resources.php:	'jquery.ui.position' => [
42 Sites/wiki.vvfh.org/resources/Resources.php:		'scripts' => 'resources/lib/jquery.ui/jquery.ui.position.js',
43 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.position',
44 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.autocomplete.js: *	jquery.ui.position.js
45 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.dialog.js: *	jquery.ui.position.js
46 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.menu.js: *	jquery.ui.position.js
47 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.tooltip.js: *	jquery.ui.position.js
48 
49 [root@colo11 /usr/home/schmehl]# grep -r "jquery.ui.core" Sites/wiki.vvfh.org/*
50 Sites/wiki.vvfh.org/resources/Resources.php:	'jquery.ui.core' => [
51 Sites/wiki.vvfh.org/resources/Resources.php:		'scripts' => 'resources/lib/jquery.ui/jquery.ui.core.js',
52 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core.styles',
53 Sites/wiki.vvfh.org/resources/Resources.php:	'jquery.ui.core.styles' => [
54 Sites/wiki.vvfh.org/resources/Resources.php:				'resources/lib/jquery.ui/themes/smoothness/jquery.ui.core.css',
55 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core',
56 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core',
57 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core',
58 Sites/wiki.vvfh.org/resources/Resources.php:		'dependencies' => 'jquery.ui.core',
59 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core',
60 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core',
61 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core',
62 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core',
63 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core',
64 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core',
65 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core',
66 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core',
67 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core',
68 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core',
69 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core',
70 Sites/wiki.vvfh.org/resources/Resources.php:			'jquery.ui.core',
71 Sites/wiki.vvfh.org/resources/lib/jquery.ui/PATCHES:themes/smoothness/jquery.ui.core.css:
72 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.datepicker.js: *	jquery.ui.core.js
73 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.sortable.js: *	jquery.ui.core.js
74 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.droppable.js: *	jquery.ui.core.js
75 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.selectable.js: *	jquery.ui.core.js
76 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.tabs.js: *	jquery.ui.core.js
77 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.spinner.js: *  jquery.ui.core.js
78 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.accordion.js: *	jquery.ui.core.js
79 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.progressbar.js: *   jquery.ui.core.js
80 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.autocomplete.js: *	jquery.ui.core.js
81 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.dialog.js: *	jquery.ui.core.js
82 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.button.js: *	jquery.ui.core.js
83 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.slider.js: *	jquery.ui.core.js
84 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.menu.js: *	jquery.ui.core.js
85 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.tooltip.js: *	jquery.ui.core.js
86 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.draggable.js: *	jquery.ui.core.js
87 Sites/wiki.vvfh.org/resources/lib/jquery.ui/jquery.ui.resizable.js: *	jquery.ui.core.js
88 Sites/wiki.vvfh.org/skins/Vector/skin.json:			"jquery.ui.core": [
89 Sites/wiki.vvfh.org/skins/Vector/skin.json:				"skinStyles/jquery.ui/jquery.ui.core.css",

The problem may be the given code example in Extension:WikiEditor/Toolbar customization does not guarantee the code runs after the toolbar has been initialized. There are at least one report of the same issue in the talk page.

@TheDJ: wrote those instructions. Maybe you need to call that function inside a setTimeout() to force a delay.

@TheDJ, you're going to have to walk me through that, or send me to an instruction page. I'm not a programmer. How do I  call that function inside a setTimeout() to force a delay?

And what about the deprecated warnings? Is there something I need to do? Or just ignore them?

With setTimeout:

var customizeToolbar = function() {
    /* Your code goes here */
    $('#wpTextbox1').wikiEditor('addToToolbar', {
        section: 'advanced',
        group: 'format',
        tools: {
            "highlight": {
                label: 'Highlight',
                type: 'button',
                icon: 'images/highlight.png',
                action: {
                    type: 'encapsulate',
                    options: {
                        pre: "<span style=\"background-color: yellow\">",
                        post: "</span>"
                    }
                }
            }
        }
    });
};
/* Check if view is in edit mode and that the required modules are available. Then, customize the toolbar … */
if ($.inArray(mw.config.get('wgAction'), ['edit', 'submit']) !== -1) {
    mw.loader.using('user.options').then(function() {
        // This can be the string "0" if the user disabled the preference
        if (mw.user.options.get('usebetatoolbar') == 1) {
            $.when(
                mw.loader.using('ext.wikiEditor.toolbar'), $.ready
            ).then( function() { window.setTimeout(customizeToolbar, 500) } );
        }
    });
}

Deprecation warnings can be ignored for now. To fix them you should locate first where are they being used and replace them by the correct replacement: mw.config.get() instead of calling wg* variables directly.

Right now the editor is so flaky it's ridiculous. Sometimes it appears. Sometimes it doesn't. Sometimes the yellow highlighter appears. Sometimes it doesn't. The Publish and Cancel buttons come and go. The Find and Replace button comes and goes. Why was all this crap written in Javascript? It seems to be highly unreliable.

It may be caused by another error. Leave the error console open and look for errors when the entire editor doesn't appear. Note that it requires JavaScript because browsers don't provide such functionality.

What I'm finding is that I get different errors depending upon which skin I use:

Vector - the editor appears but the yellow highlighter button I added never does

This is the console output: No errors, only warnings, but no yellow highlighter, despite repeated reloads.

[Warning] This page is using the deprecated ResourceLoader module "jquery.ui.widget".
[Warning] This page is using the deprecated ResourceLoader module "jquery.ui.position".
[Warning] This page is using the deprecated ResourceLoader module "jquery.ui.core".
Please use "mediawiki.ui.button" or "oojs-ui" instead.

Monobook - the editor appears but the yellow highlighter button never does. Console is the same. Ditto for Modern.

Cologne Blue - the same behavior as the others, but with an error in the console

[Error] TypeError: null is not an object (evaluating 'sidebar.appendChild')
	rfmenu (index.php:341)
	fire (load.php:45:128)
	fireWith (load.php:46:436)
	ready (load.php:49:422)
	completed (load.php:49:938)
[Warning] This page is using the deprecated ResourceLoader module "jquery.ui.position". (load.php, line 55)
[Warning] This page is using the deprecated ResourceLoader module "jquery.ui.widget". (load.php, line 86)
[Warning] This page is using the deprecated ResourceLoader module "jquery.ui.core". (load.php, line 11)
Please use "mediawiki.ui.button" or "oojs-ui" instead.

And finally, Timeless, the skin I prefer - no editor ever, no publish or cancel buttons, no search/replace button - nothing at all

[Error] TypeError: null is not an object (evaluating 'sidebar.appendChild')
	rfmenu (index.php:341)
	fire (load.php:45:128)
	fireWith (load.php:46:436)
	ready (load.php:49:422)
	completed (load.php:49:938)
[Warning] This page is using the deprecated ResourceLoader module "jquery.ui.position". (load.php, line 55)
[Warning] This page is using the deprecated ResourceLoader module "jquery.ui.widget". (load.php, line 86)
[Warning] This page is using the deprecated ResourceLoader module "jquery.ui.core". (load.php, line 11)
Please use "mediawiki.ui.button" or "oojs-ui" instead.

I think what this tells me is that skins make a difference in whether or not the editor loads, but the customized button I created is a different problem. At this point, I'm getting very frustrated with this.

UPDATE: And, just like that, the editor suddenly appears in Timeless - still no custom highlighter button. The behavior of the editor is so flaky and unreliable that it's almost not worth having. There has to be some underlying cause for this behavior, but where would I look to find it?

2nd UPDATE: I found this log, but it's empty: less log/errors.log. You're probably going to tell me I don't have error logging enabled. Off to Google again.

This likely has nothing to do with the editor. You probably have some custom script, or outdated/broken extension that is throwing JS errors, which breaks the rest of the JS on the page. Whatever is creating the sidebar.appendChild error is at least one of the causes, so you should track that down. The fact that it happens randomly makes it seem to be a race condition, perhaps a script relying on another script to load first, or a certain element to be created.

As for error logs, those are only server side things, like PHP errors. You won't find client side errors there, those are only in your browser console.

I just installed 1.29 about a month ago. All my extensions have been installed from the MediaWiki Extensions Directory, and all of them are supposed to be for 1.29.

I greped the files for sidebar.appendChild, but it returned nothing. I assume this means the suspect Javascript is in the db. How can I trace down the offending file?

Maybe try disabling all other gadgets and see if it changes anything.

I enabled the debug console but found nothing useful.

I opened console, clicked on edit, then looked at the results. This is the Javascript that's causing the error:

/*************
*** Regex menu framework 1.2
*** by [[m:user:Pathoschild]]
*** documentation: http://meta.wikimedia.org/wiki/User:Pathoschild/Script:Regex_menu_framework
*************/

	/* create menu */
		var container = document.createElement('div');
		container.setAttribute('class','portlet portal collapsed');
		container.setAttribute('id','p-regex');
		sidebar.appendChild(container);

How do I find this thing and get rid of it?

UPDATE: Never mind. I found it. It was a gadget under advanced. I deleted it, and the error message is gone, and the editor now appears. But I'm still not getting the custom button that I added.

I spent some time figuring out how to add a Comodo SSL icon to the footer. After I got it working, I checked it in all the skins. In Cologne Blue there are no icons at all. The Powered By and Copyright icons aren't even there. In Modern, the icons didn't appear. Just the Alt text was there, linked to the relevant sites. In Monobook, the Copyright icon was on the far left, the Comodo in the middle and the Powered by on the far right. In Vector, the order was reversed from what it is in my preferred skin, Timeless.

Are there no rules for skins at all? It seems there ought to be a requirement for some defaults that would appear in all skins. Either that's not the case, or it's not being honored. Shouldn't MediaWiki at least require that the bundled skins behave as expected?

You didn’t say the technique you used to make it work. Generally speaking there is no guarantee that all skins support all skinning features; Vector is the reference skin, MonoBook has still some support, Minerva is the default skin on mobile, and Timeless is currently experimental, others are probably less supported.

To customise the footer icons, you can use $wgFooterIcons, or the hooks SkinGetPoweredBy and SkinCopyrightFooter, but again there is no guarantee they will be displayed on all skins.

I used this:

$wgFooterIcons = [
        "copyright" => [
                "copyright" => [], // placeholder for the built in copyright icon
        ],
        "poweredby" => [
                "mediawiki" => [
                        // Defaults to point at
                        // "$wgResourceBasePath/resources/assets/poweredby_mediawiki_88x31.png"
                        // plus srcset for 1.5x, 2x resolution variants.
                        "src" => null,
                        "url" => "//www.mediawiki.org/",
                        "alt" => "Powered by MediaWiki",
                ]
        ],
        "comodo" => [
                "comodo" => [
                        "src" => "/images/trusted-site-seal-sm.png",
                        "url" => "https://www.comodo.com",
                        "alt" => "SSL by Comodo",
                        "width" => "94",
                        "height" => "49",
                ]
        ],
];

I can't log-in on my wiki. The message "There has been a problem whlie transfering your data. The process has been canceled [...]. Please return to your last page, reload it and try to log-in again." I've done this five times and I still can't access my account.

I'm using MW 1.27.1.

See Topic:T7irqyk4rhfy3ohk.

I tried <code>$wgMainCacheType = CACHE_DB;</code> and <code>$wgMainCacheType= CACHE_ANYTHING;</code> and I still can't access my account.Before I changed the values it's default code was <code>$wgMainCacheType = CACHE_NONE;</code>

Before this happened I tried to move my domain from http://mywiki to https://mywiki but I couldn't access my wiki. So I undid my change and this happened. Is this problem related to my login issue?

Did you remember to reset $wgServer to the non-HTTPS URL?

What is the best way to make a MediaWiki installation send an email for testing purposes?

I'm working to get SMTP configured properly but am not sure how to easily trigger the wiki to send a test message. Thanks for any suggestions!

You can request a new password on the login page, it should send an email. Or when logged as user, you can also authenticate your email from the preferences.

If you have your own SMTP server: If you can it is better to monitor the SMTP server to check if it really send the emails during your initial setup. If you cannot, be careful about the spam filters in the receiving email address. If you don’t receive the email there are two possibilities: either it was not send by MediaWiki and/or your SMTP server, either the receiving address put it in the Spam folder or even discarded the email because your SMTP server don’t have a good (enough) reputation.

When it will work you should monitor your SMTP server to keep and ideally improve its reputation (be sure it don’t send spam, add mechanisms like SPF and/or DKIM, check and monitor major DNSBLs, fill forms in major email providers to certify your good practices, etc.). You don’t have to do all these actions, but the more you do the better your email quality and deliverability will be.

All this does not really apply if you send MediaWiki emails through an email provider (Gmail, Yahoo, Microsoft, etc.), although you should anyway monitor the emails are really sent, for instance once a month or once a year.

Am creating acount using api, while calling curl am getting invalid csrf token error

how can i solve it

Provide the valid token previously requested, and propagate the same cookies received when you requested the token.