You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: b.a.price[at]open.ac.uk [Submitted to the original trac issue database at 4.39am, Friday, 24th April 2009]
Since the new version, I am regularly finding that Potlach continuously says "saving data" and often ends up not saving the changes no matter how long I leave it. This happens whether I use my home or work ISP and I never had any problems like this in the previous version.
The text was updated successfully, but these errors were encountered:
Author: b.a.price[at]open.ac.uk [Added to the original trac issue at 12.43pm, Friday, 24th April 2009]
I've only tried to edit relatively short ways usually modifying an existing way as opposed to creating a new one, also editing the outlines of buildings.
Author: Richard [Added to the original trac issue at 12.45pm, Friday, 24th April 2009]
If you can supply a URL of a problem area I can take a closer look.
However it's worth noting that the servers have been very, very busy since the API changeover, with the backlog of mapping from the outage period and also a few teething problems. In such cases it's generally best to come back later, I'm afraid. Certainly when the servers have been running well I haven't noticed any particular problem with Potlatch except in the case of very large relations.
Reporter: b.a.price[at]open.ac.uk
[Submitted to the original trac issue database at 4.39am, Friday, 24th April 2009]
Since the new version, I am regularly finding that Potlach continuously says "saving data" and often ends up not saving the changes no matter how long I leave it. This happens whether I use my home or work ISP and I never had any problems like this in the previous version.
The text was updated successfully, but these errors were encountered: