[Michael]

in reply to: Incompatibility with BadgeOS 1.3.4 & Leaderboard #3384

The 1.0.5 Leaderboard update that should be available, or really soon available, should fix this issue.

[Michael]

in reply to: Display Pic in Auto Message Box #3376

If any of you are comfortable enough with adding a shortcode to your functions.php, I have a quick solution available.

https://gist.github.com/tw2113/9534628

Top part is added to your functions.php file, bottom part is example usage. I’ve tested this and it saves fine without doing the html encoding. It will simply return an tag with the src parameter you provide.

[Michael]

in reply to: Display Pic in Auto Message Box #3350

Ah, yeah, I was trying it out after your initial message, as I had someone else mention vine embeds not working in Chrome recently, so I wanted to see what was up.

In short html entity encoding. It’ll work great, as is, for basic text, but the moment people start adding some media to it, and saving many times, it’s going to get screwy like that. I already filed a bug to find a work around for this, so hopefully we’ll have some sort of update soon.

Best solution I can think of, in the meantime, is to add any images last, after you’ve finished editing/typing all the rest. If you need to save/edit after that, you’ll need to convert the < or > or so back. Not a day-long job, just a momentary pain.

Thank you kindly for the bug report though, it’s appreciated and will help current and future customers with the same add-on 🙂

[Michael]

in reply to: Display Pic in Auto Message Box #3346

So I’m clear, it’s showing the image’s url instead of the image itself?

[Michael]

in reply to: Exclude Site Admin from Leader Board #3317

Best option I can see at the moment is adding a filter to badgeos_leaderboard_update_leaders. That’ll get you the value stored in the _badgeos_leaderboard_leaders meta key, and also provide the leaderboard ID, and original values. You’d have to remove the administrators from the value, and re-update the meta key.

Hopefully that makes sense, but I can do up some quick code if needed.

[Michael]

in reply to: Activity Codes not working #3302

From the looks of the spot for where that message is set, there’s something that is preventing access to the achievement.

From the source code that could include:

-the provided ID isn’t for an achievement
-the user has exceeded max earnings
-if it happens to have a parent achievement and user doesn’t have access to the parent. ( Parents can include having to complete sequential steps )

let me know if that helps at all or if we need to debug further.

[Michael]

in reply to: Message for achievements #3266

Sander, my suggestion for using the widget is not related to the auto-messages premium extension. It’s related to BadgeOS core and would do a job of letting your users know that they earned a new achievement.

Auto-messages is not meant for providing a popup for every single achievement earned, as has been mentioned before. It’s meant for larger milestones like completely long courses or high point accumulation.

I can’t say much yet but we do have something in the works that should address this issue and misconception. Please be patient for a little while longer.

[Michael]

in reply to: Message for achievements #3258

There is the widget available that shows the user’s achievements. Have it in a place that shows on all pages, and they have constant view of their latest. For what it’s worth

[Michael]

in reply to: On recording points… #3197

I know from other peoples questions that our extensions, by design, are never set to delete user meta like point totals. Any time that does happen, it’s done by the user, like with manually resetting a point total.

However, since they are just that, user meta, it could be possible that other extensions and plugins could erase those values from the database. Not something that’s going to be easily trackable, but it’s possible.

With the leaderboard addon, there is one place that does any sort of deleting, and it is within the leaderboard regeneration. However, that’s just deleting one post meta key that stores the cached version of the leaderboard itself. It’s still going to query and regenerate the content used to show, and that’s content that it won’t be deleting.

So the questions at hand are what is triggering issues with user meta, and why is the automated rebuild trigger not firing like it should.

Regarding the automated process, the flow is essentially like this.

The badgeos_award_achievement hook is run, and the user ID is passed into it.
In our callback for the hook, we fetch the leaderboards and loop through them all, and use a “maybe add user” function to see if the user ranks on each board. If the user DOES rank, we add the user to the specific leaderboard. At that point we run through everything to make the leaderboard update itself to include the new user. We then update the post meta that stores that leaderboard’s data, placing the user in the correct ranked location.

The first roadblock I could see is the function attached to the badgeos_award_achievement hook not firing like it should. It’s prioritized pretty low, at 1000. The other is that the user doesn’t actually rank to meet the settings for the leaderboard yet. That returns false and exits out of the process. Lastly, during the update leaders process, if their is no leaderboard ID or an empty array of leaders, it also returns false and bails early.

Hopefully this is easy enough to follow, and I’m getting all of this from the /includes/ranking-engine.php file in the plugin.

[Michael]

