[@emaralive Moderator 4 days, 20 hours ago]

Out of curiosity, why did you switch from MPM Prefork to MPM Worker (PHP-FPM)?

[@emaralive Moderator 1 week, 3 days ago]

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.

[@emaralive Moderator 1 week, 4 days ago]

Don’t deactivate BuddyPress because BP Classic requires that BuddyPress is activated. So, for you, just install and activate BP Classic.

[@emaralive Moderator 1 week, 4 days ago]

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.

[@emaralive Moderator 1 week, 5 days ago]

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-tag the payload and & response look normal, of which, the numeric 1 indicates that the function wp_delete_term() returned a value of true and thus the term was deleted. So now we need to solve the mystery of why tags.js appears 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.js the conditional checks for a numeric value of 1 which should be satisfied due to the response being a numeric value of 1 and that row should have been removed according to the code within that condition, along with not receiving the An error occurred while... error message.

So now, you will need to step through the code of tags.js in an attempt to understand what might be occurring. So, you will need to utilize the “source” tab within “DevTools” and select the tags.js file 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.js in 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.js in which you will have line numbers, instead of the minified tags.min.js.

OK, this should be enough for now and, hopefully, help to determine the next steps to take.

[@emaralive Moderator 1 week, 6 days ago]

An error occurred while processing your request. Please try again later.

The above error message appears to originate from the WordPress tags.js file, line 83 with line 84 adding the message to the DOM; if the AJAX action of delete-tag has completed after the function wp_delete_term() has returned a value of false or 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).

[@emaralive Moderator 2 weeks, 5 days ago]

This has been fixed in ticket #9309. Specifically, Changeset 14146 resolves the issue for the 14.0 branch and changeset 14145 for trunk.

The general public will just have to wait until the next release for the changes slated for the 14.0 branch to go into effect.

[@emaralive Moderator 3 weeks, 5 days ago]

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.

[@emaralive Moderator 1 month, 3 weeks ago]

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:

Navigation menus

[@emaralive Moderator 2 months, 3 weeks ago]

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_screen filter hook with a callback that returns a value of true. A one-liner approach is as follows:

add_filter( 'bp_view_no_access_redirect_to_login_screen', '__return_true' );

[@emaralive Moderator 2 months, 3 weeks ago]

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?

[@emaralive Moderator 2 months, 3 weeks ago]

What theme are you using?

[@emaralive Moderator 2 months, 3 weeks ago]

OK, thanks, I’ll open a trac ticket for this issue when time allows, most likely later this week.

[@emaralive Moderator 2 months, 3 weeks ago]

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.

[@emaralive Moderator 2 months, 3 weeks ago]

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.

[@emaralive Moderator 2 months, 3 weeks ago]

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 Eleven

No other plugins were activated other than what is indicated above.

FWIW – engagements.js is 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?

[@emaralive Moderator 2 months, 4 weeks ago]

You will have to provide more information, such as from which page/url are you attempting to “subscribe/unsubscribe”?

[@emaralive Moderator 2 months, 4 weeks ago]

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?

[@emaralive Moderator 3 months, 1 week ago]

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

[@emaralive Moderator 3 months, 1 week ago]

For reference, see Trac ticket #9327.

[@emaralive Moderator 3 months, 1 week ago]

For reference, see Trac ticket #9328.

[@emaralive Moderator 3 months, 1 week ago]

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.

[@emaralive Moderator 3 months, 1 week ago]

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.

[@emaralive Moderator 3 months, 1 week ago]

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.

[@emaralive Moderator 3 months, 2 weeks ago]

You would have to ask the researcher who submitted the CVE or the indicated authoritative bodies as to why.