Save buttons (page / database) -- confusing situation

[Filip Callewaert]

I quite thoroughly work in databases and bumped into this annoying situation from time to time: 
when I work in a page's edit-mode and also involve the database in my work, numerous times I found myself saving the page, without first saving the database, losing all changes I made in the dbase <frustration>. I did not seem to learn the lesson. Slowing down to better understand why I make this mistake, I made some screenshots, and indeed this is confusing. When you scroll the database down, sometimes and sometimes not, there is a floating database-menu. It is not consistent. When it does not show up: my "bijwerken"-button (save) is the one of the page, not the database. And of course I click that button, but then I lose all changes in the database. Several times. When I scroll up, then I see the two save buttons (but even still then I make mistakes in pushing the page save button instead of the database save button). Grrr. 

Sometimes I ask myself: why asking all these efforts of the user, why not auto-save every input and change in the database?

[Divya Sriram]

Hey @Filip Callewaert - I totally hear you (and have lost a lot of content myself and kicked myself for forgetting to press save). The Beta version will fix this problem and autosave all the changes you make to the database automatically!

[Filip Callewaert]

The autosave is really a must, I think! thx!