Developer forum

Could be one of your groups /special-effects/smoke-haze/stage-fan/ that is not translated to the language you are in.

In settings for customized URLs you have some options related to - show 404 for products not in "Shop", Language and similar. Try to disable them one by one, and see if one of those settings are the reason - then you will also better understand what is wrong.

Also if you look at the respsonse headers of your 404 request in browser dev tools, there can be a header x-dw-404 or something like that - sometimes it will contain a reason.

Hi Nicolai,

- Tried disabling the customized url settings => no effect

- Group is only available in 1 language

- Headers don't give a clue: 

Might it be related with the url provider?

I think we need a URL to see if we can find the cause

Hi Nicolai,

Here you go:  (...)/shop/product-detail-page/special-effects/smoke-haze/stage-fan/mk-ii-remote-control-for-af1-and-af2/a-1

Hi Davy

What a setup! Below is my guess based on what I could find.

You have assortments - specifically a second hand assortment - with 30000 users? (Those users should be in one group and the group should be used for assortment)

Then you have a lot of single products in the assortment - but not the 2 in special-effects/smoke-haze/stage-fan/ group.

Your query does not check for assortments - so the products show up on the list.

When you go to product detail for the product, it will give you a 404 because the product is not in assortment.

Ni Nicolai,

It's a complex setup indeed, we took it recenlty over.

1) When you move the product to another category, there is no issue. So it all points to the group. When looking into the assortments, I can see it's based on products, not on groups. There is no group selection in the assortment used and these products are already selected

2) The query didn't use the assortment context. Adding it to the used query, didn't result in the products without 404. (Also reindexed just to be sure)

Ps:Thanks for the user tip, wasn't aware!

Hi Nicolai,

Any other ideas I might pursuit?

Kr

Hi Nicolai,

Many thanks! I can confirm there's a lot of custom work implemented but there is no overview document. If I find the cause, I'll update this thread!

We talked about this - it can also be that you have 2 routes - that would be group paths - that goes to the same group - it is the group path that is the problem - the last node "Stage fan" - so there might be a ghost record in the database or a product in parent group named "Stage fan". So might not be custom code, but a data issue.