-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CreateDate tag format issue in the xml #93
Comments
From [email protected] on June 19, 2014 02:20:32 It'll be good to see progress on this, as it affects every map upload on every deployment, and the manual edit needed to correct the problem is generally missed by SB. Many thanks for work on this. |
From [email protected] on June 19, 2014 02:23:56 Example from XML file: |
From [email protected] on August 12, 2014 03:50:05 Fix as per the instructions from those who logged the issue. Example output from my test run just now 2014-08-12 08:13:59. Needs testing in the MapCatalog now, which should be a priority - as already pointed out, this is a minor issue but a major annoyance to deployed staff. Status: Fixed |
From [email protected] on August 16, 2014 07:37:47 Date format is fixed as requested. |
From [email protected] on August 16, 2014 08:21:16 Testing of upload to MapCatalog done, uploaded to here: http://www.mapaction.org/map-catalogue/mapdetail/3448.html The date definitely passes correctly. |
From [email protected] on August 16, 2014 09:17:44 Status: Started |
Testing version 3,1,5429.42421 and answers some of Claire's points above.
|
From [email protected] on May 29, 2014 22:14:59
For the map catlogue createdate tag to work correct the date needs to be shown as yyyy-mm-dd NOT dd/mm/yyyy as it is currently showing (or at least it has for the Serbia mission). The map catalogue parses the xml date as 0000-00-00 which means the latest maps do not show in the correct location and a manual edit has to be made.
Original issue: http://code.google.com/p/mapaction-toolbox/issues/detail?id=93
The text was updated successfully, but these errors were encountered: