[trunk] some menu translations only available after manually synchronizing
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Odoo Server (MOVED TO GITHUB) |
Fix Released
|
Low
|
OpenERP's Framework R&D | ||
Bug Description
1) Steps to reproduce the issue you have observed:
Edit bzr_set.py for checkout the trunk.
Checkout OpenERP sources by bzr_set.py
start server as:
cd server
bin/openerp-
start web server as:
cd web
./openerp-web.py
- Start web brouser and open OpenERP page (localhost:8080)
- Create new database without demo data in RUSSIAN language.
- Install applications according to attached image - 0-install.png
Part of OpenERP terms are untrunslated. It is a bug !
Look at attached image - 1-untranslated_
I have included the openerp-server.conf in attachment.
I have founded a workaround.
- Update all installed modules by schedule update of base module - 2-schedule_
- and start the updating/upgrading process - 3-upgrade_
- logout and login
Now all terms are translated - 4-workaround.png
4) The platform your are using
server revision:
-------
revno: 4164
tags: openerp-
committer: <email address hidden>
branch nick: trunk
timestamp: Mon 2011-01-03 09:47:15 +0100
message:
[FIX] account: removed translate=True on account type in order to fix the translations
addons revision:
-------
revno: 4164
tags: openerp-
committer: <email address hidden>
branch nick: trunk
timestamp: Mon 2011-01-03 09:47:15 +0100
message:
[FIX] account: removed translate=True on account type in order to fix the translations
Related branches
| Chertykov Denis (chertykov) wrote | #1 |
| Olivier Dony (Odoo) (odo-openerp) wrote | #2 |
| Changed in openobject-server: | |
| assignee: | nobody → OpenERP's Framework R&D (openerp-dev-framework) |
| importance: | Undecided → Low |
| milestone: | none → 6.0-rc2 |
| status: | New → Confirmed |
| summary: |
- [trunk] strange localization problem + [trunk] some menu translations only available after manually + synchronizing |
| Changed in openobject-server: | |
| status: | Confirmed → In Progress |
| milestone: | 6.0-rc2 → 6.0 |
| Olivier Dony (Odoo) (odo-openerp) wrote | #3 |
| Changed in openobject-server: | |
| status: | In Progress → Fix Released |
| Chertykov Denis (chertykov) wrote | #4 |
Hello,
This problem comes from the fact that some modules create records in the namespace of the base module, with the consequence that translations are in 'base' too. And of course when 'base' is initially loaded the target records do not exist yet, so the translations are skipped, and are missing when the modules are installed later.
The workaround is indeed to trigger an update of the translations of 'base': either executing the "Synchronize translations" wizard or simply updating the "base" module should work (don't think you need both).
We need to add a little post-processing after the installation each module to resolve such "unresolved translations", and will do so asap.
Thank you for the detailed bug report!