For the sake of clarity, are you stating that you are setting your permalink structure to /%postname%/.html as opposed to /%postname%/?
/%postname%.html
I’m importing an old site that had parmalinks like maysite.com/name-article.html, so I set the parmalinks to /%postname%.html.
But now, since buddypress doesn’t have a / after the %/, it’s breaking the forum tab URLs, even though the buddypress links don’t contain the .html because they don’t follow the custom parmalink rules.
I solved it with chatgpt which had made me a plugin to put .html also in the forum (which like buddypress does not depend on the parmalinks that are set on wp).
Apparently, this is the current behavior of the bp_rewrites_get_url() function, i.e., the missing trailing slash, when the permalink structure is missing a trailing slash. Hence, a permalink of /%postname%/.html will result in a URL with a missing trailing slash, e.g.:
site.url/members/<user_name>
This causes a 404 error when bbPress tries to concatenate the URLs for the following:
- Replies Created
- Engagements
- Favorites
- Subscriptions
What’s peculiar is that “Topics Started” isn’t affected because, for bbPress, all member area URLs (navigation links) are based on either the bp_displayed_user_domain() or the bp_loggedin_user_domain() functions and both of these functions have the bp_rewrites_get_url() function in the chain for return.
Regardless, this appears to be problematic due to some 3rd party themes and plugins that make use of various other BP functions that have bp_rewrites_get_url() function in the chain for return.
