• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

On TWiki.org, TWiki:TWiki.SitePermissions aggregates the ALLOWWEB* settings in WebPreferences for all webs.

It does not work on my installation of Dakar (but I've just noticed it works on develop.twiki.org). Weird.


What do you mean "it doesn't work"? Specifics? CC
Note that SitePermissions is misleading; Setting ALLOWTOPICCHANGE to the null string is not the same thing as not setting it. SitePermissions must be fixed to reflect this, or removed - otherwise it is dangerous!! CC
I've updated SitePermissions to include a warning about this. However thr underlying problem still needs to be addressed. - AA
What underlying problem?????? CC
That the display presented by TWiki:TWiki.SitePermissions can't communicate the difference between the difference between
   * Set ALLOWWEBCHANGE = TWikiAdminGroup
   * #Set DENYWEBCHANGE = 
and
   * Set ALLOWWEBCHANGE = TWikiAdminGroup
   * Set DENYWEBCHANGE = 

If I understand correctly, the former resticts modifications to the TWikiAdminGroup but since DENY has priority the second example means "DENY nobody", i.e. ALLOW everbody. Thus the two examples are woldly different in result, but would be displayed exactly the same by TWiki:TWiki.SitePermissions

The flaw is not with the access control mechanism, it is with the way it is being communicated. The result could be misleading and dangerous. -- AA


This is the result of using a SEARCH to pull out the value setting rather than asking TWiki what the setting is. I originally implemented this feature using the TWiki:Plugins.TopicVarsPlugin - but was told by Peter that SEARCH was the way to go.

I believe that plugin's functionality should become part of the core and extraction of topic's variable should have its own syntax, e.g.

=%Main.WebPreferences.ALLOWWEBCHANGE%
-- MC
OK, this is understood, is not a bug, so I have rescoped it as an enhancement. CC


Y. Sorry, it started as a bug because on my install egrep was not being found so the table broke silently.

MC

Edit | Attach | Watch | Print version | History: r13 < r12 < r11 < r10 < r9 | Backlinks | Raw View |  Raw edit | More topic actions
Topic revision: r13 - 2005-08-03 - MartinCleaver
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback