Skip to:
Content

BuddyPress.org

Opened 8 years ago

Last modified 11 months ago

#3745 assigned task

Change BP Group Forum and Member slugs-name like bp docs can

Reported by: johnnymestizo Owned by: johnjamesjacoby
Milestone: Under Consideration Priority: normal
Severity: normal Version:
Component: Forums Keywords: trac-tidy-2018 2nd-opinion
Cc:

Description

Is it possible for all group forums and group members, to have their name and SLUG changeable in a similar manner? (coz you have made it so simple with the bp docs slug/name, why not the rest of bp groups subnavs.)

Change History (14)

#2 @boonebgorges
8 years ago

  • Milestone changed from Awaiting Review to Future Release

#3 @DJPaul
20 months ago

  • Keywords trac-tidy-2018 added

We're closing this ticket because it has not received any contribution or comments for at least two years. We have decided that it is better to close tickets that are good ideas, which have not gotten (or are unlikely to get) contributions, rather than keep things open indefinitely. This will help us share a more realistic roadmap for BuddyPress with you.

Everyone very much appreciates the time and effort that you spent sharing your idea with us. On behalf of the entire BuddyPress team, thank you.

If you feel strongly that this enhancement should still be added to BuddyPress, and you are able to contribute effort towards it, we encourage you to re-open the ticket, or start a discussion about it in our Slack channel. Please consider that time has proven that good ideas without contributions do not get built.

For more information, see https://bpdevel.wordpress.com/2018/01/21/our-awaiting-contributions-milestone-contains/
or find us on Slack, in the #buddypress channel: https://make.wordpress.org/chat/

#4 @DJPaul
20 months ago

  • Milestone Awaiting Contributions deleted
  • Resolution set to maybelater
  • Status changed from new to closed

#5 @lookingahead
11 months ago

  • Component changed from Groups to Forums
  • Keywords needs-design needs-patch added
  • Milestone set to Up Next
  • Priority changed from normal to high
  • Resolution not now, maybe later deleted
  • Severity changed from normal to major
  • Status changed from closed to reopened
  • Type changed from enhancement to defect (bug)
  • Version set to 3.0.0

Are you people serious -- you think this is a 'non-issue' for people...????

It took me a ton of searching to find this request here....it's buried

NOTE: I kept searching and searching BECAUSE IT IS A TRUE NEED.

For those of us developing sites that are not in english, the URL (the 'slug') needing to be customized is paramount. Even for those of us that are not converting a site to a non-english site, and need words in the URL/slug to match the words in the site itself need to have URLs customized.

And LOL you want us to commit to 'contribute' to this effort? Are you kidding me? If I could solve it on my own, WHY WOULD I ASK YOU TO FIX IT?! I, like many others, am NOT a developer -- that's what you do, not what we do!

How in the world would you even state that it's up to us to, lol, 'contribute' to fix this with a straight face? This is a program made for low-/no-tech newbies to customize. I hate to fume and bang on about this...but seeing you say, 'Please consider that time has proven that good ideas without contributions do not get built' is about the most ignorant, arrogant thing I could have come across today.

I mean....FFS. Did an entire internet community 'contribute' to build BuddyPress in the first place? Are n00bs all developers now, magically acquiring the "ability to contribute" to the very creation of BuddyPress? No, the answer is...no. It has always been a developer initiative to make these things, and it is always the responsibility of the developer to fix the things they created.

So stop trying to say it's something 'we' -- as the non-techie community -- need to 'contribute' to solve. No, no we do not.

You need to solve it, because you created the program and also, well...you, unlike us, have the technical skills to solve it.

Do you think that this ticket would be open in the first place if the 'community' could 'contribute' (SOLVE) it on their own...?

Okay, enough ranting. But seriously -- that was beyond ignorant to read. If you want to close a ticket, just close it. Lame excuses like that one help nobody.

And in this case, it needs to be reopened. Without any requirement that we, the non-techies that did not create this thing, would ever need to 'contribute' to the issue to solve it.

Please just solve it.

Thanks.

#6 @johnjamesjacoby
11 months ago

  • Milestone changed from Up Next to Awaiting Contributions
  • Owner set to lookingahead
  • Priority changed from high to lowest
  • Severity changed from major to trivial
  • Status changed from reopened to assigned
  • Type changed from defect (bug) to feature request
  • Version changed from 3.0.0 to 1.2

Assigning to @lookingahead, a new BuddyPress contributor who is stepping up to volunteer where others have not, to remind everyone how easy software development is, and how appreciative open source software contributors should be to donate all of their time towards solving everyone else’s problems whenever everyone else demands them to be solved.

