Closed steve8x8 closed 8 years ago
Since there are side-effects under certain circumstances, it's better not to completely drop the pattern but to restrict overwriting existing wid values. 334-key.diff.txt is the latest approach at this. Feedback welcome!
The ultimate () solution seems to be: if there's a cachepmo.aspx link/form, it's certainly a PMO cache and there are almost no other ways to get hold of the WID. The more generic cache.aspx pattern can only serve as an emergency brake. I'll commit a corresponding change when more tests have succeeded (this might even become a bugfix release, depending on hardware access). (*) There's no ultimate solution as there's no ultimate server-side software release.
This should be merged with Issue #332
In a WID search, to get hold of all Wherigos in the area:
* Error in parseCache():data.split * WID affected: GC67MJV /.../lib/details.rb:359:in
block in parseCache': undefined method
key?' for nil:NilClass (NoMethodError)It turns out that a spurious match in the comment section caused the WID to be overwritten. The patch attached 334-key.diff.txt fixes this; side-effects are to be investigated.