The ‘Open Modal’ action opens further pages in the Modal itself, rather than in the main window. Eg. if I use modal to open the Sign In box/page on my website, the customer portal post-login opens inside the same modal. How I expect it to behave is that, after signing in inside the modal, the modal should go away and redirection to the signed-in customer portal should happen in the main window.
Not sure if this is indeed the intended behaviour, but in its current state, the modal action seems useful only to display popup tooltips etc.
I made the sign-in page & Customer dashboard page in 1 app on Softr. When I open the sign-in page using the new ‘Open Modal’ action and sign in, the dashboard opens within that same modal.
How I expect it to work is exactly how Login on this forum (community.softr.io) works.
It has been a few weeks since I last tried it, but I haven’t seen any updates addressing this, so I believe the behaviour is still the same as described above.
We are having the same error. It’s not a good UX. It sends the user to our homepage in the Modal after they sign in. Worse still, if they close the modal, they’re not logged in.
Our current work around is to have TWO sign-in pages: one that is just for Modals and gives the user the instructions to close the popup and refresh the page they were on…
Here would be the code.
useraccounts1 is the id/name of the signup block. Change it by yours. Also, this code is set to do a history back (1 page back before the signup modal was opened) in the parent page (and as a consequence will close automatically the modal)
<script>
window.addEventListener('submit-form-success-useraccounts1', () => {
const currentPageUrl = window.location.href;
_setCookie('signInUpRedirectionUrl', encodeURIComponent(currentPageUrl), 1);
setTimeout(() => {
window.parent.history.go(-1);
}, 100);
function _setCookie(name, value, days) {
var date = new Date();
date.setTime(date.getTime() + (days * 24 * 60 * 60 * 1000));
var expires = "expires=" + date.toUTCString();
document.cookie = name + "=" + value + ";" + expires + ";path=/;" + 'SameSite=Lax; Secure';
}
});
</script>
Found the same behavior with modals inside container blocks.
I second what others have said in this thread…it’s indeed a bad UX. Especially since the screen becomes un-scrollable when the user keeps the modal open, which is very unintuitive with the current modal behavior inside containers.
@Jjenglert I have the same question as @s.matah.
Is this is intended behavior or something you guys want to adres at some point.
Right. When you search modals here in the community, you find a lot of questions and complaints. It would be a powerful feature if it was integrated better (ex. behavior, back button, …).
This is typical of Softr, unfortunately. Once features are released, Softr moves on to other new features before finishing, improving, or even integrating them with other native features. There’s been so many I’ve configured where I get to a certain point in building and I have to stop, wait, or try to hack together a workaround because they don’t work in a practical, let alone useful way.
In the meantime, would it be possible to at least prevent the full website from becoming unscrollable whenever a modal is opened specifically from inside a container block ( I understand the normal behavior for preventing scrolling but in this case modals actually become unusable).
Hope it will be fixed soon!
