Closed (fixed)
Project:
Achievements to Mozilla Open Badges Bridge
Version:
7.x-1.1
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
23 May 2012 at 12:02 UTC
Updated:
11 Jun 2012 at 18:52 UTC
Comments
Comment #1
wvd_vegt commentedHi
Found the cause of the missing buttons
I use some of the default images that came with the achievement module (and parts of its api code as a starter) and these images have an extension jpg instead of png. Changing the test in amobb.js to include jpg fixes the missing buttons.
Now all is left i find out where the posting to open badges goes wrong (the assertion seems to fail).
Comment #2
wvd_vegt commentedHi
It seems to be a problem of the achievement module in that it's default images are jpg (which open badges does not support).
So I will post an issue there and close this one.
Comment #3
wvd_vegt commentedHi
Sorry, still run into problems with the images, I converted the default achievement images to png, adjusted the configuration to use them, but still this amobb module does not pick up these default badges (they are not present in the $achievements array).
The actual values are stored in variables 'achievements_image_locked', 'achievements_image_secret' and 'achievements_image_unlocked'.
I changed the code a bit in amobb.module/amobb_assertions() to read:
Comment #4
Royce Kimmons commentedAs you figured out, the Open Badges framework only supports .png, and this is why any unlocked images you're using in an achievement must be .png. If the images aren't .png, then the javascript won't include the "Send to Mozilla..." button (amobb.js line 9).
In the latest version (which I'm releasing right now), I've updated the code to resemble what you suggested with default images except that I have it make sure that the default image is a .png.
And, if I didn't explain this elsewhere, if you're still having issues with Mozilla recognizing the badge, make sure that you're developing on a server that is web accessible (e.g., MAMP and other local development environments won't work to test that functionality).
Hope this helps!
Comment #5
Royce Kimmons commentedComment #6
Royce Kimmons commented