bugMapOSMatic - Bugs: bug #31175, Asking to recreate old map directs...

 
 

bug #31175: Asking to recreate old map directs to completely different already rendered map

Submitter:  Maxime Petazzoni <mpetazzoni>
Submitted:  Thu 30 Sep 2010 07:40:49 PM UTC
   
 
Category:  web Severity:  5 - Blocker
Priority:  * 8 Status:  Fixed
Privacy:  Public Assigned to:  mpetazzoni
Open/Closed:  Closed Release:  2010.10
* Mandatory Fields

Add a New Comment Rich Markup
   

Fri 10 Dec 2010 08:36:18 PM UTC, comment #2: 

This is now fixed, but it is now impossible to recreate some of the very old maps (ID < 4500) because some of them (for the ones rendered by administrative boundary) lack the corresponding OSM ID -- we used to not store it every time. In these cases, the "Recreate" button does not appear. For the other, the user is now correctly redirected to a new job, or an existing recent rendering.

Maxime Petazzoni <mpetazzoni>
Group administrator
Fri 29 Oct 2010 09:11:50 PM UTC, comment #1: 

Blocker for next release. This is a regression of an important feature.

This can probably be solved by sanitizing the job database.

Maxime Petazzoni <mpetazzoni>
Group administrator
Thu 30 Sep 2010 07:40:49 PM UTC, original submission:  

Asking to recreate a very old map directs the user to a completely irrelevant map that was rendered recently or is in the queue. It is possible some information checked by rendering_exists() is missing from the old map entries, but the code should understand that and behave properly.

Reported on Aug 5th, 2010 by "Roumano".

Maxime Petazzoni <mpetazzoni>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by daviddecotigny (Updated the item)
  • -email is unavailable- added by mpetazzoni (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2010-12-10 mpetazzoni StatusConfirmed Fixed
        Open/ClosedOpen Closed
    2010-11-02 daviddecotigny ReleaseNone 2010.10
        Planned ReleaseNone 2012.04
    2010-10-30 mpetazzoni Priority5 - Normal 8
    2010-10-29 mpetazzoni Severity4 - Important 5 - Blocker

    Back to the top

    Powered by Savane 3.13-bb6a.
    Corresponding source code