We are seeing this same error <https://netsuitepro...
# suitecommerce
g
We are seeing this same error https://netsuiteprofessionals.slack.com/archives/C29HR0BFG/p1710533167951979 on every SC/A site running on 2024.1 NS account, in addition to that, we noted that running the site with seodebug=T the shopping.js and shopping-templates.js are returning a 500 internal error (see attached screenshot), the result is: source code of the page not generated (div main is empty), so, this is going to cause SEO problems sooner or later. Is someone else aware of this problem? And more important, is someone from NS aware of this problem?
s
The fix for this was pushed live this morning.
g
Oh great, thanks for letting us know @Steve Goldberg, we'll be testing
s
OK, but just be aware that it may not be provisioned to your account yet. You should get an update from your support rep
👍🏽 1
k
will this eventually be rolled out to all accounts?
s
Sure
f
still getting the 200 status for 404 pages for our live site.
s
Do you have a case number?
f
Case#5615559 | Defect 758730
s
OK, we are talking about different errors
f
I don't understand... I see this as a critical bug affecting all 2024.1 SC sites, but the fix you're talking about getting rolled out now is for something else? When can we hope to have this bug fixed?
s
The bug Gustavo is referring was a critical bug and we fixed it. The one you referenced in your case and issue number appears to be only affecting you and taking a quick look at it, it looks like it is difficult to reproduce. The case, for example, references that it is easily reproducable by visiting a non-existent image file and yet when I run a quick check on that I can see that it produces a 404 and not a 200
f
every URL i've tested on the site returns a 200 status code in the network log, I've seen zero exceptions. the page says 404 in the content, but the status code is consistent.
s
1. It redirects to the SCA application 2. It processes the URL 3. It can’t find the URL 4. It returns a 404 page and 404 error code Or am I missing something?
I’m using https://httpstatus.io/ to test
Google says its a valid 404
f
My chrome network log still shows a 200 for any bad URL:
the same URL in httpstatus.io says connection timed out, which doesn't tell me much
s
I get 404s
Same result in a fresh/incognito browser?
f
It's now returning the 404 code on several machines I tested, and getting a 404 in the httpstatus.io site as well. I'm glad I took a screenshot before so I know I'm not crazy. Great to see it working properly, thanks for your help!
s
OK good. It could be related to the other bug (I don’t know) and it could be that the result was cached in your browser