JS error while saving the page

  • Resolved Nishad

    (@nishadup)


    5 months, 4 weeks ago

    I encountered a JavaScript error during page updates. The error stemmed from accessing the property of an iFrame without first checking if it’s empty. I’ve implemented a temporary fix on the site to address this issue. This fix should be included in the next release.

    • This topic was modified 5 months, 4 weeks ago by Nishad. Reason: screenshot added
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Manjurul Islam

    (@manjurulislam)

    Hi @nishadup,

    Thank you for reaching out to RioVizual.

    We have tested it with iframe and it’s working fine on our end. We are unable to replicate the issue from our end.

    Could you please provide us with more details or a screenshot of the error you have encountered? This will help us identify the issue and provide a fix in the upcoming release.

    Thanks and have a wonderful day!

    Thread Starter Nishad

    (@nishadup)

    Hi @manjurulislam,

    I am sorry, somehow the screenshot is not went trough. Here is the screenshot.

    https://ibb.co/RY4bGrD

    Basically the error coming from riovizual\build\index.js below code

    && document.querySelector("iframe")&&(e=document.querySelector("iframe").contentDocument.body.querySelectorAll(".wp-block-riovizual-tablebuilder, .wp-block-riovizual-prosandcons, .wp-block-riovizual-pricingtable"));

    To fix the issue, i made the code as below

    && document.querySelector("iframe").contentDocument&&(e=document.querySelector("iframe").contentDocument.body.querySelectorAll(".wp-block-riovizual-tablebuilder, .wp-block-riovizual-prosandcons, .wp-block-riovizual-pricingtable"));

    Hope that helped. expecting this fix on next release.

    Thread Starter Nishad

    (@nishadup)

    Hi @manjurulislam,

    Any update on this?

    Plugin Support Manjurul Islam

    (@manjurulislam)

    Hi?@nishadup,

    We have released a new version that includes the fix. Please update to the latest version and check if it resolves the issue on your end. Let us know if the issue persists.

    Thread Starter Nishad

    (@nishadup)

    Hi @manjurulislam,

    Thanks a ton. it worked.

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