SOLVED: 404 console warnings for source map files in builder

Bugs
1

Bricks Version: 1.6
Browser: Safari 16.2
OS: macOS 13.1

Seeing these errors in the console logs while editing in Bricks Builder (these don’t appear to affect front-end users thankfully):

[Error] Failed to load resource: the server responded with a status of 404 () (frontend.js, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (swiper-bundle.min.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (typed.min.js.map, line 0)

image
image3456×142 47.5 KB

2

Hi Dustin,
Thanks so much for your report!

The .map files are not required for operation and do not affect functionality one bit, but of course, the 404s shouldn’t be there.

Best regards,
timmse

1 Like
3

Hi Dustin,
We’ve fixed this bug in Bricks 1.7 beta, now available as a manual download in your Bricks account: Account – Bricks

Please let us know if you are still experiencing issues.

Best regards,
timmse

4

Hi @timmse ,

I tested this with 1.7 beta and I believe the three 404 errors are gone, however now there’s a new 404 present in their place…

[Error] Failed to load resource: the server responded with a status of 404 () ({{ data.sizes.large.url, line 0)

image
image1546×386 108 KB

5

Hi Dustin,

Could you please let us know these errors occur in which particular page?
In builder? Same in incognito?

Those codes seem like coming from inline scripts to me. :thinking:

6

It’s entirely possible. I have it installed on two staging sites now and only see the issue in the one, so it may be environmental.

From the source code in the browser I see the following references:

<link rel='preload' href='{{ data.sizes.large.url }}' as='image' srcset='' sizes=''/>

<script type="text/html" id="tmpl-attachment-details-two-column">
    		<div class="attachment-media-view {{ data.orientation }}">
    			<h2 class="screen-reader-text">Attachment Preview</h2>
    			<div class="thumbnail thumbnail-{{ data.type }}">
    				<# if ( data.uploading ) { #>
    					<div class="media-progress-bar"><div></div></div>
    				<# } else if ( data.sizes && data.sizes.large ) { #>
    					<img loading="eager" decoding="sync" fetchpriority="high"  class="details-image" src="{{ data.sizes.large.url }}" draggable="false" alt="" />
    				<# } else if ( data.sizes && data.sizes.full ) { #>

I tried disabling other plugins such as SEOPress but didn’t seem to make any difference unfortunately.

As I was writing this, I just realized… in this staging site I have disabled some of the WP image sizes in favour of the Bricks custom image sizes… I wonder if this is causing an issue. Will look into this further. Nevermind, I forgot I rolled back all those changes from a previous backup the other night so the tests I was running with WP image sizes isn’t applicable here. Forget I said it :stuck_out_tongue:

I’m unsure why this is happening.

7

Seems like this is coming from WordPress code directly: WordPress/wp-includes/media-template.php at master · WordPress/WordPress · GitHub

Not sure why this is only a problem in this one site though that I can find. All my WP installs are on the same version (6.1.1).

8

This seems related to certain performance optimization plugins that try to preload some large images.

Try check which plugin generates that tag.

Let’s continue the conversation in your thread Browser Console errors when Editing in Bricks Builder 1.7 beta 1