I’m hating that the builder saves automatically anything you do.
So if it bugs out and stops responding and you reload the changes will be saved… it’s ok that the changes are saved but not that the previous version is deleted.
Undo will not work anymore after an auto save.
I would like to have the option to save manually.
Hey @David, the auto-save feature is crucial since we are a cloud-based tool. If we disable this, users could lose their whole progress.
But I can understand that it causes some problems in certain cases. We are already aware of that and we are working on the backup feature where you’ll be able to restore previous versions of your website.
There will be two ways to do so:
Copy of the website will be automatically saved every XX minutes / every XX elements changed or added.
You’ll be able to manually create a specific version point, let’s say you created everything and now you want to start experimenting with some scripts that might break your build. In that case, you would create a custom saving point so you can always revert changes to that version.
This will solve both problems: auto-save will remain active to ensure progress is saved all the time and you’ll be able to revert to previous versions of the website if you break anything.
What do you mean lose their whole progress?
Did you even read what I said?
I keep losing my pages because of this forced auto save.
Your auto save is deleting my previous progress, it’s not just saving, it’s OVERWRITING.
So it’s not an auto save feature at all. It’s an OVERWRITE FEATURE FROM HELL.
Or maybe even AUTO DELETE. Or even Automatic Destroyer of pages.
I just read the first half of what you wrote and above are my thoughts.
I won’t change them and will leave them here for future reference, as the points still stand.
Also the undo feature is super bugged, I’m sure you also know about this, so many times I have tried to undo 1 thing it didn’t at all and undid something else, and then it auto saves and it’s just over. The page is destroyed by that point.
Hey David, as I said before, we are fully aware of the issues, and we are working on bringing the backup / restore points feature.
I’m not sure how you use the builder, so you are getting this feature to create such issues for you. All it does is just save your progress and changes while your session is active (before the page refresh). It’s how all the cloud-based tools work.
It doesn’t overwrite or delete anything, it just records the new changes you are making and saves them on the cloud. You can still undo them while your session is active. Yes, certain undo bugs have been reported (undo is not registering certain actions such as loop and class creation), and those will be sorted as soon as possible. Everything else works just fine and we didn’t get any reports around this feature.
Since you stated that you only read the first half of my response, I suggest reading everything and bearing with us since we are still a fresh product, and it’s normal to experience bugs and broken things at this stage.
It would be nice if we could stay positive and calm and give us some time to resolve everything. We are a small team that is trying our best, but it’s impossible to push all the fixes and features at the same time. We have to create a priority list.
Thanks for understanding and I hope you’ll enjoy Divhunt in the future.
Be at least somewhat understanding. We are an open beta, small team, released 3 months ago, it’s huge project, we are also doing development work + helping you guys, and not only answering questions but also helping with website changes.
Things will be sorted out in future, especially bugs, it would be a lot more helpful if you describe and explain bugs, then explain the idea or your vision of a better system, that’s the right way.
Ok my dudes, thanks.
You are right. You said 3 months?
Then great job, seems amazing.
I’m just frustrated that I’ve lost my progress so many times.
Even just now nuked an entire section that I built days ago, now I have to rebuild it and still can’t rebuild it as I’m having other issues.
But yeah, it’s the looped items that give me a lot of headache, especially when it comes to undo.
Your main issues are coming from undo functionality, so you break something, try to revert it, and undo makes it even worse? Or you are experiencing some other bugs that we are not aware that exist?
Yes, it’s basically that but you are already aware of it.
Still I think autosave shouldn’t be an OVERWRITE from hell feature.
There should at least be the ability to disable it, as it’s truly horrendous that it deletes our progress in the past anytime there’s a mistake due to the user or due to bugs.
Too many ways to destroy the page and set it in stone.
Hey David, as mentioned before, it’s not up to auto-save, it’s up to Undo feature problems. Auto-save is working correctly, the Undo is one making issues, and we are working on a fix.
Personally I love the auto save feature. I can make some changes, and immediately see changes.
Yes, Undo is an issue, but I know it will be fixed properly as soon as possible.
There a couple of ways to prevent encountering issues from Auto Save when Undo is not possible.
Duplicate the block and use Settings → Visibility to Hide it. Then make your changes in the copied block. If anything goes wrong, you can restore the hidden block.
Duplicate the block, convert to component, and Lock it, the Hide with Settings → Visibility
This is the same idea, but goes a step further and prevents you from Accidentally changing your copied block. Even though it’s hidden, you can still select the layers in the layers panel and accidentally make changes.
There may be other options as well but that is what I use. For the moment, it works well enough for my needs .