Settings should be well-organized, predictable, and contain a manageable number of options (emphasis added).
The question I have is, what happens when the number of settings your application has does become unmanageable?
In the current application I'm working on, a "Miscellaneous" section was somewhat used as a dumping ground for any one-off configurations that came up as different clients requested new features. As you can imagine, over the years this has built up to a rather large amount of editable fields.
The task I now have is to go through through and reorganize it so it all doesn't fall under a generic miscellaneous category, but the heart of the problem is that the number of ways a user can configure the application is just too unwieldy.
The more we categorize our options, the harder it is for the user to navigate as there are too many sections to discover and go through. The more we limit the number of categories and try to include as much as possible within each group, the more we run into the old problem of grouping settings together that don't really belong.
Really, all our problems stem from the fact that the application is highly customizable, and contains a multitude of configurable settings.
Is there any reading material on trying to manage an inherently large and somewhat unmanageable amount of settings within an application? I know that seems contradictory, but it is the current situation I find myself in.