Audio files not playing


#1

I have a WP site that was running on an old version of PHP and WP. I updated to PHP 7, so I could upgrade WP. Everything was working prior to that. Now the audio will not play.

The error I get on the play is:
Error loading audio files
Couldn’t load the audio files from the server. Please try again later.

The other thing I see in the error log tells me that there is not table called podlove_modules_contributors_episodecontribution, which is true.

Any ideas of where I can look?

Thanks

Website http://myfeethurtshow.com
PHP Version 7.1.12
WordPress Version 4.9.1
WordPress Theme Oblique v2.0.7
WordPress Database Charset utf8
WordPress Database Collate
Publisher Version 2.6.3
Web Player Version no web player found
Twig Version 1.35.0
open_basedir ok
curl Version 7.57.0
iconv available
simplexml ok
max_execution_time 30
upload_max_filesize 2M
memory_limit 256M
disable_classes
disable_functions
permalinks ok (/%postname%/)
podlove_permalinks ok
podcast_settings ok
web_player ok
podlove_cache on
assets

0 errors
0 notices
Nice, Everything looks fine!


#2

As an addendum, the direct files to the audio works fine. I’ve removed and recreated pages and they still don’t play.


#3

Try saving permalink settings, sometimes they get lost in an update.


#4

Ok, just tried. Same issue. Thanks


#5

Also, saw that there is a cache for the plugin. I cleared that out as well. No change. Any ideas? thanks.


#6

Im getting the same issue. My audio only works when I download and play it; It won’t work if I try to stream it.


#7

I have this error as well.

Error loading audio files
Couldn’t load the audio files from the server. Please try again later.

The player is attempting to use an address that I suppose is for tracking? but It seems to break all functionality of the plugin.

https://www.paulmeier.com/podlove/file/1/s/webplayer/c/episode/In-a-Manner-of-Speaking-episode-1-February-2018.mp3

which, of course, results in nothing because it doesn’t exist.

Whereas the asset is located at

I know that this error has been reported before. Were you ever able to solve it?


#8

Nevermind. Disabled tracking and everything works fine. Thanks!