Has anyone actually tried this deployment? I am going round and round again with support to get this to work. Second modal back button doesnât show up on first try, then when it does appear after initial try, it closes out all modals.
We are currently checking this Ben. Once the fix is deployed, we will also update here
Thanks for looking into the problem David. But, like I thought, your solution is why I may have seemed reluctant to use chat support:
âNew features are only available on the newer block versions, so opening the page in Studio and refreshing didnât help here - itâs a block-level limitation, not a version issueâŚ,
Unfortunately there isnât a direct like-for-like replacement for the Inbox block right now, so your options are:
1. Rebuild that section using other current blocks (not inbox) that can cover the same use case
2. Use the Vibe Coding block to build a custom version with the behavior you needâ
What youâre telling me is that despite requests over the years to improve inbox blocks (i.e. an original feature) it wonât work. Also, legacy list blocks on all apps will need to be replaced in order for modal back buttons to work as well. Letâs be clear about the context; modal behavior has NEVER been sufficient, and Softr is leveraging me to switch from the inbox block to others that are inappropriate for the scenario, or spend more time with expensive AI credits.
So here is the problem:
- Youâre asking for significant re-configuration on multiple blocks and apps
- Legacy blocks have better style settings anyway
- Softr has neglected the inbox block for years
This is exactly what users were complaining about recently. We can build apps relatively fast, but not business apps that just work. What they were complaining about is true; with all of its pivoting, Softr is deprecating existing features instead of improving them when Softr iterates like this.
How about Softr update the inbox block, like it said it would, instead of essentially deprecating it? More users will adopt it for its inherent usefulness, rather than disregard it for its limitations. This way we can use it with other native features, like modal back buttons, that should just work with it.
Thanks for the detailed feedback Ben, passing this to the product team.