mikblog

That’s not my plugin ?? I’m merely trying it out before deciding which one to use on some of my sites. WavePlayer

Thanks, I appreciate the advice but, yes, that’s one of those special cases ??

Since, you’re overwriting the original [audio] shortcode it would only make sense to keep all original features (from the user’s perspective anyway). Otherwise, if I have some special rules somewhere with regard to autoplay or say, preloading, all that is lost, as soon as wavesurfer is activated. Just my two cents.

It’s not critical for my project but desirable. The main issue, however, is not being able to cache the waveforms as images. What I like about your plugin is that it has a small footprint but loading the waveforms each time somewhat diminishes that advantage. I’m presently benchmarking a commercial plugin that does waveform caching, autopaly and more but it has a much larger footprint, so I’ll need to do some more tests.

Don’t get me wrong, though. You did a great job with that plugin, just giving you my feedback.

I was able to do what I wanted with CSS, so all good here. Cheers!

Thanks, I see your point. I shouldn’t have called it the fall-back image, rather a placeholder image to display while the actual waveform is loading.

The placeholder image doesn’t have to match the waveform. It can be a generic looking waveform with a “waveform loading” text across it. Something I could (optionally) supply via general settings to appear on all players.

I’ll try adding some background image to the player’s div via styles for now.

Fair enough ??

How about having a fall-back image to display while the waveform is loading?

Or an optional parameter to supply a background image to override the waveform permanently?

Or lazy load for multiple players? Is any of that doable?

Anyone?

The download issue is consistent across several sites I run. Anyone’s got the Woocommerce downloads working with 4.9?

Sure. it’s a regular Woocommerce link for downloadable products. It looks like this:

https://www.SHOPDOMAIN.com/?download_file=2920&order=wc_order_55c410612307c&email=CLIENTEMAIL&key=eac077baffa92c3d90be35df4b15612e

Normally, that should trigger a download of the purchased file. With version above 4.6.13 it simply goes to the directory where the file sits and gets the 403 error, since the directory isn’t accessible directly.

The download method in Woocommerce is X-Accel-Redirect/X-Sendfile

Thank you

Thank you for the suggestion. Unfortunately, it didn’t make any difference.

It only works if I go back to 4.6.13 or disable the plugin. Were there any major changes moving from 4.6.13 to 4.8?