301 redirect not working - CMS collection

Publishing help Project settings
1

I have set up redirects for a CMS collection. It is not working.

Old collection slug: /refrigerator-repair/[cms page]
New collection slug: /refrigerator-freezer-repair/[cms page]

I set up the redirect as:
Old: /refrigerator-repair/(.*)
Redirect: /refrigerator-freezer-repair/%1

I have read the article from web flow and do not understand what I am doing wrong. Any help appreciated, thank you!

Here is my site Read-Only: LINK
(how to share your site Read-Only link)

2
  1. Make sure you’ve republished.
  2. Your browser caches old redirects. It may be fixed and you wouldn’t know it.

Open chrome dev tools CTRL+SHIFT+I, click the networks tab and then checkmark disable caching.

image

Try accessing your new redirect with dev tools open and see if it works while ignoring the cache.

If that still doesn’t do it, see if you’ve missed some important escape chars. I’m thinking the / just before your wildcard group might need to be escaped.

3

Hi @memetican thanks for the reply.

I was still getting a 404 error even when I disabled the cache.

I added in the escape characters and now I am getting a 500 error, “something unexpected happened”

Any idea? Thank you!

4

Ah, it was an error on my part. I was missing the closing ) in “(.*)”
Thanks for the help @memetican

1 Like
5

Was it just missing in like /refrigerator-repair/(.*
I have the same problem, but I’m sure i’ve tripple checked everything - and i keep getting a 404 error for my perfectly fine 301 redirect.

I tried everything.

All redirects I added yesterday work fine, but today they don’t.
I need to revert to the old/wrong url, because i cannot change this.

Does anybody know more about this?
Does it happen often that redirects take much more time to propagate?
Can there be a bug where it does not work?