Jump to content

Skizzerz

Administrators
  • Content Count

    151
  • Joined

  • Last visited

Posts posted by Skizzerz

  1. If it's big and may cause timeouts on the web, use the importDump.php maintenance script from the command line. This involves first uploading the xml file onto the server somewhere, and then running the script on the file.

    It will still take a long time, but will not time out because maintenance scripts do not have time limits on execution.

  2. I recommend taking a look at the help page about Templates. It goes over what templates do (and don't do), and how you can easily copy templates from one wiki to another. Keep in mind that many templates require extensions such as ParserFunctions, Scribunto, or TemplateStyles to be installed on your wiki before they will work properly. You can find that help page at Help:Templates on mediawiki.org.

    You don't need a template to make an FAQ page -- the template is just some additional wikitext behind the scenes.

  3. Lack of highlighting generally indicates that the call to pygments is failing for some reason or another. You may wish to temporarily enable debug logging to better understand why this is happening. Chances are the issue lies with your choice of OS: I believe that the extension only ships a linux binary of pygments, but not a mac binary. You may need to install pygments separately and point to it via $wgPygmentsPath.

  4. Blank page indicates a PHP error: see here for how to diagnose it: https://www.mediawiki.org/wiki/Manual:Common_errors_and_symptoms#You_see_a_Blank_Page

    I note that your wiki is currently running 1.31.0 which has known security vulnerabilities. You should ensure you always keep MediaWiki up-to-date. Right now, that means upgrading to one of the following versions:

    • 1.31.12 LTS (EOL June 2021)
    • 1.35.1 LTS (EOL September 2023)
  5. MediaWiki 1.30 went end of life a year and a half ago (June 2019), and is no longer receiving any security or maintenance updates. You should definitely upgrade that wiki if it is exposed to the internet in any fashion. See Version lifecycle for more information on MediaWiki EOL dates.

    For PHP and MySQL versions, check the Compatibility page

    The general recommendation is to install the dependencies (apache, PHP, mysql) via your distribution's package manager and then keep them updated via said package manager on a regular basis. MediaWiki remains compatible with the older versions present in package managers from e.g. Debian stable for quite some time. Unless you are doing a very exotic setup (or if you're on Windows) there's generally no need to install the underlying dependencies manually.

  6. If you're already on Apache 2.4.x, upgrading it to a later version of 2.4.x shouldn't introduce any issues with upstream applications. There should be nothing you need to do for your wiki, just upgrade apache. (that said, you should also endeavor to keep the rest of your tech stack up to date, which means updating mysql, mediawiki, your server's kernel, etc. as things come in)

  7. Check Special:Version on the wiki to see if they have any extensions that seem related to the feature in question, and then searching mediawiki.org about it is your best bet. There's no one answer that will 100% work for any arbitrary feature. For things that appear in the page itself, editing/viewing the source of the page may help as well (you may need to go through some nested template rabbit holes first though)

  8. You need to login to the API first (generally this is done by using a bot password generated at Special:BotPasswords). You will need to ensure the bot password used has the appropriate scopes to do whatever you want it to do (such as edit pages).

    The login API will attempt to set some cookies. You are required to save these cookies in your python script and present them to all future API requests, so it can pull up your logged-in session.

  9. You need to use the #tag parser function, see https://www.mediawiki.org/wiki/Help:Magic_words#Miscellaneous for more information on that. <ref> does not allow embedding any wiki markup inside of it, but {{#tag:ref}} does

    Example (untested, may require modification to work):

    {{#tag:ref|Contents of the primary footnote/reference goes here.{{#tag:ref|Secondary footnote/reference goes here|name=secondary}}|name=primary}}

    This example is the equivalent of the following. Note the following markup does not work, this is meant to just give a better visualization of what the above text is doing:

    <ref name="primary">Contents of the primary footnote/reference goes here.<ref name="secondary">Secondary footnote/reference goes here</ref></ref>

     

  10. That is most likely the HotCat gadget. To get it on your wiki you'd need to

    1. Install the Gadgets extension: https://www.mediawiki.org/wiki/Extension:Gadgets
    2. Set up the HotCat gadget on your wiki:
      1. Export the gadget from Wikipedia: https://en.wikipedia.org/wiki/Special:Gadgets/export/HotCat (this will download a .xml file)
      2. Go to [[Special:Import]] on your wiki and import the .xml file you just downloaded
      3. Edit the page [[MediaWiki:Gadgets-definition]] on your wiki and add a new line containing the text shown on the export page in step 1
    • Like 2
  11. VisualEditor in 1.35 no longer requires Parsoid to be running. You should decommission your Parsoid server if at all possible and remove all references to it in your LocalSettings.php.

    Other extensions (such as Math) may also have their own config that point to external services. If you make use of a local Mathoid instance, for example, VisualEditor will automatically try to use a local Parsoid instance. Be careful of that as well (mostly by not configuring such extensions to use those services).

  12. There are no scripts that MediaWiki ships with to repair corruption in the text table caused by manual modifications, because that is not a supported scenario. However, modifying an existing table entry (compared to making a new one) should take effect right away. Try rebuilding your caches with the rebuildall.php script; it's possible the old version is simply being cached, and that will cause it to be re-parsed. You may run into exceptions when doing that, you'll need to clean that up manually if it occurs.

  13. Yes, this is possible. First you'll want the OpenID Connect extension: https://www.mediawiki.org/wiki/Extension:OpenID_Connect

    The OpenID Connect extension requires the PluggableAuth extension as a prerequisite: https://www.mediawiki.org/wiki/Extension:PluggableAuth

    One of the configurations for PluggableAuth (on the second link) allows for local logins in addition to OIDC. You'll want the following in your LocalSettings.php (after loading both extensions):

    $wgPluggableAuth_EnableLocalLogin = true;

     

  14. On 9/19/2020 at 10:03 PM, C.Syde65 said:

    (delete-rootuserpages) = Lets you delete [[User:Username]] but not [[User:Username/subpage 1]]

    (delete-usersubpages) = Lets you delete [[User:Username/subpage 1]] but not [[User:Username]]

    This is correct.

  15. While MediaWiki could be used for all of those things (although you'd need to likely create some custom extensions for your use cases), it is definitely not designed or intended to be any of those things.

    MediaWiki is best used for a collaborative environment where users can work together on creating pages/articles for some purpose. It has been used for encyclopedias, documentation, guides, how-tos, and knowledgebases. Others use it as a general-purpose content management system, although that sort of setup requires a lot of effort.

    See https://www.mediawiki.org/wiki/Manual:Deciding_whether_to_use_a_wiki_as_your_website_type to determine if a wiki is right for what you want to do. For your three examples, my opinion is that a wiki is not the correct software to use for all of them -- use apps designed for that purpose instead.

×
×
  • 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.