I recently handed over a Glide account to a customer.
I suppose he must have opened the app from the builder because when I open it in the builder right now the home screen has been replaced by something else.
Luckily I always set auto-publishing to “off” and these features were not published since the live site is still as I published it 2 months ago.
However when I click “discard changes” in the builder, nothing changes, I also don’t have the option to go back.
My first question is → Did I miss something? Am I the only one with this issue and how should I revert it back to it’s original state? I already restarted the browser, removed my cookies & browsing history, did a hard refresh …
Also this feels quite dangerous to me since we don’t have any version control in Glide or proof of when the last changes were made and by whom …
When auto-publishing is set to off, changes in the builder are not automatically pushed to the app in production, which seems like expected behavior
The auto-publishing feature does not prevent an admin or member of the team to make changes in the builder. Changes would not be pushed to production because auto-publishing is set to off, but the changes in the builder would remain.
Is it possible that you client simply made changes to the app in the builder? Possibly changed the style of a tab and the components got wiped?
That’s precisely what happened.
However if I clicked “Discard Changes” instead of Publishing it, the version of the app in the builder should have gone back to where it was at that moment in Production.
And that didn’t happen. However Glide’s customer support had a back-up and they restored it for me.