Author: Richard
[Added to the original trac issue at 8.14am, Sunday, 24th May 2009]

This should have been fixed last night in r15192 (now deployed I think). If you can reproduce the problem now please let me know.

But please, be a bit more civil than resorting to insults like "obviously this terrible tool" I am hardly going to be inclined to help you. Come on, we're all volunteers doing the best we can. I am hardly sitting here writing code that intentionally destroys your work, though with language like that I could be tempted to.

Author: Gibuld
[Added to the original trac issue at 9.40am, Wednesday, 27th May 2009]

Replying to [comment:2 Richard]:

This should have been fixed last night in r15192 (now deployed I think). If you can reproduce the problem now please let me know.

But please, be a bit more civil than resorting to insults like "obviously this terrible tool" I am hardly going to be inclined to help you. Come on, we're all volunteers doing the best we can. I am hardly sitting here writing code that intentionally destroys your work, though with language like that I could be tempted to.

Author: Gibuld
[Added to the original trac issue at 9.42am, Wednesday, 27th May 2009]

Richard,
Please be aware that I didnt intend to offend you. I only wanted to describe my feelings when working with Potlatch.
The situation today is as follows:
Working with Potlatch offline is good, as long as it can connect to the server when saving.
When the connection fails, then Potlatch is hanging for ever and the exclamation triangle is blinking. After aborting the pending save, I then can press the triangle with the result connection to server lost or so. Repeating the save then leads to nothing to save.
And this is the point: Connections to the server may fail and can be repeated no problem. But what should not happen is, that Potlatch then forgets what had to be saved. Especially: Potlach still displays my work, but Potlatch is unable to save it again. Isnt this terrible for a user who also works as volunteer ?
Two subsequent saves this morning behaved this way. Logging in again then proved, that nothing at all had been saved.
Best regards,
Gibuld

Author: Richard
[Added to the original trac issue at 10.31am, Wednesday, 27th May 2009]

Ah, ok, if this is a "doesn't save after warning triangle" issue then it's now a duplicate of #1864 (or #1864 is a duplicate of this, or whatever). :)

I'm on deadline in the day job at the moment so haven't got any spare minutes to look at it - hopefully next week.

In the meantime it does say in the help to save often in case of server problems. It really really means it!