How should filters be updated or modified

[salcode]

I think it is worth considering whether it makes sense to detect filters in the way proposed in #24

In that issue @garyjones writes:

There are some filters that are not prefixed with genesis_ which should be checked for:

• get_the_content_limit
• get_the_content_limit_more_link
• get_the_content_limit_allowedtags
• the_content_limit
• g_ent (deprecated in 2.0.0)

In #26 @srikat mentions his own fork, which forgoes filters entirely, which I think is an interesting approach. Personally, I only ever use this plugin to display the actions and I wonder if others use the plugin in the same way (i.e. might it make sense to drop filters entirely)

[christophercochran]

@salcode Filters are so weird, and some have very specific needs, I'm not sure it will be possible to completely automate. There also becomes the challenge of how do you visually represent some of these filters.

For removing them, I could, though my vision with this plugin has always been a super simple guide to find the hook or filter you need simple and easily without disrupting the workflow too much. I will admit, because of filters function in their current state, there is little use unless you know all the arguments, and other details of the filter.

One my future wants and thought is to create a reference guide in the admin, especially for these filters, that will give more details on the hook and how to use it properly. Where in the index 'visual' hooks can be linked to on the site, and taken there to see where it is, as well as linking to the reference guide from the front end to the admin, for additional details if needed.