Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter emilykellymfr

    (@emilykellymfr)

    Alright, I added that snippet to my functions.php file, yet it doesn’t seem to have changed anything. When I try to play podcasts, I still get the same error.

    For now, I am just working on building a child theme so that I can update the site’s theme. When I updated the theme a few weeks ago, that temporarily fixed the issue, so maybe it will fix the issue again.

    Thanks again for all of your help!

    EDIT: Alright, so I just found the call to wavesurfer.js in Seriously Simple Podcasting’s class-ss-frontend.php. Out of curiosity, I changed the version number in the call to the wavesurfer.js source code to 2.0.5 which is the most current version of wavesurfer.js. Making this change made it so that nothing happened when the play button was pressed. Not exactly what I wanted, but I thought I’d try it since I have seen in other forums that the version number had created problems before.

    Interestingly, if I revert the version number in that particular line back to 1.2.8, the button works. Hmmm… I am not sure what to think of this. What are your thoughts?

    • This reply was modified 6 years, 11 months ago by emilykellymfr.
    Thread Starter emilykellymfr

    (@emilykellymfr)

    Hi,

    I just searched the header and function files and neither seems to reference it. Also, I should have mentioned that I did have that plugin installed, but the problem was present before I installed the plugin. I honestly installed it to see if that would affect the issue at all, which it didn’t. It is back to be deactivated, since it didn’t change the problem either way.

    I am guessing that the issue has something to do with the Seriously Simple Podcasting plugin, but I do not want to deactivate that because it is the heart of our website.

    Currently, I am thinking about updating the theme again because that provided a temporary fix a few weeks ago when this play button issue previously presented. Fixing this issue was the first assignment I received when I started the webmaster position I am in now, so I do not know when this issue originally presented or what may have caused it.

    I do not know if you know anything about the podcasting plugin, but any other ideas you have on this topic would be much appreciated!

    Thank you!

    Thread Starter emilykellymfr

    (@emilykellymfr)

    Thanks for your reply @helldog2018! However, I actually do not have that particular plugin installed on our site; that is why I am super confused as to why Wavesurfer is being called. I do, however, have the plugin Seriously Simple Podcasting for the site. I have tried contacting the developer about this issue, but have not gotten any helpful responses.
    I have looked through all of the files utilized by the Seriously Simple Podcasting plugin, but none of them call Wavesurfer.js (that I can tell, but I am not super experienced with this matter). Does that plugin use Wavesurfer? If it does, how would I go about fixing this error?

    • This reply was modified 6 years, 11 months ago by emilykellymfr.
Viewing 3 replies - 1 through 3 (of 3 total)