Migrate theme translations from stage to production

RESOLVED FIXED

Status

defect
P1
normal
RESOLVED FIXED
10 years ago
9 years ago

People

(Reporter: stas, Assigned: stas)

Tracking

Details

(Whiteboard: [on March 2])

Filing this bug as a follow-up to bug 548126 (which has more details on the whole l10n plan). 

On March 2, when 1.0 is scheduled to go live, stage will have new strings, but production will have new posts.

1) PROD: Push 1.0 code live

2) PROD: Re-scan theme strings with WPML

   * new strinsg in 1.0 will be added to the WPML "string translation" panel, with no translations for now.

3) STAGE: Change all localizers to "Subscribers"

   * in order to lock the string translations on stage

4) STAGE: export every locale's theme translations to a PO file using WPML

5) PROD: import every locale's PO file using WPML

   * this has to be done separately for each locale and for each context (which there are 2). This means about 30 imports at the moment.
   * should take approximately 30 minutes.

6) PROD: Add "edit_others_pages" to the "Localizer" user role.

   * From now on, localizers work only on production.

Between point 2 and 5, there will be a short window of time where the new strings in 1.0 will be displayed in English on production.
Priority: -- → P1
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
w00t! thanks Alex!
Product: Websites → Websites Graveyard
You need to log in before you can comment on or make changes to this bug.