Tag Info

Hot answers tagged

8

Add to LocalSettings.php: $wgGroupPermissions['*']['createaccount'] = false; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['read'] = false; But of course admin is able to edit pages.


7

I've used MediaWiki as a CMS on quite a few occasions, though my goal has been to publish (i.e. allow anyone else to view and only editors access to write) content but restrict edit access. To lock down write privileges: $wgGroupPermissions['*']['createaccount'] = false; $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['*']['editpage'] = ...


7

Yes, you need to protect it so that it can only be edited by administrators: You can designate a page as a protected page by clicking the 'Protect page' tab ('protect' in the drop-down menu in Vector), and supplying a comment (a brief textual description of why you are protecting the page).


7

The Special:Version page lists all of the installed extensions for a MediaWiki instance. Also see http://noc.wikimedia.org/conf/ for example of real configuration employing all these extensions, though using it directly would be overkill.


6

If you don't want to use the export-and-reinstall method suggested by danlefree, you might also find the Nuke extension useful. Once installed, visiting the special page Special:Nuke as an administrator gives you a form like this: There are also several built-in MediaWiki maintenance scripts that could be useful, including: cleanupSpam.php, which ...


6

Your question is unclear, and appears to be based on several misunderstandings of how the software works. Assuming I'm guessing correctly: You have a website running the MediaWiki software, and this site is not one of the ones operated by the Wikimedia Foundation. You have reasonably high privileges within the software, but no privileges outside the ...


5

I strongly suggest you run through the Wiki Choice Wizard over at WikiMatrix.org


4

http://en.wikibooks.org/wiki/Special:Version Shows you all the extensions that they are using


4

The easiest way to handle this situation (if you don't mind a nuke'n'pave) would be to export all wiki pages created or edited by your username, reinstall the wiki, and import the export file you'd generated. "Reinstall" in this context would mean: Export articles created by you (presumably logged in as the WikiSysop user or similar) Drop the MW database ...


4

If you're able to install extensions on the site at all then you could try the one for Google Analytics at http://www.mediawiki.org/wiki/Extension:Google_Analytics_Integration Otherwise, another solution might be to try a "web beacon". That's where you insert a resource from an external site into a page so you can track the hits for it when pages are ...


4

You can take the -pages-articles.xml.bz2 from Wikimedia backup dumps site and process them with WikiTaxi(download in upper left corner). Wikitaxi Import tool will create a .taxi(around 15Gb for Wikipedia) file out of the .bz2 file. That file will be used by WikiTaxi program to search through articles. The experience is very similar to the browser experience. ...


3

The second one is better form as it clearly marks the index.php as being the in web root and not in some other subdirectory.


3

Adding this to LocalSettings.php did the trick. It's probably better to not use unlimited, but pick sane defaults instead of "unlimited". $wgMaxShellMemory = unlimited; $wgMaxShellFileSize = unlimited;


3

The version of MediaWiki used by Wikipedia is 1.17wmf1, which I'm guessing stands for Wikimedia Foundation. They use a customised version of the software for their own purposes. I think all you can do is hope they include that new editor in a future release. Or else you could try and download the scripts that they're using and reverse engineer the pages, but ...


3

Another way is: Go to Special:SpecialPages of a given wiki, and check if it has Special:PopularPages; example: http://en.wikipedia.org/wiki/Special:SpecialPages - doesn't have it http://www.alsa-project.org/main/index.php/Special:SpecialPages - has it If you have Special:PopularPages, then you can use that to list page views (counts); but not if it isn't ...


3

Yes, you can use the #switch function to do this. There are some examples on this article - generating dynamic content with mediawiki. The documentation on #switch is here: http://www.mediawiki.org/wiki/Help:Extension:ParserFunctions#.23switch


3

You could use a webcrawler tool which will save the site as HTML files. All the links will be converted, so you can open the main page, say, and then click on links and get to all the site. There are a number of these tools available. I use wget, which is command line based and has thousands of options, so not very friendly. However it is quite powerful. ...


3

Solution {{#dpl:category=Backup|format=,*,[[%PAGE%]]\n,}}


3

Note: Since MediaWiki 1.6, the MediaWiki core has a Google site map generator... It is a command-line utility, and it is located at maintenance/generateSitemap.php in your MediaWiki directory. The command line is "php generateSitemap.php sitename" and is run from the maintenance directory at the server's command line interface. See ...


3

You can do that by editing (or creating, if it doesn't exist) the page Project:Book sources (or a translated version of that name, if the language of your wiki is not English). In the source of that page, MAGICNUMBER will be replaced by the ISBN. You can look at the version of this page on English Wikipedia for inspiration.


2

The easiest way to handle this situation is to install extension DeleteBatch. Use Special:AllPages on your wiki to get a script file of the page names you want deleted, and load it into Special:DeleteBatch.


2

In theory, you could write a MediaWiki extension to do whatever you like to a MediaWiki instance, including to do the things you mentioned. Short of that, and short of the "nuke'n'pave" suggested by danlefree, you might find the User Merge and Delete extension useful: you can use it to consolidate multiple spambot accounts into a single account whose edits ...


2

You have to set some config variables and fix your htaccess file. Here is a actual blog post which describes all the steps: http://paulschreiber.com/blog/2010/07/07/how-to-install-mediawiki-on-a-subdomain/


2

DokuWiki http://www.dokuwiki.org/dokuwiki It has user authentication built in to prevent unauthorized access.


2

It is possible when substing the template. For example ~~<includeonly>~~</includeonly> will display as ~~~~ when the template is transcluded normally, and as a timestamp when substed.


2

You can use the following robots.txt file if you wish to block all robots from accessing your pages. # robots.txt for www.domain.com to block all bots User-agent: * Disallow: / If you wish to block all all URLs that include a question mark (?) you can use the following format # robots.txt for www.domain.com to block URL with ? mark User-agent: * ...


2

Fix Method 1 Update your MediaWiki to the latest version and this resolves this problem. Fix Method 2 If you prefer to use an outdated version then this will fix this problem. Edit includes/ProxyTools.php, after line 70 wfGetIP(). After static $ip: { $ip = "10.10.10.10"; return $ip; } Change 10.10.10.10 to the same IP address of your external internet ...


2

The skin used for Wikipedia, Vector, is the default skin for MediaWiki version 1.17 and above. By editing the CSS files that make up the skin you can change it to look how you want, given enough CSS skills.



Only top voted, non community-wiki answers of a minimum length are eligible