[@emaralive Moderator 2 weeks ago]

Hi @asmaajaved,

Wonderful news, glad you could resolve the issue. 🙂 🎉

[@emaralive Moderator 3 weeks, 3 days ago]

The answer to your initial post can be found at the following:

BP Template Pack JavaScript and Style assets are now only loaded into the community area of your site

As to your 2nd post, most likely via the following:

wp_localize_script( 'bp-nouveau', 'BP_Nouveau', apply_filters( 'bp_core_get_js_strings', $params ) );

[@emaralive Moderator 3 weeks, 4 days ago]

I see that this is a multisite installation, not that this should matter, it’s just that more information gets revealed over time. I noticed that define(‘WP_ALLOW_MULTISITE’, true); is listed twice; is this verbatim or just something that happened with copy & paste, just curious?

As to base64_decode, this may not apply, this would have been a malicious attempt to obfuscate, I was just trying to rationalize why you aren’t finding where the BP_GROUPS_DEFAULT_EXTENSION constant is being defined.

Perhaps I should ask the question differently; what tool are you using to search for the BP_GROUPS_DEFAULT_EXTENSION constant? Typically constants are defined in wp-config.php, it appears, however, the BP_GROUPS_DEFAULT_EXTENSIONcan be defined in a child theme'sfunctions.php` or a “Must Use” plugin, etc, etc.

[@emaralive Moderator 3 weeks, 4 days ago]

Hiding – not easily seen.

The constants you’ve indicated are for WordPress and are typically defined within wp-config.php, if you search for one of those constant names, does it show up in your search results?

[@emaralive Moderator 3 weeks, 5 days ago]

Hmmm… is this a production or development or staging site? We know the constant is being set. Would someone actually use a base64_decode hack to hide the fact?

[@emaralive Moderator 3 weeks, 5 days ago]

Well that’s odd unless someone has used the const keyword to define it. Search for just BP_GROUPS_DEFAULT_EXTENSION and see what that finds.

The Bottom line is that this constant is being set to the value of “forum”, just need to find how and where.

[@emaralive Moderator 3 weeks, 5 days ago]

Thanks,

BP_GROUPS_SLUG (deprecated), as indicated is deprecated and shouldn’t be defined/used. However, BP_GROUPS_DEFAULT_EXTENSION is defined as “forum” which is what is causing the initial 404 redirect (page not found). Apparently, there was a “forum” nav item for any given group and now there is not therefore, that page can’t be found.

Somewhere, perhaps wp-config.php, there is a line that contains define( 'BP_GROUPS_DEFAULT_EXTENSION', 'forum' );, find it and either remove it or comment it out and then you won’t need the redirect plugin. Perhaps, the bbPress plugin was previously activated and all groups had “Group Forum” enabled and thus the constant being defined as it was.

[@emaralive Moderator 3 weeks, 5 days ago]

@asmaajaved – out of curiosity, I’m interested in knowing the value that is set for the BP_GROUPS_DEFAULT_EXTENSION constant. This information can be found within the Site Health Info tab, e.g., wp-admin/site-health.php?tab=debug, scroll down to the last panel (BuddyPress Constants) then open the panel and find the aforementioned constant.

This might provide an additional clue as to what may be occurring.

[@emaralive Moderator 4 weeks, 1 day ago]

Let’s not do that, I would prefer not to get involved in that way.

It looks like after group creation, there should be a 302 redirect to the newly created group page. Since you are able to delete groups, I assume you are doing so from wp-admin > groups page.

Notwithstanding the 302 redirect after group creation. Since the groups appear to be created, you should be able to access any of the created groups directly, e.g.:

https:example.com/groups/new-group

I’m not sure if this is actually a BuddyPress issue.

I’ll ask around and see if anyone else on the team has heard of this.

[@emaralive Moderator 4 weeks, 1 day ago]

Unfortunately, I’ve not seen this before, so it may take a while to figure what is going on. Until I can duplicate this anomaly, it is hard to say what a fix would be.

[@emaralive Moderator 4 weeks, 1 day ago]

For some reason you are getting a 404 page (Page not found”). Does this happen immediately after you create a group? Meaning, after creating a group you should be taken to the newly created group page but you are redirected to a 404 page, is this correct?

Also, this anomaly happens with all group types (public, private & hidden)?

[@emaralive Moderator 4 weeks, 1 day ago]

Hi @davesumpter,

It would depend on the theme in use on how you would edit the Site Title link, assuming the Site Logo has the same link as the Site Title, you would use a URL similar to:

