Not compatible with WP 6.2?

  • Using learndash. Just installed. H5P appears in settings menu but doesn’t appear in the admin menu (so no way to add/interact with content). I am running WP 6.2. I’ve put it into troubleshooting mode (with just H5P plugin activated) and it still doesn’t show up. Just wondering if there is a compatibility issue or how I might resolve this.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author icc0rz

    (@icc0rz)

    There shouldn’t be any changes to how it appears in WP 6.2 or the plugin. I just installed it on vanilla WP 6.2 without any issues. It’s often the case that such issues comes from a third-party plugin or theme.

    We are having the same issue. wp core 6.0 and higher.

    LearnDash LMSDeactivate?|?TranslateLearnDash LMS Plugin – Turn your WordPress site into a learning management system.Version 4.5.3 | By?LearnDash?|?Visit plugin site?|?Changelog


    15 verbose messages

    h5p.js [violation ] avoid using document.write(). <url>

    issue on firefox chrome edge.


    [Violation] Avoid using document.write().
    h5p.js:382 [Violation] Avoid using document.write(). https://developers.google.com/web/updates/2016/08/removing-document-write
    (anonymous) @ h5p.js:382
    each @ jquery.js:2
    each @ jquery.js:2
    H5P.init @ h5p.js:379
    (anonymous) @ h5p.js:2821
    c @ jquery.js:2
    fireWith @ jquery.js:2
    ready @ jquery.js:2
    H @ jquery.js:2
    h5p.js:382 [Violation] Avoid using document.write(). https://developers.google.com/web/updates/2016/08/removing-document-write
    (anonymous) @ h5p.js:382
    each @ jquery.js:2
    each @ jquery.js:2
    H5P.init @ h5p.js:379
    (anonymous) @ h5p.js:2821
    c @ jquery.js:2
    fireWith @ jquery.js:2
    ready @ jquery.js:2
    H @ jquery.js:2
    h5p.js:382 [Violation] Avoid using document.write(). https://developers.google.com/web/updates/2016/08/removing-document-write
    (anonymous) @ h5p.js:382
    each @ jquery.js:2
    each @ jquery.js:2
    H5P.init @ h5p.js:379
    (anonymous) @ h5p.js:2821
    c @ jquery.js:2
    fireWith @ jquery.js:2
    ready @ jquery.js:2
    H @ jquery.js:2
    h5p.js:382 [Violation] Avoid using document.write(). https://developers.google.com/web/updates/2016/08/removing-document-write
    (anonymous) @ h5p.js:382
    each @ jquery.js:2
    each @ jquery.js:2
    H5P.init @ h5p.js:379
    (anonymous) @ h5p.js:2821
    c @ jquery.js:2
    fireWith @ jquery.js:2
    ready @ jquery.js:2
    H @ jquery.js:2
    h5p.js:382 [Violation] Avoid using document.write(). https://developers.google.com/web/updates/2016/08/removing-document-write
    (anonymous) @ h5p.js:382
    each @ jquery.js:2
    each @ jquery.js:2
    H5P.init @ h5p.js:379
    (anonymous) @ h5p.js:2821
    c @ jquery.js:2
    fireWith @ jquery.js:2
    ready @ jquery.js:2
    H @ jquery.js:2
    h5p.js:382 [Violation] Avoid using document.write(). https://developers.google.com/web/updates/2016/08/removing-document-write
    (anonymous) @ h5p.js:382
    each @ jquery.js:2
    each @ jquery.js:2
    H5P.init @ h5p.js:379
    (anonymous) @ h5p.js:2821
    c @ jquery.js:2
    fireWith @ jquery.js:2
    ready @ jquery.js:2
    H @ jquery.js:2
    h5p.js:382 [Violation] Avoid using document.write(). https://developers.google.com/web/updates/2016/08/removing-document-write
    (anonymous) @ h5p.js:382
    each @ jquery.js:2
    each @ jquery.js:2
    H5P.init @ h5p.js:379
    (anonymous) @ h5p.js:2821
    c @ jquery.js:2
    fireWith @ jquery.js:2
    ready @ jquery.js:2
    H @ jquery.js:2
    h5p.js:382 [Violation] Avoid using document.write(). https://developers.google.com/web/updates/2016/08/removing-document-write
    (anonymous) @ h5p.js:382
    each @ jquery.js:2
    each @ jquery.js:2
    H5P.init @ h5p.js:379
    (anonymous) @ h5p.js:2821
    c @ jquery.js:2
    fireWith @ jquery.js:2
    ready @ jquery.js:2
    H @ jquery.js:2
    h5p.js:382 [Violation] Avoid using document.write(). https://developers.google.com/web/updates/2016/08/removing-document-write
    (anonymous) @ h5p.js:382
    each @ jquery.js:2
    each @ jquery.js:2
    H5P.init @ h5p.js:379
    (anonymous) @ h5p.js:2821
    c @ jquery.js:2
    fireWith @ jquery.js:2
    ready @ jquery.js:2
    H @ jquery.js:2
    h5p.js:382 [Violation] Avoid using document.write(). https://developers.google.com/web/updates/2016/08/removing-document-write
    (anonymous) @ h5p.js:382
    each @ jquery.js:2
    each @ jquery.js:2
    H5P.init @ h5p.js:379
    (anonymous) @ h5p.js:2821
    c @ jquery.js:2
    fireWith @ jquery.js:2
    ready @ jquery.js:2
    H @ jquery.js:2
    20[Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as 'passive' to make the page more responsive. See
    jquery.js?ver=1.15.6:2 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
    add @ jquery.js?ver=1.15.6:2
    (anonymous) @ jquery.js?ver=1.15.6:3
    each @ jquery.js?ver=1.15.6:2
    each @ jquery.js?ver=1.15.6:2
    on @ jquery.js?ver=1.15.6:3
    bind @ jquery.js?ver=1.15.6:3
    H5P.CoursePresentation.initTouchEvents @ eee9b04d241aa1bf4c7533e1c8b91633d40f96cd.js:2593
    H5P.CoursePresentation.attach @ eee9b04d241aa1bf4c7533e1c8b91633d40f96cd.js:1768
    H5P.newRunnable @ h5p.js?ver=1.15.6:954
    (anonymous) @ h5p.js?ver=1.15.6:137
    each @ jquery.js?ver=1.15.6:2
    each @ jquery.js?ver=1.15.6:2
    H5P.init @ h5p.js?ver=1.15.6:93
    (anonymous) @ h5p.js?ver=1.15.6:2821
    c @ jquery.js?ver=1.15.6:2
    fireWith @ jquery.js?ver=1.15.6:2
    ready @ jquery.js?ver=1.15.6:2
    H @ jquery.js?ver=1.15.6:2
    jquery.js?ver=1.15.6:2 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
    Plugin Author icc0rz

    (@icc0rz)

    @cwyattjibc The violation warning seems like an unrelated issue. Could you create a new ticket for this and include your browser version + OS. I’m not seeing this on any of my computers.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Not compatible with WP 6.2?’ is closed to new replies.