Closed Bug 596051 Opened 15 years ago Closed 15 years ago

Localizing templates does not allow changing titles

Categories

(support.mozilla.org :: Knowledge Base Software, task, P2)

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: paulc, Assigned: erik)

References

Details

After bug lands, this is a separate but dependent bug to make sure localizing a template does not allow changing its title. This comes at the request of the SUMO team. The reason for disallowing changing titles: to avoid confusion of remembering what you called your localized version when translating a new article. The article will have the English name. This simplifies the process for translators.
Are we basically locking up the localized document's title/slug once there is an approved translation? Is this any different than with the default locale? I assume we we still need a special workflow to be edited if the user has certain special permission?
The request was that a template must have the same title across all locales at any point.
That is interesting. That means the slugs will be the same in all locales. Which also means the algorithm in Bug 596369 isn't really required.
(In reply to comment #3) > That means the slugs will be the same in all locales. Which also means the > algorithm in Bug 596369 isn't really required. Only slugs for templates. The algorithm is still required for regular articles.
(In reply to comment #4) > (In reply to comment #3) > > That means the slugs will be the same in all locales. Which also means the > > algorithm in Bug 596369 isn't really required. > > Only slugs for templates. The algorithm is still required for regular articles. Oh my bad, I missed the keyword "templates".
Or we could implement the fallback from bug 596369 for template lookups as well. That might be seen as more consistent and a more positive, "enabling" behavior than a restriction that invisibly kicks in as soon as you stick a T: in front of your page name.
Assignee: nobody → erik
Kadir and Michael signed off on the above approach.
...which was already implemented, as it turns out.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.