Opened 8 years ago
Last modified 5 years ago
#2976 new defect (bug)
Forum slug settings should be translatable
Reported by: | netweb | Owned by: | johnjamesjacoby |
---|---|---|---|
Milestone: | 2.7 | Priority: | high |
Severity: | normal | Version: | |
Component: | Locale - i18n/l10n | Keywords: | needs-patch |
Cc: | espellcaste@…, jmdodd@… |
Description
All of the "default" slugs should be translatable so that a fresh install on a non US English install will include the localised slugs for in each of these sections:
- Forum Root Slug
- Single Forum Slugs
- Forum User Slugs
Watch out for bbp_form_slug_conflict_check()
checks on each slug when patching this
Change History (12)
#2
follow-up:
↓ 4
@
8 years ago
- Cc jmdodd@… added
I'm not sure this is something that should be translated given that it directly affects rewrite rule generation. The blog options for category_base
and tag_base
are filterable but not translatable in WordPress.
#4
in reply to:
↑ 2
;
follow-up:
↓ 6
@
8 years ago
#5
in reply to:
↑ 1
@
8 years ago
Replying to espellcaste:
Maybe related, but allow the settings slug to be changed also would be a good idea.
Which slug do you mean?
#6
in reply to:
↑ 4
@
8 years ago
Replying to netweb:
Replying to jmdodd:
I'm not sure this is something that should be translated given that it directly affects rewrite rule generation. The blog options for
category_base
andtag_base
are filterable but not translatable in WordPress.
They are actually translatable, e.g
category_base
/tag_base
!== Slug of the "Uncategorized" term.
#7
@
8 years ago
Related: #meta1892
#8
@
7 years ago
- Milestone changed from Under Consideration to Awaiting Review
- Owner set to johnjamesjacoby
- Priority changed from normal to high
These can be translatable, as defaults, but some of the logic will need to change with how default values are checked.
Let’s do this shortly after 2.6 ships, for a 2.6.1.
#10
follow-up:
↓ 12
@
7 years ago
Noting that now that users can change their "user dashboard language" separately from the "site language" any changes here should only ever reflect the "site language" and not any users "user language"
#12
in reply to:
↑ 10
@
5 years ago
- Milestone changed from 2.6.2 to 2.7
Replying to netweb:
Noting that now that users can change their "user dashboard language" separately from the "site language" any changes here should only ever reflect the "site language" and not any users "user language"
It's kind of an interesting idea, to have these slugs translate based on the user. How cool would that be.
But yes, also somewhat impossible given the current implementation.
Moving to 2.7 so this can have more thought.
(@espellcaste having the edit
slug be configurable is a good idea!)
Maybe related, but allow the settings slug to be changed also would be a good idea.