Bob

SOLUTION:

The 4.1 update contained some changes to CSS classes in the mediaelement audio player. I was able to resolve the issues after some time with the Safari web inspector and reviewing my custom CSS. I had checked before posting here, but hadn’t gone deep enough.

Thanks so much for all this, Craig!

Before starting this thread, I checked the Codex re: the Audio Shortcode, which says the basic features supported are src, loop, autoplay, and pre-load. I was disappointed that track numbers couldn’t be toggled off, so it’s great to know that it actually can be done here. It’d be nice if the Codex were updated to include this info.

As for the plugin, are you saying your code could be pasted as-is into a basic plugin without any additional code aside from the standard header and license (as described here)?

Thanks again!

-Bob

Craig: Calling a solution ‘terrible’ without offering an alternative helps nobody. If you have a solution, then great – I’d love to see it. Otherwise, you’re just trolling.

My post acknowledged that this solution could change with future updates.

For newcomers to WP and coding, here are some details:

Modifications are best done via a child theme, but this is not always possible or feasible. Editing the WP core files, while a last resort, is acceptable if you’re careful and know what you’re doing.

One of the caveats to the solution I provided is that when the WP core is updated, your edits will be overwritten if/when a new version of the media.php file is installed. (I don’t know how WP updates work, so I don’t know if, say, incremental updates might only include files which have been changed.)

In addition to line numbers changing if code is added, removed, or modified earlier in the file, the entire implementation of audio players could change at some point, requiring major alterations to this solution or a completely new one (e.g., if new classes are assigned to the track titles, then you can’t use the ones I provided above when searching the code).

At a minimum, you’ll have to re-edit media.php whenever it’s overwritten.

Regarding the quotes, in media.php, there’s a javascript which attaches them to song titles and then outputs the result as a single entity, which means -unless I’m missing something- that they cannot be targeted with CSS. In other words, quotes can only be removed via CSS if they’re added via CSS.

Bottom line: if you know the difference between a text editor and a word processor, and between WP core files and child themes; and are aware that a single typo can wreak havoc with a web site; and are aware of the above caveats, then the solution I provided is perfectly safe, if less than ideal.

Oh, and this topic is now resolved.

Sorry for the extra post – the forum only offers the ‘mark as resolved’ option when you first post, not if you edit after posting.

A programmer friend helped me figure it out.

You must edit the file media.php located in the folder wp-includes. The following line numbers are valid as of WordPress 3.9.2, but of course they can change with updates.

To remove quotes, delete the html code for open quotes and close quotes from lines 1103 and 1115.

Line 1103 before editing:

<span class="wp-playlist-item-meta wp-playlist-item-title">& #8220;{{ data.title }}& #8221; </span>

Line 1103 after editing:

<span class="wp-playlist-item-meta wp-playlist-item-title">{{ data.title }} </span>

Line 1115 before editing:

<span class="wp-playlist-item-title">& #8220;{{{ data.title }}}& #8221;</span>

Line 1115 after editing:

<span class="wp-playlist-item-title">{{{ data.title }}}</span>

Note: Remove the space between the ampersand and the pound sign when searching the code. I put it there only because this forum interpreted the html even when I used the block quote or code markup.

To remove track numbers, go to line 1208 and change 'tracknumbers' => true, to 'tracknumbers' => false,.

Here’s the full block of code where the output is specified:

extract( shortcode_atts( array(
		'type'		=> 'audio',
		'order'		=> 'ASC',
		'orderby'	=> 'menu_order ID',
		'id'		=> $post ? $post->ID : 0,
		'include'	=> '',
		'exclude'   => '',
		'style'		=> 'light',
		'tracklist' => true,
		'tracknumbers' => false,
		'images'	=> true,
		'artists'	=> true
	), $attr, 'playlist' ) );

I had a similar problem:

In Opera 23 for Mac, the audio players appeared only if I was logged in as admin. When I was logged out, they did not appear.

Disabling the cache resolved the issue – thanks, Tobias!

Did not have the issue in Safari, Chrome, or Firefox on the Mac.

A friend did observe this issue in Firefox, Chrome, and IE on Windows 8.1, and disabling the cache did fix it.

Opera 23.0
Mac OS 10.9.4
WordPress 3.9.2
TablePress 1.4

(i.e., everything is current)

Nice to see that Simon updated the plugin. Unfortunately, by the time the update was released I had moved on to another solution.

@almooj-craig: These options appear when you change from auto to manual in

General Settings -> Minify -> Minify Mode

@venturavan: Some general info about blocking vs non-blocking scripts is here.

That article didn’t provide enough info for me to resolve minification issues, or fully explain all those settings, but it’s a start.

If you have any other caching plugins installed but inactive, try deleting them.

I got a fatal error message (might have been a different one) when I first tried to install W3 Total Cache.

Then I realized that while I had inactivated WP Super Cache (another caching plugin), I had not deleted it.

After deleting WPSC, I was able to install W3 Total Cache without incident.

Hope this helps.

Update:

After hunting around folders on my server, I discovered one that contains files with these exact names. It’s part of a paid plugin called WP Lightbox Ultimate.

Also: when I disable the Lightbox plugin, these 404 errors go away, and so do other issues that had appeared in YSlow and Google Page Speed (and other diagnostic tools) related to these image files and plugin scripts.

So it appears that the problem is an interaction between W3 Total Cache and the plugin.

I don’t recall seeing the 404 errors when using WP Super Cache, but that plugin wasn’t working well on my site. I replaced it with W3 Total Cache yesterday and noticed an immediate improvement, both subjectively and in the performance scores at YSlow, etc.

I’ve contacted the Lightbox plugin developer.

If anyone has ideas how I might otherwise look into this, I’d appreciate any pointers.

Thanks!

Correction: third file in list should be’prev.png’, not ‘pref.png’.

Thanks for the clarification!

The table I’m referring to is the ‘Current Sidebars’ list in the the control panel (a.k.a. the ‘management screen’, as it’s called at the StudioPress site).

When I create a custom sidebar with the plugin, add a Text Widget to it, and then inspect it on a page with Firebug, I see something like this:

div id="text-3" class="widget widget_text"

Each different sidebar has a different id number (“text-7′, ‘text-8’ etc). I’ve used the ID number to target CSS to change things like the background color of the sidebar.

I thought it’d be nice to have those ID#s in the table.

Or are those IDs being assigned to the widgets, not the sidebars?

Hope this is clearer.

Thanks, Ron!

WordPress 3.5.32.
Genesis 2.0.0-RC1
Dynamik Website Builder v1.2.1
Genesis Simple Sidebars 1.0.0

Great! Thanks so much!

Same problem here.

Peter: do you have an ETA for the next version?

Thanks!