[tryton-dev] Re: Best Linux Server

2014-04-04 Thread alisonken1
Slackware. Not as hard as people think. Although you don't have auto-dependency resolution, I've had servers running for 10 years with only security updates. As an example, I just retired an old 486 machine for our electronics store. On Sunday, March 2, 2014 12:13:29 AM UTC-8, M. Janaki Meena

Re: [tryton-dev] Duplicate translations

2014-04-04 Thread Sergi Almacellas Abellana
El 04/04/14 18:36, Cédric Krier ha escrit: Dear translators, I just discover that the changeset [1] generates duplicate translations for the error message defined in translation.xml. You have to manually delete the old one from your database and po file. If you don't this can generate a tracebac

Re: [tryton-dev] Assign values in a new field

2014-04-04 Thread Sergi Almacellas Abellana
Hi inteligent solutions :) El 04/04/14 21:35, solucionesdeinteligen...@gmail.com ha escrit: I defined a new field called serie in the sale module (file sale.py) as show: serie = fields.Selection([ ('n', 'Remision'), ('c', 'Serie C'), ('e', 'Serie E'), ('f', 'Serie F'),

[tryton-dev] Assign values in a new field

2014-04-04 Thread solucionesdeinteligencia
I defined a new field called serie in the sale module (file sale.py) as show: serie = fields.Selection([ ('n', 'Remision'), ('c', 'Serie C'), ('e', 'Serie E'), ('f', 'Serie F'), ('p', 'Serie P'), ('s', 'Serie S'), ], 'Serie', required=True) The first question is h

Re: [tryton-dev] Duplicate translations

2014-04-04 Thread Cédric Krier
On 04 Apr 18:36, Cédric Krier wrote: > Dear translators, > > I just discover that the changeset [1] generates duplicate translations > for the error message defined in translation.xml. > You have to manually delete the old one from your database and po file. > If you don't this can generate a trac

[tryton-dev] Duplicate translations

2014-04-04 Thread Cédric Krier
Dear translators, I just discover that the changeset [1] generates duplicate translations for the error message defined in translation.xml. You have to manually delete the old one from your database and po file. If you don't this can generate a traceback when the server will try to raise those err