Skizzerz

Pretty standard composer stuff, but it's very intimidating if you aren't already familiar with it. The last response in that linked issue is correct -- you need to run the composer command from your wiki root (same directory where LocalSettings.php is). You may have casing issues as well. Generally speaking (and I cannot confirm whether this is correct for chameleon or not), the value for $wgDefaultSkin must be all lowercase but the value inside of wfLoadSkin() should have a capital first letter.

Normally, wiki accounts cannot be deleted. The UserMerge extension may be installed on the wiki in question which would allow for an administrator to reattribute your edits to someone else and then delete your account. Other wikis may have different policies regarding closing or deleting accounts. The best way to find out for sure would be to contact the administrators of the wiki in question, rather than asking on a general-purpose support forum; we have no way of knowing which account you'd like deleted. (If you are referring to your account on these forums rather than a wiki account, use the "Contact Us" link at the bottom of the page to request an account closure)

Look for $wgActorTableSchemaMigrationStage in your LocalSettings.php. If you see it, delete it from there entirely.

Usually running update.php fixes that. Try it again and see if the update script gives you any error messages.

This question is not relevant to this forum; please contact whomever asked you to do this on their Wikipedia talk page.

php.ini is a system configuration file. If you host your own server, you can find the ini file location in phpinfo(). If you have hosting elsewhere, contact your host and ask them to change the value in php.ini. Once changed in php.ini, you should modify your LocalSettings.php file as indicated. As a side note, this is only relevant if you are still stuck on PHP 5. The most recent version of MediaWiki does not support PHP 5. If you are using PHP 7, the warning is meaningless and you can safely ignore it.

You can always include a comment in the wiki markup. Comments are not shown on the page itself, but are visible when editing. Comments begin with <!-- and end with --> Example: <!-- This is a comment that will be displayed while editing, but not visible in the page itself. You can use this to leave notes for editors. --> If you see typos by a different user on a talk page, it's usually poor etiquette to modify someone else's comments. A talk page is used for discussion about a page, and are generally held to different standards compared to mainspace pages.

A blank white page indicates a PHP error, see the How to debug page on mediawiki.org for more information on obtaining the actual error messages. Once you know the error message, if you are having troubles figuring out what it means, post back here and we can help you out. I notice that you are attempting to load the extension twice in your LocalSettings.php; you have both a require_once for the WikiEditor files as well as wfLoadExtension. You should use either wfLoadExtension or require_once, but never both. Moving forwards, extensions should be loaded via wfLoadExtension, as the require_once method is now deprecated in recent versions of MediaWiki and support for it is being removed. Finally, your MediaWiki version (1.27) is going to be end of life next month. You should begin plans to migrate to a more recent version if you wish to continue receiving security updates and improvements.

MediaWiki 1.32.1 has been officially released. Below are a highlight of changes made in this patch release. Changes Fixed an issue in the API list=users which mistakenly reported users as missing Removed hard-coded Google site search from database error screens In addition, other bugs related to backend databases were fixed. Upgrading To upgrade from 1.32.0 to 1.32.1, unpack the new files in-place over the old ones. You do not need to run the database upgrade script (update.php) to upgrade from 1.32.0 to 1.32.1. As always, we recommend making a backup of your files before upgrading.

The WikiForum extension seems like it does most of what the extension you linked did.

Moderation: Moved thread to MediaWiki Support forum. If you believe this thread was moved in error, please provide more details by editing the OP or making a reply. For troubleshooting 500 errors, see the How to debug manual on mediawiki.org. If you can't figure it out but can get exact error messages (from error logs or such), posting those here would allow for additional assistance.

It'd look like $dbw->insert( 'lookups', [ 'lu_name' => $name, 'lu_url' => $url, 'lu_group' => $group, 'lu_order' => 1, 'lu_group_order' => $groupOrder ] );

Never use the raw query() function, use the insert() wrapper instead which properly escapes everything, handles db prefixes, etc. for you. (or the select() wrapper for SELECT queries, or the update() wrapper for UPDATE queries, etc.)

.mw-search-result-data { display: none; } .mw-search-result { display: flex; flex-direction: row; box-sizing: border-box; } .mw-search-result-heading { border: 1px solid black; padding: 0.5rem; width: 25%; } .searchresult { border: 1px solid black; padding: 0.5rem; width: 75%; } You may find the above to be useful as a starting point. This is still missing a couple of things, such as sizing on mobile screens (you'll need to add some @media queries to break on screen size and provide relevant CSS for smaller devices -- the flexbox layout will let you easily collapse it back into multiple rows with the heading on one row and the result underneath rather than side-by-side)