Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter SinOB

    (@sinob)

    Hi slickremix

    Typical, it would work when you try it.

    That system-info-page is an absolutely excellent idea. I’ve never seen one of those in a WordPress plugin before.

    Based on it working on your site but not on mine I realsied it would probably be easier for me to debug than for you. The solution that worked for me was; delete the plugin on my end, do some manual database pruning, do a reinstall, finally regenerate the shortcode again. This appears to have resolved the issue for me. Thank you for taking the time to investigate and feedback.

    Kind regards
    Sinead

    Thread Starter SinOB

    (@sinob)

    Yes it is the case. As mentioned earlier the plugin is working as expected with pinterest when the feed type is changed to individual pins. It is only exhibiting a problem with the boards feed type. It also was not exhibiting this issue prior to my recent update.

    SinOB

    (@sinob)

    The code from Mr3lade is spot on. (Thanks Mr3lade by the way – I hadn’t spotted it was also causing duplicate entried in the activity stream)

    Posted code can get a bit messed up when posting to WordPress support so make sure you haven’t forgotten to comment out that last line. The specific line that causes the duplicate email to be sent is
    wp_new_user_notification( $user_id )

    I am experiencing the same issue
    Wordpress version 4.0
    BP version 2.1.1

    BP Disable Activation Reloaded version 1.2.1

    When a new user registers two ‘New user registration’ emails are sent to my admin email address.

    I suspect this is because in your code you are calling wp_new_user_notification() and
    bp_core_activate_signup() . Since bp_core_activate_signup() is a core bp function that aldeady calls wp_new_user_notification() two emails are sent. Removing wp_new_user_notification() on line 199 of bp-disable-activation-loader.php will probably stop this.

    Thread Starter SinOB

    (@sinob)

    Thanks for looking into this. Also thank you for the link to the correction. Applying your change to my local version appears to resolve the problem.

    I look forward to the release of the update

    Thanks & Regards

Viewing 5 replies - 1 through 5 (of 5 total)