Hi all,
I’ve tested connecting URL redirects to products, producttags and producttaggroups. I’ve created some redirects, products, producttags and taggroups and tried to connect them by using the Path Match as Reference. For Products this goes well, but whenever I try to do it with producttags and groups I get errors.
- With the groups it doesn’t really matter because after clicking the error away I can still save it and it connects. Does anybody know why?
2.With the tags I get an error that looks a little bit the same. I can’t do the same as with the groups. If I try to save after clicking the error away the error pops back up.
@Eddie_Growrs, good morning and sorry for the late response!
The process throws the eror after insert product tag group with id=19: the field CMS website redirect with id=65 couldn’t pass the validation. You can open the integrated model > find the after insert data process for product tag group and check what are requirements for CMS website redirect link are set there.
I’ve been looking into this problem on and off for a few weeks now. If I look within the architect I’m not getting any good information on what is missing. I’ve tried comparing the trace from my application with a similar one and I think I’ve found what maybe is going on.
I think that whenever the proces that should create a cmswebsiteredirect is creating one but has problems connecting it to the website (and with that to the webpage) where all redirects should be. In the tracer the it has created a redirect for the producttag but that’s all it does. As soon as the action ‘commit_record_cms_url’ runs it starts getting errors, not before it.
Hi Eddie, you could check the settings on the translation for the website. There, you should have a webpage for producttag set:
This page is used for creating the url.
For Producttag I’ve found the solution. To create URLs there needs to be a webpage set for the classic CMS in the settings for the translation.
To get this to work I needed the component M9352
I don’t know if this is the best practise or if this is the old way, for now this is the only way I could get this to work.
The only problem I still have is the producttaggroup that still won’t work for the same reason.
So apparently the error about the producttaggroup that won’t create an URL is something that’s also happening in the application of a customer, both in the test, acceptance and production models.
The only thing that has kept the error from being known is because at the customer they haven’t used the producttaggroups as url pages. Up till now the producttaggroups that have URLs have gotten those through an import.
This makes the error a bit more urgent to solve.
