Skip to Content

Contributors

  • Re: New Odoo17 translated fields
    Since v16, there's also a method made available by the ORM to update translations without overriding the context:


    On Thu, Feb 1, 2024 at 1:52 PM Johan Van Hirtum <notifications@odoo-community.org> wrote:

    Beautiful ! Thank you very much David -)

     

    With kind regards,

     

    Van Hirtum Johan

     

    Van: David Vidal [mailto:notifications@odoo-community.org]
    Verzonden: donderdag 1 februari 2024 13:08
    Aan: Contributors
    Onderwerp: Re: New Odoo17 translated fields

     

    The ORM does it for you. Simply use the `lang` context:

     

    ```python

    record.with_context(lang='es_ES`).field_name = translated_string

    ```

     

    You can get your active languages with `self.env['res.lang'].get_installed()` and loop over them if you want to do it at once.

     

    El jue, 1 feb 2024 a las 12:52, Johan Van Hirtum (<notifications@odoo-community.org>) escribió:

    Dears,

     

    Knows someone good developer documentation around the new translated fields in Odoo17 ? That there are stored in de database as jsonB field is clear. But I see nowhere how to set de translated terms for a field in a python method ( an on change or depends structure for ex. ). There must normally be a some variables where the translation are stored till the create method creates the model ? But I see nothing there.

    I want to use a python translation package ( deepL, deep-translator ) to give a first translation automatically when the translatable field is typed in the ID. Users can adapt, if they want to, but mostly, these translation are simply good -)

     

    Thanks for helping me out.

     

    With kind regards,

     

     

    Van Hirtum Johan

    _______________________________________________
    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

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


    by Silvio Gregorini - 02:06 - 1 Feb 2024
  • RE: New Odoo17 translated fields

    Beautiful ! Thank you very much David -)

     

    With kind regards,

     

    Van Hirtum Johan

     

    Van: David Vidal [mailto:notifications@odoo-community.org]
    Verzonden: donderdag 1 februari 2024 13:08
    Aan: Contributors
    Onderwerp: Re: New Odoo17 translated fields

     

    The ORM does it for you. Simply use the `lang` context:

     

    ```python

    record.with_context(lang='es_ES`).field_name = translated_string

    ```

     

    You can get your active languages with `self.env['res.lang'].get_installed()` and loop over them if you want to do it at once.

     

    El jue, 1 feb 2024 a las 12:52, Johan Van Hirtum (<notifications@odoo-community.org>) escribió:

    Dears,

     

    Knows someone good developer documentation around the new translated fields in Odoo17 ? That there are stored in de database as jsonB field is clear. But I see nowhere how to set de translated terms for a field in a python method ( an on change or depends structure for ex. ). There must normally be a some variables where the translation are stored till the create method creates the model ? But I see nothing there.

    I want to use a python translation package ( deepL, deep-translator ) to give a first translation automatically when the translatable field is typed in the ID. Users can adapt, if they want to, but mostly, these translation are simply good -)

     

    Thanks for helping me out.

     

    With kind regards,

     

     

    Van Hirtum Johan

    _______________________________________________
    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 johan - 01:50 - 1 Feb 2024
  • Re: OCA/connector-telephony Mantainers/PSC
    +1
    Thanks for stepping up Nicolas.
    I did some contributions there a while ago,  but haven't been active on it.

    /Daniel

    On 30/01/2024 12:46, Simone Orsi wrote:
    Is great to see people stepping up to take over. 
    Thanks! :thumbs-up:



    On Tue, Jan 30, 2024 at 1:22 PM Enric Tobella Alomar <notifications@odoo-community.org> wrote:
    Open a PR on https://github.com/OCA/repo-maintainer-conf adding you the right teams

    El mar, 30 ene 2024 a las 13:17, Pedro M. Baeza (<notifications@odoo-community.org>) escribió:
    OK for me.

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



    --
    Enric Tobella Alomar
    CEO & Founder

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



    --
    Simone Orsi

    Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

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


    --
    DANIEL REIS
    MANAGING PARTNER

    M: +351 919 991 307
    E: dreis@OpenSourceIntegrators.com
    A: Avenida da República 3000, Estoril Office B, 3º Escr.34, 2649-517 Cascais


    by Daniel Reis - 01:21 - 1 Feb 2024
  • Re: New Odoo17 translated fields
    The ORM does it for you. Simply use the `lang` context:

    ```python
    record.with_context(lang='es_ES`).field_name = translated_string
    ```

    You can get your active languages with `self.env['res.lang'].get_installed()` and loop over them if you want to do it at once.

    El jue, 1 feb 2024 a las 12:52, Johan Van Hirtum (<notifications@odoo-community.org>) escribió:

    Dears,

     

    Knows someone good developer documentation around the new translated fields in Odoo17 ? That there are stored in de database as jsonB field is clear. But I see nowhere how to set de translated terms for a field in a python method ( an on change or depends structure for ex. ). There must normally be a some variables where the translation are stored till the create method creates the model ? But I see nothing there.

    I want to use a python translation package ( deepL, deep-translator ) to give a first translation automatically when the translatable field is typed in the ID. Users can adapt, if they want to, but mostly, these translation are simply good -)

     

    Thanks for helping me out.

     

    With kind regards,

     

     

    Van Hirtum Johan

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


    by David Vidal - 01:05 - 1 Feb 2024
  • New Odoo17 translated fields

    Dears,

     

    Knows someone good developer documentation around the new translated fields in Odoo17 ? That there are stored in de database as jsonB field is clear. But I see nowhere how to set de translated terms for a field in a python method ( an on change or depends structure for ex. ). There must normally be a some variables where the translation are stored till the create method creates the model ? But I see nothing there.

    I want to use a python translation package ( deepL, deep-translator ) to give a first translation automatically when the translatable field is typed in the ID. Users can adapt, if they want to, but mostly, these translation are simply good -)

     

    Thanks for helping me out.

     

    With kind regards,

     

     

    Van Hirtum Johan


    by johan - 12:51 - 1 Feb 2024
  • Re: OCA/connector-telephony Mantainers/PSC
    Great, I didn't know about the new repository to manage these things. It seems like a good idea to manage this in a repo. 
    The PR is ready: https://github.com/OCA/repo-maintainer-conf/pull/15

    Thanks!! 

    On Tue, Jan 30, 2024 at 9:47 AM Simone Orsi <notifications@odoo-community.org> wrote:
    Is great to see people stepping up to take over. 
    Thanks! :thumbs-up:



    On Tue, Jan 30, 2024 at 1:22 PM Enric Tobella Alomar <notifications@odoo-community.org> wrote:
    Open a PR on https://github.com/OCA/repo-maintainer-conf adding you the right teams

    El mar, 30 ene 2024 a las 13:17, Pedro M. Baeza (<notifications@odoo-community.org>) escribió:
    OK for me.

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



    --
    Enric Tobella Alomar
    CEO & Founder

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



    --
    Simone Orsi

    Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

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


    by Nicolas Rodriguez Sande - 02:30 - 30 Jan 2024
  • Re: OCA/connector-telephony Mantainers/PSC
    Is great to see people stepping up to take over. 
    Thanks! :thumbs-up:



    On Tue, Jan 30, 2024 at 1:22 PM Enric Tobella Alomar <notifications@odoo-community.org> wrote:
    Open a PR on https://github.com/OCA/repo-maintainer-conf adding you the right teams

    El mar, 30 ene 2024 a las 13:17, Pedro M. Baeza (<notifications@odoo-community.org>) escribió:
    OK for me.

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



    --
    Enric Tobella Alomar
    CEO & Founder

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



    --
    Simone Orsi

    Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

    by Simone Orsi - 01:45 - 30 Jan 2024
  • Re: OCA/connector-telephony Mantainers/PSC
    Open a PR on https://github.com/OCA/repo-maintainer-conf adding you the right teams

    El mar, 30 ene 2024 a las 13:17, Pedro M. Baeza (<notifications@odoo-community.org>) escribió:
    OK for me.

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



    --
    Enric Tobella Alomar
    CEO & Founder


    by Enric Tobella Alomar - 01:21 - 30 Jan 2024
  • Re: OCA/connector-telephony Mantainers/PSC
    OK for me.

    by Pedro M. Baeza - 01:16 - 30 Jan 2024
  • OCA/connector-telephony Mantainers/PSC
    Hello, is there an active maintainer of the OCA/connector-telephony repo? I saw that there are some people trying to migrate modules but no one is active to review/merge them. 

    If there is no active PSC i volunteer as PSC of the repository, since i use these modules in v14.0 and now i need them in v16.0. So I volunteer to be the PSC and bring the repository back to life since it appears to be abandoned.  

    I'm currently PSC of OCA/payroll and the other HR repositories, you can see some of my work there. 

    Hope this week finds you well. 
    Kind regards. 

    by Nicolas Rodriguez Sande - 01:10 - 30 Jan 2024
  • Re: Reducing the size of a database
    Mail message table is typically 50 per cent of database or more. Frankly 6 years is not a lot. In my country fiscal authorities require 7 years, some other legal requirements need 50 years.

    On Wed, 24 Jan 2024, 5:36 am Holger Brunn, <notifications@odoo-community.org> wrote:
    > In my experience a
    
    
    > huge amount of records can be deleted by deleting old chatter
    
    
    > records.
    
    similar experience here, and for that we have
    https://github.com/OCA/server-tools/tree/14.0/autovacuum_message_attachment
    and its migrations to higher versions in the PRs.
    
    You should run the third query from
    https://wiki.postgresql.org/wiki/Disk_Usage
    anyways to first get an impression where the space goes.
    
    
    
    -- 
    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 "Graeme Gellatly" <graeme@moahub.nz> - 09:25 - 23 Jan 2024
  • Re: Reducing the size of a database
    > In my experience a
    
    > huge amount of records can be deleted by deleting old chatter
    
    > records.
    
    similar experience here, and for that we have
    https://github.com/OCA/server-tools/tree/14.0/autovacuum_message_attachment
    and its migrations to higher versions in the PRs.
    
    You should run the third query from
    https://wiki.postgresql.org/wiki/Disk_Usage
    anyways to first get an impression where the space goes.
    
    
    -- 
    Your partner for the hard Odoo problems
    https://hunki-enterprises.com

    by Holger Brunn - 05:35 - 23 Jan 2024
  • Re: Reducing the size of a database

    Hi,


    In my experience a huge amount of records can be deleted by deleting old chatter records.


    Kind regards, Ronald


    On 23-01-2024 15:57, Florian Laporte wrote:

    Dear Victor,

    How large are these databases? Database size usually does not become problematic as a result of too many sale orders or stock movements. You would need an insane amount.
    If this is the case, and you’ve verified that the size is not caused by large blobs/filestore, the only thing you can do is mass-delete records based on some arbitrary parameter like their create_date or write_date. There are many records Odoo won’t let you delete, though. It will ask you to archive them instead, because they are still referenced elsewhere. Archiving will obviously do nothing for database size.

    Sincerely,

    Florian L


    On Tue, 23 Jan 2024 at 15:22, Victor Champonnois <notifications@odoo-community.org> wrote:

    Dear contributors,

    Some of our customers have been using their database for more than 6 years. They want to reduce the size of the database, by archiving/aggregating old data (accounting entries, sales lines, stock movements, etc.). It would also be easier to do exports, pivot tables and so on.

    I see different solutions :

    1. Manually aggregate old data, with a specific method  by type of tables (account move lines, stock picking, sale order lines). For instance, aggregate old accounting entries with annual miscellaneous operations. Of course, we should keep a backup of the old data somewhere.

    2. Mass delete all the old and unused records, such as canceled POs, articles created by mistake. I don't see a way to do this quickly.

    Maybe an alternative solution would be a module that sets a "limit date" that acts as an automatic filter when doing exports, pivots, etc.

    Do you know any tool or procedure that would help with this ?

    Best regards,
    -- 
    Victor Champonnois - Coop IT Easy
    Tel : +32 475 81 01 12

    _______________________________________________
    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 "Ronald Portier" <rportier@therp.nl> - 04:21 - 23 Jan 2024
  • Re: Reducing the size of a database
    I've seen this module:
    
    https://apps.odoo.com/apps/modules/13.0/muk_autovacuum/
    
    Obviously this can't be used on just any models, but for some models I 
    guess such an approach can work.
    
    Another idea I've proposed to a customer once, was to have a moment at 
    end of year where you create an "archive copy instance" for that year, 
    where people can login but not change anything. The code at that point 
    is also frozen and copied with. It's a dirty approach, as you'll after N 
    years be sitting with N archive instances, but there's a chance that at 
    some point they'll start agreeing to delete the oldest instance (as at 
    least here in NL, there's a year limit to which you are obliged to keep 
    financial history). The upside to this approach is that you can 
    aggressively start deleting records from live.
    
    -Tom
    
    
    

    by Tom Blauwendraat - 04:20 - 23 Jan 2024
  • Re: Reducing the size of a database

    Dear Victor,

    How large are these databases? Database size usually does not become problematic as a result of too many sale orders or stock movements. You would need an insane amount.
    If this is the case, and you’ve verified that the size is not caused by large blobs/filestore, the only thing you can do is mass-delete records based on some arbitrary parameter like their create_date or write_date. There are many records Odoo won’t let you delete, though. It will ask you to archive them instead, because they are still referenced elsewhere. Archiving will obviously do nothing for database size.

    Sincerely,

    Florian L


    On Tue, 23 Jan 2024 at 15:22, Victor Champonnois <notifications@odoo-community.org> wrote:

    Dear contributors,

    Some of our customers have been using their database for more than 6 years. They want to reduce the size of the database, by archiving/aggregating old data (accounting entries, sales lines, stock movements, etc.). It would also be easier to do exports, pivot tables and so on.

    I see different solutions :

    1. Manually aggregate old data, with a specific method  by type of tables (account move lines, stock picking, sale order lines). For instance, aggregate old accounting entries with annual miscellaneous operations. Of course, we should keep a backup of the old data somewhere.

    2. Mass delete all the old and unused records, such as canceled POs, articles created by mistake. I don't see a way to do this quickly.

    Maybe an alternative solution would be a module that sets a "limit date" that acts as an automatic filter when doing exports, pivots, etc.

    Do you know any tool or procedure that would help with this ?

    Best regards,
    -- 
    Victor Champonnois - Coop IT Easy
    Tel : +32 475 81 01 12

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


    by florian.laporte - 03:56 - 23 Jan 2024
  • Reducing the size of a database

    Dear contributors,

    Some of our customers have been using their database for more than 6 years. They want to reduce the size of the database, by archiving/aggregating old data (accounting entries, sales lines, stock movements, etc.). It would also be easier to do exports, pivot tables and so on.

    I see different solutions :

    1. Manually aggregate old data, with a specific method  by type of tables (account move lines, stock picking, sale order lines). For instance, aggregate old accounting entries with annual miscellaneous operations. Of course, we should keep a backup of the old data somewhere.

    2. Mass delete all the old and unused records, such as canceled POs, articles created by mistake. I don't see a way to do this quickly.

    Maybe an alternative solution would be a module that sets a "limit date" that acts as an automatic filter when doing exports, pivots, etc.

    Do you know any tool or procedure that would help with this ?

    Best regards,
    -- 
    Victor Champonnois - Coop IT Easy
    Tel : +32 475 81 01 12

    by Victor - 03:21 - 23 Jan 2024
  • Re: Filling in product catalogue by vendors (external parties - i.e. portal users)
    Hello Miroslav,
    
    thank you for the input. This is OCA's mailing list and as such focuses on free OCA's modules or modules by OCA contributors not yet in OCA's repositories. The modules you have mentioned generally (judging by their description) provide a way to setup new supplier records by themselves and then some communication around pricelists/products.
    
    However these have limitations that I am trying to overcome here:
    1) I am stringly against possibility of creating a new contact in the system by just filling in the publicly available form on the website as the Website Vendor Form Registration module does. This poses numerous risks: flooding the system with nonsense, innocent and not so innocent duplication of entries, etc... My solution here is a survey with a module that allows to create a res.partner record from the information collected (by dynamically mapping fields from survey to target model). When the module is matured enough I'll create a PR in OCA repo.
    
    2) The other modules work with already existing products and pricelists. My original question was aimed more towards how to help creating these in a safe way (the same risks as above) and move part of the work to suppliers themselves.
    
    
    But thank you for trying to help here.
    
    Best regards
    
    	Radovan Skolnik
    
    
    On sobota 20. januára 2024 11:21:58 CET Apm Consultancy wrote:
    
    > Hi,
    
    > My 5c suggestion is, before going farer and further here, to look at the
    
    > following existing functionalities, I must admit not exhausted list: - 
    
    > Supplier Relationship Management Bundle Apps [1]  -  Purchase Order Showing
    
    > Vendor PriceList [2]  - Website Vendor Registration Form in Odoo [3]  -
    
    > Vendor Portal for Product PriceLists [4] I hope (believe) that you can
    
    > figure out your first-step working scenario which will satisfy your desire
    
    > not to rely on "external hands" data management. However, because your
    
    > initial more important business requirement looks like to be minimising or
    
    > eliminating the internal workload of the procurement team , still a process
    
    > that is implementing a "horizontal integration" across vendors must be
    
    > architected (designed), which is also possible, but probably not with the
    
    > existing (like above) functionalities. Eventually, that might be the
    
    > second-step scenario which will meet your business functional requirements
    
    > to decrease the internal workload of the procuring people. Another
    
    > e-catalog-based approach is also feasible but that would require adapting
    
    > the purchasing strategy and operations of the company' sourcing process.
    
    > 
    
    > 
    
    > 
    
    > 
    
    > Best regards,
    
    > Miroslav Lorinkov
    
    > (  apmcservice@gmail.com [5]  )
    
    > 
    
    > On Fri, Jan 19, 2024 at 5:12 AM Radovan Skolnik <
    
    > notifications@odoo-community.org [6] > wrote: Hello,
    
    > I am working with a client that works in food supply industry - i.e. they
    
    > purchase groceries and other food stuff and prepare food on large scale. An
    
    > example would be hundreds/thousands portions of bolognese sauce made of
    
    > beef, tomato sauce, ... Now the company is just starting their operations
    
    > and are collecting information about possible suppliers and products
    
    > available. Their idea is something like sending out Rf? (P as proposal
    
    > maybe) let's say for that tomato sauce where the vendors would provide
    
    > information such as: description, origin, packaging, price, ... My
    
    > experience strongly suggests not allowing external parties to be allowed to
    
    > create business records such as products in the system but this is the kind
    
    > of scenario they describe as the desired outcome. I have used a 3rd party
    
    > module which extends the RfQ functionality to fill in the prices by
    
    > suppliers (so effectively changing one attribute in purchase.order.line).
    
    > But in this case the scenario should lead to creation of new
    
    > product.[template|product] and also product.supplierinfo by the suppliers.
    
    > AFAIK Odoo out-of-the-box does not have anything even close to this. Has
    
    > anyone faced similar requirement? Any recommendations on how to tackle this
    
    > one? Any advice is greatly welcome.
    
    > Best regards
    
    > Radovan Skolnik
    
    > 
    
    > 
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 [7]
    
    > Post to: mailto: contributors@odoo-community.org [8]
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe [9]
    
    > 
    
    > 
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 [10]
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe [11]
    
    > 
    
    > 
    
    > 
    
    > [1]
    
    > https://apps.odoo.com/apps/modules/16.0/supplier_relationship_manage_bundle
    
    > / [2]
    
    > https://apps.odoo.com/apps/modules/16.0/vendor_pricelist_purchase_order/
    
    > [3] https://apps.odoo.com/apps/modules/16.0/vendor_registration_form/ [4]
    
    > https://apps.odoo.com/apps/modules/16.0/vendor_pricelist_portal/ [5]
    
    > mailto:apmcservice@gmail.com
    
    > [6] mailto:notifications@odoo-community.org
    
    > [7] https://odoo-community.org/groups/contributors-15
    
    > [8] mailto:contributors@odoo-community.org
    
    > [9] https://odoo-community.org/groups?unsubscribe
    
    > [10] https://odoo-community.org/groups/contributors-15
    
    > [11] https://odoo-community.org/groups?unsubscribe
    
    
    
    
    

    by Radovan Skolnik - 10:56 - 22 Jan 2024
  • Re: OCA 2024 Membership
    Hi Luis,

    You can just send me a photo and I will upload for you.
    Normally it syncs to your Github profile.

    I'll message you from within the system so you can talk to me directly about this.

    Take care,
    Rebecca

    On Fri, 19 Jan 2024 at 13:12, Luis A. Pinzón <notifications@odoo-community.org> wrote:
    Hi Rebecca.
    
    Please, could you tell me how I can update my profile photo? In the 
    details I have no option to do so.
    
    thank you so much
    
    
    Luis Pinzón
    
    
    

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



    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association

    by Rebecca Gellatly - 07:11 - 22 Jan 2024
  • Re: Can we improve our 2024 OCA Membership numbers in the next few days and set a new record?
    I love your enthusiasm Michael.

    Most of the final renewal invoices have gone out today. 
    I'm still waiting on a few of the companies who like a corporate invoice to come back to me with their list of members for the year to invoice.

    In regards to the members list showing - this is refreshed as invoices are reconciled.
    I've requested the latest bank statements, so anyone who has paid by bank transfer in the last couple of weeks won't be showing yet, but should tomorrow once I have been able to reconcile them.

    The paypal payments will reconcile directly and often the Stripe ones but I notice a couple from last week haven't - I have to wait till the end of each month to do the manual Stripe reconciliation.

    If anyone thinks they should have received an invoice and haven't yet please get in touch with me at membership@odoo-community.org and I can look into it or as Michael says, go ahead and buy online!

    To be shown on the member's list you need to have completed this survey: https://odoo-community.org/survey/start/ec93270c-f080-4ef0-821d-f5ec4531f371
    Some people also don't want to be shown on the list and opt out.

    I hope this helps everyone and also that Michael's enthusiasm is contagious amongst our contributors!

    Have a great week everyone.
    Rebecca



    On Mon, 22 Jan 2024 at 02:37, Michel Stroom <notifications@odoo-community.org> wrote:
    Dear OCA Community,

    I apologize for being direct, but I believe we can increase the total number of OCA members in 2024 significantly.

    As of today, only 47 OCA members are listed in the 2024 directory.
    It seems that many 2023 OCA members prefer being served rather than taking the initiative to purchase their memberships online (see my previous email encouraging online membership purchases).

    AND,

    • You don’t need to buy the OCA 2024 membership to ask questions this year.
    • Nor do you need an OCA membership to receive answers from our wonderful community regarding Odoo and the OCA apps.

    BUT,

    If you asked a question in 2023 and received valuable assistance from our community that benefited:

    • your business,
    • the company you work for,
    • or helped your customer,

    Isn’t that reason enough to buy the 2024 OCA Membership?

    Let’s significantly 
    increase our total membership in the next few days and set a new record in total OCA members.


    Have a great day, and don’t forget to purchase the 2024 OCA Membership TODAY – it’s only 50 Euros.

    OCA Membership 2024: https://odoo-community.org/shop/24-msm-2024-oca-member-503809#attr=




    Best regards,

    Michel Stroom

    OCA member 2023 and 2024
    Using Odoo since version 8


    -- 
    Office Everywhere
    e: mstroom@office-everywhere.com





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



    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association

    by Rebecca Gellatly - 07:11 - 22 Jan 2024
  • Workers on odoo.sh

    Hi community,

    I have something that's puzzling me.

    We migrated an Odoo instance from odoo.sh to our server, in multiprocessing mode with workers=8. A thing with multiprocessing mode is that each of these 8 workers has their own cache, so that whenever Odoo is restarted or cache gets otherwise cleared, it takes 8 HTTP calls for all caches to be filled again, so only from the 9th call things can start getting faster. I've always thought that this is a necessary evil in Odoo. Fabien seems to have done some tests with shared cache, but AFAIK these are just tests.

    Now I've checked their previous odoo.sh instance which is configured with 5 workers. Long ago I read "somewhere" (can't find it anymore) that SH workers are not really workers, which intrigued me; at that time I thought they must be threads, or (gunicorn?) WSGI threads, but I didn't pay any more attention to it. But my tests reveal that on their instance, any second RPC call is already quicker, and on shell, I see Odoo is started with workers=0, so in multithreaded mode. I see no sign of gunicorn anywhere.

    In Odoo's documentation however, they explicitly warn against workers=0 because of the GIL:

    https://www.odoo.com/documentation/17.0/administration/install/deploy.html

    What am I looking at here? Did odoo.sh find a magic cure for the GIL, or are they just not following their own advice and preferring the memory frugality and cachiness of workers=0 above possible GIL-induced performance hits ?

    -Tom


    by Tom Blauwendraat - 11:21 - 21 Jan 2024