Background: In the good old days, we used to call anything that didn't work, or "worked" wrong, a bug if we could fix it, and a feature if it was either unfixable or at least not feasible to fix.
Here's what I'm seeing, in V2 pre: when adding a new item, if you pick "Save & New", all well and good, you stay in the edit screen... but when you're done, if you accidentally Save & New, then after getting a new screen, realize you have no more to add, you can't Save because there's no content, and if you Cancel, all of the preceding entries are lost.
Dammit! I went back to verify this, and it turns out that NONE of my Save & New entries are saved, even when the last one is Saved.
Am I doing something wrong?
FOLLOWUP: If you APPLY and THEN do "Save & New", the entry is saved... but I'd have to call this a workaround rather than a fix... seems like it will be easy enough to make the "Save & New" code execute the "Apply" first and then do what it's doing now, eh?
Here's what I'm seeing, in V2 pre: when adding a new item, if you pick "Save & New", all well and good, you stay in the edit screen... but when you're done, if you accidentally Save & New, then after getting a new screen, realize you have no more to add, you can't Save because there's no content, and if you Cancel, all of the preceding entries are lost.
Dammit! I went back to verify this, and it turns out that NONE of my Save & New entries are saved, even when the last one is Saved.
Am I doing something wrong?
FOLLOWUP: If you APPLY and THEN do "Save & New", the entry is saved... but I'd have to call this a workaround rather than a fix... seems like it will be easy enough to make the "Save & New" code execute the "Apply" first and then do what it's doing now, eh?