Dave Lester

The text of that page is currently not configurable through the WordPress administrative interface. If you’d like to modify that text, you’ll need to edit the text in include/awards.php

I do not currently have plans to add support for this, but if members of the community wish to add this feature I’m happy to merge it into the codebase. A github issue to track this is here: https://github.com/davelester/WPBadger/issues/62

Yes, expiration date is one of the fields you may specify when awarding a badge.

I’m noticing two problems with your badge description:

1. It exceeds 128 characters, which is the maximum new of characters you can include according to the Open Badges specification.
2. It includes special characters, probably as a result of copy/pasting the description from Microsoft word. Try typing the description normally without those special characters.

The next release of WPBadger (0.7) will hopefully fix this. I will come back and let you know when it’s released, but in the meantime I’m marking this as resolved.

Correct. When you create an award and badge in WPBadger, the pages (and assertion files) are automatically created. I am trying to understand why the assertion looks good (https://www.ooe13.org/awards/569610717240721/json/), but the badge URL isn’t working.

Is it possible that you changed the status of your badge to be unpublished or draft? That’s the only problem that immediately comes to mind.

Looks like the assertion file WPBadger is valid, but I’m not sure why the links are not working — the urls should be correct.

Could you provide some basic information to help me debug, like the version of WordPress that you’re using, and what version of WPBadger you have installed?

Can you please share a link to the award? I’d like to lok at the assertion file WPBadger generates and see if there’s a problem with that. Otherwise, the error you’re receiving from the backpack isn’t one I’ve seen before.

Hi Ben,

Happy to hear that you’ve got the plugin working. In your email client, you may need to whitelist the domain name the notice was sent from — the plugin uses WordPress’ default way of sending emails, so I’m not sure how else to fix this problem. I would assume that if the badge creation email is being caught in your spam folder, then other wordpress emails would also be trapped there.

Dave

Can you let me know what version of WordPress you’re running? 3.4.2 or higher is required

Make sure you add it to the functions.php of the theme you wish to use — this will be in the /wp-content/themes/themename/ folder

You should be able to add the code below the <?php in your file

The url that the plugin is trying to access for a list of your public badge groups is a broken link — “https://beta.openbadges.org/displayer//groups.json&#8221; should have an ID between /displayer/ and /groups.json. This ID is supposed to be automatically retrieved by the plugin, based upon your email address.

Can you double-check that you’re entering the correct email address for your Mozilla backpack account?

Great. For future reference of folks who may stumble upon this thread, the new URL for the badge validator is https://validator.openbadges.org/

It’s correct that badge versions in the current version of the plugin must be x.x or x.x.x.

Hi Ben,

Did you recently change the theme that you’re using on your WordPress site? It’s possible that the theme you switched to doesn’t have post-thumbnails enabled, which adds the ability to set a Featured Image. You should be able to solve this one of two ways:

1. Switching back to the theme you originally had active when you installed the plugin
2. Adding the following code to your theme’s functions.php file:
   

   add_theme_support( ‘post-thumbnails’ );

   , which was similar advice to what I shared in this ticket.

Let me know how it goes!

+1!