Troubleshooting

The plugin deactivated itself after activation

The addon requires both PeepSo and bbPress to be active. If either is inactive it displays “PeepSo bbPress Integration requires PeepSo and bbPress both to be installed and active” and deactivates itself. Activate both plugins, then reactivate the addon. See Requirements.

The Forums tab is not showing on profiles

• Confirm the Forums Tab switch is on in Configuration.
• The tab is hidden for members whose bbPress role is bbp_blocked.
• Confirm the member has forum data to show.

The group forum tab is missing

• Confirm the PeepSo Groups plugin is active and Enable Group Integration is on.
• The group must be linked to a bbPress forum from the forum edit screen metabox.
• As of version 2.3.0 the group forum tab is only shown when the linked forum has at least one topic. Create a topic in that forum, or expect the tab to stay hidden. See Group forums.

Activities are not appearing in the stream

An activity is posted only when the site-wide activity switch for that type is on and the member has that activity type enabled in their PeepSo preferences. Check both. See Member preferences.

Subscribers are not notified

Notifications are created inside the activity handlers, so the matching activity type must be enabled in addition to the notification switch. Confirm the subscriber actually subscribed to the forum (for topics) or topic (for replies).

Known issues to be aware of

These are observed in the current code and are listed here so administrators know what to expect. They are candidates for a future release.

• Duplicate new-forum activity. The duplicate guard used by topic and reply activity is commented out for the new-forum handler, so a forum can post more than one activity if its hook fires repeatedly.
• Paginated favorites and subscriptions. The AJAX “Load More” handlers for favorites and subscriptions filter by a fixed meta value rather than the member id, so pages beyond the first may not be scoped to the member.
• Registration performance on large sites. The routine that enables member activity defaults iterates over every user on the site each time a user registers, which can be slow on large communities.
• Asset caching. Front-end and admin assets are enqueued with a time() version, so browsers re-download them on every load.
• Version shown in the settings header. The settings header may display an older version string than the installed release because of an internal version property that trails the plugin header.

If you hit a problem not covered here, contact the Wbcom Designs support team.