Action Omnibus: assorted useful actions and filters

[tellyworth]

WordPress.com uses a number of hacked-in actions and simple filters for various plugins. It's likely that the actions we've added will be useful to others too, so I'm proposing in this ticket that we add them to core.

Patch forthcoming. All of these actions and filters are simple one-liners with no conditional code, so they are low risk. A few just add extra parameters to existing actions.

[DrewAPicture]

Hi @tellyworth, thanks for the patch. Some notes on action-omnibus-1.diff​:

• Any new parameters added to hooks need corresponding changelog entries in the hook docs, e.g. addition @since entries for the current version mentioning that the parameter was added
• @since versions should use the 3-digit, x.x.x style
• Parameter descriptions should end with a period
• Parameter types, variables, and descriptions should be vertically aligned with spaces, each section separated by a single space and wrapped at the 80-120 character mark, no tabs inside of the DocBlocks
• There should be a blank line directly before a hook doc if the line above is equally indented
• Hooks should be only have a corresponding DocBlock in one location, with duplicate comments pointing to the file where the original is located (even if it's in the same file), e.g. /** This filter|action is documented in path/to/file.php
• Hook lines should follow core coding standards for spacing

All that said, realistically, these actions and filters should be submitted via individual tickets since they span several different files and components.

[jorbin]

While many of these have the potential to be a great addition to core, I think each one should be discussed individually.

[wonderboymusic]

We can perhaps attack these one at a time here.

[wonderboymusic]

Here's some more commit juice for you - these can easily be done here and split across commits, rather than making 11 new tickets.

[DrewAPicture]

I'll take a look. Let's move this off the milestone pending ready patch(es).