Associate languages with products, not locations

RESOLVED FIXED

Status

P1
major
RESOLVED FIXED
9 years ago
9 years ago

People

(Reporter: wenzel, Assigned: wenzel)

Tracking

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

9 years ago
Languages should be valid per product, not per location. Probably need to slightly denormalize this, we don't want a separate languages table as the language list comes from product-details.

Locations should have a placeholder %LANG% that the respective language code is filled into when generating the final download URL.
(Assignee)

Updated

9 years ago
Priority: -- → P1
(Assignee)

Updated

9 years ago
Blocks: 550510
(Assignee)

Updated

9 years ago
Depends on: 558731
(Assignee)

Updated

9 years ago
Blocks: 558732
(Assignee)

Comment 1

9 years ago
Okay, placeholder syntax is going to be ":lang" minus the quotes.

I also decided to go for some more assumptions: If there are no entries in the language table for a given product, that means the product is available in all languages, OR the concept of language is not applicable. That'll save us another few thousand DB entries.
(Assignee)

Comment 2

9 years ago
The tuxedo part is done: http://github.com/fwenzel/tuxedo/commit/cc82b898d398526f114c0c0b60f32b04386563a6

Sentry and Bouncer to follow.
(Assignee)

Comment 3

9 years ago
That's fixed and live in production.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.