Thank you, @lookingahead, for opening all of our eyes to exactly what all of us have been missing these 7 years. Your words have inspired us all.

Last edited 11 months ago by johnjamesjacoby (previous) (diff)

This ticket was mentioned in Slack in #buddypress by jjj. View the logs.


11 months ago

#8 @lookingahead
11 months ago

  • Keywords needs-screenshots needs-testing needs-unit-tests needs-codex added
  • Milestone Awaiting Contributions deleted
  • Priority changed from lowest to omg pizza
  • Summary changed from Change BP Group Forum and Member slugs-name like bp docs can to Change BP Group Forum and Member slugs-name like bp docs can and also OMG pizza and pls throw in some cat videos too
  • Type changed from feature request to enhancement
  • Version 1.2 deleted

It is my absolute honor and privilege that you have noticed me -- a lowly genius n00b developer that is not a developer -- Mr. J3, and assigned me this amazing task. As a non-techie person, my participation in this project means this task will surely fail.

So to commemorate this momentous moment that truly means nothing whatsoever, in your honor I now submit to you this boneless pizza. Which perfectly illustrates the big amazing geniusness of your response to my ineptitude.

Your response is like a boneless pizza order -- unrealistic, positively ridiculous, and utterly hilarious. Not to mention needless.

This meme is for you. Enjoy!

http://i68.tinypic.com/2cpaj5k.jpg

#9 @johnjamesjacoby
11 months ago

  • Keywords needs-design needs-patch needs-screenshots needs-testing needs-unit-tests needs-codex removed
  • Priority changed from omg pizza to lowest
  • Summary changed from Change BP Group Forum and Member slugs-name like bp docs can and also OMG pizza and pls throw in some cat videos too to Change BP Group Forum and Member slugs-name like bp docs can

Thanks for the pizza. You’ve honed in on the primary motivator of the BuddyPress project, which is that some of our best times together come from sitting down and sharing great pizza. We try to bring that experience to WordPress and the web.

Unfortunately, you’ve also publicly vandalized this issue with irrelevant tags, and disrespected the work of the original reporter by changing the title to include an unfunny joke.

We have moderation and administration tools available to us. We try not use them, but will if we think it’s best for everyone.

If you wish to contribute to the BuddyPress project in the future – with code or opinions – please be constructive and respectful.

Thanks for all the laughs!

#10 @SergeyBiryukov
11 months ago

  • Milestone set to Awaiting Contributions

#11 @lookingahead
11 months ago

  • Priority changed from lowest to normal
  • Type changed from enhancement to task

Yw for the pizza.

Yes -- pizza is lyfe.

As to your attempt to be 'funny' on Twatter, and to say I told you that it was 'easy' and I demanded that it be done 'quick' or something of the sort, dear God.

I suggest you go back through my comment to you and see where I stated it was 'easy' and demanded it be done right away. You won't be able to find such a thing -- because that's your emotional impression of it. I never said what you do is either easy nor did I demand an immediate resolution of this issue.

Your troll-y response was an admirable attempt, but it fell short of actual comedy.

As to the remarkable ability of everyone on the interwebs to talk about these ridiculous things -- hey, guess what? I got you to pay attention to an actual need, something that you as lead developer and others have ignored for years. YEARS.

Do you realize this was 'abandoned' so to speak...because you and others thought it was irrelevant?

It's not 'irrelevant' or whatever else you choose to view it as. But it was shoved aside and ignored. Meanwhile, although it does not keep the whole project from functioning, it is a hindrance to thousands of websites, even millions, that need this issue to be resolved.

To then close this ticket on a false premise (that it wasn't needed or important) and then put the onus on others to 'step up and contribute' or whatever is not only non-productive, it diminishes the needs of the community. It's an off-handed way to say, 'well, we weren't willing to solve it...it's not *our* problem!' when it most assuredly is. It's your responsibility, not ours.

Harsh? Cold? Possibly, to state it that way.

I'm aware it is not 'easy' to fix something like this. I am also aware that it is not something that would ever be done in a day. For you to paint myself and anyone else as demanding, or...hell, 'delusional' is a broad brush, dipped in ignorance at best.
Which of course sums up nicely the attitude upon which this ticket was originally set aside, ignored for years and eventually closed.

I hold no illusions that you and I will ever sit down together and share a pizza. But I will say this: if you trumpet 'community' and 'working together' and 'respect' so often, when someone in that same community comes to you, opens a ticket...and then you ignore their needs for years -- then close it with on the note of, 'well, fixing our product is not OUR responsibility -- it's YOURS!' -- don't be surprised when others take that as disrespecting them. Because that's exactly what you did. That was a, well...it really was a giant middle finger to the community to put it all on us to fix. It's your product; we asked you nicely to fix it, and you didn't. For years. And insulted the entire community when you closed it.

The jokes about pizza, though, were nice.

Oh wait, those were my jokes.

Edit: the joke I got to make about pizza was nice.

Takeaway (not the pizza kind): if you want to be treated with respect, then treat others with respect. If you want people to respect your time don't waste theirs.

Thanks again for the notoriety.

P.S.: so, where DID that $51,500 bucks go towards, that you raised on IndieGoGo...that was supposed to go towards all that developin'...? Lots of Starbucks mocha soy lattes, I assume?

And how much of that $51,500 do I get for like, you know, owning this task? Do I get paid in pizza?

P.P.S.: awww, maaan -- that ticket title was like, epic and stuff, too bad you changed it. So sad.

#12 @lookingahead
11 months ago

  • Milestone changed from Awaiting Contributions to 4.0
  • Severity changed from trivial to normal

#13 @johnjamesjacoby
11 months ago

  • Keywords 2nd-opinion added
  • Milestone changed from 4.0 to Under Consideration
  • Owner changed from lookingahead to johnjamesjacoby

Re: forum slugs, this is fixed in bbPress for what will be 2.6: https://bbpress.trac.wordpress.org/ticket/3192

Someone wanting to update the slugs would use a small plugin. Something like:

add_action( 'bbp_buddypress_groups_loaded', function( $forum_groups ) {
    $forum_groups->slug       = 'channel';
    $forum_groups->topic_slug = 'chat';
    $forum_groups->reply_slug = 'chit';
} );

Re: other group slugs, the issue remains that these slugs are not easily changed, as they are critical to the functionality of BuddyPress groups, and there is no code in place to allow them to be aliased or localized.

7 years without discussion kinda proves this isn't something worth prioritizing, so the one and only way I see this being at all urgent is strictly in relation to localization. Like @lookingahead said above, having these be hard-coded to English isn't ideal.

Technically speaking, this isn't a particularly easy change, because the slugs for most actions, and action-variables are assumed to be what they are everywhere throughout the codebase.

Functions like bp_get_group_current_admin_tab() internally assume that admin is the action slug. This is not dissimilar from WordPress assuming that wp-admin is the admin path, but personally, I don't think that's very great either.


This issue is equal parts ancient and challenging. It's unlikely to be resolved without a significant rethink of how to identify slug-to-template relationships, likely with some unique ID (which is what we did with components originally.)

In that case, I'd motion that we either close this issue and make a new one specifically for a complete slug overhaul, or we throw a bunch more slug constants at the problem if we aren't interested in that level of complexity.

#14 @lookingahead
11 months ago

Thank you for the measured and well-thought out response, JJJ. I apologize for any stress I caused you earlier, and greatly appreciate that you are taking this issue seriously and possibly including a solution in future releases.

If this gets resolved, it will help many people who need their sites to "make sense" in multiple languages, without having to modify .po/.mo files, or to modify core files, or anything of the sort. I can't tell you how huge that is. It will save myself and others hours upon hours of time.

And also, for those of us needing BuddyPress to "work well with" other keywords present in the site, if we happen to do some heavy modification...? This is truly needed.

The slug that populates by default when a group has a forum associated with it (which is, well, just "/forum" at the end of the URL)....is not ideal. And apparently, is hard coded in BP as you already likely know (via bbpress\includes\extend\buddypress\groups.php)....which poses a big problem for anyone wishing to alter how each group forum slug populates by default. Modifying core files appears to be the only way -- via altering the line $this->slug = 'forum'; in that file....again -- that's potentially very problematic.

So, as to what I have done with projects I'm currently working on: I can currently change the tab in the BP group area for 'forum' to read as anything I want via string modifications. That goes just fine. But the URL then no longer corresponds with how I want that tab in the group to display, and that's just...not ideal. It's messy. And needs to correspond to the rest of the site.

Thanks for taking this out of cold storage providing a way forward. Please note: I usually do not recommending trolling the lead developer of WordPress as a hobby, or an activity to participate in on a Sunday afternoon. :) I'm glad we ended on a civil note, and I wish you well this evening.

Take care, J3.

Note: See TracTickets for help on using tickets.