We can only provide support to licensed customers. If you are licensed, please add your forum username to the Forum users page in your Account area and then post in the correct forum.
We can only provide support to licensed customers. If you are licensed, please add your forum username to the Forum users page in your Account area and then post in the correct forum.
We can only provide support to licensed customers. If you are licensed, please add your forum username to the Forum users page in your Account area and then post in the correct forum.
At first I thought this might be an issue with unstable sort order when caching route filters. They are ordered by length of the replacement, but in this case both replacement values are the same, meaning the last one in the set wins. However, when stabilizing the sort order in either direction...
Not in a first class way, but they're ultimately just database entries so you can just insert them using the entity system or directly (just make sure to run any cache rebuild methods if doing the latter).
You should check your server logs to identify what rule is being triggered. It will almost certainly just be a false positive from an overzealous rule that is incompatible with XF.
It's worth having the domain owner check DNS records to ensure any entries for the old record are removed. This can't be checked externally since the records will be obscured by Cloudflare reverse proxying, but you can take a look at the access log for the old server to see if any traffic is...