Through some messing around I found that changing the filename and then updating the URL would cause the player to work as intended again but this was a short fix, only lasting an hour or two. I then went to another site that I’m using to create a new version of this one thinking the problem might be with WP being outdated but that had the same issue.
Now it seems the issue isn’t just happening to the podcasts I’m publishing now but it’s started crawling back and effecting older posts too – going back six weeks so far.
I’m completely out of ideas at this point.
]]>The customer support is amazing as well, even for the free version.
Support good plugins or they go away, people!
]]>Not sure why libsyn hasn’t kept this going, but I’m about to dump them and switch to a podcast host that takes “full” support seriously. libsyn spent so much time on the new version of their website yet let this important piece just languish until it died.
]]>Still having issues with the Libsyn plugin and it’s blocks.
It’s causing an error that breaks beaver builder and other editors.
error: https://s.mikezielonka.com/p9ur7WvW
]]>Is it possible to replace the WordPress default player with something nicer?
Thank you!
]]>However, if you’ve got non-Administrators who contribute to your site that need to upload an MP3 then you’ll quickly see massive errors in this plugin’s coding.
First: Each user must input the Client ID and Client Secret in the WordPress back-end. Every other plugin I’ve used that uses Key/Secret settings has the Administrator set these up for everyone, then they set who has access. What Libsyn has done here is incredibly insecure.
But wait, there’s another problem: The permissions checks in LPH for showing the Admin Menu so you can get at the LPH settings and put those in check for ‘administrator’ status, so a non-administrator simply cannot enter this REQUIRED information.
So what does a clever webmaster do? They edit the plugin and change the permissions check from ‘administrator’ to ‘upload_files’ (as it should be) and then hand over the ID/Secret to the contributor.
BUT WAIT THERE’S MORE
So the Contributor enters in the ID/Secret and then LPH redirects them to log into Libsyn for no reason whatsoever.
What’s the point of these API keys if you need to log in to Libsyn itself to get this to work?
Do we actually need to give a Contributor full login access to Libsyn to just upload an MP3 via WordPress?
What is going on here? This isn’t just annoying, it’s also incredibly insecure to demand all this broad sharing of credentials.
]]>Recently, I decided to switch back to Libsyn, as I prefer that interface and their statistics.
So, I need help on how to change the following Advanced Options:
1) Import Podcast Box is currently checked – since I moved back to Libsyn, so I don’t know how to uncheck this box
2) Migrate Media Box is currently checked – since I moved back to Libsyn, I don’t know how to get this box to uncheck.
So, I can still use the Powerpress plugin with now being hosted on Libsyn.
Please help.
]]>If I put in a local file it loads the page fine.
It sounds similar to the issue encountered here but the person never gave their resolution. Has anyone heard of issues like this with Libsyn hosted files?
https://www.ads-software.com/support/topic/new-post-timing-out-with-error500-and-breaking-the-page/