in reply to: Incompatibility with BadgeOS 1.3.4 & Leaderboard #3170

Judy, you should be fine to re-install and activate the leaderboard plugin, even before the update mentioned earlier. Just make sure that BadgeOS core is active first.

We’ll be getting this issue fixed really soon regardless. I know our head developer knows the issue and how to fix.

[Michael]

in reply to: Exclude Site Admin from Leader Board #3085

I don’t believe so at the moment, but it may make for a good setting. I’ll suggest it.

[Michael]

in reply to: Incompatibility with BadgeOS 1.3.4 & Leaderboard #3078

It’s something we need to pinpoint and fix, to be honest. It’s a very strange bug from what I remember.

[Michael]

in reply to: Incompatibility with BadgeOS 1.3.4 & Leaderboard #3075

Are you on the latest version of Leaderboard? It’s an error that some were having before today’s 1.3.4 update, so it’s not exclusive.

[Michael]

in reply to: Refresh Report Data? #3040

If you’re familiar and comfortable with custom post types, you’ll be able to make a lot of sense out of this. All of the achievements are post types. We actually use a post type to create post types, which I personally think is genius. The achievement name given ends up being the post type slug during registration. However, once you rename it, it creates and registers an *new* post type and doesn’t actually convert any posts under the previous name. That’s what it sounds like is going on for you.

If I were in your position, I’d check the database for wp_posts rows that have the old post_type name and either convert them to something else or delete them completely. Hope that gives you an idea of what may be going on!

[Michael]

in reply to: On recording points… #3024

Good evening Chris

How are you checking the values of the user points? is it via the frontend or perhaps their user profile through the admin? I’m curious if perhaps some caching plugins are in play and showing cached versions of pages from before the points were awarded.

The leaderboard addon should be self refreshing whenever it detects that a user has new points, but intended design doesn’t always work out in execution. Not sure what could be going on here without more access to possibly debug or check error logs, if any.

Sadly we don’t offer grouping of certain people right now, but it may not be a bad idea to look into as a possible feature or extension. I’ll file an enhancement issue for this one, and we’ll see what may come of it.

[Michael]

in reply to: Auto Message Don't Appear #3002

Is this with the Auto Messages extension? or just with general notification messages when visiting achievement pages?

Yeah, we allow for administrators to revoke individual steps as well as the end result. That’s by design, though not necessarily explained the best.

Is this with the Reports addon? You have 40 difference challenges set up, but in the reports addon, it only shows 6 of them?

[Michael]

in reply to: Generating Activity Code #2996

2. Sounds like a possible bug. Will file a github issue for it.

3. I don’t believe we have time restriction in regards to when the achievement(s) can be earned.

4. As far as I’ve seen, all of our available shortcodes are on the Help/Support page.

[Michael]

in reply to: Generating Activity Code #2994

1. Well, something I’m not sure I clarified enough. My idea involves 2 separate individual achievements. Not two separate condition sets within one.

Create one that is earned, say through completely steps. Then create a second achievement that is triggered by the earning of the first one.

As an example. “Frequent visitor” achievement. Triggered once the user has visited and logged in 20 times. Next is “Frequent commentator” achievement. Triggered once the user has commented 30 different times. Imagine out a few other similar ones.

Lastly, is “Active community member”. This one is a steps completed one, and the steps are to earn specific achievements. Earn “Frequent Visitor”, “Frequent commentator” and any others that you imagined.

They’re separated out enough that the last badge doesn’t rely on the dynamic dropdowns all from within one screen. That’s what I meant by chaining. Sorry for the confusion 🙂

[Michael]

in reply to: Generating Activity Code #2986

Could you provide a screenshot for the 2nd part? Not quite following there.

For the first part, for example, you could have them do the complete process to earn a specific achievement, and then create a separate achievement that is only rewarded once the first achievement is awarded. It ends up separating them out a bit more than perhaps desired, but it should work at that level.

[Michael]

in reply to: Update not Updating, or is this a bug? #2961

It looks like we have a small typo in one of the files used to check for updates. The version numbers for plugins, used in different parts of a WP install, strangely are ready from different parts of a plugin. Parts use a readme.txt, parts use a comment block at the top of the primary plugin file.

If you have 1.0.3 listed in the plugin list, you should be fine and updated. To get rid of the update “nag”, you can safely edit the plugin’s readme.txt file and make that say 1.0.3 as well. Right now it likely says 1.0.2. We’ll get that fixed for all future stuff though, so thank you for pointing this issue out. Thankfully it’s not anything that breaks the website.

[Author]

Posts