I have set up the Wiki module and removed all permissions from the Standard user (see image). However, when a Standard user views the wiki pages, they have access to the administration features (see image). Am I just missing a configuration option?
If not and you're testing a "Standard User" on an account that of which is set to Operator, the Operator flag on the account will override the Standard User settings.
It happens a lot. Many different modules, manage content, and is sporadic in its implementation. Always test the site from a standard user logged in, not one switched from your main account as @LoneTreeLeaf said. It has been a headache for those of us in the past... 😊
Yep, there's several sections of the site that allow the Operator status to override the permissions. Even the page visibility is overridden by being logged into a Operator account.
As @Wise suggested, it's best to have two accounts entirely for testing your sites permissions. Have your test account remain as a non-operator (this is default) and create profiles with differing roles on that non-operator account. This makes testing all the different permissions a breeze.
Is this a screenshot from one of your members?
If not and you're testing a "Standard User" on an account that of which is set to Operator, the Operator flag on the account will override the Standard User settings.
Aha! That may be it. It is an Operator that has switched profiles to a "Standard" test user. Does that happen only for the Wiki settings?
It happens a lot. Many different modules, manage content, and is sporadic in its implementation. Always test the site from a standard user logged in, not one switched from your main account as @LoneTreeLeaf said. It has been a headache for those of us in the past... 😊
Yep, there's several sections of the site that allow the Operator status to override the permissions. Even the page visibility is overridden by being logged into a Operator account.
As @Wise suggested, it's best to have two accounts entirely for testing your sites permissions. Have your test account remain as a non-operator (this is default) and create profiles with differing roles on that non-operator account. This makes testing all the different permissions a breeze.