> In reviewing the content of FlexWiki it is evident that the Rename
> function has been used in ways that cause damage to the integrity of
> the content, and in a manner that makes it difficult to recover the
> prior content. Would it be possible to restrict access to only those
> security principals with the ManageNamespace right?
At the moment, IIRC, there's no way to ask the engine if someone has
ManageNamespace. About the closest you can get is asking if someone has Edit
on _ContentBaseDefinition, but frankly, that's not really the same thing.
It's certainly possible in theory to add an operation like an overload of
HasPermission(). It probably wouldn't even be important to cache it, which
would make implementation a bit easier. We're going to want it in any event
to support dynamic display of the Lock/Unlock buttons in the web front end
(support for Lock/Unlock is present in the engine but not yet exposed).
All this is a small-to-medium job. Feel like taking it on? It would involve
modifying IContentProvider to add an overload of HasPermission [1], then
implementing it everywhere that needed it. Most providers could inherit a
default implementation from ContentProviderBase, which would just forward it
to Next. FileSystemStore and SqlStore would implement it to always return
true.
[1] I think it should look like this:
public bool HasPermission(NamespacePermission permission);
where NamespacePermission looks like this:
public enum NamespacePermission
{
Manage
}
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flexwiki-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
