I’m not certain if this is a bug for v1.5 beta or something else going on.
I can’t roll back the the version to 1.4.0.2 to test without php errors around the new section/container in the browser.
So maybe this needs clarified.
In Safari v15.5 only (Chrome/Firefox don’t show this error), when I run the developer console I see these 404 error (and the browser says it has trouble).
[Error] Failed to load resource: the server responded with a status of 404 () (fa-brands-400.woff2, line 0)
[Error] Failed to load resource: the server responded with a status of 404 () (fa-brands-400.ttf, line 0)
The screenshot shows it better:
I can see those folders and files on my server.
I’m beginning to think that this is some sort of Safari setting/block.
On iPhone (Safari) I get an error and no site load at all unless I continue to reload the site (eventually it loads).
Can someone check this and confirm it’s not just me?
The path is missing the /assets/ in Safari. In Chrome, however, it is correct. I can’t reproduce the problem, though, so I’m guessing a plugin or caching conflict.
Can you deactivate all plugins one by one and check if the problem persists?
Thanks for the response. It IS a mystery. I have other 1.5b sites on test and none are showing this error on Safari.
I have tried deactivating all plugins, flushing server cache and even resetting the permalinks, but still this issue appears.
Here’s a video of me running through that:
As you can see at the end, I try another installation (blueprint site build) and the issue doesn’t appear.
A proper head-scratcher this one, but concerned that the client can’t/won’t approve the rebuild since there is risk against visitors using Safari browsers.
FWIW, I’m seeing the same issue in macOS Safari with the console 404 errors and disabling all plugins didn’t do the trick for me either. I don’t have quite the same issue in iOS Safari though - everything loads fine in iOS Safari.
I’m not totally sure it’s a Bricks issue though, as when I look at the HTML source code it’s pointing to the /assets/ despite it missing in the 404 errors it throws. It’s as if Safari is stripping out the /assets/ part somehow or I guess its’ actually trying multiple variations of the URL because there’s no actual display issue because it does eventually load…
At the moment, we think it’s a Safari bug because the icons are displayed anyway.
If they were not displayed, it would be a real problem. Nevertheless, we are trying to find out the problem, and if we can fix it, we will.
I’m pushing that staging site with WooCommerce. I see a lot of people asking about Bricks & Woo and thus far v1.5beta been excellent to work with. Keep up the great work you do here.
I didn’t notice it before as it only occurred in Safari. I’ll provide a fix in 1.5 stable.
!