Skip to:
Content
Pages
Categories
Search
Top
Bottom

BuddyPress 2.0 + P2 = broken mentions and notifications

  • @careb

    Participant

    Wordpress 3.8.1 (multisite with subdirectories); buddypress 2.0; P2 1.5.3;

    http://teambox.dongguk.ac.kr/debug/

    When using more than 10 @username in a post, BuddyPress freaks out and repeats one of the mentions and adds incremental numbers after the @username, like:

    @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia
    @steve @jake0 @jake1 @jake2 @jake3 @jake4

    If I try to edit the post, the correct @usernames are there without the numbers. Everything looks normal. When I publish, the numbers reappear. Notification emails do not go out to users after the names begin repeating or the numbers get added.

    How do I know it’s BuddyPress 2.0?

    I’ve been using BuddyPress 1.9.2 for almost a month without this issue. To be sure though I used the filter to disable mentions the problem went away completely.

    How do I know it’s P2?

    When I use another theme, the problem goes away.

    To really see how bad it is, I made a test post with more than 25 @usernames:

    @amber @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber0 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber1 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber2 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber3 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber5 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber6 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber7 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber8 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber9 @barney0 @barney2 @barney3 @barney4 @barney5 @barney6 @barney7 @barney8 @barney9 @beth0 @beth1 @barney0 @beth2 @beth3 @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber3 @amber @beth4 @beth5

    what what typed:
    @amber @barney @beth @catw @david @dermot @kingsley @hahapauli @leeg @matt @mckerron @michael @patty @phymus @qiana @sabs @sherwin @stuart @virginia @timr @jenhowell77 @siegler @jake @groba @buckley @heath @daniel @daryl @stacy @virginia @steve @paige @patty @amber @johnwendel @calebx

Viewing 2 replies - 1 through 2 (of 2 total)
  • @r-a-y

    Keymaster

    I just tried mentioning 11 users on P2 and couldn’t duplicate your issue.

    It appears this issue only occurs when you view the post on the frontend since you state that the correct content shows up when you edit the post.

    Try the recommendation I listed in the ticket you opened:
    https://buddypress.trac.wordpress.org/ticket/5565#comment:1

    If that doesn’t work, what other plugins are you using?

    @careb

    Participant

    Yes, using the filter to disable mentions solves the problem above, but then mentions are disable. It’s not a desirable outcome.

    Other plugins – Network:
    Advanced Access Manager
    Akismet
    BackWPup
    Blue Login Style
    BP Sticky Groups
    BuddyPress
    BuddyPress Docs
    Enable Media Replace
    Enhanced Media Library
    Hashtag
    Multisite Global Search
    Multisite User Management
    Network Shared Media
    TinyMCE Advanced
    User Groups
    User Switching
    WordPress MU Sitewide Tags Pages
    WP-CMS Post Control
    WP-Mail-SMTP
    WP-Memory-Usage
    WP Better Emails

    Other plugins – Local:
    Broken Link Checker
    Disable Sitewide Tags (Single Blog only)
    Eyes Only: User Access Shortcode
    Google Doc Embedder
    HTML Editor Reloaded
    Subscribe2
    Unified Media Folder
    WP-Polls
    WP Native Dashboard

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘BuddyPress 2.0 + P2 = broken mentions and notifications’ is closed to new replies.
Skip to toolbar