WAIT: 404 page critical error

Bricks Version: 1.6.1
Browser: Chrome
OS: Windows

I’m working on a website, had some other things to finish last week and came back to it. Updated to 1.6.1.

Now the 404 page *(doesn’t have a template yet) has a boxed look, it loads the default bricks 404 message, and then a message there is a critical error on the site (while the rest of the site seems to work fine).

Sources shows:
Failed to load resource: the server responded with a status of 500 () – While the page is loading.

On issues it states:

  1. Audit usage of navigator.userAgent, navigator.appVersion, and navigator.platform

  2. A page or script is accessing at least one of navigator.userAgent, navigator.appVersion, and navigator.platform. Starting in Chrome 101, the amount of information available in the User Agent string will be reduced.

To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData.

Note that for performance reasons, only the first access to one of the properties is shown.

  1. AFFECTED RESOURCES

  2. 1 source
    PixelParallel.js:1

Link can be send via private message (site is under construction).

Hi Michael,
Thanks so much for your report!

Is the problem still prominent or have you been able to solve it in the meantime?

Best regards,
timmse

Just checked, it’s still there.
It’s a site under dev so haven’t got to setting a template yet.

I’ll pm the link since it’s not in the open yet.

Hey,
For me it looks like this (not boxed and no critical error):

Best regards,
timmse

Hi Timmse,

I updated to 1.6.2 today - it’s gone now indeed.
One thing left is that the alignment on phones is incorrect:

FYI:
I’ll add a template anyway so no rush for me. More so you know.
(And I don’t know who translated this but ‘Hola’ is not a very professional word in Dutch :wink: )