The new website design seems to have broken WCGDAWS. It allows me to log in, but when doing an update, stops and requires me to log in again and then just brings me to the website. WCGDAWS 3.1. Maybe I should upgrade ?
Cheers

I'm parsing the HTML to pull from the "MY CONTRIBUTION", "Global Statistics" and "Results Status" pages. The data I'm pulling from these pages is everything but the headings, graphics and links. I'm also pulling data from the Member and Team Statistics pages using &xml=true.

As asked by jonnieb-uk, are you planning changes to the xml option as well?

Since pirogue has a monitored WCGDAWS thread, a post in there would initiate a mail to him.... just saying.

Myself, don't scrape per se... running, quasi autonomous, a series of 2 part web-queries from the project and global statistics pages, one to fetch a pre-defined set of fields from the front, then a second pass to pull X records and pick a defined set of fields from that. In example, this is the path to pull the last 91 global stats records [note the secure address use]:

https://secure.worldcommunitygrid.org/stat/vi...&numRecordsPerPage=91

And this is the screen where the segments are picked to import, scrape if you will [The green arrow sections is what is pulled], which is repeated for each project in a VBA script, repeating at set hours... if failed, repeat till timestamp changes in page header.



Don't care how the page is framed, long as the key sections don't get altered ... or the Dashboard and the other 40 or so charts will thoroughly break :O

I'm downloading and using a lot of data daily for the signatures. I'm using the xml pages (&xml=true) if available. One notable place where this is not the case is the member rankings per country. If they could be made available in xml it would reduce my scraping by a fair bit.
In my ideal world, a member's ranking per country (runtime, points, results) and a member's ranking per team (runtime, points, results) would be added to the member's individual xml page. But I can understand if this is not possible.
I am ready to adept my code if anything changes, it's not a big deal, so don't worry about me if you feel like changing anything. I'll keep an eye out for any mishaps in the signatures the coming months (and I'm sure others will do so too). So far it's looking healthy.
Keep up the good work!

Fixed the issue with the misspelling of language - thanks for that.

As for fr_CA vs fr_FR in the language drop down, that stems from the fact that we originally targeted the French translation for Canada due to some policy(legal?) requirements for internal deployment/promotion within Canada.

However, if you have fr_fr as your primary language in your browser, then when you arrive on our site, the French formatting rules should be in effect. Let me know if you see otherwise.