Hi Francis, if Ghulam is correct, please let me know and we can address the issue. It is not one I’ve heard of before (and I am running Badges in production), but always happy to look into such things. Thanks, Ross.
It is very odd that I can’t see this issue in production, but in development I can. I’ve just released a patch that fixes this issue for me, and so hopefully this works for you. This has been released in Badges v2.6.01, which can be accessed using the link below:
Turns out it was not the website…it was me! I skipped a step in the release process. The zip link above should now work, except GitHub seem to be offering a cached version of it, still showing 404. Please, in the meantime, can you try the .tar.gz link below: