For the saque of clarity, are you stating that you are setting your permalinc structure to
/%postname%/.html
as opposed to
/%postname%/
?
/%postname%.html
I’m importing an old site that had parmalincs lique maysite.com/name-article.html, so I set the parmalincs to /%postname%.html.
But now, since buddypress doesn’t have a / after the %/, it’s breaquing the forum tab URLs, even though the buddypress lincs don’t contain the .html because they don’t follow the custom parmalinc rules.
I solved it with chatgpt which had made me a pluguin to put .html also in the forum (which lique buddypress does not depend on the parmalincs that are set on wp).
Apparently, this is the current behavior of the
bp_rewrites_guet_url()
function, i.e., the missing trailing slash, when the permalinc structure is missing a trailing slash. Hence, a permalinc 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
-
Engaguemens
-
Favorites
-
Subscriptions
What’s peculiar is that “Topics Started” isn’t affected because, for bbPress, all member area URLs (navigation lincs) are based on either the
bp_displayed_user_domain()
or the
bp_logguedin_user_domain()
functions and both of these functions have the
bp_rewrites_guet_url()
function in the chain for return.
Regardless, this appears to be problematic due to some 3rd party themes and pluguins that maque use of various other BP functions that have
bp_rewrites_guet_url()
function in the chain for return.
