MediaWiki is designed for two basic access modes:. If you intend to have different view permissions than that, MediaWiki is not designed for your usage. See T Data is not necessarily clearly delineated by namespace, page name, or other criteria, and there are a lot of leaks you'll have to plug if you want to make it so see security issues with authorization extensions for a sample.
Other wiki software may be more suitable for your purpose. You have been warned. If you must use MediaWiki, there are three basic possibilities:. See also: Manual:Parameters to Special:Export.
It is not possible to export the contents of a page that cannot be read since r In LocalSettings. If you want to completely remove access to a user, e. However, using User Merge and Delete extension you can merge the account in another one and delete the former; the original account will then "disappear". If you want to preserve history readability i. Since MediaWiki 1.
You may want to have pages editable only by their creator, or ban viewing of history, or any of a number of other things. None of these features are available in an unhacked version of MediaWiki. If you need more fine-grained permissions, see the See also section for links to other wiki packages that are designed for this, as well as hacks that attempt to contort MediaWiki into something it's not designed to be but may work anyway.
Other wiki software may have better support for fine-grained access control than MediaWiki:. If you want better access control but want to use MediaWiki, this is a list of extensions and hacks to allow restrictions not possible in the software proper.
These hacks may be out-of-date check the version they're for. Please don't ask in official MediaWiki support channels if something goes wrong with a third-party hack. Translate this page. Other languages:. You can use the ConfirmAccount extension if you want to set up an account confirmation queue.
If not you may still proceed as follows. New users will still be able to be created by sysops, in the following manner:. Revoking the edit right already prevents affected users from creating new pages and talk pages. If anonymous users can't view your page, neither can search engines. Your site will not be indexed on Google. It seems to me that some people don't know math well. Decimal number especially.
Now, if not logged in, you can see the page called Hauptseite , but also the login page? But I shouldn't have. So what's wrong? Dear Friends,. I got a question. Please excuse if explained before, but it seems tricky to me. I am not quite familiar with Mediawiki-intallations at the moment. Please let me know some suggestions. I want to use a Wiki to organise the cooperation in my company, but we need a more familiar platform.
It is possible to restrict alot of user-rights, of course. But we are looking for a way to define a set of specific PCs to access the Installation. I do not mind a range of IPs or providers, but a set of 20 specific computers, located around the world. Any ideas? I'm using MediaWiki 1. Can someone help. I'm baffled by this: If I try to password-protect the folder where MediaWiki is installed with. All I want is for users to have to use a password to gain access to the main page.
In the section Restrict editing of all pages , the subheads are. These sections describe how to prevent anonymous editing etc. Managing a wiki is complex and daunting enough already; at least the documentation should clarify, not confuse! I've changed. Starting from MediaWiki version 1. Use the Protect feature. By default, any sysop can protect pages so only other sysops can edit them. This does not require editing configuration files. To impose a blanket restriction on editing for all pages, but allow a few such as sandboxes, join request pages, etc.
This may not fit too often, but you could also use the Restrict editing of certain specific pages method mentioned above, with all name spaces protected, and only a special one editable by everyone which has all the pages you want editable.
Schools and other institutions may want to block all edits not from a few specified IP address ranges. To do so, see Manual:Bloquear y desbloquear. The only way to do this at present without modifying the code is to go to Special:Blockip and systematically rangeblock every one of the address ranges that you don't want to be able to edit. This will work for all future versions of MediaWiki. It will not work on a per-namespace basis. Use the user blocking functionality to deprive a user of all edit access.
MediaWiki does not include a possibility to give rights to separate users directly; instead rights are always given to a user group. There is no way in the core software to change permissions of particular users in order to restrict or allow editing particular pages, except by changing their usergroup. There are separate rights for creating talk pages createtalk and creating non-talk pages createpage. If you need per-namespace control finer than that, it is not possible in core MediaWiki, and requires an extension such as Extension:Lockdown.
If you have enabled the ability to upload files, these will be served directly by the underlying web server. As a result, account-based access to the file is unrestricted by default. If sensitive files are uploaded to an internet-accessible wiki, you may wish to add restrictions on where these can be accessed from. On Apache, if your local network were If you need to protect even the sidebar, main page, or login screen for any reason, it's recommended that you use higher-level authentication such as.
To prevent anyone but sysops from viewing a page, it can simply be deleted. To prevent even sysops from viewing it, it can be removed more permanently using Manual:RevisionDelete. To completely destroy the text of the page, it can be manually removed from the database. In any case, the page cannot be edited while in this state, and for most purposes no longer exists.
To have a page act normally for some users but be invisible to others, as is possible for instance in most forum software, is a very different matter. MediaWiki is designed for two basic access modes:. This is the mode used by Wikipedia and its sister projects. This is basically the same as the above, in terms of technical implementation just an extra check for every page view , which is why it exists.
This is the mode of operation used by certain private wikis such as those used by various Wikimedia committees. If you intend to have different view permissions than that, MediaWiki is not designed for your usage. Data is not necessarily clearly delineated by namespace, page name, or other criteria, and there are a lot of leaks you'll have to plug if you want to make it so see security issues with authorization extensions for a sample.
Other wiki software may be more suitable for your purpose. You have been warned. If you must use MediaWiki, there are three basic possibilities:. You will have to reapply it every time you upgrade the software, and it may not be updated immediately when new security fixes or upgrades of MediaWiki are released. Third-party hacks are, of course, not supported by MediaWiki developers, and if you're having problems you shouldn't ask on MediaWiki-l, mediawiki, or other official support channels.
A number of hacks are listed in Category:Page specific user rights extensions. Read about security issues with authorization extensions if you plan to use one of those. It is not possible to export the contents of a page that cannot be read since r
0コメント