Last modified: 2009-05-30 23:17:45 UTC
Gentlemen, allow us to examine what happens when one does $wgGroupPermissions['*' ]['read'] = true; $wgGroupPermissions['*' ]['edit'] = false; $wgGroupPermissions['*' ]['createaccount'] = false; Users will still see lots of Login/Create Account items to click on, only to find at the end of the click trail no button to create account. Indeed, this is after they have clicked on "edit this page", to only be then told they had to create an account. The impression is a trail of "sucker clicks", "false advertisement", "bait and switch". Note the URL above for a test drive. Therefore the navigation items should be adjusted to show what can actually be navigated to. (I couldn't add suresh at hserus dot net, the owner into the CC box above.)
Surely you could simply change the MediaWiki:Userlogin text to reflect what settings were in effect?
> Surely you could simply change the MediaWiki:Userlogin Kludge workaround. Two wrongs don't make a right. Ah, two functionalities glued into the same message: 'userlogin'=> 'Log in / create account' No wonder it is not easy for the program to detect the values of the above array and only print what is possible. (Actually if it was my wiki, I wouldn't have it on clampdown mode, so would never know about the special case of a anti-wiki wiki. Anyways, if indeed you want to make Mediawiki ready for such clampdown wikis, do adjust what gets sent to the screen according what the values of the array are.) Let's put it this way: you check the array before allowing users to create new accounts, right. OK, then also check the array before inviting users to create a new account!
And furthermore, there are tons of pop-up messages e.g., "You can edit this page" etc. Instead of having the sysop hack up each, just display the ones that the software can follow through on its part of the deal. No more bait and switch. Indeed in the HTML, say "view source" instead of "Edit this page", if that is what current permissions only allow.
*** This bug has been marked as a duplicate of bug 17630 ***
