Hi all, we just cut a new release that should address this issue. You can find links to the new version on the download page: Download | OpenRefine
Thank you to everyone for your patience, and special thanks to the folks who reported the issue as well as @abbe98 and @tfmorris for their efforts to triage and remediate this issue!
Thanks so much, Rory
Thanks everyone for looking into this issue and solving it so fast.
Big Thanks to @Rory and the others.
Just one question, before I install the new release. Do I lose my project history if I install the new version? I have a couple of unfinished projects that I want to upload. See below the screenshot. Or shall I export backup files with the old version and import them into the new version?
Thx for help.
Best,
Felix
Nevermind, I think I found the respective infos here:
Installing OpenRefine | OpenRefine
I just wanted to pass on my thanks to you and all the others who have worked on solving this issue. Also thanks @abbe98 for keeping the OpenRefine-Wikimedia telegram group updated. I VERY much appreciate how speedily this issue was resolved.
| Rory
September 2 |
- | - |
SaraThomas:
Can I assume that when this issue is resolved for Wikidata that it will also resolve Wikimedia Commons
I think there will be an update required to the CommonsExtension as well, but I haven’t worked on that extension so I’ll let someone more familiar with that code to verify.
I'm not familiar with the CommonsExtension either, but it wouldn't surprise me if it's depending on the default user agent provided by the Wikidata Toolkit.
This would mean that it could be subject to future restrictions by Wikimedia (they discourage library default user strings).
Whoever is currently maintaining this extension should review its usage of WDTK.
Tom
There is a pre-release for the Commons extension fixing its issues here: Release Commons extension 0.1.5 - prerelease · OpenRefine/CommonsExtension · GitHub
I will make a proper release once I get a few more positive reports.
