“rootweb只有”自定义操作的属性只适用于沙箱解决方案？为什么？

Question

我有一个web应用程序范围的功能，这些功能会提供多个网站集合和子区域。

该功能还包含一个导航元素，它将新的自定义操作组添加到“站点设置”页面。我想要的是，只需在网站集的rootweb的设置页面上显示该自定义组（类似于'网站集管理程序的组）。

我的方法是为组中的每个定制使用'rootwobonly=“true”'。不幸的是，如果您正在部署农场解决方案，此属性似乎没有效果。这是一个解决方法吗？这似乎非常不一致，我仍然努力了解它为什么不起作用，而且显然这就是它是： http://msdn.microsoft.com/en-us/library/ms460194.aspx

是否有其他方法可以通过我想要的方式？我真的不想为此元素添加另一个功能;我的解决方案具有大量的功能。

Answer 1

I totally agree that this is inconsistent and a bit misleading. Assuming that tranforming the solution to the Sandbox is a none starter, a few thoughts...

1. You could maybe re-scope the feature to the Web (I'm assuming that it is currently the scoped at the Site) and the just activate it on the root web. That would probably raise another issue though as I suspect that you don't want the feature to show up in the list of available features for each web. To get round that you could make the feature hidden and then activate by PowerShell or whatever on the root web only. However, I suspect you won't really like that idea (it's a bit ugly).

2. Just have the GroupId of your custom action set to SiteCollectionAdmin that way it shows up in the Site Collection Admin group and will only show up on the root web. However, suspect you want a number of links and don't want to pollute the SiteCollectionAdmin group (hence the need for a custom group) so that won't cut it.

3. A spin off idea is just place one link in the SiteCollectionAdmin group and send your user to a custom application page which just houses your links. The draw back of this is that it requires an extra click-through but the up side is that you can now do much more on your launch page than you could every do in a you elements file e.g. selectively show/enable items according to the specific user, as you've got full code behind access to the OM.

4. (This is what I did to work around the work round this issue). Create your custom group and add the custom actions as required. Then set the Rights attribute of every custom action in the group to be ManageWeb (or Full Mask). The effectively means that your custom actions are all only accessible to site collection admins. If all custom actions in the custom group are inaccesible to the end user then the custom group won't show up (what's the point in showing and empty group). The effect of this is that the custom group will only show up for Site Collection Admins. Although your custom actions will still show up if a Site Colection Admin drills into site settings of a sub web they won't show up for a user who is only an admin/owner at a sub-web only.

Option 4 is the way I'm going as I reckon showing the custom group for Site Collection Admins is no real shakes and actually might be useful rather than having to go back up the tree to Site Collection settings.

I hope that helps