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
Check this box only after you have successfully completed both the above tasks
Please provide a brief description of the problem. Please do not forget to attach the relevant screenshots from your side.
The new Obsidian Login Block is not creating a valid ConfirmAccountUrl. The user who needs to confirm their account is sent an invalid URL and therefore, they are unable to confirm their account.
There error is that there is a / missing between the domain and the page route.
In our instance, this is the URL that is created: https://my.bedfordalliance.churchConfirmAccount?cc=....
It should be: https://my.bedfordalliance.church/ConfirmAccount?cc=....
Expected Behavior
There should be a / between the domain and the page route.
Actual Behavior
There is not a / between the domain and the page route.
Steps to Reproduce
See above.
Rock Version
v15.1, v16.0
Client Culture Setting
en-US
The text was updated successfully, but these errors were encountered:
Please go through all the tasks below
Please provide a brief description of the problem. Please do not forget to attach the relevant screenshots from your side.
The new Obsidian Login Block is not creating a valid
ConfirmAccountUrl
. The user who needs to confirm their account is sent an invalid URL and therefore, they are unable to confirm their account.There error is that there is a
/
missing between the domain and the page route.In our instance, this is the URL that is created:
https://my.bedfordalliance.churchConfirmAccount?cc=....
It should be:
https://my.bedfordalliance.church/ConfirmAccount?cc=....
Expected Behavior
There should be a
/
between the domain and the page route.Actual Behavior
There is not a
/
between the domain and the page route.Steps to Reproduce
See above.
Rock Version
v15.1, v16.0
Client Culture Setting
en-US
The text was updated successfully, but these errors were encountered: