Currently, if we haven’t saved the builder changes and then navigate to another template or page or template, the browser displays a notification. In this situation, we need to close the notification, save the builder, and go back to the page we were trying to navigate to. This process can be much smoother.
It would be great if, when the builder is not saved and we want to go to another page, a native Bricks notification was displayed with two options: “Cancel” and “Save and Continue”. In fact, clicking the Save and Continue button will both save the Builder and navigate to the desired page.
It’s a very interesting idea. While testing the beta version, I realized something was missing. But I didn’t know what. I suspect the Bricks team doesn’t look at feature requests because bugs are a priority for them. I hope it’s okay to tag them.
Hi @Matej, Would you please consider this feature request?
thanks for the request. I see the value in it, but isn’t that the same as we don’t have instant navigation enabled? You still get a popup, and you have a choice to cancel or not.
In fact, it doesn’t matter whether instant navigation is enabled or not. The browser notification is one thing. That is, if I have not saved the changes in the builder and we want to go to another page, this notification will appear and we have two choices. As you know, if we cancel, we will stay on the same page. If we choose leave, we will go to the desired page, but the changes on the previous page will be deleted.
What we are talking about is improving the workflow and, in fact, instead of the leave option, we will have the save and continue option, which, when selected, will both save the settings and move us to another page. Please note that this is not a specific feature. I remember when I used to work with Elementor there was something like this in the editor. If you think you need more details, I will reinstall Elementor and send you a video.
Hey @HOSEIN, I think I understand now. So this feature request would not depend on whether instant navigation is enabled or disabled. If I understand correctly, what we should do is add a custom pop-up when a user tries to leave the builder and there are unsaved changes. That pop-up should offer three options:
The first option would be Cancel, which simply keeps the user in the builder.
The second option would be Save and proceed (or Save and exit), which saves the builder and then exits the website.
The third option would be Exit without saving, which leaves the website without saving any changes.
If you can confirm this, I think I can create a feature request for this internally, as I believe it would be a nice improvement.
Yes, you got it exactly right. Elementor didn’t have the third option you mentioned, but it’s a good idea and overall I think it would be a very useful feature in the builder.
