Jump to content

Skizzerz

Administrators
  • Content Count

    128
  • Joined

  • Last visited

Everything posted by Skizzerz

  1. 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_
  2. Wiki pages are not files; they are not stored on a filesystem anywhere (which is what makes something a "file"). Pages are stored in the database, so filesystem concepts like extensions do not apply to them.
  3. You can run MediaWiki on anything so long as you can run a web server, PHP, and a database server on it. Most people run it on linux, but there's quite a few that run on windows as well. See https://www.mediawiki.org/wiki/Manual:Installation_requirements for more details.
  4. delete-rootuserpages lets you delete the page [[User:Username]], whereas delete-usersubpages only lets you delete e.g. [[User:Username/subpage 1]], [[User:Username/subpage 2]], etc. If you have the delete permission, you are correct in that you don't need either of the other two.
  5. I'm not familiar with that extension or how it operates, but I can give some insight into MediaWiki's permissions model in a nutshell: Various actions within the wiki are restricted to users who possess certain permissions. Permissions are granted to or revoked from groups. A user belongs to one or more groups. If any of the groups a user belongs to is granted the permission and none of the groups a user belongs to has revoked the permission, the user is allowed to perform that action. The ability to revoke permissions is probably used in less than 1% of wikis and
  6. There's a couple of extensions that can do stuff like that, FlaggedRevs is probably the most popular one of the bunch: https://www.mediawiki.org/wiki/Extension:FlaggedRevs It's rather heavyweight and difficult to configure, however, so you may instead be more interested in the alternatives. They're linked in the "See Also" section at the bottom of that page.
  7. A blank white page indicates a PHP error. This manual goes into a bit more depth on how to view and diagnose those errors. By default, sensitive actions on the wiki break out of frames (such as editing, registering for a new account, updating your preferences, etc.). You will need to configure $wgEditPageFrameOptions if you wish for your framed version of MediaWiki to allow such actions while still being inside of a frame.
  8. There could be a large number of reasons as to why this error is happening. If you don't see anything in your error logs, follow the advice shown and set $wgShowExceptionDetails = true; at the bottom of your LocalSettings.php in order to display the error details on-screen. Without those details, nobody will be able to assist you.
  9. Yes, the https://www.mediawiki.org/wiki/Extension:Auth_remoteuser extension lets you automatically authenticate people to the wiki given arbitrary external credentials. How exactly to set it up will vary based on the authentication provider (what actually validates that the usernames/passwords are valid, when using this extension you're bypassing the normal MediaWiki login flow so your user account password on the wiki will not be checked). For sending a credential through a link, you would need some sort of processing server-side to extract the credential, validate it, and then set the approp
  10. MediaWiki is not really designed for access control schemes were certain users can see pages that other users are unable to see, but https://www.mediawiki.org/wiki/Extension:Lockdown facilitates that method of operation. This would allow you to lock down certain wiki pages (such as every page in a particular namespace) so that only people with the correct group can read them. Then you simply add that group to the wiki accounts for the people that should have access, and when they log in they can view the pages. If you are referring to a solution outside of MediaWiki (not having restricted
  11. 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.
  12. 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.
  13. 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.
  14. Did you install parsoid and ensure it's accessible?
  15. 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.c
  16. 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.
  17. 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.
  18. 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 bl
  19. If you see $wgDBmwschema in your LocalSettings.php, delete that line entirely.
  20. 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.
  21. 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.
  22. 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
  23. 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.
  24. Skizzerz

    GTag

    Version 1.1.0

    70 downloads

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