Untag geocache from checker

Hi.

I sent in a geocache for approval with a checker regaring belt-colour in BadgeGen. Cloned the checker, and tagged it with the assigned GC-code. But I got a reply from the reeviewer that it was not allowed anymore...

So my problem is that I now have a unpublished cache with a tag to a checker, and I can't use another checker because the GC-code is occupied... Is there a way to uncheck the geocache and reassign a different checker to it, or do I have to delete the cache altogheter? I got a feeling that the reviewer's don't like the last appoach.

Thanks!

We can only disable the tag and make a new checker for you if you give as the link for the tag to disable and the new challenge criteria for the new checker

OK!
Thank you very much!

I find it a bit strange that Project-GC makes it trivial for the average account to clone a checker, but virtually impossible to delete it again. It would be nice if those accounts would also have access to the "Tools / My scripts and tags" menu to be able to delete their cloned checkers. Would be sufficient if just all editing related buttons would be disabled and the Remove button kept enabled instead of hiding their tags completely.

But since you don't have access to that menu, here is what you can do:
Open your cloned checker that you want to delete. The address bar of your browser should show something like this:

Quote
https://project-gc.com/Challenges/GC12345/76543

From there you need to copy the number at the very end, "76543" in this example.
Then open this URL:

Quote
https://project-gc.com/Tools/Challenges?edit&tagId=76543

At the very end you need to put in the same number that you copied.
This should bring you to a page of the checker script with all its checker tags listed below.
On this page do a text search (e.g. Ctrl-F) for your GC code to find your cloned tag.
Once you have found it, you should be able to click the "Remove tag" button on the right side to delete your cloned tag.



Edited 1 time(s). Last edit at 10/12/2024 07:37AM by KaiserVonChina. (view changes)

I think the bug actually is that it can be removed. When the web UI showing the delete button was create there was no reason to not show the button when one owns the tag. Since cloning didn't exist back then. Also the API backend only checks that one owns it.

Users regularly have the problem that they cloned a checker and then need to get rid of it again, i.e. because the reviewer didn't approve their challenge and they now want to use the same GC code for a different challenge.

The simplest solution from the user's perspective would of course be that the Clone-dialog would not always reject cloning a new checker when the user already has cloned one for that GC code. It could check that the existing tag was cloned by the same user that wants to clone a new tag and then offer to replace the old tag with the new one.
But if there already is a tag from somebody else, it should not be possible to replace that one with the "clone" button.
If you want to be more restrictive, you could allow this only while the cache is not yet published.