Closed simahawk closed 7 years ago
sounds like translations are not handled for files. Basically we just write the full xml value (qweb view case) in the proper lang. The issue is that translations are just strings and they are detected via JS if I'm not wrong. So, either we find a way to load translations from the translated version or we have to handle a special case and export ir.translation records related to the records we are exporting. Need to investigate.
current status when exporting companies on MTS (w/ 2 companies and 2 logo fields):
added a sanity check message to show collision w/ models and indicate what are we pulling from core compilations. Example:
sanity check: show when a model has no name field and no xmlid fields declared
Getting bad xmlids is super easy. Now there's a check for this too:
PS: I hate this rule of strict versions.... I WANT alpha and beta... :(
I'm fast tracking this as I need these improvements ASAP
addresses #68 and #48
Based on #37 (ready to be merged)
TODO: guess mimetype for extension.