You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
a user notes that "appointment" being quite a long word to type, [they] will try to use apmt.day to go to appointment.day; but we currentl redirect apmt.day (with or without trailing slash) to appointment.day/user/ which goes to a "Sorry, this page could not be found." instead of the splash page. also applies to the empty/root path, which results in an error page. If it's not too difficult it would be neat to redirect https://apmt.day/ to https://appointment.day/.
Describe the solution you'd like
apmt.day should go to appointment.day. We can look at other routes that we may need to consolidate
The text was updated successfully, but these errors were encountered:
Once we move the frontend routing back to our application it should be easy to conditionally redirect based on no path (to appointment.day) vs path (for /user/)
Is your feature request related to a problem? Please describe.
a user notes that "appointment" being quite a long word to type, [they] will try to use apmt.day to go to appointment.day; but we currentl redirect
apmt.day
(with or without trailing slash) toappointment.day/user/
which goes to a "Sorry, this page could not be found." instead of the splash page. also applies to the empty/root path, which results in an error page. If it's not too difficult it would be neat to redirect https://apmt.day/ to https://appointment.day/.Describe the solution you'd like
apmt.day should go to appointment.day. We can look at other routes that we may need to consolidate
The text was updated successfully, but these errors were encountered: