You might be wondering why ConfigPress exists at all. For none tech-savvy users the AAM configurations might look like some sort of programming language and too complicated to even bother trying to understand it. Why just not simply add all the settings to AAM UI as checkboxes, input fields and drop-downs?
Our first thought was exactly as it have just been mentioned above. Indeed, majority of developers that create large-scale plugins or themes, think very similar way.
However let’s explore the downside of this idea. AAM has over 100 different features and most of them can be configurable to some extend. If we’ve started to add checkboxes and drop-downs to existing AAM UI, we would ended-up with very confusing, overwhelming plugin that had hundreds of buttons to click, check, select etc.
This is the main reason we decided to introduce ConfigPress to alter AAM core behavior with few simply lines of INI-based configurations and when any of the existing configurations are used frequently, then we move it to UI. For example, ability to edit or delete existing capabilities was available to enable/disable with ConfigPress only. Now you can do that on the Settings tab.
Everything that you can find in AAM plugin today is the result of constant collaboration between end users like you and our team. We do not come-up with new features, we carefully analyze feedback and implement new features on demand. That is why do not hesitate to contact us if you have any questions or suggestions.
In order to use AAM configurations, simply go to the Settings area and you will notice a ConfigPress tab with a simple text area where you can enter configurations.
Technically you can use ConfigPress to define configurations for any plugins that support ConfigPress, that is why all AAM settings need to be grouped into [aam] section. Basically just add [aam] before you start entering any other configurations.
If you are a software developer and understand the problem of hard-coding, you can use stand-alone ConfigPress plugin to avoid it. For more information about this subject check ConfigPress article.
List of all available ConfigPress options is coming later. Currently we are in the process of refactoring existing AAM implementation and standardizing naming convention. If you have any questions about what configurations to use for your specific needs, please do not hesitate to contact us.