Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
TWiki Access Control | ||||||||
Line: 128 to 128 | ||||||||
The same rules apply to ALLOWTOPICCHANGE/DENYTOPICCHANGE and APPLYTOPICRENAME/DENYTOPICRENAME. Setting ALLOWTOPICCHANGE or ALLOWTOPICRENAME to en empty value means the same as not defining it. Setting DENYTOPICCHANGE or DENYTOPICRENAME to an empty value means that anyone can edit or rename the topic. | ||||||||
Changed: | ||||||||
< < | ![]() | |||||||
> > | ![]() ![]() | |||||||
See "How TWiki evaluates ALLOW/DENY settings" below for more on how ALLOW and DENY interacts. | ||||||||
Line: 181 to 183 | ||||||||
| ||||||||
Added: | ||||||||
> > | Access control and INCLUDEALLOWTOPICVIEW and ALLOWTOPICCHANGE only applies to the topic in which the settings are defined. If a topic A includes another topic B, topic A does not inherit the access rights of the included topic B. Examples: Topic A includes topic B
| |||||||
Access Control quick recipesObfuscating Webs | ||||||||
Line: 228 to 239 | ||||||||
Hide Control Settings | ||||||||
Changed: | ||||||||
< < | ![]() | |||||||
> > | ![]() Edit topic preference settings under More topic actions menu. Preferences set in this manner are not visible in the topic text, but take effect nevertheless. Access control settings added as topic preference settings are stored in the topic meta data and they override settings defined in the topic text. | |||||||
Alternatively, place them in HTML comment markers, but this exposes the access setting during ordinary editing. |