Update: This is now working for custom domains.

I would also very much like this working with custom domains. It’s expected behaviour on logout; it shouldn’t throw visitors back to the home page (unless you want the log out to do that).

Is there any progress on this feature? It’s not just useful for real life sign-ups – another case is for users who recieve a fwded email when blasts set to automatically add info – if the person who then recieves fwd email clicks on the link they will need to log out first – at the moment this dumps them back at the home page – the path back to the page they are on might not be obvious at all.

Is this seriously still not resolved??? What a pain in the *! I’m trying to set up a quick sign-in page for an event that we’re using for signing in to an event in real-life, and I want to make it easy to hit the sign-up button, which says “thanks for signing up” then redirects to a page which logs them out and then directs back to the signup page.

No idea how to make this work while this URL issue continues, please fix ASAP.

Is this seriously still not resolved??? What a pain in the *! I’m trying to set up a quick sign-in page for an event that we’re using for signing in to an event in real-life, and I want to make it easy to hit the sign-up button, which says “thanks for signing up” then redirects to a page which logs them out and then directs back to the signup page.

No idea how to make this work while this URL issue continues, please fix ASAP.

@luke and @clara, I have updated the response to this question. Unfortunately, Luke, you’re correct that this solution isn’t working with custom domains. I will update this page when the issue is resolved.

The page_id solution doesn’t seem to be working? What is the point of the request.current_signup.logout_url liquid variable – which seems to generate the logout?page_id string? Or am I doing something wrong?

JK! There seems to be a way! Instead of linking to example.com/logout, send them to
example.com/logout?page_id=125
(with the page_id you want the user to land on after signing out). Seems to work so far, and it would be great to see this documented…

Can I bump this? It would be great to be able to control this.

Is this still not possible? Seems so important, especially regarding landing pages for email blasts when emails might get forwarded to others and trigger wrong assumptions of supporter.

+1 for this.

It would be great if this feature or something like it could be added.

A use case:

Person A creates an supporter account using a shared computer. They forget to log off.

Person B then visits the nation on the shared computer. They would like to sign up as a supporter. They go to the Sign Up page, but cannot sign up because Person A is still logged in. The Sign Up form prompts the visitor to log out if they are not in fact Person A. Person B clicks “log out”.

At this point, a sensible UI flow would log out of Person A’s account and redirect Person B back to the Sign Up page so they can sign up as a supporter. On the other hand, redirecting to the homepage disrupts Person B’s experience — they have to navigate back to the Sign Up page, which some visitors won’t actually do. This loses the opportunity to convert them into a supporter.