[buddypress-trac] [BuddyPress Trac] #9063: New pages slug do not support WordPress subpages

[buddypress-trac]

#9063: New pages slug do not support WordPress subpages
--------------------------+------------------------------
 Reporter:  slaFFik       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Core          |     Version:  12.0.0
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+------------------------------

Comment (by slaFFik):

 I'm a bit surprised by the reaction but I will try my best to provide more
 context and thoughts about almost each paragraph in your reply.

 1) First of all, thank you for your (and other BP contributors) work on
 this big release. I have never belittled its importance or value.
 I think I even showed my gratitude several times over the past years in BP
 slack channel, either via words or emojis. That's not much, I know, sorry
 about that.

 2) I have not contributed to BP in any way for the past several years. You
 are right about that, and that's why I haven't filled any
 severity/priority/milestone fields. I simply not sure what, have little
 context, etc. After so many years off (like you rightfully said) - I'm a
 regular user having memories of how the older version of BP has worked in
 the past.
 I didn't expect that I should ''**not**'' share my experience and
 frustration.

 3) The ticket was created after one of other core contributors said me to
 do so after I asked the question in the Slack channel.
 Isn't what this channel for?

 4) To answer your first question:

 > Are you serious ?

 Yes, I am, otherwise I wouldn't create the ticket.
 Unfortunately, we have a misunderstanding here that I hope we will
 clarify.

 5) I waited "almost 6 months since beta1 to complain" because 2 reasons:
 I'm not contributing to BuddyPress right now (for years, as you stated)
 and because I haven't used BuddyPress for years. I'm not sure how you
 expect me to provide feedback earlier with these prerequisites.
 I didn't participate in v12 development, testing, etc. which is obvious
 for everyone, especially for you.

 6) Your reply about "BP Classic" plugin: that's awesome, thank you for
 mentioning it.
 Initially, I forgot about it, then I saw a notification in BP admin area,
 then I decided to go "vanilla-BuddyPress". And I provided my feedback
 based on vanilla BP and my past experience using older BP.

 BTW, the notification that mentions BP Classic has no wording about pages
 structure, it just mentions 3rd plugins and themes (and I have none).

 7) Regarding this part:

 > so details you can fix with the Site Navigation Block from your Site
 Editor or custom CSS seems really a water drop into the ocean.

 This is a visual change, not the URL structure change.
 From SEO perspective it might be beneficial to have a `/community/` page
 with some intro content, and then `/community/members/` with actual
 members directory, for example.

 With regular pages I can easily do that. With WooCommerce pages (like, My
 Account, purchases, etc) I can do that. Same with EDD, and different LMS
 plugins.

 BuddyPress (out of the box) doesn't allow me to do that - and that's fine
 if it's a mindful decision that was made.
 I'm not aware of that decision, that's why I wrote about a regression -
 because I compare my previous experience with older BP with the new
 experience with new BP.

 8) I would (humbly!) appreciated it if you could share with me what's
 wrong with "the way you shared your concerns". I fail to see what's wrong
 with it.
 Mentioning the "regression"? I specifically said "to me", pointing to my
 personal opinion which may differ from yours, of course. And that's fine.

 I think, if one removes my former BP contributions from the equation and
 absence of BP development activity, my ticket is fine.

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/9063#comment:2>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac