Need a working solution to redirect on page-forbidden and page-not-found

[markschmucker (Mark S)]

I’ve read other posts about how to potentially do this but am looking for a working solution. I’m also aware I can customize site texts, but that’s not a solution for this use case.

What would you like done?

A way to redirect to one url on page-forbidden, and another url on page-not-found. It can be a plugin, a theme component, some javascript that I paste into admin > customize > theme > custom css/html, or some other solution. I do not want to set up Apache or Nginx. The urls will not change often and can be hard-coded.

When do you need it done?

In the next two weeks.

What is your budget, in $ USD that you can offer for this task?

Open to suggestions.

*** If interested, please PM me. Do not post here saying “I’ll do it”.

[bloomexperiment (Tracey)]

@markschmucker

*** If interested, please PM me. Do not post here saying “I’ll do it”.

FYI this is discouraged here on Meta.

People are encouraged to first publicly reply to topics in Marketplace if they are interested in taking on the work.

There is historical discussion on this here:

@sam

If everyone is doing all contact in private, how does anyone know that marketplace works? All we have is one post topics, that automatically close after 1 month

I would say, if you are taking on a marketplace topic, it is beneficial if you reply to the public topic

@riking

My takeaway from the replies to this topic is that the fact someone is responding to the posting should be public, so that Marketplace doesn’t look like a ghost town of unfulfilled requests.

@sam

Absolutely.

My ideal chain of events is:

1. You post job on marketplace
2. Bob-the-builder, posts a reply saying Hi, I would love to build this for you!
3. You PM Bob-the-builder with an email address so they can continue discussion at your preferred location
4. You take on the work, you post on the topic, hi this has been filled by Bob-the-builder, thank you!
5. Bob-the-builder, finishes building it
6. Potential follow up on the topic with any public artifacts (if it is prior to 30 days)

[markschmucker (Mark S)]

Apologies, please post here then. I’ve had cases in the past where someone posted publicly “I’ll do it”, but I didn’t want to hire that person. Other (better) candidates then don’t throw their hat in the ring because the job is taken.

[pfaffman (Jay Pfaffman)]

Maybe you just want the detailed 404 site setting?

Provides more details to users about why they can’t access a particular topic. Note: This is less secure because users will know if a URL links to a valid topic.

That does stuff like

• Oops! This topic has been deleted and is no longer available.
• Oops! That page is private.
• Oops! That page doesn’t exist or is private. (that one didn’t exist–I think you might want to change the text to remove the “or is private” part)

[markschmucker (Mark S)]

I’ve tried that, but I don’t see any difference. If I go to /foo with it enabled or disabled, I get the same thing. (I’ve customized the text to try to give them a clue why, but that’s not very satisfactory.)

[pfaffman (Jay Pfaffman)]

But /foo doesn’t exist, so that’s the right message (you can customize it to say just “does not exist” and remove “not found” as I wrote while you were writing your reply)

You want to change the behavior for page-forbidden. That works as you ask

@markschmucker

A way to redirect to one url on page-forbidden, and another url on page-not-found.

I’m pretty sure this feature does what you’re asking for.