|
Post by Peter on Aug 31, 2012 6:31:13 GMT -7
|
|
|
Post by CoconutCurry on Aug 31, 2012 9:55:49 GMT -7
Spamming this everywhere: If people can decide what content they want on pages, I'll make templates on my next day off to make it easier on everyone!
|
|
|
Post by HardcoreMiner on Aug 31, 2012 12:47:51 GMT -7
I'm giving protections for pages so you need to be registerd to edit them.
|
|
|
Post by Peter on Aug 31, 2012 13:33:04 GMT -7
No Need..
When I set up the Wiki it's globally set to needing to be logged in to edit/create
|
|
|
Post by HardcoreMiner on Sept 1, 2012 7:33:53 GMT -7
Why I'm not admin anymore Peter?
|
|
|
Post by Peter on Sept 1, 2012 12:49:02 GMT -7
Was playing with the settings a bit... Trying to understand what each category doses.. Can you let me know what you can't do as user that you need to do so I know exactly what is what...
Cheers,
|
|
|
Post by HardcoreMiner on Sept 2, 2012 9:19:33 GMT -7
Was playing with the settings a bit... Trying to understand what each category doses.. Can you let me know what you can't do as user that you need to do so I know exactly what is what... Cheers, Well as a normall user I can create and edit articles.This protection seems to only affect unregisterd and new users.
|
|
|
Post by CoconutCurry on Sept 3, 2012 1:24:29 GMT -7
That's good. If its too restrictive, people won't use it.
Can you make different user categories, or is it limited to "user" and "admin"?
|
|
|
Post by Peter on Sept 3, 2012 1:46:50 GMT -7
The default is Beauracrat, Admin and User.. Admins can I believe change user groups and settings form the "special Pages" link but I haven't played with that..
What do we need some sort of "moderator" role half way between user and admin ??
|
|
|
Post by Peter on Sept 3, 2012 1:52:51 GMT -7
This is what it currently is.. (all) - Create discussion pages (createtalk)
- Create new user accounts (createaccount)
- Create pages (which are not discussion pages) (createpage)
- Read pages (read)
- Use of the write API (writeapi)
- Autoconfirmed users
- Edit semi-protected pages (autoconfirmed)
Bots - Be treated as an automated process (bot)
- Edit semi-protected pages (autoconfirmed)
- Have one's own edits automatically marked as patrolled (autopatrol)
- Not create redirects from source pages when moving pages (suppressredirect)
- Not have minor edits to discussion pages trigger the new messages prompt (nominornewtalk)
- Use higher limits in API queries (apihighlimits)
- Use of the write API (writeapi)
Bureaucrats- Edit all user rights (userrights)
- Not be affected by rate limits (noratelimit)
Administrators- Block a user from sending e-mail (blockemail)
- Block other users from editing (block)
- Bypass IP blocks, auto-blocks and range blocks (ipblock-exempt)
- Bypass automatic blocks of proxies (proxyunbannable)
- Change protection levels and edit protected pages (protect)
- Create new user accounts (createaccount)
- Delete pages (delete)
- Delete pages with large histories (bigdelete)
- Edit other users' CSS files (editusercss)
- Edit other users' JavaScript files (edituserjs)
- Edit semi-protected pages (autoconfirmed)
- Edit the user interface (editinterface)
- Have one's own edits automatically marked as patrolled (autopatrol)
- Import pages from a file upload (importupload)
- Import pages from other wikis (import)
- Mark others' edits as patrolled (patrol)
- Mark rolled-back edits as bot edits (markbotedits)
- Move files (movefile)
- Move pages (move)
- Move pages with their subpages (move-subpages)
- Move root user pages (move-rootuserpages)
- Not be affected by rate limits (noratelimit)
- Not create redirects from source pages when moving pages (suppressredirect)
- Override files on the shared media repository locally (reupload-shared)
- Overwrite existing files (reupload)
- Quickly rollback the edits of the last user who edited a particular page (rollback)
- Search deleted pages (browsearchive)
- Unblock themselves (unblockself)
- Undelete a page (undelete)
- Upload files (upload)
- Upload files from a URL (upload_by_url)
- Use higher limits in API queries (apihighlimits)
- View a list of unwatched pages (unwatchedpages)
- View deleted history entries, without their associated text (deletedhistory)
- View deleted text and changes between deleted revisions (deletedtext)
Users - Create discussion pages (createtalk)
- Create pages (which are not discussion pages) (createpage)
- Edit pages (edit)
- Mark edits as minor (minoredit)
- Move files (movefile)
- Move pages (move)
- Move pages with their subpages (move-subpages)
- Move root user pages (move-rootuserpages)
- Override files on the shared media repository locally (reupload-shared)
- Overwrite existing files (reupload)
- Purge the site cache for a page without confirmation (purge)
- Read pages (read)
- Send e-mail to other users (sendemail)
- Upload files (upload)
- Use of the write API (writeapi)
|
|
|
Post by Peter on Sept 3, 2012 1:56:24 GMT -7
Ok I CAN add user groups, but it's a coding config within the localsettings.php file, so a little more involved than just checking boxes.. If we think we need it I can do it though
|
|
|
Post by CoconutCurry on Sept 3, 2012 8:16:11 GMT -7
If its not too difficult, I would make it so non-users couldn't create or edit any pages. What is the protocol going to be to delete pages, or lock them from further edits?
|
|
|
Post by anglewyrm on Sept 3, 2012 10:26:40 GMT -7
If its not too difficult, I would make it so non-users couldn't create or edit any pages. What is the protocol going to be to delete pages, or lock them from further edits? Examining the official wiki, people who have contributed have often registered. And all cases of vandalism were from unregistered ip addresses. So the requirement to register seems like it would do little harm to the creative process while introducing minimal bureaucracy. The idea of locking a page from further edits is a bad one, for at least three reasons: - Wiki quality is the result of crowd sourcing, not individual authorship. Articles are edited and improved upon. Locking would prevent that from happening.
- MineColony is not a finished product. Information can therefore expire, and new information may be necessary. It cannot be objectively stated that a page is complete.
- There is always someone else who can do a better job. Locking would engender an attitude of personal ownership. "I" wrote this article; nobody mess with it, it's good enough. If it wasn't in "my" version, then there's a valid important reason I didn't include it.
Another great cautionary tale can be seen on the Dwarf Fortress Wiki. An admin decided to segment the articles into version numbers that the whole article applies to. The result is that articles are copy/pasted into redundant pages, lots of extra grunt work that no one wants or does was created, and many articles are auto-updated with version numbers that don't apply.
|
|
|
Post by CoconutCurry on Sept 4, 2012 9:58:40 GMT -7
The only pages I would want to lock are pages about items that still exist in the mod but don't do anything (like the scepter) and pages specific to one version of the mod (like say, RC17 glitches). I wouldn't want there to be only one author, but there's no reason for the article to be continuously updated since there is no new information being added.
|
|