[Michael]

in reply to: Upgrade from single site license to 25 site license #6645

Yes, we should be able to accommodate that. We’d be able to provide a discount code for the original price you paid, that can be applied one time to the 25 license option.

Would you like me to set up that discount coupon for you?

[Michael]

in reply to: Narrow Leaderboard #6644

From the looks of it, you have the following being put out inline with other css:

td {
width:100%
}

It’s around line 1819 of that page, right before some .woocommerce-invalid:after selector.

It’s not clear what is adding it, but some plugin or perhaps your theme is, and if you can deactivate plugins until it goes away, that could help narrow down the offending source.

[Michael]

in reply to: Completed steps show up in reports but do not auto issue the next level badge #6541

I haven’t forgotten, just a heads up.

[Michael]

in reply to: Congratulation Modal Link #6540

Glad to hear it Ryan. 🙂

[Michael]

in reply to: Congratulation Modal Link #6538

The snippet I pasted above should be ready and good to go as is, and put in your theme’s functions.php. I wouldn’t edit the plugin files yourself because the changes would be lost next update.

[Michael]

in reply to: Congratulation Modal Link #6536

I forgot to specify that my code above should go in your functions.php file. I would need to see the actual errors encountered when clicking otherwise.

Is the site live somewhere? or is it all on your own computer or private network?

[Michael]

in reply to: Installation #6535

This one is peculiar because you’re technically in the WP Admin at the time of this error, and we have the following added to the callback for that:

if ( !is_admin() ) {
	return;
}

Somehow it’s not being determined to be in the WP Admin.

Not sure what the mtekk_adminkit stuff is but it looks to be using the wp_kses_allowed_html() function and is somehow having our filter applied to it.

[Michael]

in reply to: Installation #6534

Filed an issue for this on our internal reporting.

Out of curiosity, are you trying to use the shortcode before you’ve created any leaderboards? That’s the only way I can think of offhand for why that error would trigger.

[Michael]

in reply to: Updating the Plugin #6531

We missed a version number used to check for updates in the main file. You can find the following at line 79 of badgeos-reports.php

'version' => '1.0.0',

Update it manually to 1.0.1 and the upgrade notice should go away. You’ve got the fixes in the release already.

[Michael]

in reply to: Congratulation Modal Link #6497

Hi Ryan,

How comfortable are you with filters/hooks in WordPress?

The following should work, as that function applies a custom filter at the very end.

function ryan_badgeos_congrats_render_achievement( $output, $achievement_id ) {

	$points = get_post_meta( $achievement_id, '_badgeos_points', true );

	$output = '';
	$output .= '<div class="badgeos-congrats-achievement">';
	$output .= '<p class="title">' . get_the_title( $achievement_id ) . '</p>';
	$output .= '<div class="image">' . badgeos_get_achievement_post_thumbnail( $achievement_id ) . '</div>';
	$output .= '<div class="content">';
	if ( $points ) { $output .= '<strong class="points">' . sprintf( __( '%d Points', 'badgeos-congrats' ), $points ) . '</strong>'; }
	$output .= '<p>' . get_post_meta( $achievement_id, '_badgeos_congratulations_text', true ) . '</p>';
	$output .= '<p><a href="' . bp_core_get_user_domain( bp_loggedin_user_id() ) . '">' . __( 'View Details', 'badgeos-congrats' ) .'</a></p>';
	$output .= badgeos_congrats_render_send_to_credly( $achievement_id );
	$output .= '</div>';
	$output .= '</div>';

	return $output;
}
add_filter( 'badgeos_congrats_render_achievement', 'ryan_badgeos_congrats_render_achievement', 10, 2 );

Essentially we’re adding a filter to the one provided, and outputting the exact same markup EXCEPT the view details href attribute which now gets the user domain of the current logged in user.

Let me know if you encounter any issues with this, or have any other questions related to it.

[Michael]

in reply to: Completed steps show up in reports but do not auto issue the next level badge #6336

Honestly, I’m at the point where I’d need to talk with someone who knows the system more than myself. I’m not the original developer so there’s always areas that I’m not the most familiar with or most knowledgeable about. This is one of those cases.

[Michael]

in reply to: 404 Page Error for Basic Badge Links #6312

Wish I was able to find a solvable solution, but it was quite the odd situation as you recapped above.

Hopefully we’ll see you around in the future.

[Michael]

in reply to: 404 Page Error for Basic Badge Links #6310

I still have no answer, but I haven’t technically given up either.

Any recent changes I should know about?

[Michael]

in reply to: Completed steps show up in reports but do not auto issue the next level badge #6309

From what I recall seeing when I was last in there, there were some steps that were marked as earned earlier than the threshold that it was checking for. Because of that, they were getting taken out of consideration. I don’t know the logic of the design decision for that part, but that’s what I saw at least with the 1 user I was testing things with. I imagine it could also be applying to others as well.

It’s something that isn’t going to be properly solved by a code change, and I don’t have a great answer on how to get around it at this point honestly.

[Michael]

in reply to: Reports Not Working #6267

Thank you for your patience with the holiday yesterday and all.

1. I would need to be able to log in and see what may be going on with this one.

2. I believe this part queries based on the logs, and not the user data stored. You’d need to go through the logs and clean that up as necessary.

3. Looks like we missed a version number bump when we released 1.0.1. If you would like, you can edit the spot yourself. It’s going to be in the badgeos-reports.php around line 79. 'version' => '1.0.0' needs to be changed to 1.0.1 and the update notice should go away shortly afterwards.

[Michael]

in reply to: Changing the variable Points? #6265

As is, the best way would be to add a filter callback to the gettext filter and do some sort of regex that checks for “Points”, “points”, “Point”, “point”, and any other variation you may have.

I did have an enhancement issue for it at one point, but I think it got closed as “wontfix”

[Michael]

in reply to: Completed steps show up in reports but do not auto issue the next level badge #6250

Bit of a longshot question, and using jstrick2 user and the SMB share achievement as examples.

Do you know if some of jstrick2’s SMB steps were earned before the achievement based on them was set up?

Inside one of the functions used is a check between earned times and “last activity”. We check to see if the last activity is greater than the earned time, and if it is, unset the achievement from a returned value. As per our inline documentation: “Drop any achievements earned before our since timestamp”. From the best I can tell with the access I have, some of the steps are being unset because they’re earlier than the checked for “since” value, which is why I’m asking if it’s known if they were already earned.

That’s the best I think I can do at the moment without recreating everything as best I can locally so I could really dig into it, and sadly I don’t have a great answer for some sort of solution.

[Michael]

in reply to: Completed steps show up in reports but do not auto issue the next level badge #6244

No fix for this type of issue was in 1.4.4.

I’m investigating and doing the best I can to not break anything at the same time. Difficult though because I don’t have the same access to tools I usually do. I have a couple hunch leads though.

[Michael]

in reply to: Completed steps show up in reports but do not auto issue the next level badge #6226

Any changes regarding the user level for my account?

[Michael]

in reply to: Completed steps show up in reports but do not auto issue the next level badge #6183

Responded for some more information by email. Majority of debugging discussion will be done here though, and not over email.

[Author]

Posts