Forum Replies Created
-
Go to “Site Health Info”, click the “Copy site info to clipboard” button and then post the content as a reply or post the content on a site like “pastebin(dot)com” and in a reply, provide a link to the content.
There is more to your story than you are revealing. What is the version of BuddyPress?
My point is that this doesn’t appear to be a BuddyPress issue. If you create a WordPress post and that post shows up as a BuddyPress activity, then the tracking is working, regardless of whether featured images are showing within an Activity item as delayed as opposed to instantly.
IOW, the issue appears to reside with FIFU itself or networking issues that are causing the delay (since images are sourced externally).
If you still believe that this is a issue with BuddyPress then I suggest that you open a ticket and provide facts that support your claim.
On their (FIFU) plugin page (WordPress Plugin directory) it states:
[PRO] bbPress and BuddyBoss Platform integration
Which most likely means that you would have to upgrade to the PRO version. Additionally, they only claim integration with bbPress and BuddyBoss Platform. Integration with BuddyPress is not stated.
Closing this topic.
BuddyPress 14.5.0 was released on July 7, 2026 and is compatible with WordPress 7.0 branch.
BuddyPress 14.5.0 was released on July 7, 2026 and is compatible with WordPress 7.0 branch.
You will need to provide additional information, such as:
- Steps to reproduce the error
- Full stack trace for the error
- Active Theme
- Active Plugins
There is information available in the User Handbook for BuddyPress that may have answers to your questions.
The BP Classic plugin will convert the URL directories into normal pages. Additionally, you shouldn’t have to copy any template files, unless you are attempting to overload/override the standard (default) templates.
Last but not least, in the future, when you require help, create your own topic instead of trying to piggyback on someone else’s issue/topic.
Out of curiosity, why did you switch from MPM Prefork to MPM Worker (PHP-FPM)?
Yeah, unfortunately, the “very large arrow” was a result due a change with the WordPress 6.9 branch. This was previously reported in the Support forum topic -> Can’t register new users .
Subsequently, Trac ticket #9324 was opened and resolves the issue, however, the ticket won’t be incorporated until the next BuddyPress release.
If you read through the indicated Support forum topic (specifically, here) there were some potential “workarounds” provided, prior to opening the Trac ticket. I suppose, since there is a patch that contains the CSS rules, those rules could be used as yet, another workaround until the next release.
Don’t deactivate BuddyPress because BP Classic requires that BuddyPress is activated. So, for you, just install and activate BP Classic.
If your current version of BuddyPress is greater than or equal to 12.0.0, you will need to install and activate the BP Classic plugin/add-on to restore pages.
Interesting regarding “creating a term” because there should have been a payload with 10 key:value pairs & response with XML data, however, let’s put a pin it for now and focus on
delete-tag, which may solve the “creating a term” issue, as well. As an aside, “creating a term” may be using the normal “form” method, the same as when “JavaScript” is disabled but, this is mere conjecture since we don’t have all the facts.Backing up to
delete-tagthe payload and & response look normal, of which, the numeric1indicates that the functionwp_delete_term()returned a value oftrueand thus the term was deleted. So now we need to solve the mystery of whytags.jsappears to be functioning in an abnormal way or in IOW, ‘what the heck is going on?’.On another note, when the “delete” link is clicked does the background color of the row change to hex color value of #faafaa? Furthermore, if you look at line 50 of
tags.jsthe conditional checks for a numeric value of1which should be satisfied due to the response being a numeric value of1and that row should have been removed according to the code within that condition, along with not receiving theAn error occurred while...error message.So now, you will need to step through the code of
tags.jsin an attempt to understand what might be occurring. So, you will need to utilize the “source” tab within “DevTools” and select thetags.jsfile so that it shows in the code window, then select line 50 to set a breakpoint, then delete a category, then step through the code to make sure the condition of line 50 is being stepped through. Additionally, make sure the code in the code window matches code from GitHub. The path top->domain->wp-admin->js where the targeted file should be residing.NOTE: As an aside, your file might be named
tags.min.jsin which case you won’t have sequential line numbers. If this is the case, you may want to temporarily add the following to the wp-config.php file (you can remove or comment it out after you have finished debugging):define( 'SCRIPT_DEBUG' true );This will load
tags.jsin which you will have line numbers, instead of the minifiedtags.min.js.OK, this should be enough for now and, hopefully, help to determine the next steps to take.
An error occurred while processing your request. Please try again later.The above error message appears to originate from the WordPress
tags.jsfile, line 83 with line 84 adding the message to the DOM; if the AJAX action ofdelete-taghas completed after the functionwp_delete_term()has returned a value offalseor a numeric `0′.The following is an excerpt from the docblock for said function:
* @return bool|int|WP_Error True on success, false if term does not exist. Zero on attempted * deletion of default Category. WP_Error if the taxonomy does not exist.You might want to debug the AJAX call via “DevTools” of your web browser, start with looking at the results (Status, Payload & Response) for admin-ajax.php when deleting a term (Category, Tag or Series).
The Topic Owner created a Trac ticket with the same info that was posted in this thread. See Trac ticket #9333 for future info/dispostion.
Navigation menu items are associated with their respective “active component”, that is, what would be considered “main menu” items. Read through the following document to see if it may shed some insight as to what you should do:
The slug you provided corresponds to the Simple CAPTCHA Alternative with Cloudflare Turnstile plugin.
The simplest solution is to force BuddyPress to use the standard WordPress login form, this can be accomplished by utilizing the
bp_view_no_access_redirect_to_login_screenfilter hook with a callback that returns a value oftrue. A one-liner approach is as follows:add_filter( 'bp_view_no_access_redirect_to_login_screen', '__return_true' );You will have to provide more information. BuddyPress doesn’t have an announcement page, are you using a plugin that generates this page and if so, what plugin?, I’m not sure if this is something special or a normal group activity item.
As to your reference to “BB Forum”, do you mean bbPress or some other plugin and if the latter, what plugin?
What theme are you using?
OK, thanks, I’ll open a trac ticket for this issue when time allows, most likely later this week.
Do you have a link to the specific “Cloudflare Turnstile” plugin that you are utilizing? I’m asking because there appears to be several plugins that are available via the WordPress plugin directory.
Thanks for the link and I’m not going to speculate as to why that topic went unanswered. The short of the story is that BuddyPress requires “JavaScript” (JS) to fully function properly, especially when utilizing the BP Nouveau template pack (relies on AJAX – Asynchronous JavaScript and XML). Thus, given the scenario of the short story, it doesn’t make sense to have JS disabled.
As far as I can tell, “subscribe/unsubscribe” functions as expected when BuddyPress is activated or deactivated, thus I’m not able to duplicate your claim. Additionally, this was tested in the following environment:
WordPress: 6.9.1
BuddyPress: 14.4.0 – activated & deactivated
bbPress: 2.6.14 – activated
theme: Twenty ElevenNo other plugins were activated other than what is indicated above.
FWIW –
engagements.jsis responsible for the functioning of the subscription process for bbPress. It could be that this script is not being enqueued due to some other undisclosed factor or, if enqueued, a javascript error caused by a conflict with a theme or other plugin, however, this is just speculation since I am not able, at this time, to duplicate the issue you have described.As to:
I have seen other messages on this topic dating back a number of years but no clear answer
I’m not aware of such topics within the BuddyPress support forums, could you provide a specific topic with this claim?
