dak's Emu Mob wrote:I got the following error:... Another case of a recalcitrant apostrophe? ... Almost all of my caches are listed twice.
oops sorry, yes we forgot to quote the apostrophe before we fed it into sql. sql uses the apostrophe as a quote character, so any apostrophe in a string has to be preceded (or "quoted") with a backslash "". ugh
unfortunately the query that we forgot to quote the apostrophe was the one that searched for pre-existing logs. this mean that it found no pre-existing logs and happily added the new ones! given the number of duplicate logs, we've reversed the import so your logs are back to where they were before the import.
dak's Emu Mob wrote:Also, the "Importing logs for dak's Emu Mob" page says that it only imported my finds from 10 Dec 2003 instead of 21 Sep 2003.
All caches were listed on the GC.com site when I did the Ctrl-A/Ctrl-C.[/quote]your list could be referring to caches not on the system. unfortunately this import is not written to create caches based on the copy and pasted text. it can only put a log against a cache that is already in this sytem. we thought that it would create too many problems. on reflection, though, we feel a little more comfortable that the code is solid (other than creating all your duplicates!) so we might put in the code to set up a new cache (owner="Unknown", etc) of course, we could be wrong - can you have a look to see if the caches in that time period are on this system?
dak's Emu Mob wrote:I've been credited with a find on an archived Adelaide cache (Heavy Metal)--I haven't cached in South Australia yet. I've just worked out why this has happened. I logged a locationless cache called "Heavy Metal" recently.
ha! who would have thought that that could occur! this will happen when you try to import again. you can either let us know and we'll delete it, or when the copy and pasted text is in the input box, just change the cache name to "Geocache" which will be ambiguous and then leave the ambiguity radio button at "None of the above" and it won't be imported. (it really is quite funny though...)
dak's Emu Mob wrote:The following cache is archived, but is shown in blue instead of red: The froggiest frog cache. On the other hand, "Scullin Cross Bones" has been archived, but is shown as active.
it could be a timing issue. sadly, the secondary side doesn't sent out archived caches - it just pretends they don't exist, which causes all sorts of problems for GSAK users. we detect an archived cache when the cache does not appear in any feed for 48 hours. froggiest was archived on 11 sept US time which could be 12 sept our time + 2 days = tonight. fingers crossed, it will be automatically archived tomorrow. if not, we'll investigate why. having said all that, scullin is in a different category! we have no idea why it isn't archived! we'll investigate.
dak's Emu Mob wrote:Is this total only supposed to reflect Australian caches, or does it include OS and locationless caches?
ugh, at the moment: neither. it's a total of whatever caches are in the system, which is most of the australian caches and the occasional os and locationless cache. we know that's not a lot of help. if you want to get your overseas caches in, just send us a GSAK GPX file and we can import the caches. alternatively, wait a bit and we'll modify the import wizard to create new caches if if can't find them. we want to get the totals to line up with the secondary site so everyone can understand them.
in the meantime, there's no harm in re-trying the import. this time it should only import the logs it needs to! when we write the create cache code, you can do the import again and it will only import required caches and logs.
