Forum Replies Created
-
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?
You will have to provide more information, such as from which page/url are you attempting to “subscribe/unsubscribe”?
It looks like this issue/bug is isolated to the BP Nouveau template pack. Meaning, changing the “View” slug to something different while utilizing the BP Legacy template pack appears to work as expected.
Can you confirm that you have the BP Nouveau template pack enabled?
MediaPress is authored and maintained by BuddyDev, you might want to contact their support forum, via either of the following:
- BuddyDev Support Forum – BuddyDev site
- MediaPress Support Forum – WordPress site
For reference, see Trac ticket #9327.
For reference, see Trac ticket #9328.
You should submit a ticket with the type set to “enhancement”, with the details you have expressed here, such that your proposal can be considered and dispatched accordingly.
Afterwards, if you decide to submit a PR, the ticket can be referenced which will attach the PR to the ticket.
You should submit a ticket with the type set to “enhancement”, with the details you have expressed here, such that your proposal can be considered and dispatched accordingly.
Afterwards, if you decide to submit a PR, the ticket can be referenced which will attach the PR to the ticket.
By default, BuddyPress utilizes the “rewrites” URL parser which creates an equivalent of “pages” which are located from the dashboard @ Settings -> Buddypress -> URLs.
If you require “pages” then you will have to install and activate the BP Classic add-on/plugin of which BuddyPress associated pages will show within WordPress “Pages”.
As for wpForo, they claim integration with BuddyPress, so you should ask your integration questions within their wpForum Integration forum.
You would have to ask the researcher who submitted the CVE or the indicated authoritative bodies as to why.
Wordfence posted this alert on January 22, 2026, which can be found here. Similarly, Patchstack had reported the alert on January 23, 2026, which can be found here.
In either case, both sites indicate that this was patched in BuddyPress version 14.3.4, which the release was announced in March of 2025, approximately 10 months ago. See the following:
- BuddyPress 14.3.4, 12.5.3 & 11.4.4 Security Releases – support forum announcement
- BuddyPress 14.3.4, 12.5.3 & 11.4.4 Security Releases – Blog/News announcement
- BuddyPress 14.3.4, 12.5.3 & 11.4.4 are available – BP Team Updates
Additionally, in the future, you may want to consider refraining from double posting.
There may be some confusion as to what should transpire here. I believe what was expected was that you would share the data from an “error log” as opposed to the generic WordPress (WP) error message of “There has been a critical error on this website.”
The link that is included in the generic WP error message should have eventually led you to information regarding, to paraphrase, “How to Troubleshoot” for example, this situation may be related to a “plugin conflict” whereby steps could be taken to isolate the conflict, see A Plugin is causing compatibility issues. Have you tried deactivating plugins other than BuddyPress in an attempt to determine whether a “plugin conflict” exists?
Furthermore, there is information about Debugging in WordPress, this information will help you configure WP such that you could provide/share error data from an error log, which is what the other moderator was asking you to share.
Note: there are plugins that can facilitate the configuration for debugging, that information is found near the bottom of the “Debugging in WordPress” page.
For reference, the topic owner (TO) has opened trac ticket 9325
What is the model of the iPhone and what is the version of the Safari browser that you are using?
Better yet, a ticket might be more appropriate for this situation, use the following link to submit a ticket:
AFAIK, the ability to upload a cover image with the Twenty Twenty-Five theme is the same as the Twenty Eleven theme, which was posted here.
This appears to be a duplicate topic thus closing this topic.
I was able to locate someone with an iPhone and I wasn’t able to duplicate the issue you described:
With:
- WordPress 6.9
- BuddyPress 14.4.0
- Twenty Eleven theme
- iPhone 16 Pro
- ios 26.2 <- Safari browser
Steps:
Pressing the “Select your file” button produces the following selections:- Photo Library
- Take Photo or Video
- Choose file
Selected and uploaded a photo from the “Photo Library” which uploaded successfully, i.e., “Your new cover image was uploaded successfully”.
You appear to be double posting, see User Profile Cover Image not uploading in the Iphone Safari Browser.
The difference is the other topic specifies the Safari browser. Is this isolated to the Safari browser or do other installable browsers have this same issue as well? Additionally, what theme is being used on the website?
Just so you know, I don’t have an Iphone, so I’ll have to check and see if someone on the team has one and can duplicate this issue.
The standard message for BuddyPress (BP) is “Sorry, that username already exists!” which appears to differ from what you’ve indicated, perhaps you elaborate as to why there is a difference. Furthermore, additional info would be helpful, such as:
- Is this is “single site” or “multisite” installation?
- Is this the “standard” or “membership requests” registration process?
- Can the assumption be made that BP 14.4.0 is currently installed?
