powershelldon

Hello, see the screen shot for the error.
https://1drv.ms/u/s!AvgmB3xfwQeWkB2c4RJkDc5P-z0j?e=oFfbMS

No, and it’s the last one that was my initial problem. You can even see the comment posting form, in HTML, with the wrong post ID. And the problem definitely was introduced in 1.4.8.2; my guess is that it’s doing something in interrupt The Loop, and so WordPress’s function to display the comment form no longer has the current post ID.

You’re welcome to email me at DonJ over at PowerShell.org; I can restore the plugin to our site if you’d like to observe the behavior, and probably even set up a “stage” site that you could fuss around with as Admin.

Confirmed. BadgeOS is doing something to The Loop, and the comment form is getting the wrong comment_post_ID field. It always gets the oldest post ID, rather than the one being displayed. Deactivating all BadgeOS plugins is the only solution.

We’re looking at a big retroactive award as well – and it’s not something BadgeOS could do very easily. Currently, BadgeOS is triggered by events (hooks) in WordPress, meaning it’s notified when someone actually does something like post a comment or complete a lesson. It isn’t scanning a log to see what happened in the past – it’s entirely of-the-moment.

For the benefit of others, I was initially confused by this, too. “Submission” does not mean “submitting content to be approved and then displayed on the site,” which in WordPress terms is what ‘submission’ usually means. E.g., BadgeOS isn’t letting someone submit a post for approval and publication.

In BadgeOS terms, it should probably be called “Evidence” or “Application,” as in, you are applying for an achievement and providing whatever evidence the achievement requires. An admin must manually review your application and approve it, which would then award you.