Skip to Content

Contributors

  • Re: Technical Question: Restart Odoo process after res.partner model change
    Hi Pedro,
    
    I did not want to offend anyone and have also tried to do justice to 
    your expertise.
    
    Reading your answer tells me I asked the wrong questions.
    
    Regads,
    
    Janik
    
    On 6/21/24 09:03, Pedro M. Baeza wrote:
    
    > Janik, I'm afraid your deployment process is not correct, not an Odo 
    
    > bug, as both updating or installing changes DB schema, but obviously 
    
    > the Python code should be reloaded for this to happen (aka, the 
    
    > service should be restarted). Questioning an expert like Graeme with a 
    
    > lot of years of experience in such basic things is not a good practice 
    
    > IMO.
    
    >
    
    > Regards.
    
    >
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    >
    
    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH
    Tel: +41 44 244 7222
    
    

    by Janik von Rotz - 09:47 - 21 Jun 2024
  • Re: 16.0 translations
    Exactly. Alternatively it can be done in the language settings by updating and overwriting the language.



    Best regards
    Christian



    Von: "Holger Brunn" <notifications@odoo-community.org>
    An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
    Gesendet: Donnerstag, 20. Juni 2024 23:42:15
    Betreff: Re: 16.0 translations

    the i18n_extra mechanism still works exactly as it used to.
    
    That includes that translations are only overwritten on the first init of a 
    module, or with -u $module --i18n-overwrite.
    
    
    
    -- 
    Your partner for the hard Odoo problems
    https://hunki-enterprises.com

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Christian Zöllner - 09:25 - 21 Jun 2024
  • Re: Technical Question: Restart Odoo process after res.partner model change
    Janik, I'm afraid your deployment process is not correct, not an Odo bug, as both updating or installing changes DB schema, but obviously the Python code should be reloaded for this to happen (aka, the service should be restarted). Questioning an expert like Graeme with a lot of years of experience in such basic things is not a good practice IMO.

    Regards.

    by Pedro M. Baeza - 09:01 - 21 Jun 2024
  • Re: Technical Question: Restart Odoo process after res.partner model change

    Hi Graeme,

    there is no own code so there is no bug. I am pretty sure what I described is reproducible with any Odoo setup.

    As I understand updating the database schema for a running Odoo process without restarting the process is simply not possible.

    I assume Odoo has an internal state of the field defined in the module code. Only if the process is restarted the state is updated.

    Regards,

    Janik

    On 6/20/24 22:02, Graeme Gellatly wrote:
    Then that is a bug in your own code, or you have not also restarted another running odoo process with the old info. -u has worked forever.

    On Fri, Jun 21, 2024 at 6:45 AM Janik von Rotz <notifications@odoo-community.org> wrote:

    Hi Tom

    Thanks for the reply.

    I did another test with the same results.

    The Odoo log tells that it updated the tables for the module, but it didn't.

    Cheers,

    Janik


    Init Odoo database with the required modules:

    ```
    task start
    docker-odoo-install -d 16.0 -i partner_fax,contacts,module_auto_update
    ```

    Then clicked *Apps > Auto-Upgrade Modules*.

    Getting the hash for `partner_fax`: `d1db56b45a4c5baa9a6cb0c571c37b0c394d8840`

    Then changing the file:

    ```
    cd oca/partner-contact
    vi partner_fax/models/res_partner.py
    ```

    By adding:

    ```python
    xy = fields.Char()
    ```

    Then clicked *Apps > Auto-Upgrade Modules*.

    The Odoo log:

    ```
    2024-06-20 18:32:03,665 1 INFO 16.0 odoo.modules.registry: module partner_fax: creating or updating database tables
    ```

    Getting the hash for `partner_fax`: `b8236a3734e752fa62b669674afaa1db750f031d`

    When doing a restart.

    ```
    task restart
    ```

    I still get this message:

    ```
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ...e" AS "write_date", "res_partner"."fax" AS "fax", "res_partn...
                                                                 ^
    ```

    The issue can be resolved by installing the module:

    ```
    docker-odoo-install -d 16.0 -i partner_fax  
    ```

    On 6/20/24 19:57, Tom Blauwendraat wrote:
    Hi Janik

    -i is wrong anyway, it installs, -u is what you need

    I dont know why the field update does not trigger, it should - did you restart odoo beforehand?

    20 jun. 2024 18:58:18 Janik von Rotz <notifications@odoo-community.org>:

    Hi Tom

    I tested this module and like it! However, it seems its only doing an update and not an install, which does not update the database schema.

    Cheers, Janik

    Here is how I tested the module with https://odoo.build/:

    Init Odoo database with the required modules.

    ```
    task start
    docker-odoo-install -d 16.0 -i partner_fax,contacts,module_auto_update
    ```

    Checking the hash: `"partner_fax": "b8236a3734e752fa62b669674afaa1db750f031d"`

    Then changing a module file.

    ```
    vi oca/partner-contact/partner_fax/models/res_partner.py
    ```

    Adding:

    ```python
    xy = fields.Char()
    ```

    Then clicked *Apps > Auto-Upgrade Modules*.

    When doing a restart.

    ```
    task restart
    ```

    I still get this message:

    ```
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ...e" AS "write_date", "res_partner"."fax" AS "fax", "res_partn...
                                                                 ^
    ```

    Resolving the issue by installing the module:

    ```

    docker-odoo-install -d 16.0 -i partner_fax
    ```

    On 6/20/24 17:42, Tom Blauwendraat wrote:
    module_auto_update

    20 jun. 2024 17:22:17 Janik von Rotz <notifications@odoo-community.org>:

    Hello Odoo contributors,
    
    I am developing, deploying and fixing Odoo for a while and there is one 
    issue I haven't bothered enough to come up with a proper solution or 
    strategy.
    
    The problem is simple: I have an Odoo instance running with a module 
    that extends the res.partner model. The res.partner code of this module 
    is updated with a new field. The Odoo server is restarted and exits with 
    a "column does not exist" error.
    
    The same procedure works for modules that extend other models than 
    res.partner or res.user. As I understand the res.partner (and other) 
    tables are queried when the Odoo process starts. The SQL queries fail, 
    because the model code does not match the database schema.
    
    The solution to the problem seems obvious, before starting the Odoo 
    server with the new code you install module (odoo-bin -i ...). However, 
    automating this step in a deployment pipeline is difficult as you don't 
    know which module needs to be updated. Always updating the base module 
    seems like an overkill.
    
    Do you know this problem? Have you solved this problem?
    
    I would be glad to hear from you.
    
    Regards,
    
    Janik
    
    Here is a guide to reproduce the issue with https://odoo.build/:
    
    1. Init a new datbase and start the Odoo server: `task start db; task 
    init-db; task start native`
    
    2. Install the contacts module: `task install-module contacts`
    
    3. Stop the Odoo process.
    
    4. Add a new field to the res.partner code: `vi 
    odoo/odoo/addons/base/models/res_partner.py`
    
    ```python
    
    xy = fields.Char()
    
    ```
    
    5. Start the Odoo server: `task start native`
    
    It fails with:
    
    ```
    
    ...
    
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ..."message_bounce", "res_partner"."name" AS "name", "res_partn...
    ```                                                        ^
    
    
    
    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH
    Tel: +41 44 244 7222
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH 
    Tel: +41 44 244 7222

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH 
    Tel: +41 44 244 7222

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH 
    Tel: +41 44 244 7222

    by Janik von Rotz - 08:42 - 21 Jun 2024
  • Re: 16.0 translations
    Our customer isn't happy with the german translation of "Salesperson", which is "Vertriebsmitarbeiter", and would like "Kundenberater" instead.

    Hi Matthieu, in case this helps, if your pain point is about the QWeb report: https://github.com/OCA/server-ux/tree/16.0/template_content_swapper

    -- 
    田代祥隆 Yoshi Tashiro
    コタエル株式会社 / Quartile Limited



    On Fri, Jun 21, 2024 at 6:42 AM Holger Brunn <notifications@odoo-community.org> wrote:
    the i18n_extra mechanism still works exactly as it used to.
    
    That includes that translations are only overwritten on the first init of a 
    module, or with -u $module --i18n-overwrite.
    
    
    
    -- 
    Your partner for the hard Odoo problems
    https://hunki-enterprises.com

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Yoshi Tashiro. - 02:56 - 21 Jun 2024
  • Re: 16.0 translations
    the i18n_extra mechanism still works exactly as it used to.
    
    That includes that translations are only overwritten on the first init of a 
    module, or with -u $module --i18n-overwrite.
    
    
    -- 
    Your partner for the hard Odoo problems
    https://hunki-enterprises.com

    by Holger Brunn - 11:41 - 20 Jun 2024
  • RE: 16.0 translations

    Hi,

     

    I total share your pain with the German translation in that point and also on “Credit Note” where we need to replace “Gutschrift” with “Rechnungskorrektur”.

     

    For these two values I’ve solved it this way, because I could not find another solution. It removes the original value and adds a new.

    You need to translate “Salesperson” in your custom module the same as it is translated in Odoo, and then add a new key/value pair to the collection.

     

    from odoo import _, models

     

    class SaleOrder(models.Model):

        _inherit = "sale.order"

     

        def _compute_l10n_din5008_template_data(self):

            result = super()._compute_l10n_din5008_template_data()

            for record in self:

                values = record.l10n_din5008_template_data

     

                # replace salesperson from list

                sales_person_label = _("Salesperson")

                values = [x for x in values if x[0] != sales_person_label]

     

                if record.user_id:

                    values.append((_("Contact Person"), record.user_id.name))

                record.l10n_din5008_template_data = values

          return result

     

    I know this is a very poor solution and would be happy for other, more generic suggestions.

     

    Best Regards,

    Christopher

     

    From: Matthieu Mequignon <notifications@odoo-community.org>
    Sent: Donnerstag, 20. Juni 2024 16:11
    To: Contributors <contributors@odoo-community.org>
    Subject: 16.0 translations

     

    Hi guys,

    We do have a customer which would like to translate a term used in a python method in a odoo module.
    I know translations have changed a lot in 16.0, that and now field translations are stored as jsonb values.

    To give you more context, here's a bit of code https://github.com/odoo/odoo/blob/16.0/addons/l10n_din5008_sale/models/sale.py#L12-L32

    Our customer isn't happy with the german translation of "Salesperson", which is "Vertriebsmitarbeiter", and would like "Kundenberater" instead.

    In the previous versions of odoo, it was possible to create a `l10n_extra` folder, and drop a new translation for the term, and that's it.

    Now it's not possible anymore, and I'm looking for ways of doing it.
    For instance, if some python code is raising an exception with some translated text that you're unhappy with, you cannot change it.

    I noticed there was a few issues on this matter on github.com/odoo/odoo

    I'm guessing that we aren't near close of having a solution from Odoo, and was wondering if there was anything in OCA about this?

    Thanks!

    ---

    Matthieu Méquignon


    by Christopher Rogos - 10:26 - 20 Jun 2024
  • Re: Technical Question: Restart Odoo process after res.partner model change
    Then that is a bug in your own code, or you have not also restarted another running odoo process with the old info. -u has worked forever.

    On Fri, Jun 21, 2024 at 6:45 AM Janik von Rotz <notifications@odoo-community.org> wrote:

    Hi Tom

    Thanks for the reply.

    I did another test with the same results.

    The Odoo log tells that it updated the tables for the module, but it didn't.

    Cheers,

    Janik


    Init Odoo database with the required modules:

    ```
    task start
    docker-odoo-install -d 16.0 -i partner_fax,contacts,module_auto_update
    ```

    Then clicked *Apps > Auto-Upgrade Modules*.

    Getting the hash for `partner_fax`: `d1db56b45a4c5baa9a6cb0c571c37b0c394d8840`

    Then changing the file:

    ```
    cd oca/partner-contact
    vi partner_fax/models/res_partner.py
    ```

    By adding:

    ```python
    xy = fields.Char()
    ```

    Then clicked *Apps > Auto-Upgrade Modules*.

    The Odoo log:

    ```
    2024-06-20 18:32:03,665 1 INFO 16.0 odoo.modules.registry: module partner_fax: creating or updating database tables
    ```

    Getting the hash for `partner_fax`: `b8236a3734e752fa62b669674afaa1db750f031d`

    When doing a restart.

    ```
    task restart
    ```

    I still get this message:

    ```
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ...e" AS "write_date", "res_partner"."fax" AS "fax", "res_partn...
                                                                 ^
    ```

    The issue can be resolved by installing the module:

    ```
    docker-odoo-install -d 16.0 -i partner_fax  
    ```

    On 6/20/24 19:57, Tom Blauwendraat wrote:
    Hi Janik

    -i is wrong anyway, it installs, -u is what you need

    I dont know why the field update does not trigger, it should - did you restart odoo beforehand?

    20 jun. 2024 18:58:18 Janik von Rotz <notifications@odoo-community.org>:

    Hi Tom

    I tested this module and like it! However, it seems its only doing an update and not an install, which does not update the database schema.

    Cheers, Janik

    Here is how I tested the module with https://odoo.build/:

    Init Odoo database with the required modules.

    ```
    task start
    docker-odoo-install -d 16.0 -i partner_fax,contacts,module_auto_update
    ```

    Checking the hash: `"partner_fax": "b8236a3734e752fa62b669674afaa1db750f031d"`

    Then changing a module file.

    ```
    vi oca/partner-contact/partner_fax/models/res_partner.py
    ```

    Adding:

    ```python
    xy = fields.Char()
    ```

    Then clicked *Apps > Auto-Upgrade Modules*.

    When doing a restart.

    ```
    task restart
    ```

    I still get this message:

    ```
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ...e" AS "write_date", "res_partner"."fax" AS "fax", "res_partn...
                                                                 ^
    ```

    Resolving the issue by installing the module:

    ```

    docker-odoo-install -d 16.0 -i partner_fax
    ```

    On 6/20/24 17:42, Tom Blauwendraat wrote:
    module_auto_update

    20 jun. 2024 17:22:17 Janik von Rotz <notifications@odoo-community.org>:

    Hello Odoo contributors,
    
    I am developing, deploying and fixing Odoo for a while and there is one 
    issue I haven't bothered enough to come up with a proper solution or 
    strategy.
    
    The problem is simple: I have an Odoo instance running with a module 
    that extends the res.partner model. The res.partner code of this module 
    is updated with a new field. The Odoo server is restarted and exits with 
    a "column does not exist" error.
    
    The same procedure works for modules that extend other models than 
    res.partner or res.user. As I understand the res.partner (and other) 
    tables are queried when the Odoo process starts. The SQL queries fail, 
    because the model code does not match the database schema.
    
    The solution to the problem seems obvious, before starting the Odoo 
    server with the new code you install module (odoo-bin -i ...). However, 
    automating this step in a deployment pipeline is difficult as you don't 
    know which module needs to be updated. Always updating the base module 
    seems like an overkill.
    
    Do you know this problem? Have you solved this problem?
    
    I would be glad to hear from you.
    
    Regards,
    
    Janik
    
    Here is a guide to reproduce the issue with https://odoo.build/:
    
    1. Init a new datbase and start the Odoo server: `task start db; task 
    init-db; task start native`
    
    2. Install the contacts module: `task install-module contacts`
    
    3. Stop the Odoo process.
    
    4. Add a new field to the res.partner code: `vi 
    odoo/odoo/addons/base/models/res_partner.py`
    
    ```python
    
    xy = fields.Char()
    
    ```
    
    5. Start the Odoo server: `task start native`
    
    It fails with:
    
    ```
    
    ...
    
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ..."message_bounce", "res_partner"."name" AS "name", "res_partn...
    ```                                                        ^
    
    
    
    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH
    Tel: +41 44 244 7222
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH 
    Tel: +41 44 244 7222

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH 
    Tel: +41 44 244 7222

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by "Graeme Gellatly" <graeme@moahub.nz> - 10:01 - 20 Jun 2024
  • Re: Technical Question: Restart Odoo process after res.partner model change

    Hi Tom

    Thanks for the reply.

    I did another test with the same results.

    The Odoo log tells that it updated the tables for the module, but it didn't.

    Cheers,

    Janik


    Init Odoo database with the required modules:

    ```
    task start
    docker-odoo-install -d 16.0 -i partner_fax,contacts,module_auto_update
    ```

    Then clicked *Apps > Auto-Upgrade Modules*.

    Getting the hash for `partner_fax`: `d1db56b45a4c5baa9a6cb0c571c37b0c394d8840`

    Then changing the file:

    ```
    cd oca/partner-contact
    vi partner_fax/models/res_partner.py
    ```

    By adding:

    ```python
    xy = fields.Char()
    ```

    Then clicked *Apps > Auto-Upgrade Modules*.

    The Odoo log:

    ```
    2024-06-20 18:32:03,665 1 INFO 16.0 odoo.modules.registry: module partner_fax: creating or updating database tables
    ```

    Getting the hash for `partner_fax`: `b8236a3734e752fa62b669674afaa1db750f031d`

    When doing a restart.

    ```
    task restart
    ```

    I still get this message:

    ```
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ...e" AS "write_date", "res_partner"."fax" AS "fax", "res_partn...
                                                                 ^
    ```

    The issue can be resolved by installing the module:

    ```
    docker-odoo-install -d 16.0 -i partner_fax  
    ```

    On 6/20/24 19:57, Tom Blauwendraat wrote:
    Hi Janik

    -i is wrong anyway, it installs, -u is what you need

    I dont know why the field update does not trigger, it should - did you restart odoo beforehand?

    20 jun. 2024 18:58:18 Janik von Rotz <notifications@odoo-community.org>:

    Hi Tom

    I tested this module and like it! However, it seems its only doing an update and not an install, which does not update the database schema.

    Cheers, Janik

    Here is how I tested the module with https://odoo.build/:

    Init Odoo database with the required modules.

    ```
    task start
    docker-odoo-install -d 16.0 -i partner_fax,contacts,module_auto_update
    ```

    Checking the hash: `"partner_fax": "b8236a3734e752fa62b669674afaa1db750f031d"`

    Then changing a module file.

    ```
    vi oca/partner-contact/partner_fax/models/res_partner.py
    ```

    Adding:

    ```python
    xy = fields.Char()
    ```

    Then clicked *Apps > Auto-Upgrade Modules*.

    When doing a restart.

    ```
    task restart
    ```

    I still get this message:

    ```
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ...e" AS "write_date", "res_partner"."fax" AS "fax", "res_partn...
                                                                 ^
    ```

    Resolving the issue by installing the module:

    ```

    docker-odoo-install -d 16.0 -i partner_fax
    ```

    On 6/20/24 17:42, Tom Blauwendraat wrote:
    module_auto_update

    20 jun. 2024 17:22:17 Janik von Rotz <notifications@odoo-community.org>:

    Hello Odoo contributors,
    
    I am developing, deploying and fixing Odoo for a while and there is one 
    issue I haven't bothered enough to come up with a proper solution or 
    strategy.
    
    The problem is simple: I have an Odoo instance running with a module 
    that extends the res.partner model. The res.partner code of this module 
    is updated with a new field. The Odoo server is restarted and exits with 
    a "column does not exist" error.
    
    The same procedure works for modules that extend other models than 
    res.partner or res.user. As I understand the res.partner (and other) 
    tables are queried when the Odoo process starts. The SQL queries fail, 
    because the model code does not match the database schema.
    
    The solution to the problem seems obvious, before starting the Odoo 
    server with the new code you install module (odoo-bin -i ...). However, 
    automating this step in a deployment pipeline is difficult as you don't 
    know which module needs to be updated. Always updating the base module 
    seems like an overkill.
    
    Do you know this problem? Have you solved this problem?
    
    I would be glad to hear from you.
    
    Regards,
    
    Janik
    
    Here is a guide to reproduce the issue with https://odoo.build/:
    
    1. Init a new datbase and start the Odoo server: `task start db; task 
    init-db; task start native`
    
    2. Install the contacts module: `task install-module contacts`
    
    3. Stop the Odoo process.
    
    4. Add a new field to the res.partner code: `vi 
    odoo/odoo/addons/base/models/res_partner.py`
    
    ```python
    
    xy = fields.Char()
    
    ```
    
    5. Start the Odoo server: `task start native`
    
    It fails with:
    
    ```
    
    ...
    
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ..."message_bounce", "res_partner"."name" AS "name", "res_partn...
    ```                                                        ^
    
    
    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH
    Tel: +41 44 244 7222
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH 
    Tel: +41 44 244 7222

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH 
    Tel: +41 44 244 7222

    by Janik von Rotz - 08:41 - 20 Jun 2024
  • Re: Technical Question: Restart Odoo process after res.partner model change
    Hi Janik

    -i is wrong anyway, it installs, -u is what you need

    I dont know why the field update does not trigger, it should - did you restart odoo beforehand?

    20 jun. 2024 18:58:18 Janik von Rotz <notifications@odoo-community.org>:

    Hi Tom

    I tested this module and like it! However, it seems its only doing an update and not an install, which does not update the database schema.

    Cheers, Janik

    Here is how I tested the module with https://odoo.build/:

    Init Odoo database with the required modules.

    ```
    task start
    docker-odoo-install -d 16.0 -i partner_fax,contacts,module_auto_update
    ```

    Checking the hash: `"partner_fax": "b8236a3734e752fa62b669674afaa1db750f031d"`

    Then changing a module file.

    ```
    vi oca/partner-contact/partner_fax/models/res_partner.py
    ```

    Adding:

    ```python
    xy = fields.Char()
    ```

    Then clicked *Apps > Auto-Upgrade Modules*.

    When doing a restart.

    ```
    task restart
    ```

    I still get this message:

    ```
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ...e" AS "write_date", "res_partner"."fax" AS "fax", "res_partn...
                                                                 ^
    ```

    Resolving the issue by installing the module:

    ```

    docker-odoo-install -d 16.0 -i partner_fax
    ```

    On 6/20/24 17:42, Tom Blauwendraat wrote:
    module_auto_update

    20 jun. 2024 17:22:17 Janik von Rotz <notifications@odoo-community.org>:

    Hello Odoo contributors,
    
    I am developing, deploying and fixing Odoo for a while and there is one 
    issue I haven't bothered enough to come up with a proper solution or 
    strategy.
    
    The problem is simple: I have an Odoo instance running with a module 
    that extends the res.partner model. The res.partner code of this module 
    is updated with a new field. The Odoo server is restarted and exits with 
    a "column does not exist" error.
    
    The same procedure works for modules that extend other models than 
    res.partner or res.user. As I understand the res.partner (and other) 
    tables are queried when the Odoo process starts. The SQL queries fail, 
    because the model code does not match the database schema.
    
    The solution to the problem seems obvious, before starting the Odoo 
    server with the new code you install module (odoo-bin -i ...). However, 
    automating this step in a deployment pipeline is difficult as you don't 
    know which module needs to be updated. Always updating the base module 
    seems like an overkill.
    
    Do you know this problem? Have you solved this problem?
    
    I would be glad to hear from you.
    
    Regards,
    
    Janik
    
    Here is a guide to reproduce the issue with https://odoo.build/:
    
    1. Init a new datbase and start the Odoo server: `task start db; task 
    init-db; task start native`
    
    2. Install the contacts module: `task install-module contacts`
    
    3. Stop the Odoo process.
    
    4. Add a new field to the res.partner code: `vi 
    odoo/odoo/addons/base/models/res_partner.py`
    
    ```python
    
    xy = fields.Char()
    
    ```
    
    5. Start the Odoo server: `task start native`
    
    It fails with:
    
    ```
    
    ...
    
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ..."message_bounce", "res_partner"."name" AS "name", "res_partn...
    ```                                                        ^
    
    
    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH
    Tel: +41 44 244 7222
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH 
    Tel: +41 44 244 7222

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Tom Blauwendraat - 07:56 - 20 Jun 2024
  • Re: Technical Question: Restart Odoo process after res.partner model change

    Hi Tom

    I tested this module and like it! However, it seems its only doing an update and not an install, which does not update the database schema.

    Cheers, Janik

    Here is how I tested the module with https://odoo.build/:

    Init Odoo database with the required modules.

    ```
    task start
    docker-odoo-install -d 16.0 -i partner_fax,contacts,module_auto_update
    ```

    Checking the hash: `"partner_fax": "b8236a3734e752fa62b669674afaa1db750f031d"`

    Then changing a module file.

    ```
    vi oca/partner-contact/partner_fax/models/res_partner.py
    ```

    Adding:

    ```python
    xy = fields.Char()
    ```

    Then clicked *Apps > Auto-Upgrade Modules*.

    When doing a restart.

    ```
    task restart
    ```

    I still get this message:

    ```
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ...e" AS "write_date", "res_partner"."fax" AS "fax", "res_partn...
                                                                 ^
    ```

    Resolving the issue by installing the module:

    ```

    docker-odoo-install -d 16.0 -i partner_fax
    ```

    On 6/20/24 17:42, Tom Blauwendraat wrote:
    module_auto_update

    20 jun. 2024 17:22:17 Janik von Rotz <notifications@odoo-community.org>:

    Hello Odoo contributors,
    
    I am developing, deploying and fixing Odoo for a while and there is one 
    issue I haven't bothered enough to come up with a proper solution or 
    strategy.
    
    The problem is simple: I have an Odoo instance running with a module 
    that extends the res.partner model. The res.partner code of this module 
    is updated with a new field. The Odoo server is restarted and exits with 
    a "column does not exist" error.
    
    The same procedure works for modules that extend other models than 
    res.partner or res.user. As I understand the res.partner (and other) 
    tables are queried when the Odoo process starts. The SQL queries fail, 
    because the model code does not match the database schema.
    
    The solution to the problem seems obvious, before starting the Odoo 
    server with the new code you install module (odoo-bin -i ...). However, 
    automating this step in a deployment pipeline is difficult as you don't 
    know which module needs to be updated. Always updating the base module 
    seems like an overkill.
    
    Do you know this problem? Have you solved this problem?
    
    I would be glad to hear from you.
    
    Regards,
    
    Janik
    
    Here is a guide to reproduce the issue with https://odoo.build/:
    
    1. Init a new datbase and start the Odoo server: `task start db; task 
    init-db; task start native`
    
    2. Install the contacts module: `task install-module contacts`
    
    3. Stop the Odoo process.
    
    4. Add a new field to the res.partner code: `vi 
    odoo/odoo/addons/base/models/res_partner.py`
    
    ```python
    
    xy = fields.Char()
    
    ```
    
    5. Start the Odoo server: `task start native`
    
    It fails with:
    
    ```
    
    ...
    
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ..."message_bounce", "res_partner"."name" AS "name", "res_partn...
    ```                                                        ^
    
    
    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH
    Tel: +41 44 244 7222
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH 
    Tel: +41 44 244 7222

    by Janik von Rotz - 06:56 - 20 Jun 2024
  • Re: Technical Question: Restart Odoo process after res.partner model change
    Hi Janik,

    Another option is click-odoo-update, a nice contribution by Acsone. Hope it helps.

    Regards,

    On Thu, Jun 20, 2024 at 5:42 PM Tom Blauwendraat <notifications@odoo-community.org> wrote:
    module_auto_update

    20 jun. 2024 17:22:17 Janik von Rotz <notifications@odoo-community.org>:

    Hello Odoo contributors,
    
    I am developing, deploying and fixing Odoo for a while and there is one 
    issue I haven't bothered enough to come up with a proper solution or 
    strategy.
    
    The problem is simple: I have an Odoo instance running with a module 
    that extends the res.partner model. The res.partner code of this module 
    is updated with a new field. The Odoo server is restarted and exits with 
    a "column does not exist" error.
    
    The same procedure works for modules that extend other models than 
    res.partner or res.user. As I understand the res.partner (and other) 
    tables are queried when the Odoo process starts. The SQL queries fail, 
    because the model code does not match the database schema.
    
    The solution to the problem seems obvious, before starting the Odoo 
    server with the new code you install module (odoo-bin -i ...). However, 
    automating this step in a deployment pipeline is difficult as you don't 
    know which module needs to be updated. Always updating the base module 
    seems like an overkill.
    
    Do you know this problem? Have you solved this problem?
    
    I would be glad to hear from you.
    
    Regards,
    
    Janik
    
    Here is a guide to reproduce the issue with https://odoo.build/:
    
    1. Init a new datbase and start the Odoo server: `task start db; task 
    init-db; task start native`
    
    2. Install the contacts module: `task install-module contacts`
    
    3. Stop the Odoo process.
    
    4. Add a new field to the res.partner code: `vi 
    odoo/odoo/addons/base/models/res_partner.py`
    
    ```python
    
    xy = fields.Char()
    
    ```
    
    5. Start the Odoo server: `task start native`
    
    It fails with:
    
    ```
    
    ...
    
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ..."message_bounce", "res_partner"."name" AS "name", "res_partn...
    ```                                                        ^
    
    
    
    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH
    Tel: +41 44 244 7222
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    Lois Rilo Antelo
    ERP Consultant Manager at ForgeFlow S.L.

    by Lois Rilo Antelo - 06:20 - 20 Jun 2024
  • Re: Technical Question: Restart Odoo process after res.partner model change
    module_auto_update

    20 jun. 2024 17:22:17 Janik von Rotz <notifications@odoo-community.org>:

    Hello Odoo contributors,
    
    I am developing, deploying and fixing Odoo for a while and there is one 
    issue I haven't bothered enough to come up with a proper solution or 
    strategy.
    
    The problem is simple: I have an Odoo instance running with a module 
    that extends the res.partner model. The res.partner code of this module 
    is updated with a new field. The Odoo server is restarted and exits with 
    a "column does not exist" error.
    
    The same procedure works for modules that extend other models than 
    res.partner or res.user. As I understand the res.partner (and other) 
    tables are queried when the Odoo process starts. The SQL queries fail, 
    because the model code does not match the database schema.
    
    The solution to the problem seems obvious, before starting the Odoo 
    server with the new code you install module (odoo-bin -i ...). However, 
    automating this step in a deployment pipeline is difficult as you don't 
    know which module needs to be updated. Always updating the base module 
    seems like an overkill.
    
    Do you know this problem? Have you solved this problem?
    
    I would be glad to hear from you.
    
    Regards,
    
    Janik
    
    Here is a guide to reproduce the issue with https://odoo.build/:
    
    1. Init a new datbase and start the Odoo server: `task start db; task 
    init-db; task start native`
    
    2. Install the contacts module: `task install-module contacts`
    
    3. Stop the Odoo process.
    
    4. Add a new field to the res.partner code: `vi 
    odoo/odoo/addons/base/models/res_partner.py`
    
    ```python
    
    xy = fields.Char()
    
    ```
    
    5. Start the Odoo server: `task start native`
    
    It fails with:
    
    ```
    
    ...
    
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ..."message_bounce", "res_partner"."name" AS "name", "res_partn...
    ```                                                        ^
    
    
    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH
    Tel: +41 44 244 7222
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Tom Blauwendraat - 05:40 - 20 Jun 2024
  • Technical Question: Restart Odoo process after res.partner model change
    Hello Odoo contributors,
    
    I am developing, deploying and fixing Odoo for a while and there is one 
    issue I haven't bothered enough to come up with a proper solution or 
    strategy.
    
    The problem is simple: I have an Odoo instance running with a module 
    that extends the res.partner model. The res.partner code of this module 
    is updated with a new field. The Odoo server is restarted and exits with 
    a "column does not exist" error.
    
    The same procedure works for modules that extend other models than 
    res.partner or res.user. As I understand the res.partner (and other) 
    tables are queried when the Odoo process starts. The SQL queries fail, 
    because the model code does not match the database schema.
    
    The solution to the problem seems obvious, before starting the Odoo 
    server with the new code you install module (odoo-bin -i ...). However, 
    automating this step in a deployment pipeline is difficult as you don't 
    know which module needs to be updated. Always updating the base module 
    seems like an overkill.
    
    Do you know this problem? Have you solved this problem?
    
    I would be glad to hear from you.
    
    Regards,
    
    Janik
    
    Here is a guide to reproduce the issue with https://odoo.build/:
    
    1. Init a new datbase and start the Odoo server: `task start db; task 
    init-db; task start native`
    
    2. Install the contacts module: `task install-module contacts`
    
    3. Stop the Odoo process.
    
    4. Add a new field to the res.partner code: `vi 
    odoo/odoo/addons/base/models/res_partner.py`
    
    ```python
    
    xy = fields.Char()
    
    ```
    
    5. Start the Odoo server: `task start native`
    
    It fails with:
    
    ```
    
    ...
    
    psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
    LINE 1: ..."message_bounce", "res_partner"."name" AS "name", "res_partn...
    ```                                                        ^
    
    
    -- 
    We are hiring: https://www.mint-system.ch/jobs
    Send application to: jobs@mint-system.ch
    
    CTO Mint System GmbH
    Tel: +41 44 244 7222
    
    

    by Janik von Rotz - 05:22 - 20 Jun 2024
  • Re: OCA Weblate, why the lack of speed?

    Hi Jakob,

    sorry you are right. I can share your pain today as i was also trying to interact with part of our infrastructure that was equally lacking reliability and peformance. However, i am pretty sure that we will soon (as in volountary soon) have solutions for these problems. In the meantime thank you for your willingsness to help

    Best Frederik

    Am 20.06.24 um 16:03 schrieb Jakob Krabbe:
    Thank you for your reply!
    After a few days with Weblate and 504 Gateway Time-out, I'm now moving 
    on with other tasks. I hope you or maybe Stephané could post a notice on 
    this list when such upgrade has been made!
    
    regards,
    
    // jakob
    
    
    
    Den 2024-06-17 kl. 09:37, skrev Frederik Kramer:
    
    > Hi Jakob,
    
    > 
    
    > afaik, OCA uses weblate because it doesn't just us as much as Transifex 
    
    > charged us. If i am not mistaken we run Weblate ourselfes and if i 
    
    > understood (Stephané Bidoul, who is the master of OCAs hardware 
    
    > architecture) we are about to migrate on a more powerful hardware server 
    
    > (also for that purpose). But Stephané can certainly be more precise on 
    
    > that. So in the best case it should improve somewhen soon :-)
    
    > 
    
    > Best and thanks for the question
    
    > 
    
    > Frederik
    
    > 
    
    > Am 17.06.24 um 09:07 schrieb Jakob Krabbe:
    
    >> Greetings!
    
    >> I've done plenty of translating for Odoo in Sweden. Modules and
    
    >> documentation for Odoo mainly in Transifex but also some for OCA, using
    
    >> Weblate.
    
    >>
    
    >> I like the tool Weblate. Sometimes it's more helpful than Transifex!
    
    >>
    
    >> But I've always wondered why it's so slow. I often get the "500 time
    
    >> out" -error and it's more frequently before lunch than after!
    
    >>
    
    >> Who's in charge? What's the plan, if any...?
    
    >>
    
    >> I assume others has experienced the same. I'm new to this e-mailing list
    
    >> and maybe this has been discussed recently? If so, my apology for
    
    >> highlighting the issue!
    
    >>
    
    >> regards,
    
    >>
    
    >> // jakob
    
    >>
    
    >>
    
    >>
    
    >>
    
    >> -- Med vänlig hälsning / Best regards/ 顺祝商祺, Jakob Krabbe VERTEL 
    
    >> AB | Jakob Krabbe | jakob.krabbe@vertel.se 
    
    >> <mailto:jakob.krabbe@vertel.se> +46 (0)13 99 19 480 | +46 (0) 709 24 
    
    >> 54 75 | vertel.se
    
    >>
    
    >> _______________________________________________
    
    >> Mailing-List: https://odoo-community.org/groups/contributors-15 
    
    >> <https://odoo-community.org/groups/contributors-15>
    
    >> Post to: mailto:contributors@odoo-community.org 
    
    >> <mailto:contributors@odoo-community.org>
    
    >> Unsubscribe: https://odoo-community.org/groups?unsubscribe 
    
    >> <https://odoo-community.org/groups?unsubscribe>
    
    >>
    
    > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 
    
    > 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 
    
    > 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com  <mailto:frederik.kramer@initos.com>
    
    > Internet:www.initos.com  <http://www.initos.com>
    
    > 
    
    > Geschäftsführung:
    
    > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    > 
    
    > Sitz der Gesellschaft: Buchholz i.d.N.
    
    > Amtsgericht Tostedt, HRB 205226
    
    > USt-IdNr.: DE815580155
    
    > Steuer-Nr: 15/200/53247
    
    > 
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 
    
    > <https://odoo-community.org/groups/contributors-15>
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe 
    
    > <https://odoo-community.org/groups?unsubscribe>
    
    > 
    
    
    -- 
    Med vänlig hälsning / Best regards/ 顺祝商祺,
    Jakob Krabbe
    
    VERTEL AB | Jakob Krabbe | jakob.krabbe@vertel.se
    +46 (0)13 99 19 480 | +46 (0) 709 24 54 75 | vertel.se

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    -- 
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
    
    initOS GmbH
    Innungsstraße 7
    21244 Buchholz i.d.N.
    
    Tel:   +49 (0) 4181 13503 12
    Fax:   +49 (0) 4181 13503 10
    Mobil: +49 (0) 179 3901819
    
    Email: frederik.kramer@initos.com
    Internet: www.initos.com
    
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Buchholz i.d.N.
    Amtsgericht Tostedt, HRB 205226
    USt-IdNr.: DE815580155
    Steuer-Nr: 15/200/53247

    by Frederik Kramer - 04:17 - 20 Jun 2024
  • 16.0 translations

    Hi guys,

    We do have a customer which would like to translate a term used in a python method in a odoo module.
    I know translations have changed a lot in 16.0, that and now field translations are stored as jsonb values.

    To give you more context, here's a bit of code https://github.com/odoo/odoo/blob/16.0/addons/l10n_din5008_sale/models/sale.py#L12-L32

    Our customer isn't happy with the german translation of "Salesperson", which is "Vertriebsmitarbeiter", and would like "Kundenberater" instead.

    In the previous versions of odoo, it was possible to create a `l10n_extra` folder, and drop a new translation for the term, and that's it.

    Now it's not possible anymore, and I'm looking for ways of doing it.
    For instance, if some python code is raising an exception with some translated text that you're unhappy with, you cannot change it.

    I noticed there was a few issues on this matter on github.com/odoo/odoo

    I'm guessing that we aren't near close of having a solution from Odoo, and was wondering if there was anything in OCA about this?

    Thanks!

    ---

    Matthieu Méquignon


    by Matthieu Méquignon - 04:04 - 20 Jun 2024
  • Re: OCA Weblate, why the lack of speed?
    
    Thank you for your reply!
    After a few days with Weblate and 504 Gateway Time-out, I'm now moving 
    on with other tasks. I hope you or maybe Stephané could post a notice on 
    this list when such upgrade has been made!
    
    regards,
    
    // jakob
    
    
    
    Den 2024-06-17 kl. 09:37, skrev Frederik Kramer:
    
    > Hi Jakob,
    
    > 
    
    > afaik, OCA uses weblate because it doesn't just us as much as Transifex 
    
    > charged us. If i am not mistaken we run Weblate ourselfes and if i 
    
    > understood (Stephané Bidoul, who is the master of OCAs hardware 
    
    > architecture) we are about to migrate on a more powerful hardware server 
    
    > (also for that purpose). But Stephané can certainly be more precise on 
    
    > that. So in the best case it should improve somewhen soon :-)
    
    > 
    
    > Best and thanks for the question
    
    > 
    
    > Frederik
    
    > 
    
    > Am 17.06.24 um 09:07 schrieb Jakob Krabbe:
    
    >> Greetings!
    
    >> I've done plenty of translating for Odoo in Sweden. Modules and
    
    >> documentation for Odoo mainly in Transifex but also some for OCA, using
    
    >> Weblate.
    
    >>
    
    >> I like the tool Weblate. Sometimes it's more helpful than Transifex!
    
    >>
    
    >> But I've always wondered why it's so slow. I often get the "500 time
    
    >> out" -error and it's more frequently before lunch than after!
    
    >>
    
    >> Who's in charge? What's the plan, if any...?
    
    >>
    
    >> I assume others has experienced the same. I'm new to this e-mailing list
    
    >> and maybe this has been discussed recently? If so, my apology for
    
    >> highlighting the issue!
    
    >>
    
    >> regards,
    
    >>
    
    >> // jakob
    
    >>
    
    >>
    
    >>
    
    >>
    
    >> -- Med vänlig hälsning / Best regards/ 顺祝商祺, Jakob Krabbe VERTEL 
    
    >> AB | Jakob Krabbe | jakob.krabbe@vertel.se 
    
    >> <mailto:jakob.krabbe@vertel.se> +46 (0)13 99 19 480 | +46 (0) 709 24 
    
    >> 54 75 | vertel.se
    
    >>
    
    >> _______________________________________________
    
    >> Mailing-List: https://odoo-community.org/groups/contributors-15 
    
    >> <https://odoo-community.org/groups/contributors-15>
    
    >> Post to: mailto:contributors@odoo-community.org 
    
    >> <mailto:contributors@odoo-community.org>
    
    >> Unsubscribe: https://odoo-community.org/groups?unsubscribe 
    
    >> <https://odoo-community.org/groups?unsubscribe>
    
    >>
    
    > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 
    
    > 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 
    
    > 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com  <mailto:frederik.kramer@initos.com>
    
    > Internet:www.initos.com  <http://www.initos.com>
    
    > 
    
    > Geschäftsführung:
    
    > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    > 
    
    > Sitz der Gesellschaft: Buchholz i.d.N.
    
    > Amtsgericht Tostedt, HRB 205226
    
    > USt-IdNr.: DE815580155
    
    > Steuer-Nr: 15/200/53247
    
    > 
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 
    
    > <https://odoo-community.org/groups/contributors-15>
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe 
    
    > <https://odoo-community.org/groups?unsubscribe>
    
    > 
    
    
    -- 
    Med vänlig hälsning / Best regards/ 顺祝商祺,
    Jakob Krabbe
    
    VERTEL AB | Jakob Krabbe | jakob.krabbe@vertel.se
    +46 (0)13 99 19 480 | +46 (0) 709 24 54 75 | vertel.se

    by Jakob Krabbe - 04:00 - 20 Jun 2024
  • Create New Sale Order from Picking Backorder
    Hello, I need exactly this module 


    but for Odoo version 14. Do we have something similar? 

    Regards,
    Francesco Ballerini

    by Francesco Ballerini - 11:03 - 20 Jun 2024
  • Re: Please share your thoughts on the use of `x_` prefix for custom fields in Odoo
    Now we reach the veterans talk and remembering. Time flies lads !

    My two cents on this topic. I confirm what Daniel and Graeme said. The reason behind was to quickly find back the custom fields and models added by the interface and avoid searching in the code for the field and model definition. 

    Anyway such modifications should be banned for the sake of the project and the mental health 😉

    Regards, 
    Houssine 


    Le mer. 19 juin 2024, 08:08, Graeme Gellatly <notifications@odoo-community.org> a écrit :

    On Wed, Jun 19, 2024 at 5:57 PM Graeme Gellatly <graeme@moahub.nz> wrote:
    Yes but it is still exactly the same case. A model or field that is not part of a module. There is zero technical difference between creating a field via RPC and via UI. Afterall the UI is just sending the same RPC calls to the server. It absolutely does not apply to community developed modules in any way whatsoever, and it is absolutely required for any field created outside of a module (such that it gets ignored rather than removed in certain operations, it is essentially treated as data). And yes it existed in v5, and it was a major feature. This was the times of OpenBravo taking primacy with their dynamic low code DDL java thing, and OpenERP had a precursor to Studio in it. They even had a website openerp.tv dedicated to tutorials on how to do it.

    On Wed, Jun 19, 2024 at 5:41 PM Frederik Kramer <notifications@odoo-community.org> wrote:
    Well, this is not the only instance of that magical x_ I came across this (at least if I remember well) already in times of OpenERP Version 5 or so. Here for instance it again seems to be more related to backend UI changes and some reasoning is also provided by Ray

    https://www.odoo.com/forum/help-1/fixing-a-custom-field-and-database-implications-90794


    Am 18. Juni 2024 23:32:27 MESZ schrieb Graeme Gellatly <notifications@odoo-community.org>:
    I took a quick read and yes it is a misunderstanding of the documentation. If reading a specific section about creating custom models over RPC calls, do not try and apply it to module development in general. All the documentation is correct as is Daniel's statement. Just a misread.

    On Wed, Jun 19, 2024 at 9:19 AM Graeme Gellatly <graeme@moahub.nz> wrote:
    Before Odoo studio, there was another frontend editor, like way back in v5. But it is only for fields created through the UI, not modules. Never modules, it would be a nonsense.  The only time you would use in a module is if it contained dynamic field creation, e.g. like studio, or you have some kind of variable dynamic model like say custom field service worksheets. I think this is simply a misunderstanding of the documentation.

    On Tue, Jun 18, 2024 at 12:16 AM Frederik Kramer <notifications@odoo-community.org> wrote:
    Thanks Pedro, thanks Christian and Francesco for your comments,
    
    i think the first appearance of that magical "x_" was long before Odoo 
    Studio even existed but i do definitely agree that backend UI changes 
    done with Odoo Studio (or earlier through Developer Tools and Plain BE 
    functions) should be avoided in any production grade DB. However, 
    technically forbid to use that "methods" is not all too simple (if the 
    customer pretends to have certain rights on his landscape) or comes from 
    an origin where nobody even told them ;-)
    
    To me it seems (i.e. would be my conclusion) that Odoo S.A. always 
    wanted to have that "x_" prefix and the community mostly ignored it (if 
    i remember well, i have occassionaly seen app store modules that 
    followed this 'requirement').
    
    Now what bothers me most is that Odoo S.A. isn't consistent either on 
    the matter and obviously never forced to comply (would have been easily 
    possible).
    
    So probably we we better follow the "wisdom of the crowd" altogether and 
    continue to ignore that "magic convention".
    
    Best Frederik
    
    Am 17.06.24 um 13:43 schrieb Pedro M. Baeza:
    
    
    
    
    > IMO, that prefix must only apply to fields created through UI / Odoo 
    
    
    
    
    > Studio, not on community modules. And if you have to maintain that DB, 
    
    
    
    
    > I advise you to forbid both Odoo Studio and manual field creation.
    
    
    
    
    >
    
    
    
    
    > Regards.
    
    
    
    
    >
    
    
    
    
    > _______________________________________________
    
    
    
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    
    
    
    > Post to: mailto:contributors@odoo-community.org
    
    
    
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    
    
    
    >
    
    
    
    
    -- 
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
    
    initOS GmbH
    Innungsstraße 7
    21244 Buchholz i.d.N.
    
    Tel:   +49 (0) 4181 13503 12
    Fax:   +49 (0) 4181 13503 10
    Mobil: +49 (0) 179 3901819
    
    Email: frederik.kramer@initos.com
    Internet: www.initos.com
    
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Buchholz i.d.N.
    Amtsgericht Tostedt, HRB 205226
    USt-IdNr.: DE815580155
    Steuer-Nr: 15/200/53247
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    --
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    Innungsstraße 7
    21244 Buchholz i.d.N.
            
    Phone:  +49 4181 13503-12
    Fax:    +49 4181 13503-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

    Sitz der Gesellschaft: Buchholz i.d.N.
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Houssine BAKKALI - 10:00 - 19 Jun 2024
  • Re: Please share your thoughts on the use of `x_` prefix for custom fields in Odoo

    On Wed, Jun 19, 2024 at 5:57 PM Graeme Gellatly <graeme@moahub.nz> wrote:
    Yes but it is still exactly the same case. A model or field that is not part of a module. There is zero technical difference between creating a field via RPC and via UI. Afterall the UI is just sending the same RPC calls to the server. It absolutely does not apply to community developed modules in any way whatsoever, and it is absolutely required for any field created outside of a module (such that it gets ignored rather than removed in certain operations, it is essentially treated as data). And yes it existed in v5, and it was a major feature. This was the times of OpenBravo taking primacy with their dynamic low code DDL java thing, and OpenERP had a precursor to Studio in it. They even had a website openerp.tv dedicated to tutorials on how to do it.

    On Wed, Jun 19, 2024 at 5:41 PM Frederik Kramer <notifications@odoo-community.org> wrote:
    Well, this is not the only instance of that magical x_ I came across this (at least if I remember well) already in times of OpenERP Version 5 or so. Here for instance it again seems to be more related to backend UI changes and some reasoning is also provided by Ray

    https://www.odoo.com/forum/help-1/fixing-a-custom-field-and-database-implications-90794


    Am 18. Juni 2024 23:32:27 MESZ schrieb Graeme Gellatly <notifications@odoo-community.org>:
    I took a quick read and yes it is a misunderstanding of the documentation. If reading a specific section about creating custom models over RPC calls, do not try and apply it to module development in general. All the documentation is correct as is Daniel's statement. Just a misread.

    On Wed, Jun 19, 2024 at 9:19 AM Graeme Gellatly <graeme@moahub.nz> wrote:
    Before Odoo studio, there was another frontend editor, like way back in v5. But it is only for fields created through the UI, not modules. Never modules, it would be a nonsense.  The only time you would use in a module is if it contained dynamic field creation, e.g. like studio, or you have some kind of variable dynamic model like say custom field service worksheets. I think this is simply a misunderstanding of the documentation.

    On Tue, Jun 18, 2024 at 12:16 AM Frederik Kramer <notifications@odoo-community.org> wrote:
    Thanks Pedro, thanks Christian and Francesco for your comments,
    
    i think the first appearance of that magical "x_" was long before Odoo 
    Studio even existed but i do definitely agree that backend UI changes 
    done with Odoo Studio (or earlier through Developer Tools and Plain BE 
    functions) should be avoided in any production grade DB. However, 
    technically forbid to use that "methods" is not all too simple (if the 
    customer pretends to have certain rights on his landscape) or comes from 
    an origin where nobody even told them ;-)
    
    To me it seems (i.e. would be my conclusion) that Odoo S.A. always 
    wanted to have that "x_" prefix and the community mostly ignored it (if 
    i remember well, i have occassionaly seen app store modules that 
    followed this 'requirement').
    
    Now what bothers me most is that Odoo S.A. isn't consistent either on 
    the matter and obviously never forced to comply (would have been easily 
    possible).
    
    So probably we we better follow the "wisdom of the crowd" altogether and 
    continue to ignore that "magic convention".
    
    Best Frederik
    
    Am 17.06.24 um 13:43 schrieb Pedro M. Baeza:
    
    
    
    > IMO, that prefix must only apply to fields created through UI / Odoo 
    
    
    
    > Studio, not on community modules. And if you have to maintain that DB, 
    
    
    
    > I advise you to forbid both Odoo Studio and manual field creation.
    
    
    
    >
    
    
    
    > Regards.
    
    
    
    >
    
    
    
    > _______________________________________________
    
    
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    
    
    > Post to: mailto:contributors@odoo-community.org
    
    
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    
    
    >
    
    
    
    -- 
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
    
    initOS GmbH
    Innungsstraße 7
    21244 Buchholz i.d.N.
    
    Tel:   +49 (0) 4181 13503 12
    Fax:   +49 (0) 4181 13503 10
    Mobil: +49 (0) 179 3901819
    
    Email: frederik.kramer@initos.com
    Internet: www.initos.com
    
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Buchholz i.d.N.
    Amtsgericht Tostedt, HRB 205226
    USt-IdNr.: DE815580155
    Steuer-Nr: 15/200/53247
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    --
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    Innungsstraße 7
    21244 Buchholz i.d.N.
            
    Phone:  +49 4181 13503-12
    Fax:    +49 4181 13503-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

    Sitz der Gesellschaft: Buchholz i.d.N.
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by "Graeme Gellatly" <graeme@moahub.nz> - 08:08 - 19 Jun 2024