Closed Bug 775288 Opened 12 years ago Closed 12 years ago

[bedrock] l10n blocks cannot be updated once on production

Categories

(www.mozilla.org :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: pascalc, Assigned: pmac)

References

(Blocks 1 open bug)

Details

(Whiteboard: [l10n][sb-sprint-1] u=user c=L10N p=2)

If you update text of an l10n block in the svn repo of the localizer, it works locally, it works on dev-allizom but it doesn't work on production, the file remains set to the first version of the translation.

This happened twice, I had to file IT bugs to ask them to restart Apache (bug 775084, bug 774814), apparently, there is some caching in Django (or maybe jinja templates) that is causing that.

Here is what Jake Maul from IT diagnosed:

"These are fixed. I don't know what was wrong, but I restarted Apache on all of the prod nodes and now that block is gone. I suspect (but can not confirm) that Django's caching layer may have had old/bad data in it. www-dev gets restarted regularly, so it wouldn't be quite so affected by this kind of thing."

.lang files are not affected, only l10n blocks, making the feature largely broken.
Assignee: nobody → pmac
Whiteboard: [l10n] → [l10n][sb-sprint-1]
Whiteboard: [l10n][sb-sprint-1] → [l10n][sb-sprint-1] u=user c=L10N p=2
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Committed r108110 to test if our other approach works.
Test is successful! Reverted in r108116.

So this is fixed without performance drawbacks. Thanks pmac and jlongster for the research.
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
Is this in production? If so let's set as verified.
Yes, this in production. Sorry for not updating.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.