I have a web application scoped feature which provisions a number of site collections and subsites.
The feature also contains a navigation element, which adds a new custom action group to the site settings page. What I would like is for that custom group to only show up on the settings page of the rootweb of the site collection (sort of like the 'Site Collection Administration' group).
My approach was to use 'RootWebOnly="True"' for each CustomAction in the group. Unfortunately, it appears that this property has no effect if you are deploying a farm solution. Is there a workaround for this? This seems hugely inconsistent and I still struggle to understand why it wouldn't work, but apparently that's how it is: http://msdn.microsoft.com/en-us/library/ms460194.aspx
Is there any other way to get it the way I want? I would really prefer not to have to add another feature just for this element; my solution has a large number of features as it is.