Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    Could you let me know on which pages you see those errors?

    If they seem to appear on all pages of your dashboard, could you try to deactivate the Notifications module under Jetpack > Settings, and let me know if the errors disappear?

    Thanks!

    Thread Starter pingram

    (@pingram3541)

    Sure thing. It was on the front end. Here’s a url – http://www.commercialcooling.com/contact-us/

    I just checked another site running JP w/ same theme and I don’t see these errors so it must be another plugin conflicting. Ungh, plugins…wish there was a way to test without messing with the front end. I’ll try to debug once I have time and report back. Thx

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    Is this still happening for you? I don’t see the errors when accessing your site from my end, in IE11 (I don’t have Edge yet unfortunately).

    Do the errors remain when you log out of your account on that site?

    Thread Starter pingram

    (@pingram3541)

    Interesting, I no longer see the 404s on those files when logged out.

    I do however see 404s on:
    /wp-content/bower_components/neat/app/assets/stylesheets/grid/_box-sizing.scss
    /wp-content/bower_components/neat/app/assets/stylesheets/grid/_omega.scss
    /wp-content/bower_components/neat/app/assets/stylesheets/grid/_span-columns.scss

    Haven’t investigated these yet but it appears to be a sass compiler issue w/ ms edge.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    Interesting, I no longer see the 404s on those files when logged out.

    That’s most likely because the files are called inside the Notifications panel, that only appears when you’re logged in.

    Haven’t investigated these yet but it appears to be a sass compiler issue w/ ms edge.

    That does indeed seem to be an Edge feature:

    The source map file will only be downloaded if you have source maps enabled and your dev tools open.

    http://stackoverflow.com/a/35151109/1045686
    https://github.com/MaxCDN/bootstrap-cdn/issues/629

    It seems that removing all references to the map files from the built files fixes the issue.

    I’ve raised the issue with my colleagues in charge of notifications, and we’ll get this fixed. You’ll most likely need to do the same with the files loading those boostrap components.

    I’ll let you know as soon as things are fixed on our end.

    Hi

    I am seeing the exact same issue too on Edge when I try to render my WP 4.6.1 / Genesis Framework 2.3.1 blog. Confused me for a while as I am try resolve why my visual Editor seems to have stopped working and it doesn’t show the usual toolbars.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘widgets.wp.com – error 404’ is closed to new replies.