Josh Eaton

Hey, Andy. Based on your error, I think you may be looking for the bbp style pack plugin. Let me know if that’s not the case.

@vl4d, CloudFlare is likely the issue. The way the plugin is currently built, it doesn’t work with full page caching. I have planned a 0.2.0 release that will rewrite this plugin completely to support full page caching, but at this time I can’t provide a timeline for its release, as it will be a complete rewrite of the plugin.

Even creating a custom button, it likely won’t work correctly if the rest of the plugin isn’t loading. Sorry for the inconvenience.

Also if you have any page caching plugins clear the cache first as that would prevent it from loading

That’s odd.

Can you switch to the twenty sixteen theme and verify that it still doesn’t work when that is active?

I don’t have your theme to test but it may be something in the theme or in one of the other plugins that is blocking this one from loading.

Snow needs to be enabled, but do you have my plugin installed and active?

@vl4d do you have the plugin active? It does not appear to be loading at all. It wouldn’t load if you disable it, or disable jetpack, or don’t have the snow option enabled on the General Settings page.

Hi @sawatzky,

I’ve just released v0.1.4 which should fix your issue. Please update and let me know whether it’s resolved. Thanks!

Hi vl4d,

I’ve just released v0.1.4 which should fix your issue. Please update and let me know whether it’s resolved. Thanks!

Hi @vl4d, can you give me some more information on what’s not working for you? I’d be happy to re-test it on latest WordPress but knowing your issue will help me track it down. Thanks!

The problem is probably that you need to set a higher priority on your add_filter call so it runs after the plugin’s code.

something like:

add_filter( 'bbp_reply_admin_links', 'shido_custom_reply_admin_link', 20 );

@adam.hurlebaus is correct. If you’re going to support versions prior to 4.3.1, it may need to be different depending on $wp_version

Thanks Jeff, FYI if you’ve fixed it in the beta within the past few hours, then it’s probably good, but I was testing on the beta when I discovered the issue.

I can confirm that this is an issue only if you’re using the Custom Email module and running WordPress 4.3.

I was able to fix it by modifying line 584 of custom-email-admin.php to this:

do_action( 'tml_new_user_registered', $user_id, 'both' );

The issue is that in 4.3 the password isn’t sent to users any more so there’s no email to send as that second parameter, when I replace it with a non-empty string, like ‘both’. It will send the notification.

Another is when Custom Passwords isn’t enabled, the plugin should default (or at least provide the option of) to sending a password reset email instead of emailing the password in plaintext, as WP core has changed this to no longer email passwords.

Nope, I was wrong, sorry for the misinformation (it was late). ??