New Library: "Quick new point" created in wrong folder
Solved
In functions panel, I have "quick new point". When tapping one of them, the point is not created in the defined folder since new My Library of 4.28
Was there some migration issue, so I can simply repeat the migration and the correct folder will be used? Or do I really have to manually correct the folder for all "quick new point" types?
The same problem 
Hello Georg,
one year of work and testing, and this was completely missed, sorry for this. I've just fixed this, so in next 4.28.2, migration should preserve defined folders in the "Quick new point". Unfortunately, in your case, information is lost and must be manually redefined. Sorry for the extra work this caused to you!
And do migration once again? If you do not have any new data and you've not yet synchronized to the web, it may be a solution. Is it worth it? How many definitions do you have?
Hello Georg,
one year of work and testing, and this was completely missed, sorry for this. I've just fixed this, so in next 4.28.2, migration should preserve defined folders in the "Quick new point". Unfortunately, in your case, information is lost and must be manually redefined. Sorry for the extra work this caused to you!
And do migration once again? If you do not have any new data and you've not yet synchronized to the web, it may be a solution. Is it worth it? How many definitions do you have?
Hi Menion,
thank you for quick anaysis, fix of migration and reply 🙂
Since the time I have StreetComplete & Vespucci, I've reduced quick new point types to just a dozen, so for me personally, it's no big deal to correct them manually. Still, your fix of migration adds value, as it allows a smoother transition for all users migrating in the future!
Doing migration again is OK for me. I export every changed point / track because I expect I need to do migration again because of https://help.locusmap.eu/topic/36951-how-to-get-pointtrack-visibility-state-from-before-migration-to-new-my-library After re-migration, I plan to re-import the export, so existing points/tracks are updated, new ones added. Even if I would not export them, opnening new My Library, searching for empty search term and sorting by last update would allow an export of changed/new stuff quite easily.
Hi Menion,
thank you for quick anaysis, fix of migration and reply 🙂
Since the time I have StreetComplete & Vespucci, I've reduced quick new point types to just a dozen, so for me personally, it's no big deal to correct them manually. Still, your fix of migration adds value, as it allows a smoother transition for all users migrating in the future!
Doing migration again is OK for me. I export every changed point / track because I expect I need to do migration again because of https://help.locusmap.eu/topic/36951-how-to-get-pointtrack-visibility-state-from-before-migration-to-new-my-library After re-migration, I plan to re-import the export, so existing points/tracks are updated, new ones added. Even if I would not export them, opnening new My Library, searching for empty search term and sorting by last update would allow an export of changed/new stuff quite easily.
Oki, understand. New fixed version 4.28.2 will probably be published till the end of the week.
Oki, understand. New fixed version 4.28.2 will probably be published till the end of the week.
Replies have been locked on this page!