Symphony.

It would be useful to note which extensions (extension-fields) are actively used (in sections or whatever) on the extensions page. Further it would be good to list the sections in which they are currently used. In use extensions that provide fields should be difficult to disable since doing so breaks every section and page that use them. These sections cannot be deleted until the extension is re-enabled. Unless the user knows to go to http://yoursite.com/symphony/system/extensions/ they are pretty much stuck.

This is a very good point. I’ve done that myself more than once.

I think it needs to be part of a general effort to expose/streamline relationships throughout the system. Hopefully we’ll sneak some of this sort of stuff into 2.1—and this field extensions thing is a good place to start—but it’s not likely to be wholly addressed system-wide until the UI overhaul post-2.1.

As this is a feature request, it will not be considered for 2.0.x.

In use extensions that provide fields should be difficult to disable since doing so breaks every section and page that use them. These sections cannot be deleted until the extension is re-enabled. Unless the user knows to go to http://yoursite.com/symphony/system/extensions/ they are pretty much stuck.

Really? I consider this a bug and not a feature. If on 2.0.* you disable a field extension without first removing it from a section, you are screwed.