Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Skizzerz

  1. Nothing like this is built-in, so you have two options: Create the graphs in an external program and upload them to MediaWiki as image or svg files. Then, you can use the regular image embedding features to show them in the article. Install an extension such as https://www.mediawiki.org/wiki/Extension:Graph and use that to program and display the graphs.
  2. 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.
  3. 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,
  4. Look for $wgActorTableSchemaMigrationStage in your LocalSettings.php. If you see it, delete it from there entirely.
  5. Usually running update.php fixes that. Try it again and see if the update script gives you any error messages.
  6. Skizzerz


    This question is not relevant to this forum; please contact whomever asked you to do this on their Wikipedia talk page.
  7. 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.
  8. 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.
  9. 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
  10. 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 fil
  11. Version 1.3.0


    This extension uses the MediaWiki API and AuthManager framework to direct login requests with no local account to a remote wiki. The account and its preferences are imported, so the remote login only has be done once. This extension is useful for moving a community from another wiki when you do not have access to the user account database. From a user perspective, it's like they already had an account on the local wiki. For more details, see the documentation page on mediawiki.org. We recommend that you "Follow" this file after downloading by clicking the Follow button above the
  12. The WikiForum extension seems like it does most of what the extension you linked did.
  13. 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.
  14. It'd look like $dbw->insert( 'lookups', [ 'lu_name' => $name, 'lu_url' => $url, 'lu_group' => $group, 'lu_order' => 1, 'lu_group_order' => $groupOrder ] );
  15. 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.)
  16. .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
  17. MediaWiki 1.32 has been officially released. Below is a highlight of some of the release notes; you can view the full list here. Changes A new "Interface administrators" group was added, which has the ability to edit sitewide CSS/JS and the CSS/JS of other users. By default, no other group (not even "Administrators") has this capability anymore. We recommend that you do not grant this group to all of your existing administrators, instead only granting it to those who will be responsible for maintaining CSS/JS pages on the wiki. This increases your site's security in the even
  18. Unfortunately, what you seek is likely not possible by using [[Image:]] tags to embed images in pages. If you don't specify a width in the tag itself, MediaWiki defaults to 300px. You can change this default, but it will always be in px instead of percentages. An extension would be needed to change this for [[Image:]] tags, or you could directly embed the images by putting the full url of the image bare into the page (no link syntax around it) ($wgAllowExternalImages, $wgAllowExternalImagesFrom, or $wgEnableImageWhitelist) and then wrap that in a span/div which sets the width.
  19. Use the built-in watchlist feature that @HSRobinson linked above to have your owners notified on pages that they are responsible for. For moderation of changes before they go "live" to the majority of users, the FlaggedRevs extension lets edits still be made but marked by default as "unchecked" -- a reviewer would then need to look over the edit and mark it as good before the revision is fully accepted as default. There is no feature in the extension to restrict that ability to certain people on a per-page basis (although that would be easily achievable via a custom extension that hooks i
  20. Can you try upgrading your version of Translate? The latest version of the language bundle (2018.10) is compatible with MediaWiki 1.31 and I see that there were a few bug fixes for the Translate extension; it is possible that your issue was already fixed. The best way to update the extensions is as follows: Download the latest bundle. Archive the existing versions you have of those extensions in your extensions folder. A decent way to do this on a temporary basis is to rename the directories. For example, rename the "Translate" directory in your extensions directory to "Translate-
  21. That's very odd. Can you provide some additional information about your wiki? You can find all of this information on the Special:Version page on your wiki. MediaWiki version Translate version PHP version
  22. You need to mark the page for translation before you can translate it. Are you saying that you've clicked "Mark this page for translation" but it did nothing? What happens when you click that link, any error messages or other indication of things happening?
  23. The "wiki ID" is a fancy term for "the name of the database where the wiki lives." So, something in your configuration is not setting the database name and/or database prefix correctly for this wiki. My guess has to do with the fact that it's a double subdomain "en.en" and your mapping of subdomain to database name is not changing that period to something else -- periods are not valid in database names or table prefixes.
  24. Did you get the new MediaWiki files via Git or by downloading the tarball? If you got it via Git, you will need to install and update all of the dependencies yourself. See here for more information. If you used the tarball, it appears that some of the files didn't get extracted properly or were possibly missed. Re-download the tarball and re-extract it to a new, empty folder. Then copy over your LocalSettings, updated versions of extensions, and images to the new folder. It's always recommended when upgrading with a tarball release to extract to a new folder as there may be issues ca
  25. A blank page indicates PHP errors. See the how to debug manual for information on displaying the error messages so you can get more information. You may want to insert those error reporting lines at the top of mw-config/index.php instead of in LocalSettings.php.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.