Lack of interest xf_thread_redirect records, hard-coded links

This suggestion has been closed automatically because it did not receive enough votes over an extended period of time. If you wish to see this, please search for an open suggestion and, if you don't find any, post a new one.

Jake Bunce

Well-known member
Screen shot 2012-03-08 at 1.48.33 AM.webp

Redirect locations should be built at run time using the route handlers. Hard-coded links are bad.

This creates a unique problem for my Route Changer addon which needs to change those "threads" links at run time... which it can't do if the handler is not called as is the case here.

I can't imagine any other situation where this is a problem, but hard-coded links are still bad.
 
Upvote 0
This suggestion has been closed. Votes are no longer accepted.
Wont clicking a link just redirect though? As long as there is a 301 is it that bad?

Yes it will 301 redirect with my addon except in the case where you overwrite existing routes, such as with a swap of two existing routes:

Screen shot 2012-03-14 at 4.04.36 AM.webp

The old "threads" route cannot be redirected here because it is being used for something else.

It's a weird case, and one that is not likely to come up. But it's still a problem so I made a post about it.
 
On a side note, i've always thought that links in user generated content could be captured and inspected to see if they link to a node, thread, post, page etc and then they be substituted for something that is generated at run time. That way whenever the url schema changes the links in posts change too. Ok, maybe thats pie in the sky.
 
Top Bottom