Buttons approve / deny not working (frontend)

As much as it sucks to have to redo them, to a certain degree, whatever gets them to work, right?

True. Also, it was killing me trying to figure out what it was. Thanks for all your help!

Hello,

Whenever I click on either the “Approve” or “Deny” button, I also get a console error when using the web console in firefox:

ReferenceError: badgeos_feedback is not defined @
…/wp-content/plugins/badgeos/js/badgeos-achievements.js?ver=1.1.0:41

A reported issue bswelleh and I know the plugin developers have been working on things this past week and likely this week as well.

Hi, the deny button does not function properly. I have tested this out at length, both from the dashboard’s submissions queue and from a list of submissions created via shortcode and viewable on the front end of the site.

In the Dashboard, if something is denied, the person trying to earn the denied badge will generate (2) submission boxes at the end of their work, which makes it quite confusing — which one to use.

On the front end, using a list of submissions from shorcode, if a badge is denied and a student resubmits the work, the “approve” and “deny” buttons do not appear again in the submissions queue.

At the moment, the only solution is to not use the deny button at all. Any developments on this one?

Not that I’ve seen lately, but I can check for github issues related to it, and try to elevate if possible.

For those curious:
https://github.com/opencredit/badgeos/issues/226

Basically the ajax content needed for the approve/deny on single badges isn’t present, but you should be fine if you use the shortcode [badgeos_submissions]

Actually, the shortcode is not sufficient. When I use the shortcode to look at submissions for deny/approve, if an achievement is denied, the submission is difficult to find again AND the deny/approve buttons are disappear after an item has been denied. Basically, if the item gets resubmitted, there is no way of approving or denying the work because buttons are not present.

I am using the plugin for some hardcore learning in the K-12 setting for both professional development and with middle school students. I see this as the most pressing “glitch” in the software, quite frankly. It must be user-friendly to folks who are less tech-savvy (like educators who need a nice WYSIWYG interface). They aren’t going to have the skills or the wherewithal to tinker in the way that I am. Ultimately, this will deter folks from wanting to use the interface and the fun game-layer plugins and badge issuing/making tool, leading them to seek out other tools and interfaces available.

Added your reply to internal notes so that we can possibly get some improvements going as early as 1.4.0 We’ll see.

For the record, I can see what you’re getting at regarding management flow.

Thanks, Michael. Glad to be heard. I am working with schools who really appreciate the features of the plugin and want to continue to extend their use of it and enrich learning for their students.

Just got off the HipChat with some people on the team and the behavior of the submission buttons and whatnot are being reworked for the next release of BadgeOS. So here’s to hoping we get a better workflow here and soon!

OMG. This is amazing news! Thank you for letting me know:) And thank you for taking the request so seriously — this is a huge work flow need. You will make some very hard-working educators ecstatic. I am working with some really smart education innovators and they are super excited about badge learning and the BadgeOS tool. They have about 45 6th students learning together, earning badges and growing their digital media literacies. It is quite cool.

Thank you!
Best,
Sarah

Unfortunately, I’m still experiencing the ‘badgeos_feedback’ is not defined error when clicking on the ‘Approve’ or ‘Deny’ buttons.

Checked my version of badgeos_achievements.js file and the code is up-to-date.

Am I perhaps missing something?

This should be getting fixed in the pending 1.4.0 release, and if you want, you can beta test it and help confirm that it’s fixed.

You can acquire the beta2 code at https://github.com/opencredit/badgeos/archive/1.4.0-beta2.zip. If you decide to, please read https://badgeos.org/v1-4-beta-available/ first with more information on how to go about doing that, including tips on backing up your site before installing and activating.