Skip to:
Content

Opened 4 years ago

Closed 2 weeks ago

#5579 closed enhancement (maybelater)

Dynamic component names

Reported by: sooskriszta Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: I18N Keywords: trac-tidy-2018
Cc: boonebgorges, vivek@…, needle@…

Description

Related #5578

People often want to rename BuddyPress components: Perhaps someone wants to rename Groups to Schools or Friends to Connections.

Editing/creating language files as suggested at http://codex.buddypress.org/getting-started/customizing/customizing-labels-messages-and-urls/ is only a partial and temporary solution as it requires a lot of work and is wiped on updates.

Perhaps we should store Component names in database, and allow admins to change them either via Admin interface or via wp-config filters. In the language files we can then have variables %% instead of hardcoded component names. That said, we should also include in language files the Default component names in that language (in case the admin doesn't want to change the component name from whatever it would generally be called in his/her language)

Change History (7)

#1 follow-up: @boonebgorges
4 years ago

Which part of the interface are you talking about when you talk about "component names"? Like the list at Dashboard > Settings > BuddyPress > Components?

#2 @DJPaul
4 years ago

  • Milestone changed from Awaiting Review to Future Release

Component *slugs* will eventually become changeable via an admin UI, but strings (such as the component title) may also be supported in the same interface, due to how BP builds the navigation menus. Or, just thinking out aloud, perhaps the main menu becomes a custom navigation menu and then you can just use WordPress' nav menus admin screen to set the titles to whatever you want.

Your suggestion of mixing strings together using placeholders probably won't work; I've done similar things before and have had problems with regards to differences in locales about sentence structure/word order.

At either rate, I don't think the basic idea is bad so I'm going to put this into the Future Release pile until other things shape up to allow us to re-visit this ticket.

#3 in reply to: ↑ 1 @sooskriszta
4 years ago

  • Cc vivek@… added

Replying to boonebgorges:

Which part of the interface are you talking about when you talk about "component names"? Like the list at Dashboard > Settings > BuddyPress > Components?

I think we are primarily concerned about how the component names appear in the frontend.

#4 @needle
3 years ago

  • Cc needle@… added

#5 @DJPaul
20 months ago

  • Component changed from Locale - i18n to I18N

#6 @DJPaul
2 weeks 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/

#7 @DJPaul
2 weeks ago

  • Milestone Awaiting Contributions deleted
  • Resolution set to maybelater
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.