Viewing 4 replies - 1 through 4 (of 4 total)
  • Michael Beckwith

    (@tw2113)

    The BenchPresser

    Will check on and file bug if necessary. ??

    Michael Beckwith

    (@tw2113)

    The BenchPresser

    Hi Martin,

    we have a legitimate bug in regars to number 2.

    If you want to fix it yourself for the moment, here’s the steps.

    Open the includes/credly.php file in the plugin, and go to line 272. It’s going to have this code:

    $expires_in        = ( is_numeric( $fields['credly_expiration'] ) ? (int) $fields['credly_expiration'] * 3600 : 0 );

    We need to get the 3600 changed to 86400. One of the devs forgot to account for 24 hours in a day. It will definitely be getting a bug filed against it and fixed in a future release.

    Thread Starter Martin

    (@rastarr)

    Thanks for that Michael. Appreciated.

    Sure doesn’t seem like too much development is going on to actively fix all these outstanding issues though.

    Is this BadgeOS plugin an active and ongoing concern, may I ask since GitHub issues and code activity seems to be most quiet as well. Just looking for some assurances that it’s a short and long term comittment from Credly and their developers – no site wants to be stuck with outdated and unsupported software/plugins, do they?

    Plugin Author BadgeOS

    (@credly)

    Martin,

    It’s a long-term commitment. There’s been a lot of work going into BadgeOS, and we’re gearing up for a v1.1 release in the near future.

    By the way, we are involved building out BadgeOS-based sites for a range of organizations — development efforts which make the product stronger, and contribute exciting innovations back into the BadgeOS project/community. So all of our BadgeOS work feeds back into this project.

    Thanks for your ongoing interest.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Award expiration’ is closed to new replies.