Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

22 Excellent

1 Follower

About Skizzerz

  • Rank
  • Birthday October 10

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Namespaces are generally the recommended way of going about this. As you've discovered, you do need to specify the namespace in each link, however. There is no way to avoid this without an extension, although you can work around it by using a template that auto-fills the current namespace instead of directly using link markup.
  2. You'll want to install some anti-spam extensions. I recommend ConfirmEdit (adds a CAPTCHA) and AbuseFilter (lets you manually define filters that can block edits) at a minimum. This will prevent spambots from being able to easily sign up and create spam pages on your wiki. For the email issue, I can't really say what may be going on there. It could just be confirmation emails, because I'm not aware of any active security vulnerabilities that allow users to send email to arbitrary other addresses via the wiki.
  3. You could use ParserFunctions #ifeq to compare the version a page is for with the current version, and display the warning banner and related things if they don't match. More complicated things can be done as well by making use of other functions that can split strings up to compare each component of a version number independently. See https://www.mediawiki.org/wiki/Help:Extension:ParserFunctions for some more details on the ParserFunctions extension. Other extensions exist which add even more capabilities compared to what is listed there.
  4. Did you install parsoid and ensure it's accessible?
  5. The first one will cause issues so I wouldn't recommend it. For options 2 or 3: Make a very heading, such that it wraps around multiple lines on a desktop browser. See which of the options looks better there. Try it on tablet and mobile devices (or use browser dev tools to emulate those device sizes if you don't have any actual devices available), focusing mostly on normal-sized headings. These headings will probably not wrap on tablet, but may wrap on mobile. See which of the options looks better there. As for where to put it: depends. Common.css affects every skin, Vector.css affects only the vector skin. Given that skins can put edit links pretty much wherever they want, there's no guarantee that your change for vector will work properly on other skins.
  6. You can add custom CSS to your wiki to move it back to the right; you may wish to test that your edits look good across a variety of screen sizes from mobile phones up to desktops. The edit section tag is in a class called "mw-editsection", so you can use that for your selector. To add custom CSS to your wiki, edit the page MediaWiki:Common.css while logged into an administrator account, or MediaWiki:Vector.css if you wish for those changes to only apply to the Vector skin. See the manual page on mediawiki.org for more information.
  7. Limitations in MediaWiki, for the most part. Injecting javascript into <head> is a chore, injecting javascript at the end of <body> is natively supported. In practice where you put the code makes no difference whatsoever.
  8. Try the following troubleshooting steps: Verify that you have the correct analytics ID in the extension Verify that the analytics code is appearing in the page source. If it does not, you either do not have the extension enabled (check Special:Version), or the extension is configured to not track you (because you are sending DNT with your requests, or you are part of an exempt user group). If the latter case, you can modify the extension config in LocalSettings.php. If the code appears but you still see no data, ensure that your browser isn't blocking the request. Many ad blockers will block Google Analytics and some browsers such as Firefox have built-in privacy settings that may block trackers as well.
  9. If you see $wgDBmwschema in your LocalSettings.php, delete that line entirely.
  10. What error messages did you receive as part of the upgrade process? Try generating a fresh LocalSettings.php as @HSRobinson suggested (installing to a new database, modifying the database name/password in LocalSettings.php to point to the existing 1.18 database, then running the updater again). If this method works, then the likely issue is that you forgot to update some skins or extensions -- when updating MediaWiki you also need to download the updates for all skins/extensions you use. If a skin or extension doesn't have updates between 1.18 and 1.33, it is likely not compatible with 1.33 and an alternative should be found.
  11. You need access to the backend server (such as via SSH) in order to directly look at and query the database tables. If you are looking for something more powerful to generate lists of pages on-wiki based on whatever criteria, you can check out the DPL extension. Fair warning though: it's very easy to knock your wiki offline temporarily with a poorly-written DPL query.
  12. I don't see any issues on the linked page. Can you describe in more detail what your problem actually is? Screenshots or error messages are helpful
  13. If you're unable to connect, it sounds like it may be blocked by the firewall. You'll want to ensure that HTTP and HTTPS are enabled for outside connections into your NAS box.
  14. Skizzerz


    Version 1.0.0


    GTag Extension for MediaWiki The GTag extension lets you insert the new Google Analytics tracking tag on your MediaWiki site (gtag.js). Requirements MediaWiki 1.34 or later Installation Download the file (a free account is required) and extract the file to your extensions directory. We recommend that you "follow" the download so that you are notified of new updates via email when they are released. To install the extension, add the following to your LocalSettings.php file: wfLoadExtension( 'GTag' ); $wgGTagAnalyticsId = 'UA-XXXXXXXX-X'; // replace with your GA id Configuration In addition to the required $wgGTagAnalyticsId, this extension features many optional configuration variables that you may add to your LocalSettings.php file. Variable Default Description $wgGTagAnalyticsId none Google Analytics Id, for example 'UA-123456789-1'. Required. $wgGTagHonorDNT true If true, honor "Do Not Track" requests from browsers. If false, ignore such requests. $wgGTagTrackSensitivePages true If true, insert tracking code into sensitive pages such as Special:UserLogin and Special:Preferences. If false, no tracking code is added to these pages. In addition to these configuration variables, you may assign the right gtag-exempt to user groups to prevent them from being tracked. This can be useful to give to staff groups so that your internal users and staff are not tracked, giving you a better idea of who is actually using your site. For example: $wgGroupPermissions['sysop']['gtag-exempt'] = true; Support Free community support is available on the mwusers.org forums. Paid support plans are available as well.


  15. This feature is added by the Cite extension. You will need to enable the extension in LocalSettings.php before it will work. If you downloaded MediaWiki via a tarball, you likely already have the extension files downloaded; they just aren't enabled by default.
  • 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.