Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Skizzerz

  1. Assuming you're asking for a space to have a private article "draft" on-wiki, there is nothing like this out-of-the-box, and the only extension I see is unmaintained. You can copy/paste the wikitext into a local file while you're still working on it, using Show Preview on the wiki to see what it looks like but never actually saving the page until it's ready to go. If you don't care about the draft being public while it's a work in progress, you can also insert a work-in-progress notification on the top of the page while you're working on it. As for uploading data via [[Special:Upload
  2. There are a few ways to go about this; the way I would personally recommend is as follows: Ring 1 is your internal (not public-facing) wikis. Staff wiki, staging wikis, etc. Ring 2 are your public-facing wikis (main wiki, any other wikis run by the farm as opposed to users). Ring 3 are a select few user wikis, ideally active ones where the users/admins are good about reporting issues. Ring 4 is everything else. You would therefore have a directory structure as follows (assuming /var/www is your webroot): /var/www/ring1/w contains the wiki files for Ring 1 w
  3. This should now be fixed, sorry for the inconvenience!
  4. It looks like your .htaccess RewriteRule is what is blocking it. I highly recommend disabling or revisiting that rule as it will cause issues with the wiki itself as well -- you will be unable to view or edit any page with a . in it followed by letters. What is that rule supposed to be protecting against? To be clear: it isn't failing to find the files. You are getting 403 Forbidden back. Your RewriteCond is checking for a query string containing a period followed by anything EXCEPT a bunch of special characters. So having something like ".styles" or ".css" in the query string will trip i
  5. Can you please let us know the value of every setting in LocalSettings.php that has the word 'Path' or 'Directory' in it? For example: $wgScriptPath, $wgStylePath, $wgArticlePath, etc. Are you using pretty URLs/short URLs in your wiki? If so, can you please post the URL rewrite-related contents of your .htaccess file (assuming apache)? In your browser, open up the dev tools (usually by pressing F12). Go to the network tab and then refresh the site with ?debug=1 added to the end of the URL (or &debug=1 if the URL already has a '?' in it). For example: http://example.com/wiki/Pagen
  6. Is your wiki public? If so, can you please link to it?
  7. I've added a new Manuals section to the website (check the Browse tab to find it). I plan on putting up useful walkthroughs and interactive applications to make administering MediaWiki easier. Right now, I've added an app to generate configs to make "Pretty URLs". I'm looking for feedback on what you all would like to see next, is there anything in particular you feel is missing from the MediaWiki.org docs or is there some painful process that you wish had a wizard? Let me know!
  8. Generate configurations for Pretty URLs (also known as Short URLs) for MediaWiki with this handy tool. Supports both Apache and IIS! Enter what your URLs currently look like and what you want them to look like, then copy the generated configuration over to your LocalSettings.php and .htaccess or web.config. Click Here to launch the generator.
  9. With over a decade of experience with MediaWiki development, the MediaWiki Users staff offers professional services for hire. We specialize in server maintenance (installing and upgrading MediaWiki including setting up ancillary services such as the webserver, database, and backups) and extension development in the following areas: Authentication and authorization, integrating MediaWiki into your company's existing auth system. Permission setup, to ensure that everyone has access only to what they are supposed to. Updating abandoned extensions to work with modern versions of
  10. Looks like your email was already marked as confirmed, so all is well
  11. By default, nobody has permissions to do anything when Extension:OAuth is installed. You can adjust this by setting $wgGroupPermissions at the bottom of your LocalSettings.php. Here is a sample configuration: $wgGroupPermissions['user']['mwoauthmanagemygrants'] = true; // All logged-in users can manage what access consumers tied to their accounts have. Do NOT change this line to a different group. $wgGroupPermissions['user']['mwoauthproposeconsumer'] = true; // All logged-in users can propose new consumers $wgGroupPermissions['user']['mwoauthupdateownconsumer'] = true; // All logged-in use
  12. Extension:OAuth sets up the OAuth server. In other words, it lets other applications connect to you. Depending on what you want for your OAuth deployment, you'll want one of two things: If you want your wiki to be the canonical source of users, install Extension:OAuth. From there, you can register consumer applications on your wiki to obtain consumer keys and secret keys for use elsewhere to connect to your wiki. (More on this process further below) If you want your wiki to connect to some other wiki or OAuth source, install Extension:OAuthAuthentication. I'm not sure if this exte
  13. From Chad Horohoe on MediaWiki-announce:
  14. MediaWiki Users aims to be the premiere experience for obtaining support with the MediaWiki software. We have free community forums where you can ask questions from knowledgeable peers as well as a place where you can request or advertise for-pay MediaWiki services. MediaWiki Users is ad-free and supported by selling its own services for MediaWiki. Creating an account is free and easy, so join today!
  • 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.