https://example.com/members/me

The “me” is the default shortlink redirector member slug. IOW, this will redirect to the profile area of the logged in user, typically, their activity stream/feed

[@emaralive Moderator 4 weeks, 1 day ago]

Hi @jrpmedia,

Were you able to resolve this issue?

[@emaralive Moderator 4 weeks, 1 day ago]

Hi @asmaajaved,

I’m not sure if this an edge case, so more information is required, e.g.:

1. WordPress version
2. WordPress permalink setting(plain or pretty URLs)
3. WordPress theme in use
4. BuddyPress version
5. BuddyPress template pack in use
6. What does your error log reveal?

It would also help to have a screenshot of:

the single groups pages show up empty

[@emaralive Moderator 4 weeks, 1 day ago]

Hi,

The BuddyPress Featured Members plugin appears to be authored by BuddyDev. Have you tried their support forum?

BuddyDev Support – BuddyDev site

Or

[BuddyPress Featured Members] Support – WordPress Forum

[@emaralive Moderator 1 month ago]

@cactuscat

What is your permalink structure set to, e.g., plain or pretty URLs?

[@emaralive Moderator 1 month, 1 week ago]

Unfortunately, you’ve applied a band-aid at the Theme level. The next Theme update will remove your band-aid and you will have to apply it again, given the approach you’ve taken.

The bp_loggedin_user_domain( ) function should have returned a URL with a trailing slash, for example:

http://www.url.com/members/username/

Which is why the Theme has it written as:

bp_loggedin_user_domain() . $bp->notifications->slug

Something is causing the trailing slash to be missing, solving for this will be the fix. Maybe a plugin or some custom code is filtering the return value, such that is stripping the trailing slash.

Assuming you are using BuddyPress 14.3.3, see the following URL for the source code:

bp_loggedin_user_domain()

[@emaralive Moderator 1 month, 1 week ago]

OK, sounds good, I’m glad you were able to figure out the cause. May I consider this topic resolved?

[@emaralive Moderator 1 month, 1 week ago]

Hmmm… that seems odd. What does your error log reveal and does Site Heath Status reveal any critical issues?

[@emaralive Moderator 1 month, 1 week ago]

Hi @antipole,

It is difficult to say but, normally, there would be a redirect to the wp-login.php, given your example:

https://mysite.org.uk/members/myusername/messages/view/572/

The above would, normally, redirect to:

https://mysite.org.uk/wp-login.php?redirect_to=https%3A%2F%2Fmysite.org.uk%2Fmembers%2Fmyusername%2Fmessages%2Fview%2F572%2F&bp-auth=1&action=bpnoaccess

The redirect is due to a page that requires authentication and if not authenticated, there is an attempt to redirect to wp-login.php. Since this does not happen, it may be that your Redirect plugin is bypassing wp-login.php and redirecting to your 404 page, instead. I’m not sure if this is configuration issue with the Redirect plugin or just the way it works or if there is another cause.

In a nutshell the flow is:

1. bp_core_no_access()
2. bp_core_redirect()
3. wp_safe_redirect()

[@emaralive Moderator 1 month, 1 week ago]

OK, sounds good, I was just checking to see if you needed further assistance.

[@emaralive Moderator 1 month, 1 week ago]

Hi @richardrcook2,

Is this still an issue for you?

[@emaralive Moderator 1 month, 1 week ago]

Hi,

I”m not sure if it is Wordfence interfering with the upgrade process or some other plugin that might be causing the issue. What does your error log reveal?

[@emaralive Moderator 1 month, 2 weeks ago]

Hi @mike80222

This is an issue with bbPress and there is an open ticket Deprecated Warning ##3589 in bbPress Trac.

You will have to ask the folks over in bbPress as to the status of this ticket.

[@emaralive Moderator 1 month, 2 weeks ago]

Hi @dreampixel,

Thanks for bringing this to my attention. It looks like some of the notifications are not being deleted when in actuality all should be deleted that are related to the deleted user.

For example:

• new_membership_request <- this is what you initially indicated
• bbp_new_reply <- this what you indicated next
• new_message <- notification for Private Messages

The issue is that the function that deletes notifications in the event of a deleted user does not take into account that some notifications have the user_id of deleted user placed in the secondary_item_id column in the bp_notifications`database table.

Long story shorter, I have a tentative patch that I am testing that will provide a remedy for this bug. I’ll create a ticket for a fix once I’m satisfied with the patch. I’ll keep you updated as to the progress and I’ll try to fit this into the next available release.