Skip to content
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

FAQ: Describe alternatives for deprecated "Go to" features #334

Open
Lineflyer opened this issue Apr 19, 2024 · 2 comments
Open

FAQ: Describe alternatives for deprecated "Go to" features #334

Lineflyer opened this issue Apr 19, 2024 · 2 comments

Comments

@Lineflyer
Copy link
Member

This question arises on support since we issue a deprecation warning for that feature in c:geo.

Alternatives:

  • Create waypoint on an existing cache
  • Create user defined cache and add waypoints there
@eddiemuc
Copy link
Member

Users also ask what will happen to their existing "go to" waypoints on upgrade and whether this data gets lost. Anyone knows if there's a migration routine?

@moving-bits
Copy link
Member

Anyone knows if there's a migration routine?

Not necessary AFAICS, as the current "go to" solution is simply a user-defined cache with a specific ID ("ZZ0"), which got created automatically by c:geo, either by migration routine back then when we switched the old "go to" solution to using a UDC, or later, when the user started using "go to" for the first time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants