Unexpected identifier ‘https’ with jet-reviews

  • Resolved futureyoon

    (@futureyoon)


    4 months, 1 week ago

    Hi

    I am facing an issue whenever I turn on CDN AWS cloudfront with the plugin called ‘Jet-reviews’

    VM3087:2 Uncaught SyntaxError: Unexpected identifier ‘https’
    at HTMLDivElement. (jet-reviews-frontend.js?x76948&ver=2.3.4:39:27)
    at Function.each (jquery.min.js?x76948&ver=3.7.1:2:3129)
    at e..each (jquery.min.js?x76948&ver=3.7.1:2:1594)
    at Object.initInstances (jet-reviews-frontend.js?x76948&ver=2.3.4:29:18)
    at Object.init (jet-reviews-frontend.js?x76948&ver=2.3.4:15:9)
    at jet-reviews-frontend.js?x76948&ver=2.3.4:1688:13
    at jet-reviews-frontend.js?x76948&ver=2.3.4:1690:2

    the moment I turn off CDN, the issue is gone.

    I tried to exclude the plugin being loaded from the aws cloud front by doing like {plugins_dir}/jet-reviews/*.* and i confirmed it’s loading from the server directly, still the issue persists.

    Any idea how to resolve this?

    Thank you

    • This topic was modified 4 months, 1 week ago by futureyoon.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter futureyoon

    (@futureyoon)

    i am seeing this from dev tool, not sure if that helps you understand bettter

    https://app.screencast.com/zkdpuKFQUskee

    Either I turn on or off this option “Use CDN links for the Media Library on admin pages”, the issue still persists.

    • This reply was modified 4 months, 1 week ago by futureyoon.
    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @futureyoon

    Thank you for reaching out and I am happy to help!
    This seems like the issue with the plugin you are using for this. The screenshot you shared indicates that.
    As the plugin you are mentioning is a paid plugin we are unable to test this.
    The “Uncaught SyntaxError: Unexpected identifier” error is typically thrown as a result of a misspelled keyword, missing operator, or missing comma.

    I would suggest you reach out to the support of the mentioned plugin and check with them about the error.

    Thanks!

    xmf5445

    (@xmf5445)

    Hi @futureyoon

    I’m facing exactly same issue with you, have you find any solution?

    Thanks in advace!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.