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
{{ message }}
This repository has been archived by the owner on Nov 6, 2021. It is now read-only.
We have some users thinking that the sandbox site has the same functionality as the production environment especially as it has the same look and feel. So they periodically attempt to reset their passwords from the demo site (https://partnerbase.org/users/password/new) We need to put in a friendly notification on the password reset page like on the login page warning users that they are on the sandbox site and if they want to reset their password they need to go to the live site.
Here is an example of the login warning message:
We should use a similar message for the request demo page except use the language "Please be aware that partnerbase.org is a demo/test server for partner.diaper.app. If you wish to reset your password please do so at the live site https://partner.diaper.app/users/password/new.
The text was updated successfully, but these errors were encountered:
We have some users thinking that the sandbox site has the same functionality as the production environment especially as it has the same look and feel. So they periodically attempt to reset their passwords from the demo site (https://partnerbase.org/users/password/new) We need to put in a friendly notification on the password reset page like on the login page warning users that they are on the sandbox site and if they want to reset their password they need to go to the live site.
Here is an example of the login warning message:
We should use a similar message for the request demo page except use the language "Please be aware that partnerbase.org is a demo/test server for partner.diaper.app. If you wish to reset your password please do so at the live site https://partner.diaper.app/users/password/new.
The text was updated successfully, but these errors were encountered: