singout

THANKS … that worked.

Sorry for the delay in responding … I didn’t get any notice about the reply.

One additional question: Will this change be permanent? Or will it reset every time I update the plugin? Should I add something to my child theme so it doesn’t reset?

It works fine as an ADMINISTRATOR, the only level above AUTHOR. CONTRIBUTOR doesn’t even have many of the rights an AUTHOR has.

BTW, how does this qualify as being “resolved”? Sending a couple of useless links (easily searchable) that provide NO answer to the original question is not resolving anything.

Bah. The new audio player is a huge downgrade from a whole range of far superior audio plugins that were available … almost all of which are shutting down or being deprecated because of this change. Making things simpler for the few who might post audio once in a blue moon (and don’t care about how the player appears or works), but crippling the function for any serious music related blog by creating a completely non-customizable function is poor planning and lousy short-sighted coding.

Anyone find a basic audio plugin that allows the display to be customized that *isn’t* being killed by this piece of dreck? I don’t mind paying for it to be done right.

It’s beyond me as to why ANYONE could think that this is a positive change for WP. If you wanted quick and easy shortcodes for media, there were several highly customizable choices — INCLUDING the uber simple and quite elegantly customizable JetPack stuff. Mandating the crippled core method simply sucks. Hopefully some new plugin will come along to undo this awful change.

Nevermind … another plugin updated and corrected the error.

Thanks for the help.