The time has come—migration to the latest navigation, user authentication, and footer blocks is officially rolling out!
Starting tomorrow (4/17) , we’ll begin enabling this for randomly selected groups of users throughout the next week to ensure a smooth experience for everyone.
This thread will serve as the official place to ask any questions you have about the migration process. We’re here to support you every step of the way!
Keep an eye on your Studio—you should see the option to migrate appear soon. We’re excited to bring you these powerful new features and are here if you need anything!
Great news, looking forward to it! I’m still a bit hesitant in migrating, since I don’t want to take a step back on some current functionalities. Reading topics like for example the one below creates my assumption that not everything is a step forward at this moment, hence my question:
Is there an overview of known current limitations when migrating?
At the same time I’d like to migrate in the coming time, because of new (future) features and because migrating later in the future when my app is more developed will probably create more challenges.
Yes, I’m definitely planning to play with a migrated version and explore the options. I think it would help me (and other users) if there was a list of known limitations.
When I will start exploring I’ll try to list and share them, together with following this topic and Meet the new Softr 🚀
But I have some quick questions.
I used the header(top layout) and the clickable link there, I want it to open a block on thesame page but the option is not there, I can only open another page. What’s your recommended solutions to this
Secondly, I need to use blurred gated access effect that when promoting user to fill sign in form, I don’t know if there’s workaround block that can fit in.
For same page actions, we only have the “scroll to” action which will bring you to the block you want to direct users too. If you’re page is really long, maybe consider taking some sections out and putting on another pages that you can direct users too?
For blurred gated access, I don’t really know what you mean. But you can use visibility settings and show one block that has “blurred access” for that user, and then show another block that has full access for another user?
It’s a good question. I do not believe so. You’ll have to migrate, and then refresh them. Or, even better, migrate and then don’t use them and use our sign in with email code instead (more secure). Hope this helps!
I currently co-manage a large app on Softr, and we would love to make use of the new blocks, but we have 2 really big issues…
User Groups:
Because we have distinct user groups that are much simpler to manage with dedicated signup pages, switching to the new builder presents a challenge. It would require a complete rethinking of our workflow and a potential loss of our user group structure. Consequently, we’re carefully evaluating whether to proceed with the switch or wait for a more compatible solution.
The existence of distinct user groups, which we efficiently manage through separate signup pages, complicates a move to the new builder. This transition would necessitate a complete redesign of our workflow and likely the discontinuation of user groups. We’re currently in the process of determining if the benefits of the new builder justify such a significant change, or if waiting is the more prudent approach.
Current user profile block:
A critical component of our current setup is the user profile block, which facilitates smooth modifications to a wide range of profile settings. The discontinuation of this block in favour of a new one that only handles email, name, and password updates presents a significant obstacle for us.
The current user profile block plays a vital role in allowing users to modify more than just basic profile details. The fact that this block has been discontinued, and the new one seems restricted to email, name, and password changes is a major concern for our workflow.
Thanks for your post and welcome to our community.
User groups: we understand your point, and are working to make a dedicated block / experience to better onboard users to your app. It is also plausible for you to hold off on the migration until this new block arrives for onboarding to better handle your use case. With that being said, here are two options for you:
A) duplicate your app, migrate it, and see how it goes. This gives you a free “test run” to see if you like the upgrade or if it does not work for your use case yet.
B) Add a new page with a conditional form on it that acts as your onboarding flow. This way, whenever anyone creates a new account, using page rules, you always route them to the new onboarding page. Once there, they answer the questions you need to map them to the proper user groups, and then can send them to your main app pages to continue the process. In order to make this work, you’d need to create a new table to store this data, and then using automations to transfer the data to the user table once the trigger is initiated" new row created".
User profile block: the block now allows you to add more fields to it to solve for the use case you were describing. So should be all set there!
I see. If my suggested for adding an onboarding page to pull those 4 signup pages together won’t work for you, then I’m afraid you should wait for these new blocks to mature a bit more (and our new onboarding blocks to be added).
You can also watch our quick migration video, which covers what to expect and answers some common questions.