…ut may not be added When a provider class does not provide a method to output one of its registered columns, our list table should account for the possible lack of row actions. This commit adds a tracking property for the display of row actions. If a column's output is not handled by the provider class and row actions have not yet been displayed, we handle output of the row actions. Once row actions have been output once, the flag is maintained throughout the row. When the row is complete, the flag is reset for the next. One quirk - if a provider class handles the output for the first column, but does not handle row actions, and does not handle the output for the next column, row actions will be output in that second column. This feels a little weird, but I think gets us close enough. Fixes #51
For some reason the keydown event wasn't firing when it was attached to `input` and `select` elements in the quick edit form. By copying core's metho and attaching the keydown to `td`, Enter now works to save the inline form properly.
…will actually have been filtered
For Enterprise sites, only Google DFP async will be supported to start. We won't need to present the user with a picker. For other sites doing the configuration at the code level, they probably don't want their users mucking with the option.
Some key ideas: * DFP Async default configuration lives in doubleclick-for-publishers-async.php. The goal is for it to be comprehensive enough that all you need to do is do_action() for your ad tags. The last things to do are standardize the ad code configuration variables and default ad units. * 'enable_ui_mapping' is a new flag you can add to your ad tags. Functionally, it means a given ad code mapped through the admin UI to an ad tag will only be registered with that tag. * get_matching_ad_code() is a new class-level method to get the currently matching ad code for a tag. It's an abstract ion of the conditional logic in action_acm_tag() with nothing additional added. * Added support for `<select>` type URL vars in Quick Edit. @aliso had already added this for the "New Ad Code" form.
… would break backwards compat. See #52 (comment)
The plugin can now be used without any code required in the theme. The Doubleclick For Publishers Async provider includes more options in the admin to insert ads at common theme hooks, like 'before', 'before_header', and 'the_content'. The user can now choose their provider from a drop-down list on the admin page.
…avoid conflicts with filters. Make sure that columns have cb and ID. Closes #49
If the logical operator is filtered, it should set the default behavior of the dropdown, etc. See #48
…s the 'acm_logical_operator' filter. May need to include a backwards compatible solution for those users who are using that filter.