Closed iminic closed 11 years ago
The message pops up very often atm because we lost some bugfixes in a big merge, will look into it.
It needs to look 'threatening' because if the user won't reload he will most likely loose the data he's entering into the database. Since we don't know exactly what went wrong at that very point when an editor edits something we can't provide a detailed error message but, as I said before, it's important to reload so that no data gets lost while editing.
@iminic @transparencyint I could not reproduce this problem and I don't have time right now to work on this, can someone else look into this?
The fixes are not lost btw. the debounce is still in the details-views which should prevent problems when editing.
It's fine, I am happy with the explanation, and there's no need to do anything about this at the moment. i will emphasize the need to reload in the manual, and hopefully it will be enough. On Feb 26, 2013 5:19 PM, "Jan Monschke" notifications@github.com wrote:
@iminic https://github.com/iminic @transparencyinthttps://github.com/transparencyintI could not reproduce this problem and I don't have time right now to work on this, can someone else look into this?
— Reply to this email directly or view it on GitHubhttps://github.com/transparencyint/CGIP/issues/257#issuecomment-14123458 .
This message often appears even if I just started editing. It might be a bit confusing for editors. Is it possible perhaps to add an explanation about why it happens, or something like that, so that it looks less "threatening"?