• Resolved jetxpert

    (@jetxpert)


    Your plugin is causing a DevTools 404 Error on every website page that loads a BB Press or blog comments plugin code.

    Specifically, when we inspect affected page(s), we get the following DevTools warning:

    DevTools failed to load SourceMap: Could not load content for https://www.mywebsite.com/wp-content/plugins/wp-mail-smtp/assets/css/admin-bar.min.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

    Click here for details.

    This shouldn’t be happening – and could be slowing down our website.

    Please provide a fix.

    Thank you!

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter jetxpert

    (@jetxpert)

    Update:

    We may have found the root cause of this issue. We believe it is caused by the snippet provided by the developers of WP Mail SMTP to hide the Admin Bar Menu in the back-end.

    The snippet was installed using the plugin, Code Snippets, and activated only for the back-end. When we activate the snippet for the back-end AND front-end, the issue disappears.

    Above is considered a temporary fix. Would still appreciate a permanent fix since the snippet shouldn’t be impacting the front-end in the first place, only the back-end.

    Thank you.

    Plugin Author Gregor Capuder

    (@capuderg)

    Hi everyone,

    thank you for reporting this issue.

    This will be fixed in the next plugin update.

    You should not use the above-referenced code snippet, since this is just a dev tools warning.

    This warning shows up only when you open browser dev tools, so it should not affect your website’s performance.

    Have a nice day!

    Thread Starter jetxpert

    (@jetxpert)

    @capuderg,

    Thank you. Looking forward to the fix.

    Cheers!

    Plugin Author Gregor Capuder

    (@capuderg)

    Hi @marius84,

    in the next plugin update, but we don’t have an exact date of the release yet.

    Have a nice day!

    Plugin Author Gregor Capuder

    (@capuderg)

    Hi @jetxpert,

    you can resolve it by editing all *.min.css files in assets/css/ folder of the plugin and removing the sourceMappingURL comment at the end of the file.

    An example for assets/css/admin-bar.min.css, you would edit the file and remove this line:

    /*# sourceMappingURL=admin-bar.min.css.map */

    Do so for the other min.css files in that folder and this issue should not display anymore. Maybe you’ll have to clear the browser cache in order to load these changed css files.

    @marius84 I’m sorry that we can’t be more specific with the date of the next release. These warnings are not critical. They display only when a user opens the browser’s dev tools and have no impact on your site’s performance.

    Have a nice day!

    Thread Starter jetxpert

    (@jetxpert)

    @capuderg,

    Thank you. That did the trick.

    Looking forward to the permanent fix in your next plugin update.

    Cheers!

    Thread Starter jetxpert

    (@jetxpert)

    @capuderg

    Update:

    We also learned the following file is being loaded by your plugin on all website pages in the front end:

    /wp-content/plugins/wp-mail-smtp/assets/css/admin-bar.min.css

    Click here for details.

    We disabled the file using Perfmatters (any other file/script disabling plugin should do). No issues so far. This is probably a better fix rather than removing a “comment” from the file.

    Perhaps you can address this as well prior to your next plugin update.

    Thank you.

    Plugin Author Gregor Capuder

    (@capuderg)

    Hi @jetxpert,

    the admin.bar.min.css is a small CSS file and it is intended to be loaded on the frontend as well. We are displaying the admin bar menu conditionally, so if you disable the CSS file it will look strange when it is displayed.

    We’ll improve it, to enqueue the CSS file only for when admin bar is visible and not on all frontend pages… Thank you for reporting this!

    Have a nice day!

    Plugin Author Gregor Capuder

    (@capuderg)

    Hi @jetxpert,

    sorry, I replied too soon ??

    We are already loading the CSS file only for logged in users (when admin bar is visible). So this file is not loaded to your site visitors that are not logged in and don’t have the manage_options capabilities (so basically it’s loaded just for admins and network admins).

    Take care!

    Hey @capuderg,

    Thanks for the heads up. I just wanted to share that i still see the error message in dev tools in the front end eventhough i don’t display the admin bar there. Maybe there is a condition missing still?

    Cheers,
    Tilo

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Admin Bar (Could Not Load Content | 404 Error)’ is closed to new replies.