Support » Plugin: Cue by AudioTheme.com » JSON parse issue

  • Resolved thealx

    (@thealx)


    Hello. Client of mine had a problem with your plugin – on some pages JSON parse error appear and player doesn’t work correctly. It happen when another <script> element is near to the .cue-playlist-container, and script trying to use it as playlist.

    Solution:

    in /cue/assets/js/vendor/jquery.cue.min.js file
    ".cue-playlist-data, script"
    should be replaced with
    "script.cue-playlist-data"

    Hope to see this bug fixed in next version. Thank you.

    • This topic was modified 2 years, 2 months ago by thealx.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Brady Vercher

    (@bradyvercher)

    Hi @thealx, there should really only be one script tag within the .cue-playlist-container element, so that selector shouldn’t be grabbing anything outside that container. Do you have a link where we can see what’s going on?

    sure, that’s the page where you can find issue

    http://objectif-russe.fr/accueil-cas-par-cas/accueil-le-declic-russe/specificites-verbes-3/

    Website using Optimize press editor. you can see two players on the page (for testing purposes). First one did work properly, as you can see it doesn’t have any <script> inside rather than .cue-playlist-data

    Next block is the text with <a href="mailto:abc@def.gh">. it shouldn’t affect next player, but it does.

    Next player has another <script> inside of the .cue-playlist-container, it some email links protection.

    Obviously, visual editor causing troubles or some plugin placing code in wrong element. My opinion – code in your plugin can be fixed first, but it’s your decision anyway as I don’t know how it can affect it’s functionality.

    Thank you for your time looking into this problem.

    • This reply was modified 2 years, 2 months ago by thealx.
    • This reply was modified 2 years, 2 months ago by thealx.
    Plugin Author Brady Vercher

    (@bradyvercher)

    Hi @thealx, we had another user report a similar issue and tracked it down to an email protection script being injected by Cloudflare, so we went ahead and updated that selector to prevent further issues. This should be good to go with version 2.3.0.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘JSON parse issue’ is closed to new replies.