Page rule migration to redirect rule fails

I’ve just noticed a message saying page rules are deprecated.
I’m using a page rule that 301 redirects any requests to:
ntsc-uk.com/
to:
https://bordersdown.net/$2 (which keeps the url intact).

When I try to create a redirect rule instead, it refuses and tells me:
https://bordersdown.net/$2’ is not a valid value for target_url because the expression is invalid: Filter parsing error (1:1): https://bordersdown.net/$2 ^AA^ unknown identifier (Code: 20083)

Any idea what I’m doing wrong?

Sorry, markdown changed what I pasted in there to italics and I can’t edit the post. Imagine there’s an asterisk before and after ntsc-uk.com (so that www works too and all paths are redirected to the correct paths)

The ruleset engine doesn’t support (yet?) wildcards. To redirect from one domain to another, copy this example…

2 Likes

Cheers!
So presumably, I’d need to create two rules. One for the TLD and one for the www?
Trying now.

Ah no, “contains” would do it

1 Like

Ok awesome. That worked.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.