Return to Project-GC

Welcome to Project-GC Q&A. Ask questions and get answers from other Project-GC users.

If you get a good answer, click the checkbox on the left to select it as the best answer.

Upvote answers or questions that have helped you.

If you don't get clear answers, edit your question to make it clearer.

The Greasemonkey script stopped working

+1 vote
144 views
Hello,
Sorry I am French, and poorly written English.
The Greasemonkey script (https://greasyfork.org/fr/scripts/9713-geocaching-com-project-gc) stopped working for several days. It is activated, appears well in the header, but all that is in the descriptive part of the cache no longer appears (the last log summary, virtual GPS, etc).
Probably because of the change in the structure of pages GeoCaching.com made a few days ago (and causing a malfunction c: geo well).
Thank you :-)
 
Screenshot ]
[ Mac OS X 10.11 / Chrome 47.0.2526.35 / Tampermonkey 3.11 / Geocaching.com + Project-GC 1.4.5 ]
asked Nov 2, 2015 in Bug reports by Jipem (1,710 points)

1 Answer

0 votes

You are correct, it's because of changes to Geocaching.com.

We have just released a new version (two new versions actually). Using the latest (1.4.7) should make it work.

answered Nov 2, 2015 by magma1447 (Admin) (210,160 points)
I reassure you, me neither I do not understand the cause. Here I try to debug and understand.
If I move the "if (IsSettingEnabled ('collapseDownloads'))" last item of "Page_CachePage function ()" script all other features are displayed correctly. The "collapse download links" function so well is blocked from the rest, but putting that last no more discomfort.
As against the "print and download" does not automatically cache. I must click on it to close.
In short this is not a vital feature. But I like to understand and I will attempt to continue.
This is the line 554 "$('#ctl00_divContentMain div.DownloadLinks, #DownloadLinksToggle .arrow.open').hide();". causing the error "Uncaught TypeError: Illegal invocation". For if I only active 553 and disables it, the error does not appear.
Suddenly I have the same issue myself, which is good. Likely that I will be able to solve it then.

Have also found some other smaller issues which I have already commited changes for. Hoping for a new release later today.
1.4.9 was just released, should work better with that one.
All is ok with 1.4.9. Thanks ganja :-)
...