New cache details page just around the corner, may affect GeoToad "wid" queries!

[Steve8x8]

A while ago, GC started to overhaul the cache_details pages. They are making the look available to randomly chosen members (I suppose, Premium Members will be first), but the ChangeLogs suggest that it will take over sooner or later.
While I do not expect the "printable" pages to change, any modification to the cache_details pages will naturally affect GeoToad when it comes to "wid" queries; also "guid" queries may not work as expected any longer.

As I haven't seen the new design in the wild yet it's hard for me to get GeoToad ready for a transition, but *you* may have (e.g. coming the coord.info/$wid path). If so, I'd appreciate a copy of the HTML code... Warning: the HTML may contain personal information - it's up to you to render it unreadable if you care.

Please do not reply to the forum, send your contribution to my googlemail address instead.

Thanks in advance, S

[Steve8x8]

It's time for a little status report:

On Wednesday, 12 June 2013 09:03:17 UTC+2, Steve8x8 wrote:

A while ago, GC started to overhaul the cache_details pages. [...]

While I do not expect the "printable" pages to change, any modification to the cache_details pages will naturally affect GeoToad when it comes to "wid" queries; also "guid" queries may not work as expected any longer.

I was terribly wrong.

Actually, since they did not only change their cache details pages (to a surprisingly small extent, so parsing still works).
Also, the search result pages no longer contain links with "guids" (their internal database pointers).
This makes direct access to "printable" pages impossible.
(This also makes access to vital PMO cache information almost impossible. Bad luck.)
The result is documented in Issue 277.

The truth: wid (and guid) queries still work, and this also seems to be the only feasible way (now, and based on GeoToad's design) to access cdpf records for all other query types.
There has been a small glitch in "wid" query handling resulting in dropping results. A fix is available.
Although I'm quite busy with my real life (personal, and professional), there's a workaround available in SVN. It will take a while to mature, and I won't be able to release 3.18.0 very soon. Projected release date (even if the debian/changelog says otherwise) is around equinox, in about 4 weeks. You're welcome to test - as the "stable" trunk is converging to the "development" branch (and both will become 3.18.0), you may choose any of both.

I'm quite positive that upcoming "hotfixes" will change the picture again - the current situation is rather inconsistent, and one of the temporary minions will certainly change the code, and the interface, again to break GeoToad in another place.
Infinite jest.

Take care,
 S