Massive spike in 404s detected after 2.20.0

Viewing 8 replies - 1 through 8 (of 8 total)
  • Sallie Goetsch

    (@wpfangirl)

    2 years, 6 months ago

    I’m getting MIME type errors on that specific file.

    /wp-admin/admin.php?page=sucuriscan:1 Refused to apply style from 'https://domain-redacted.org/wp-content/plugins/coblocks/dist/coblocks-extensions.css?ver=7223b24b7c054f8b2d79a4a30d688f5e' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.

    I’m planning to check my Sucuri settings, but why on earth would a CSS file show ‘text/html` as a MIME type?

    mattschofield

    (@mattschofield)

    2 years, 6 months ago

    @wpfangirl Your browser didn’t receive the stylesheet MIME-type it was expecting from the server. A “text/css” was called from the server, but as it doesn’t exist, the 404 gets delivered to the browser as a “text/html”. With strict MIME checking enabled, the error message you’ve received is the right one.

    Plugin Author Jonathan Bardo

    (@jonathanbardo)

    2 years, 6 months ago

    Hey there, we are real sorry about this. A fix was merge this morning. You can expect a patch release in the next few hours.

    Plugin Author Olivier Lafleur

    (@olivierlafleur)

    2 years, 6 months ago

    A new version of CoBlocks, 2.20.1 was deployed just now, with a fix for this.

    Thanks again for your report and your patience!

    Sallie Goetsch

    (@wpfangirl)

    2 years, 6 months ago

    @mattschofield I never knew a 404 would be reported as text/html, though it does make sense if there’s an actual 404 page.

    @olivierlafleur Thank you for fixing this. I’ll install that update right away.

    ultravariety

    (@ultravariety)

    2 years, 6 months ago

    Running 2.20.1 but getting “Missing Dependencies” reported by Query Manager on every page. It’s looking for:
    wp-content/plugins/coblocks/dist/coblocks-extensions.js
    wp-content/plugins/coblocks/dist/coblocks-1.js
    wp-content/plugins/coblocks/dist/coblocks-10.js
    wp-content/plugins/coblocks/dist/coblocks-11.js
    wp-content/plugins/coblocks/dist/coblocks-12.js
    wp-content/plugins/coblocks/dist/coblocks-2.js
    wp-content/plugins/coblocks/dist/coblocks-3.js
    wp-content/plugins/coblocks/dist/coblocks-4.js
    wp-content/plugins/coblocks/dist/coblocks-5.js
    wp-content/plugins/coblocks/dist/coblocks-6.js
    wp-content/plugins/coblocks/dist/coblocks-7.js
    wp-content/plugins/coblocks/dist/coblocks-8.js
    wp-content/plugins/coblocks/dist/coblocks-9.js
    wp-includes/js/dist/edit-post.min.js

    Thread Starter Joshua Goode

    (@verygoode)

    2 years, 6 months ago

    Running 2.20.1 but getting “Missing Dependencies” reported by Query Manager on every page. It’s looking for:

    I also noticed the Query Monitor missing dependency errors that @ultravariety reports.

    Seems https://github.com/godaddy-wordpress/coblocks/pull/2162 changed how the scripts are enqueued and now there might be attempts to load editor assets in the frontend. This doesn’t occur in 2.19.1.

    The frontend shouldn’t load the editor assets so it’s not being loaded or they’re enqueued after Query Monitor does its Scripts check.

    This doesn’t result in 404s and doesn’t appear to be as problematic as the original issue but still probably shouldn’t happen. @olivierlafleur @jonathanbardo

    • This reply was modified 2 years, 6 months ago by Joshua Goode.
    Plugin Author Jonathan Bardo

    (@jonathanbardo)

    2 years, 6 months ago

    This was next on my list actually. I had to dig into the reason why scripts were set on init hook instead of enqueue_block_editor_assets where they should reside. I’m changing this now and issuing a PR. Also tested the fix in query monitor and it seems to fix it 🙂

    See this PR: https://github.com/godaddy-wordpress/coblocks/pull/2243

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Massive spike in 404s detected after 2.20.0’ is closed to new replies.