Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • Prevent accidental emails to external addresses
    Hello,

    A concern came up, about Odoo users accidentally send out email to external email addresses, such as customers or vendors.
    To goal is not the prevent this from happening, such as in a blacklist/whitelist feature, but to avoid that from happening accidentally.

    I'm not sure should looks like.
    One idea could be having a dialog box confirmation before posting a message mentioning an external user.
    Maybe we could external email from chatter messages, and only allow it from a Action menu send email option.

    On the OCA i've only found "mail_restrict_follower_selection" (https://github.com/OCA/social/tree/13.0/mail_restrict_follower_selection).
    But I'm not sure this is the solution I want to go to.
    At least it may not be enough on itself.


    Did some of you faced the same issue?
    Any thoughts, solutions, tips you can share?


    Thanks!

    --
    Daniel Reis
    Managing Director
    M: +351 919991307
    E: DReis@OpenSourceIntegrators.com
    Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal


    by Daniel Reis - 07:31 - 25 Feb 2021

    5 replies 5 replies

  • Convert quantity from an UoM to another one
    I'd like to propose a new module in product-attribute repo to convert from an UoM to another one, I would suggest "base_uom_converter" or "uom_converter".

    This conversion would work in oneway as it requires a scale to use it.

    For instance, as a developer, I'm generating sales orders from business code. I know that the sale is regarding a given distance of something "D", the work force can be translated from a scale where distance "D" would be the scale entry. The expected result "R" would be the amount of time with a given formula:
    R (hours) = scale line fix amount (hours)  + D (meter) * scale line coef ( hours / meter).

    I guess this could be hooked to the existing system while we change the uom on a sale order line but this is not the intent of this module from my point of view, that's why I suggest base_uom_converter !

    Does this exist already ? Does the OCA want to maintain such a module ?
    --
    Pierre Verkest
    06 81 12 25 20
    Github: petrus-v - Twitter: petrusv84 - Linkedin: pierre-verkest
    by Pierre Verkest - 04:01 - 24 Feb 2021

    2 replies 2 replies

    • Re: Convert quantity from an UoM to another one
      Thanks for your insight, I think this is noticeably different 🤔

      Le mer. 24 févr. 2021 à 16:37, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
      Check product_secondary_unit and the rest of the family.

      Regards.

      El mié., 24 feb. 2021 16:02, Pierre Verkest <pierreverkest84@gmail.com> escribió:
      I'd like to propose a new module in product-attribute repo to convert from an UoM to another one, I would suggest "base_uom_converter" or "uom_converter".

      This conversion would work in oneway as it requires a scale to use it.

      For instance, as a developer, I'm generating sales orders from business code. I know that the sale is regarding a given distance of something "D", the work force can be translated from a scale where distance "D" would be the scale entry. The expected result "R" would be the amount of time with a given formula:
      R (hours) = scale line fix amount (hours)  + D (meter) * scale line coef ( hours / meter).

      I guess this could be hooked to the existing system while we change the uom on a sale order line but this is not the intent of this module from my point of view, that's why I suggest base_uom_converter !

      Does this exist already ? Does the OCA want to maintain such a module ?
      --
      Pierre Verkest
      06 81 12 25 20
      Github: petrus-v - Twitter: petrusv84 - Linkedin: pierre-verkest

      _______________________________________________
      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



      --
      Pierre
      by Pierre Verkest - 05:46 - 24 Feb 2021
    • Re: Convert quantity from an UoM to another one
      Check product_secondary_unit and the rest of the family.

      Regards.

      El mié., 24 feb. 2021 16:02, Pierre Verkest <pierreverkest84@gmail.com> escribió:
      I'd like to propose a new module in product-attribute repo to convert from an UoM to another one, I would suggest "base_uom_converter" or "uom_converter".

      This conversion would work in oneway as it requires a scale to use it.

      For instance, as a developer, I'm generating sales orders from business code. I know that the sale is regarding a given distance of something "D", the work force can be translated from a scale where distance "D" would be the scale entry. The expected result "R" would be the amount of time with a given formula:
      R (hours) = scale line fix amount (hours)  + D (meter) * scale line coef ( hours / meter).

      I guess this could be hooked to the existing system while we change the uom on a sale order line but this is not the intent of this module from my point of view, that's why I suggest base_uom_converter !

      Does this exist already ? Does the OCA want to maintain such a module ?
      --
      Pierre Verkest
      06 81 12 25 20
      Github: petrus-v - Twitter: petrusv84 - Linkedin: pierre-verkest

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

      by Pedro M. Baeza - 04:36 - 24 Feb 2021
  • Issue with runbot
    Dear friends,
     
    I have checked that sometimes, when accessing runbot, we are redirected to runbot main site and we are unable to access the runbot machine. After a little investigation, it seems related to runbot1-3 as the main problem. It seems like a redirect is defined somewhere (maybe on nginx?).
     
    I don't know if this happens to everyone.
     
    Kind regards,
     
    Enric Tobella Alomar
    etobella@creublanca.es
     
    Centros Médicos Creu Blanca
    Tel: 902 202 230
     
    Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
    pueden contener información reservada y/o confidencial, destinada exclusivamente
    para el uso del destinatario o la persona responsable de entregarlo al mismo,
    estando su uso no autorizado prohibido legalmente.
    Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
    salvo ratificación escrita por ambas partes. En caso de su recepción por error,
    rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
    o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
    a su eliminación.




    Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
    pueden contener información reservada y/o confidencial, destinada exclusivamente
    para el uso del destinatario o la persona responsable de entregarlo al mismo,
    estando su uso no autorizado prohibido legalmente.
    Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
    salvo ratificación escrita por ambas partes. En caso de su recepción por error,
    rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
    o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
    a su eliminación.
    by Enric Tobella Alomar - 11:46 - 22 Feb 2021

    6 replies 6 replies

    • Re: Issue with runbot 
      Hello Jay,

If you're referring to the 14.0 migration PR, nothing wrong on runbot. 
The PR is red on Travis because one view cannot be loaded -> fix this 
and runbot should get you a build. See 
https://github.com/OCA/vertical-hotel/pull/135#issuecomment-786464703

Or are you referring to something else ?

Alexandre

On 26/02/2021 07:52, Jay Vora wrote:

> Can you help with runbot on OCA/vertical-hotel ?

> Thanks.

> 

> On Thu, Feb 25, 2021 at 6:47 PM Alexandre Fayolle 

> <alexandre.fayolle@camptocamp.com 

> <mailto:alexandre.fayolle@camptocamp.com>> wrote:

> 

>     I forgot, this should be fixed since monday evening; please drop me an

>     email if it is not.

> 

>     Alexandre

> 

>     On 22/02/2021 15:51, Alexandre Fayolle wrote:

>     > Hello Enric,

>     > 

>     > Possibly a nginx issue. I'll check this tonight.

>     > 

>     > Alexandre

>     > 

>     > On 22/02/2021 11:47, Enric Tobella Alomar wrote:

>     >> Dear friends,

>     >> I have checked that sometimes, when accessing runbot, we are 

>     >> redirected to runbot main site and we are unable to access the runbot 

>     >> machine. After a little investigation, it seems related to runbot1-3 

>     >> as the main problem. It seems like a redirect is defined somewhere 

>     >> (maybe on nginx?).

>     >> I don't know if this happens to everyone.

>     >> Kind regards,

>     >> Enric Tobella Alomar

>     >> etobella@creublanca.es <mailto:etobella@creublanca.es>

>     >> Centros Médicos Creu Blanca

>     >> Tel: 902 202 230
 
>     >> Tanto este mensaje como los documentos que, en su caso, lleve como 
>     >> anexos,
>     >> pueden contener información reservada y/o confidencial, destinada 
>     >> exclusivamente
>     >> para el uso del destinatario o la persona responsable de entregarlo al 
>     >> mismo,
>     >> estando su uso no autorizado prohibido legalmente.
>     >> Su contenido no constituye un compromiso para Creu Blanca (la empresa 
>     >> remitente)
>     >> salvo ratificación escrita por ambas partes. En caso de su recepción 
>     >> por error,
>     >> rogamos nos lo comunique por igual vía, se abstenga de realizar copias 
>     >> del mensaje
>     >> o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda 
>     >> en su defecto,
>     >> a su eliminación.
>     >>
>     >>
>     >>
>     >>
>     >> Tanto este mensaje como los documentos que, en su caso, lleve como 
>     >> anexos,
>     >> pueden contener información reservada y/o confidencial, destinada 
>     >> exclusivamente
>     >> para el uso del destinatario o la persona responsable de entregarlo al 
>     >> mismo,
>     >> estando su uso no autorizado prohibido legalmente.
>     >> Su contenido no constituye un compromiso para Creu Blanca (la empresa 
>     >> remitente)
>     >> salvo ratificación escrita por ambas partes. En caso de su recepción 
>     >> por error,
>     >> rogamos nos lo comunique por igual vía, se abstenga de realizar copias 
>     >> del mensaje
>     >> o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda 
>     >> en su defecto,
>     >> a su eliminación.
>     >>
>     >> _______________________________________________
>     >> Mailing-List: https://odoo-community.org/groups/contributors-15
>     <https://odoo-community.org/groups/contributors-15>
>     >> <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>
>     >> <https://odoo-community.org/groups?unsubscribe
>     <https://odoo-community.org/groups?unsubscribe>>
>     >>
>     > 
>     > 
> 
> 
>     -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20
>     30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le
>     Bourget-du-Lac France http://www.camptocamp.com
>     <http://www.camptocamp.com>
> 
>     _______________________________________________
>     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>
> 
> 
> 
> -- 
> SerpentCS Modules on Odoo AppStore 
> <https://www.odoo.com/apps/modules/browse?author=Serpent Consulting 
> Services Pvt. Ltd.>
> 
> The Splendid journey of 8 years 
> <https://www.youtube.com/watch?v=rue4vGQusbI>
> 
> Technology Services @ www.serpentcs.com <http://www.serpentcs.com/>
> Business Solutions @ www.serpentcs.in <http://www.serpentcs.in/>
> Enterprise Mobile Apps @ www.odooonline.com <http://www.odooonline.com/>
> Quality Assurance @ www.odooqa.com <http://www.odooqa.com/>
> SAP Hana @ www.prozone-tech.com <http://www.prozone-tech.com/>
> Portal & DMS @ www.alfray.in <http://www.alfray.in/>
> 
> 
> 
> Regards,
> ----------------------------------------------------------------------------------------------------------------------------
> <https://pbs.twimg.com/profile_images/472402041336119296/H1HdN-ST_400x400.jpeg>
> 
> 	
> Jay Vora
> Managing Director
> 
> 
> <http://in.linkedin.com/in/jaynvora>
> 
> 		
> Direct: +91-9879354457
> Office: +91-9033472982
> Skype: jaynvora
> Twitter : _jaynvora_
> 
> 	
> 
> -------------------------------------------------------------------------------------------------
> Visit our website : http://www.serpentcs.com <http://www.serpentcs.com>
> 	
> 
> _______________________________________________
> 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>
> 
-- 
Alexandre Fayolle
Senior Software Engineer
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
      by Alexandre Fayolle - 08:25 - 26 Feb 2021
    • Re: Issue with runbot
      Can you help with runbot on OCA/vertical-hotel ?
      Thanks.

      On Thu, Feb 25, 2021 at 6:47 PM Alexandre Fayolle <alexandre.fayolle@camptocamp.com> wrote:
      I forgot, this should be fixed since monday evening; please drop me an 
email if it is not.

Alexandre

On 22/02/2021 15:51, Alexandre Fayolle wrote:


> Hello Enric,


> 


> Possibly a nginx issue. I'll check this tonight.


> 


> Alexandre


> 


> On 22/02/2021 11:47, Enric Tobella Alomar wrote:


>> Dear friends,


>> I have checked that sometimes, when accessing runbot, we are 


>> redirected to runbot main site and we are unable to access the runbot 


>> machine. After a little investigation, it seems related to runbot1-3 


>> as the main problem. It seems like a redirect is defined somewhere 


>> (maybe on nginx?).


>> I don't know if this happens to everyone.


>> Kind regards,


>> Enric Tobella Alomar


>> etobella@creublanca.es


>> Centros Médicos Creu Blanca


>> Tel: 902 202 230


>> Tanto este mensaje como los documentos que, en su caso, lleve como 


>> anexos,


>> pueden contener información reservada y/o confidencial, destinada 


>> exclusivamente


>> para el uso del destinatario o la persona responsable de entregarlo al 


>> mismo,


>> estando su uso no autorizado prohibido legalmente.


>> Su contenido no constituye un compromiso para Creu Blanca (la empresa 


>> remitente)


>> salvo ratificación escrita por ambas partes. En caso de su recepción 


>> por error,


>> rogamos nos lo comunique por igual vía, se abstenga de realizar copias 


>> del mensaje


>> o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda 


>> en su defecto,


>> a su eliminación.


>>


>>


>>


>>


>> Tanto este mensaje como los documentos que, en su caso, lleve como 


>> anexos,


>> pueden contener información reservada y/o confidencial, destinada 


>> exclusivamente


>> para el uso del destinatario o la persona responsable de entregarlo al 


>> mismo,


>> estando su uso no autorizado prohibido legalmente.


>> Su contenido no constituye un compromiso para Creu Blanca (la empresa 


>> remitente)


>> salvo ratificación escrita por ambas partes. En caso de su recepción 


>> por error,


>> rogamos nos lo comunique por igual vía, se abstenga de realizar copias 


>> del mensaje


>> o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda 


>> en su defecto,


>> a su eliminación.


>>


>> _______________________________________________


>> 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>


>>


> 


> 




-- 
Alexandre Fayolle
Senior Software Engineer
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com

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



      --

      Technology Services @ www.serpentcs.com
      Business Solutions @ www.serpentcs.in
      Enterprise Mobile Apps @ www.odooonline.com 
      Quality Assurance @ www.odooqa.com
      Portal & DMS @ www.alfray.in



      Regards,
      ----------------------------------------------------------------------------------------------------------------------------
      Jay Vora
      Managing Director


      		 
      Direct: +91-9879354457
      Office: +91-9033472982
      Skype: jaynvora
      Twitter : jaynvora
       
         
      -------------------------------------------------------------------------------------------------
      Visit our website : http://www.serpentcs.com
       
      by Jay Vora - 07:51 - 26 Feb 2021
    • Re: Issue with runbot 
      I forgot, this should be fixed since monday evening; please drop me an 
email if it is not.

Alexandre

On 22/02/2021 15:51, Alexandre Fayolle wrote:

> Hello Enric,

> 

> Possibly a nginx issue. I'll check this tonight.

> 

> Alexandre

> 

> On 22/02/2021 11:47, Enric Tobella Alomar wrote:

>> Dear friends,

>> I have checked that sometimes, when accessing runbot, we are 

>> redirected to runbot main site and we are unable to access the runbot 

>> machine. After a little investigation, it seems related to runbot1-3 

>> as the main problem. It seems like a redirect is defined somewhere 

>> (maybe on nginx?).

>> I don't know if this happens to everyone.

>> Kind regards,

>> Enric Tobella Alomar

>> etobella@creublanca.es

>> Centros Médicos Creu Blanca

>> Tel: 902 202 230

>> Tanto este mensaje como los documentos que, en su caso, lleve como 

>> anexos,

>> pueden contener información reservada y/o confidencial, destinada 

>> exclusivamente

>> para el uso del destinatario o la persona responsable de entregarlo al 

>> mismo,

>> estando su uso no autorizado prohibido legalmente.

>> Su contenido no constituye un compromiso para Creu Blanca (la empresa 

>> remitente)

>> salvo ratificación escrita por ambas partes. En caso de su recepción 

>> por error,

>> rogamos nos lo comunique por igual vía, se abstenga de realizar copias 

>> del mensaje

>> o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda 

>> en su defecto,

>> a su eliminación.

>>

>>

>>

>>

>> Tanto este mensaje como los documentos que, en su caso, lleve como 

>> anexos,

>> pueden contener información reservada y/o confidencial, destinada 

>> exclusivamente

>> para el uso del destinatario o la persona responsable de entregarlo al 

>> mismo,

>> estando su uso no autorizado prohibido legalmente.

>> Su contenido no constituye un compromiso para Creu Blanca (la empresa 

>> remitente)

>> salvo ratificación escrita por ambas partes. En caso de su recepción 

>> por error,

>> rogamos nos lo comunique por igual vía, se abstenga de realizar copias 

>> del mensaje

>> o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda 

>> en su defecto,

>> a su eliminación.

>>

>> _______________________________________________

>> 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>

>>

> 

> 



-- 
Alexandre Fayolle
Senior Software Engineer
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
      by Alexandre Fayolle - 02:16 - 25 Feb 2021
    • Re: Issue with runbot
      Hi,
      this sometimes has happened to me too, usually opening the runbot instance in a new incognito window fixes it.
      I think it is caused by many runbot windows sharing the same browser window, and some session info may overlap.

      On Mon, 22 Feb 2021 at 11:47, Enric Tobella Alomar <etobella@creublanca.es> wrote:
      Dear friends,
       
      I have checked that sometimes, when accessing runbot, we are redirected to runbot main site and we are unable to access the runbot machine. After a little investigation, it seems related to runbot1-3 as the main problem. It seems like a redirect is defined somewhere (maybe on nginx?).
       
      I don't know if this happens to everyone.
       
      Kind regards,
       
      Enric Tobella Alomar
       
      Centros Médicos Creu Blanca
      Tel: 902 202 230
       
      Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
      pueden contener información reservada y/o confidencial, destinada exclusivamente
      para el uso del destinatario o la persona responsable de entregarlo al mismo,
      estando su uso no autorizado prohibido legalmente.
      Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
      salvo ratificación escrita por ambas partes. En caso de su recepción por error,
      rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
      o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
      a su eliminación.




      Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
      pueden contener información reservada y/o confidencial, destinada exclusivamente
      para el uso del destinatario o la persona responsable de entregarlo al mismo,
      estando su uso no autorizado prohibido legalmente.
      Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
      salvo ratificación escrita por ambas partes. En caso de su recepción por error,
      rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
      o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
      a su eliminación.

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

      by Simone Rubino - 04:36 - 22 Feb 2021
    • Re: Issue with runbot 
      Hello Enric,

Possibly a nginx issue. I'll check this tonight.

Alexandre

On 22/02/2021 11:47, Enric Tobella Alomar wrote:

> Dear friends,

> I have checked that sometimes, when accessing runbot, we are redirected 

> to runbot main site and we are unable to access the runbot machine. 

> After a little investigation, it seems related to runbot1-3 as the main 

> problem. It seems like a redirect is defined somewhere (maybe on nginx?).

> I don't know if this happens to everyone.

> Kind regards,

> Enric Tobella Alomar

> etobella@creublanca.es

> Centros Médicos Creu Blanca

> Tel: 902 202 230

> Tanto este mensaje como los documentos que, en su caso, lleve como anexos,

> pueden contener información reservada y/o confidencial, destinada 

> exclusivamente

> para el uso del destinatario o la persona responsable de entregarlo al 

> mismo,

> estando su uso no autorizado prohibido legalmente.

> Su contenido no constituye un compromiso para Creu Blanca (la empresa 

> remitente)

> salvo ratificación escrita por ambas partes. En caso de su recepción por 

> error,

> rogamos nos lo comunique por igual vía, se abstenga de realizar copias 

> del mensaje

> o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda 

> en su defecto,

> a su eliminación.

> 

> 

> 

> 

> Tanto este mensaje como los documentos que, en su caso, lleve como anexos,

> pueden contener información reservada y/o confidencial, destinada 

> exclusivamente

> para el uso del destinatario o la persona responsable de entregarlo al 

> mismo,

> estando su uso no autorizado prohibido legalmente.

> Su contenido no constituye un compromiso para Creu Blanca (la empresa 

> remitente)

> salvo ratificación escrita por ambas partes. En caso de su recepción por 

> error,

> rogamos nos lo comunique por igual vía, se abstenga de realizar copias 

> del mensaje

> o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda 

> en su defecto,

> a su eliminación.

> 

> _______________________________________________

> 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>

> 



-- 
Alexandre Fayolle
Senior Software Engineer
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
      by Alexandre Fayolle - 03:56 - 22 Feb 2021

  • Migrating content from Wordpress to Odoo
    Hi

    I'm faced with the task of moving a website from Wordpress to Odoo. I have a backup of the old site, is there any way to move the pages from the Wordpress site to Odoo? And mass upload of the images from the old site?

    I've experimented with parsing and processing the backup file, so I have some of the content on my computer, but it would be nice to be able to mass upload it to Odoo, so the webmaster can work on the formatting of the pages.



    Torvald Baade Bringsvor
    Bringsvor Consulting AS - Developer, consultant, allrounder

    Tel (+47) 4548 2848
    by Torvald Bringsvor - 03:30 - 21 Feb 2021

    12 replies 12 replies

    • Re: Password manager within Odoo 
      Thank you very much for the feedback. I'll go with this suggestion 
because password_security might be useful in the future. 
https://github.com/OCA/server-auth/pull/254

Am 23.02.21 um 13:37 schrieb Pedro M. Baeza (Tecnativa):

> Maybe server-auth?

>

> Regards.

>

> _______________________________________________

> 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>

>

-- 
Mit freundlichen Grüßen

Florian Kantelberg
Softwareentwickler

initOS GmbH
An der Eisenbahn 1
21224 Rosengarten

Tel.: +49 (0) 4105 5615644
Fax: +49 (0) 4105 5615610

Email: florian.kantelberg@initos.com
Internet: http://www.initos.com

Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht: Tostedt, HRB 205226
USt-IdNr: DE 815580155
Steuer-Nr: 15/200/53247
      by Florian Kantelberg - 02:16 - 12 Mar 2021
    • Re: Migrating content from Wordpress to Odoo
      I have used the migration_wordpress module in conjunction with a script I made that fetched images and pages from an Wordpress export file and fed it to the migration_wordpress module via the Odoorpc module. Kind of works, at least for the images.

      -Torvald


      tir. 23. feb. 2021 kl. 17:02 skrev Tom <tom@sunflowerweb.nl>:
      I dont have experience with it but i'd say that you could upload the images as "ir.attachment" object and then modify the URLs in the pages to point to it

      Unless odoo website module has another/better model for storing images in, im not sure about that sorry

      Feb 23, 2021 09:37:00 Sergio Corato <sergiocorato@gmail.com>:

      The modules manage the images, sorry but I don't remember how it works
      Sergio Corato


      Il giorno mar 23 feb 2021 alle ore 08:56 Torvald Baade Bringsvor <torvald@bringsvor.com> ha scritto:
      Might be that I do that actually...

      How about the images, can I upload them in a similar object?



      Torvald Baade Bringsvor
      Bringsvor Consulting AS - Developer, consultant, allrounder

      Tel (+47) 4548 2848


      søn. 21. feb. 2021 kl. 16:37 skrev Tom <tom@sunflowerweb.nl>:
      You can write an odoorpc script to loop the content and create pages on the remote odoo for it, or if it is a lot of pages, you can try uploading the content to the odoo server first, and writing a "click-odoo" script instead, which will be a bit faster.

      In both cases you'd need to do "create" actions on the "website.page" object.

      Another way would be to get the content into CSV format and then trying to import it through the Odoo UI.

      Feb 21, 2021 15:31:56 Torvald Baade Bringsvor <torvald@bringsvor.com>:

      Hi

      I'm faced with the task of moving a website from Wordpress to Odoo. I have a backup of the old site, is there any way to move the pages from the Wordpress site to Odoo? And mass upload of the images from the old site?

      I've experimented with parsing and processing the backup file, so I have some of the content on my computer, but it would be nice to be able to mass upload it to Odoo, so the webmaster can work on the formatting of the pages.



      Torvald Baade Bringsvor
      Bringsvor Consulting AS - Developer, consultant, allrounder

      Tel (+47) 4548 2848

      _______________________________________________
      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

      _______________________________________________
      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 Torvald Bringsvor - 11:56 - 2 Mar 2021
    • Re: Password manager within Odoo
      Dear Florian, It seems like great and useful modules :) 


      On Tue, Feb 23, 2021 at 7:22 PM Florian Kantelberg <florian.kantelberg@initos.com> wrote:
      Hello everyone,

I want to share my password manager vault with the community. You can 
find the current v14 Odoo modules under https://github.com/initOS/vault 
I'm not sure which OCA repository would be the best target for it or if 
you would create a new repository because it's in the current state a 
standalone application. The main features/focus of the project until now:

- Secrets are stored with an e2ee. The encryption and decryption happens 
in the browser of the user and not even the server can see the secrets.

- The private keys are stored encrypted in the Odoo database to allow 
cross device access.

- Import from various formats. Currently a custom format and mostly 
keepass databases are supported. The export to the custom format is also 
implemented.

- Internal/external users can share secrets with internal users 
(vault.inbox)

- Internal users can share a secret with an external user using an url 
and a pin. (vault.share) This is done by the extra module vault_share. 
Because the encryption of the secrets is weakened to gain some comfort I 
had to exclude it from the main module.

Suggestions, feedback and tests are more than welcome.

Best regards,

Florian



-- 
Mit freundlichen Grüßen

Florian Kantelberg
Softwareentwickler

initOS GmbH
An der Eisenbahn 1
21224 Rosengarten

Tel.: +49 (0) 4105 5615644
Fax: +49 (0) 4105 5615610

Email: florian.kantelberg@initos.com
Internet: http://www.initos.com

Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht: Tostedt, HRB 205226
USt-IdNr: DE 815580155
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

      by Jean-Charles Drubay - 02:45 - 24 Feb 2021
    • Re: Migrating content from Wordpress to Odoo
      I dont have experience with it but i'd say that you could upload the images as "ir.attachment" object and then modify the URLs in the pages to point to it

      Unless odoo website module has another/better model for storing images in, im not sure about that sorry

      Feb 23, 2021 09:37:00 Sergio Corato <sergiocorato@gmail.com>:

      The modules manage the images, sorry but I don't remember how it works
      Sergio Corato


      Il giorno mar 23 feb 2021 alle ore 08:56 Torvald Baade Bringsvor <torvald@bringsvor.com> ha scritto:
      Might be that I do that actually...

      How about the images, can I upload them in a similar object?



      Torvald Baade Bringsvor
      Bringsvor Consulting AS - Developer, consultant, allrounder

      Tel (+47) 4548 2848


      søn. 21. feb. 2021 kl. 16:37 skrev Tom <tom@sunflowerweb.nl>:
      You can write an odoorpc script to loop the content and create pages on the remote odoo for it, or if it is a lot of pages, you can try uploading the content to the odoo server first, and writing a "click-odoo" script instead, which will be a bit faster.

      In both cases you'd need to do "create" actions on the "website.page" object.

      Another way would be to get the content into CSV format and then trying to import it through the Odoo UI.

      Feb 21, 2021 15:31:56 Torvald Baade Bringsvor <torvald@bringsvor.com>:

      Hi

      I'm faced with the task of moving a website from Wordpress to Odoo. I have a backup of the old site, is there any way to move the pages from the Wordpress site to Odoo? And mass upload of the images from the old site?

      I've experimented with parsing and processing the backup file, so I have some of the content on my computer, but it would be nice to be able to mass upload it to Odoo, so the webmaster can work on the formatting of the pages.



      Torvald Baade Bringsvor
      Bringsvor Consulting AS - Developer, consultant, allrounder

      Tel (+47) 4548 2848

      _______________________________________________
      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

      _______________________________________________
      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:01 - 23 Feb 2021
    • Re: Password manager within Odoo
      Maybe server-auth?

      Regards.
      by Pedro M. Baeza - 01:36 - 23 Feb 2021

  • Odoo shared filesystem/sync

    Dear OCO community,

    I did a weekend project a while back creating a file system for Odoo. Basically if allows you to attach a directory/file to and odoo object.

    The advantage is that you can very much like with the old FTP file sharing infrastructure attach files to say invoices, order by simply saving them to the appropriate directory.

    The difference is that this is a file system on linux so no uploading and it therefore works with everything (email apps, scanning aps etc).

    It is alpha quality and slow but can easily converted into a sync app and the filesystem speed can very easily be increased.

    I will gladly contribute this to OCA base if there are interest. If not just an interesting idea consider.

    Regards

    Jacobus

    --
    Email Signature
    Logo
    Jacobus Erasmus | Director
    a: IvyWeb (Pty) Ltd | 23 Rayner Avenue, Kilnerpark, Pretoria, 0186 | South Africa
    e: jacobus@ivyweb.co.za | w: www.ivyweb.co.za
    m: +27 84 251 6888 | p: +27 84 251 6888
    by Jacobus Erasmus - 06:30 - 18 Feb 2021

    1 attachments 1 attachments

    REG_REGISTRATION_NOTICE_210125437.pdf

    2 replies 2 replies

  • RFC management system - manage partner contacts
    Hi all,
    following a discussion started on my PR https://github.com/OCA/management-system/pull/286, I desire to receive some opinion on the best way to manage additional contacts on partner connected to management system.
    My initial proposal was to do a new module mgmtsystem_nonconformity_partner because I need that contact for quality.
    Enric suggest to add the contact to the base mgmtsystem_system module.
    Another option is to create a module for each system like mgmtsystem_quality, mgmtsystem_safety and so on. 
    Then we think that may be better to have a dedicated module for all possible system-specific contact, ie mgmtsystem_partner to use for adding system-specific contacts.
    What do you think?

    Stefano Consolaro
    www.mymage.it
    by Stefano Consolaro - 11:26 - 12 Feb 2021

    1 replies 1 replies

    • Re: RFC management system - manage partner contacts
      Hello Stefano,

      Thank you for pushing the Management System project further.

      I can't get enough context from wither you message nor the liked PR.
      So I'm not sure what problem is being solved here.

      I suggest opening an "[RFC]" issue on the repo, to publish a requirements and proposed design, and gather feedback.
      I would be happy to join.

      As an advice, I find useful to write in this upfront RFC the README sections of the future module: tittle summary subtitle, description, configuration usage.
      Doing so forces you to structure the message, and saves you time later, when finalizing the modules docs.

      Thank you
      Daniel

      On 12/02/2021 10:27, Stefano Consolaro wrote:
      Hi all,
      following a discussion started on my PR https://github.com/OCA/management-system/pull/286, I desire to receive some opinion on the best way to manage additional contacts on partner connected to management system.
      My initial proposal was to do a new module mgmtsystem_nonconformity_partner because I need that contact for quality.
      Enric suggest to add the contact to the base mgmtsystem_system module.
      Another option is to create a module for each system like mgmtsystem_quality, mgmtsystem_safety and so on. 
      Then we think that may be better to have a dedicated module for all possible system-specific contact, ie mgmtsystem_partner to use for adding system-specific contacts.
      What do you think?

      Stefano Consolaro

      _______________________________________________
      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 Director
      M: +351 919991307
      E: DReis@OpenSourceIntegrators.com
      Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal


      by Daniel Reis - 11:46 - 12 Feb 2021
  • Supplier discount on all products supplied 
    Hello,

we purchase from multiple suppliers. From each one we have a pricelist where 
list prices for customers are listed. Then there is discount we have for 
current year - it changes each year. That defines our price for purchase from 
the supplier.
So I am looking for something that would allow just to change the supplier's 
discount for current year and all the purchase prices would be recalculated.

I guess this should exist but cannot find anywhere. Am I missing something? 
Thank you

Best regards

	Radovan
    by Radovan Skolnik - 04:16 - 11 Feb 2021

    2 replies 2 replies

  • requirements.txt: Repository Level vs Module Level
    Hi all,

    As i see, usually in OCA repositories "requirements.txt" file with pip dependencies is located in the root of the repository and contains a list of all python dependencies for all addons in the repository. This way it works fine, when we clone full repository, and install all dependencies for all modules there, thus when user will try to install new module on DB, 99% that all python dependencies will be satisfied.

    But, let's take for example repository partner-contact repository for Odoo 12.0 and let's try to add the module 'partner_email_check' to odoo server. For this task, i will use [odoo-helper-scripts](https://github.com/katyukha/odoo-helper-scripts) that can automatically resolve repository dependencies (including those specified by oca_dependencies.txt). So, at first i would try to fetch (clone) repository partner-contact, and in this case system will automatically fetch 42 OCA repositories following 'oca_requirements.txt', and also it will try to install python dependencies mentioned in requirements.txt. It is good for development. But installation this way on prod, may lead to a lot of unneeded modules, that polutes system with strange dependencies that are in some cases may be not installable (for example because of system dependencies).

    To solve this reason, we started to use 'assembly' approach, that assumes that we have to create separate git repository with only addons needed on server. But in this case, if assembly repo created automatically, there is no way to get python requirements for module, if it is not specified in module directory. Looking for python dependencies in manifest is also not good, because there are python packages exists, that has different name for package and python module inside package.

    So, may be it have sense to place requirements.txt inside module directory? Thus module's requirements will be always delivered with module, that will make easier installation of module. Also, i think this way, it will be much easier to generate setup.py files for modules, that will contain info about module's python dependencies.

    Possible drawbacks may be in case, when different versions of python dep will be specified in different modules. But same is applicable for repositories.

    What do you think about this?

    With regards,
    Dmytro Katyukha
    by dmytro.katyukha - 10:56 - 11 Feb 2021

    4 replies 4 replies

    • Re: requirements.txt: Repository Level vs Module Level
      I think that the number of extra external dependencies is so low (or null, as most of the modules only require Odoo Framework), that managing them manually in an extra requirements.txt per project according needed modules is affordable instead of entering in the IMO hell pip method. That's what we do in Tecnativa and Doodba scaffolding has such option in /odoo/custom/dependencies/pip.txt. Other option in v13+ is to scrap the external dependencies from manifests for getting the proper pip packages.

      Regards.
      by Pedro M. Baeza - 11:40 - 11 Feb 2021
    • Re: requirements.txt: Repository Level vs Module Level
      Hello Dmytro,

      I feel that the best solution is to adopt pip-installed modules to your workflow.
      That may need a learning curve, but it already solves all problems you describe.
      I'm not the best person to get into the detail, but I'm sure there on people on this ML that can fill in.

      If you prefer to go the Git way, my opinion is that you should to deploy OCA modules from their Git repos.
      What I do is to have each OCA repo I need as a submodule, and then have a "link-addons" with symlinks for the modules used.
      Only "link-addons" is added to the server addons path.
      The requirements.txt is maintained manually - when a new "link-addons" symlink is added, is it has specific dependencies, the requirements.txt is also updated.

      For requirements.txt inside modules, this is not an issue in recent Odoo versions, and external_Dependencies now supports the package name.
      See https://github.com/odoo/odoo/issues/25541


      I hope this is helpful
      Daniel

      On 11/02/2021 09:56, Dmytro Katyukha wrote:
      Hi all,

      As i see, usually in OCA repositories "requirements.txt" file with pip dependencies is located in the root of the repository and contains a list of all python dependencies for all addons in the repository. This way it works fine, when we clone full repository, and install all dependencies for all modules there, thus when user will try to install new module on DB, 99% that all python dependencies will be satisfied.

      But, let's take for example repository partner-contact repository for Odoo 12.0 and let's try to add the module 'partner_email_check' to odoo server. For this task, i will use [odoo-helper-scripts](https://github.com/katyukha/odoo-helper-scripts) that can automatically resolve repository dependencies (including those specified by oca_dependencies.txt). So, at first i would try to fetch (clone) repository partner-contact, and in this case system will automatically fetch 42 OCA repositories following 'oca_requirements.txt', and also it will try to install python dependencies mentioned in requirements.txt. It is good for development. But installation this way on prod, may lead to a lot of unneeded modules, that polutes system with strange dependencies that are in some cases may be not installable (for example because of system dependencies).

      To solve this reason, we started to use 'assembly' approach, that assumes that we have to create separate git repository with only addons needed on server. But in this case, if assembly repo created automatically, there is no way to get python requirements for module, if it is not specified in module directory. Looking for python dependencies in manifest is also not good, because there are python packages exists, that has different name for package and python module inside package.

      So, may be it have sense to place requirements.txt inside module directory? Thus module's requirements will be always delivered with module, that will make easier installation of module. Also, i think this way, it will be much easier to generate setup.py files for modules, that will contain info about module's python dependencies.

      Possible drawbacks may be in case, when different versions of python dep will be specified in different modules. But same is applicable for repositories.

      What do you think about this?

      With regards,
      Dmytro Katyukha

      _______________________________________________
      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 Director
      M: +351 919991307
      E: DReis@OpenSourceIntegrators.com
      Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal


      by Daniel Reis - 11:21 - 11 Feb 2021
    • Re: requirements.txt: Repository Level vs Module Level
      Hi Dmytro,

      You can achieve fine grained (per module) installation using pip.

      For OCA modules and your example: "pip install odoo12-addon-partner_email_check" should just work, as the OCA modules are available on PyPI.
      Dependencies on python libraries are installed automatically if they are declared in the manifest, as it is the case for that module.
      You can also install from git using the PEP 508 syntax for pip VCS urls: "pip install odoo12-addon-partner_email_check@git+https://github.com/OCA/partner-contact@12.0#subdirectory=setup/partner_email_check".

      You can find more information in this post from 2015 (time flies :) and how it is done in setuptools-odoo.

      > Looking for python dependencies in manifest is also not good, because there are python packages exists, that has different name for package and python module inside package.

      This particular problem is also resolved by setuptools-odoo (look for external dependencies override in the setuptools-odoo doc).
      And for Odoo >=13 you can and should declare the PyPI project name in external_dependencies in the manifest.

      Best regards,

      -sbi



      On Thu, Feb 11, 2021 at 10:56 AM Dmytro Katyukha <dmytro.katyukha@gmail.com> wrote:
      Hi all,

      As i see, usually in OCA repositories "requirements.txt" file with pip dependencies is located in the root of the repository and contains a list of all python dependencies for all addons in the repository. This way it works fine, when we clone full repository, and install all dependencies for all modules there, thus when user will try to install new module on DB, 99% that all python dependencies will be satisfied.

      But, let's take for example repository partner-contact repository for Odoo 12.0 and let's try to add the module 'partner_email_check' to odoo server. For this task, i will use [odoo-helper-scripts](https://github.com/katyukha/odoo-helper-scripts) that can automatically resolve repository dependencies (including those specified by oca_dependencies.txt). So, at first i would try to fetch (clone) repository partner-contact, and in this case system will automatically fetch 42 OCA repositories following 'oca_requirements.txt', and also it will try to install python dependencies mentioned in requirements.txt. It is good for development. But installation this way on prod, may lead to a lot of unneeded modules, that polutes system with strange dependencies that are in some cases may be not installable (for example because of system dependencies).

      To solve this reason, we started to use 'assembly' approach, that assumes that we have to create separate git repository with only addons needed on server. But in this case, if assembly repo created automatically, there is no way to get python requirements for module, if it is not specified in module directory. Looking for python dependencies in manifest is also not good, because there are python packages exists, that has different name for package and python module inside package.

      So, may be it have sense to place requirements.txt inside module directory? Thus module's requirements will be always delivered with module, that will make easier installation of module. Also, i think this way, it will be much easier to generate setup.py files for modules, that will contain info about module's python dependencies.

      Possible drawbacks may be in case, when different versions of python dep will be specified in different modules. But same is applicable for repositories.

      What do you think about this?

      With regards,
      Dmytro Katyukha

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

      by Stéphane Bidoul - 11:16 - 11 Feb 2021
    • Re: requirements.txt: Repository Level vs Module Level
      Hello,

      or... just use `pip install odoo${version}-addon-module-name` and you can forget about dependencies and about cloning over and over all the repos.

      Unless you want to use a local editable version, in which case you could simply do `pip install -e $repo/setup/module_name`.

      Extra goodie: you can pin the module version in your requirements.

      Hope this helps.
      Bests,
      S.

      On Thu, Feb 11, 2021 at 10:56 AM Dmytro Katyukha <dmytro.katyukha@gmail.com> wrote:
      Hi all,

      As i see, usually in OCA repositories "requirements.txt" file with pip dependencies is located in the root of the repository and contains a list of all python dependencies for all addons in the repository. This way it works fine, when we clone full repository, and install all dependencies for all modules there, thus when user will try to install new module on DB, 99% that all python dependencies will be satisfied.

      But, let's take for example repository partner-contact repository for Odoo 12.0 and let's try to add the module 'partner_email_check' to odoo server. For this task, i will use [odoo-helper-scripts](https://github.com/katyukha/odoo-helper-scripts) that can automatically resolve repository dependencies (including those specified by oca_dependencies.txt). So, at first i would try to fetch (clone) repository partner-contact, and in this case system will automatically fetch 42 OCA repositories following 'oca_requirements.txt', and also it will try to install python dependencies mentioned in requirements.txt. It is good for development. But installation this way on prod, may lead to a lot of unneeded modules, that polutes system with strange dependencies that are in some cases may be not installable (for example because of system dependencies).

      To solve this reason, we started to use 'assembly' approach, that assumes that we have to create separate git repository with only addons needed on server. But in this case, if assembly repo created automatically, there is no way to get python requirements for module, if it is not specified in module directory. Looking for python dependencies in manifest is also not good, because there are python packages exists, that has different name for package and python module inside package.

      So, may be it have sense to place requirements.txt inside module directory? Thus module's requirements will be always delivered with module, that will make easier installation of module. Also, i think this way, it will be much easier to generate setup.py files for modules, that will contain info about module's python dependencies.

      Possible drawbacks may be in case, when different versions of python dep will be specified in different modules. But same is applicable for repositories.

      What do you think about this?

      With regards,
      Dmytro Katyukha

      _______________________________________________
      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, Freelance in love with open source.
      by Simone Orsi - 11:16 - 11 Feb 2021
  • Any module that verify numbers, i.e., employee's citizen ID
    Dear community,

    I have a requirement to validate hr.employee's citizen ID format in my country, but I think it would be nicer if we can just extend some base modules to be more generic.

    So far, I found this, https://github.com/OCA/partner-contact/tree/13.0/partner_identification, which can verify numbers but onlty to res.partner.

    Are the more generic base module to be used with other models yet, (or at least for hr.employee)

    Thank you,
    Kitti


    by Kitti Upariphutthiphong - 06:25 - 11 Feb 2021

    6 replies 6 replies

  • Stock valuation and property propagation on Odoo 12
    Hi everyone,

    I need some technical help to understand if the problem comes from my production environment or if it's an Odoo bug.

    Starting working with stock valuation, I found that the product's `property_valuation` were not updated after changing it from the category.
    Technically `_compute_valuation_type` is never called when saving the category form whereas the `api.depends` decorator clearly sets `categ_id.property_valuation` as a dependency.
    That's a big issue because all my products stay in `manual_periodic` even if their category is set to `real_time`.

        @api.one
        @api.depends('property_valuation', 'categ_id.property_valuation')
        def _compute_valuation_type(self):
            self.valuation = self.property_valuation or self.categ_id.property_valuation

    Can someone try to set a breakpoint here to see if this computation function is called in its environment ?
    odoo/addons/stock_account/models/product.py:L48

    Thank you for your time.

    --
    Yann PAPOUIN, Ingénieur R&D | DEC
    by Yann Papouin - 12:40 - 11 Feb 2021
  • Accelerated approval of pull requests

    Dear OCA-Maintainers,

     

    i am reaching out to you to request accelerated approval of two pull requests i recently created:

     

     

    Both pull requests only contain simple migrations, no features were added, which need to be reviewed.
    I am contacting you since it is critical for my organsation to have the resulting Wheels in Wheelhouse soon.

    Many thanks in advance, you are doing a great job!  

     

    Best regards,

    Bastian Guenther | BI ERP Developer | AMETRAS intelligence GmbH

     

    by "Bastian Guenther" <Bastian.Guenther@ametras.com> - 11:55 - 5 Feb 2021

    6 replies 6 replies

    • Re: Accelerated approval of pull requests
      I'd say that rule is inspired from science, where you get three blind reviews for any research paper that you submit for publication. Here we get two transparent reviews, so the rule should be adjusted then: review 2 PRs, expect 1 PR reviewed.



      camptocamp
      INNOVATIVE SOLUTIONS
      BY OPEN SOURCE EXPERTS

      Carlos Serra-Toro
      Senior Software Engineer
      Business Solutions



      On Fri, 5 Feb 2021 at 14:37, Rafael Blasco <rblasco@rbnpro.com> wrote:

      +1

       

      Review 3 PR and expect get reviewed 1 PR (Fayolle rules!). OCA’s traffic jump come from everyone expect reviews but don’t review.

       

      Give fist receive later.

       

      J

       

       

      De: Holger Brunn
      Enviado el: viernes, 5 de febrero de 2021 13:57
      Para: Contributors <contributors@odoo-community.org>
      Asunto: Re: Accelerated approval of pull requests

       

      Hi Bastian,
       
       
      > i am reaching out to you to request accelerated approval of two pull
       
      > requests i recently created:
       
      thank you for your efforts. As contributing as a collaborative effort, I suggest 
      you review some other PRs, and then politely point those PRs' authors to your 
      own PRs. Reviewing is work we need to share.
       
      Best regards,
      Holger
       

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

      by Carlos Serra-Toro - 08:51 - 8 Feb 2021
    • Re: Accelerated approval of pull requests

      +1

      I will happy to give fist

      Op 2/5/21 om 2:37 PM schreef Rafael Blasco:

      +1

       

      Review 3 PR and expect get reviewed 1 PR (Fayolle rules!). OCA’s traffic jump come from everyone expect reviews but don’t review.

       

      Give fist receive later.

       

      J

       

       

      De: Holger Brunn
      Enviado el: viernes, 5 de febrero de 2021 13:57
      Para: Contributors <contributors@odoo-community.org>
      Asunto: Re: Accelerated approval of pull requests

       

      Hi Bastian,
       
       
      > i am reaching out to you to request accelerated approval of two pull
       
      > requests i recently created:
       
      thank you for your efforts. As contributing as a collaborative effort, I suggest 
      you review some other PRs, and then politely point those PRs' authors to your 
      own PRs. Reviewing is work we need to share.
       
      Best regards,
      Holger
       

      _______________________________________________
      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 - 04:46 - 5 Feb 2021
    • RE: Accelerated approval of pull requests

      +1

       

      Review 3 PR and expect get reviewed 1 PR (Fayolle rules!). OCA’s traffic jump come from everyone expect reviews but don’t review.

       

      Give fist receive later.

       

      J

       

       

      De: Holger Brunn
      Enviado el: viernes, 5 de febrero de 2021 13:57
      Para: Contributors <contributors@odoo-community.org>
      Asunto: Re: Accelerated approval of pull requests

       

      Hi Bastian,
       
       
      > i am reaching out to you to request accelerated approval of two pull
       
      > requests i recently created:
       
      thank you for your efforts. As contributing as a collaborative effort, I suggest 
      you review some other PRs, and then politely point those PRs' authors to your 
      own PRs. Reviewing is work we need to share.
       
      Best regards,
      Holger
       
      by Rafael Blasco (Moduon) - 02:31 - 5 Feb 2021
    • Re: Accelerated approval of pull requests 
      Hi Bastian,


> i am reaching out to you to request accelerated approval of two pull

> requests i recently created:

thank you for your efforts. As contributing as a collaborative effort, I suggest 
you review some other PRs, and then politely point those PRs' authors to your 
own PRs. Reviewing is work we need to share.

Best regards,
Holger


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
      by Holger Brunn - 01:56 - 5 Feb 2021

      1 attachments 1 attachments

      signature.asc
    • Re: Accelerated approval of pull requests
      Yes, this is the right direction.

      I deploy from Git, but don't rely on OCA merges.
      I run project specific branches where my OCA PRs are early merged, and deploy from there.

      /Daniel

      On 05/02/2021 12:07, Sergio Corato wrote:
      Perhabs create a custom PIP server should solve the problem faster?

      --
      Daniel Reis
      Managing Director
      M: +351 919991307
      E: DReis@OpenSourceIntegrators.com
      Av Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal


      by Daniel Reis - 01:16 - 5 Feb 2021

  • Review PR, that fixes web_view_searchpanel for 12.0
    Hi all,

    I would like to ask someone to review my PR related to the web_view_searchpanel module, that fixes incorrect behavior in case there is an extra search domain present in action.


    My question is to decide whether it makes sense to depend on the OCA module for this functionality, or maybe it would be better to fork it and use my own version.

    Thanks,

    With regards,
    Dmytro Katyukha
    by dmytro.katyukha - 05:51 - 4 Feb 2021
  • oca/oca.recipe.odoo repository? 
    Hi all,

I'd like to fork https://github.com/anybox/anybox.recipe.odoo which has been 
inactive/externally maintained (amongst others by Stefan Rijnhart and me) to a 
repo under the OCA umbrella, namely oca/oca.recipe.odoo.

We had the discussion before in
https://odoo-community.org/groups/contributors-15/contributors-27171
where the issue of branding was raised, that's why I suggest the new name. 
This way we also don't clash with the original on pypi etc.

Please don't let this devolve into a discussion about what to use for builds/
deployment, OCA can host various alternatives in my opinion.

The fork will probably happen anyways, but I prefer to have it under the OCA 
organization rather than some specific one just for that.

Best regards,
Holger Brunn


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
    by Holger Brunn - 11:01 - 4 Feb 2021

    1 attachments 1 attachments

    signature.asc

    14 replies 14 replies

    • Re: oca/oca.recipe.odoo repository? 
      > Could somebody with the appropriate permissions make the settings accessible

> to the maintainers (StefanRijnhart+hbrunn at the moment)?

> Currently permissions are managed via a GitHub team sync script, from the

> PSC members database. The current policy is that only PSC representatives

> and board have admin access to the repos. I'm not sure it still makes sense

> for tooling repos such as this one, but it's the way it is now. I gave you

> access, but it may only last until the team sync script kicks in again.

thanks Stéphane, I changed the bits that need changing currently, so it won't 
be super problematic if we lose access again.


> Generally, who is the address to ask about OCA github permission stuff? I

> try to avoid asking Alexandre about everything.

> I guess it's support@odoo-community.org [3] , but it will mostly end up with

> Alexandre and myself anyway ;) That's also something we'll need to work on,

> i.e. manage the bus factor for the OCA infrastructure. Cheers,

indeed, that's an important one.


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
      by Holger Brunn - 11:30 - 22 Dec 2021

      1 attachments 1 attachments

      signature.asc
    • Re: oca/oca.recipe.odoo repository?
      Hi Holger,

      On Wed, Dec 22, 2021 at 10:46 AM Holger Brunn <mail@hunki-enterprises.com> wrote:
      we're busy with this currently, but don't have access to the settings tab of 
https://github.com/OCA/oca.recipe.odoo
Could somebody with the appropriate permissions make the settings accessible 
to the maintainers (StefanRijnhart+hbrunn at the moment)?

      Currently permissions are managed via a GitHub team sync script, from the PSC members database.
      The current policy is that only PSC representatives and board have admin access to the repos.
      I'm not sure it still makes sense for tooling repos such as this one, but it's the way it is now.

      I gave you access, but it may only last until the team sync script kicks in again.
       
      Generally, who is the address to ask about OCA github permission stuff? I try 
to avoid asking Alexandre about everything.

      I guess it's support@odoo-community.org, but it will mostly end up with Alexandre and myself anyway ;)
      That's also something we'll need to work on, i.e. manage the bus factor for the OCA infrastructure.

      Cheers,

      -sbi
      by Stéphane Bidoul - 11:01 - 22 Dec 2021
    • Re: oca/oca.recipe.odoo repository? 
      Hi all,

we're busy with this currently, but don't have access to the settings tab of 
https://github.com/OCA/oca.recipe.odoo
Could somebody with the appropriate permissions make the settings accessible 
to the maintainers (StefanRijnhart+hbrunn at the moment)?

Generally, who is the address to ask about OCA github permission stuff? I try 
to avoid asking Alexandre about everything.

Thanks in advance,
Holger


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
      by Holger Brunn - 10:45 - 22 Dec 2021

      1 attachments 1 attachments

      signature.asc
    • Re: oca/oca.recipe.odoo repository? 
      > I'll take care of this this week.

yay thanks! We're busy closing PRs on
https://github.com/anybox/anybox.recipe.odoo/pulls
currently, the plan is to also add py3 tests there and then move the whole 
thing to the OCA repo


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
      by Holger Brunn - 08:55 - 3 Mar 2021

      1 attachments 1 attachments

      signature.asc
    • Re: oca/oca.recipe.odoo repository? 
      I'll take care of this this week.

Alexandre

On 04/02/2021 11:02, Holger Brunn wrote:

> Hi all,

> 

> I'd like to fork https://github.com/anybox/anybox.recipe.odoo which has been

> inactive/externally maintained (amongst others by Stefan Rijnhart and me) to a

> repo under the OCA umbrella, namely oca/oca.recipe.odoo.

> 

> We had the discussion before in

> https://odoo-community.org/groups/contributors-15/contributors-27171

> where the issue of branding was raised, that's why I suggest the new name.

> This way we also don't clash with the original on pypi etc.

> 

> Please don't let this devolve into a discussion about what to use for builds/

> deployment, OCA can host various alternatives in my opinion.

> 

> The fork will probably happen anyways, but I prefer to have it under the OCA

> organization rather than some specific one just for that.

> 

> Best regards,

> Holger Brunn

> 

> -- Your partner for the hard Odoo problems https://hunki-enterprises.com

> 

> _______________________________________________

> 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>

> 



-- 
Alexandre Fayolle
Senior Software Engineer
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
      by Alexandre Fayolle - 08:16 - 3 Mar 2021

  • Off line module or third party ?
    Hello,

    Some of my prospect need the off line possibility, would you be so kind as to inform me regarding the existing module or the best contractor ?

    Best regards

     Véronique

    Véronique Piveteau
    Helpdesk manager - Consultante
    veronique.piveteau@auguria.fr
    +33 6 81 45 58 53
    auguria.fr
    LinkedIn| Facebook| Twitter
    by "Véronique Piveteau" <veronique.piveteau@auguria.fr> - 10:51 - 1 Feb 2021

    1 replies 1 replies

  • How to test v14 upgrade scripts
    Hi all,

    we are porting to 14.0 the OCA/l10n-italy modules and developing some upgrade scripts, like this

    Our doubt: is this testable?
    In general, is it possible to test v14 upgrade scripts before OpenUpgrade is available for v14?

    Thanks!

    --
    by Lorenzo Battistini. - 10:06 - 29 Jan 2021

    4 replies 4 replies

    • Re: How to test v14 upgrade scripts 
      Il giorno ven 29 gen 2021 alle ore 11:27 Holger Brunn
<mail@hunki-enterprises.com> ha scritto:

>

> > In general, is it possible to test v14 upgrade scripts before OpenUpgrade is

>

> > available for v14?

>

> yes, you don't need OpenUpgrade for that.


We did some test using a pre-migrate script like the one linked by Lorenzo (*).
The main purpose is to change the name of the module, as well as
rename xmlids, model and tables.

Steps:

1) old_name module installation
2) add/change some data
3) checkout to commit containing new_name module, migration script and
version bumped
4) launch old_name_module update:
./odoo-bin -c etc/odoo14.cfg -d testdb -u old_name_module --stop-after-init

Output:
old_name_module: not installable, skipped

In fact pre-migrate script is not triggered.

We tried this also:
4) launch new_name_module update:
./odoo-bin -c etc/odoo14.cfg -d testdb -u new_name_module --stop-after-init

But it didn't work as well.


The only way (we have found so far) to trigger pre-migrate script is this:

1) old_name module installation
2) add/change some data
3) checkout to commit containing new_name module, migration script and
version bumped
4) execute odoo shell
    >>> from openupgradelib import openupgrade
    >>> openupgrade.update_module_names(env.cr, [('old_name_module',
'new_name_module'),], merge_modules=False,)
    >>> env.cr.commit()
5) launch new_name_module update:
./odoo-bin -c etc/odoo14.cfg -d testdb -u new_name_module --stop-after-init


Do you know a way to trigger the migration script without using odoo shell?

Thanks in advance.
S.


(*) https://github.com/OCA/l10n-italy/blob/0d65b1f7fa23facd9ef52749571a4a18a58f4045/l10n_it_vat_payability/migrations/14.0.1.0.0/pre-migrate.py
      by Sergio Zanchetta - 10:15 - 28 Apr 2021
    • Re: How to test v14 upgrade scripts 
      Il giorno ven 23 apr 2021 alle ore 15:20 Sergio Zanchetta
<primes2h@gmail.com> ha scritto:

>

> Il giorno ven 29 gen 2021 alle ore 11:27 Holger Brunn

> <mail@hunki-enterprises.com> ha scritto:

> >


> The only way (we have found so far) to trigger pre-migrate script is this:

>

> 1) old_name module installation

> 2) add/change some data

> 3) checkout to commit containing new_name module, migration script and

> version bumped

> 4) execute odoo shell

> >>> from openupgradelib import openupgrade

> >>> openupgrade.update_module_names(env.cr, [('l10n_it_codici_carica', 'l10n_it_appointment_code'),], merge_modules=False,)

Sorry, this one is obviously:

>>> openupgrade.update_module_names(env.cr, [('old_name_module', 'new_name_module'),], merge_modules=False,)
      by Sergio Zanchetta - 10:14 - 28 Apr 2021
    • Re: How to test v14 upgrade scripts 
      Il giorno ven 29 gen 2021 alle ore 11:27 Holger Brunn
<mail@hunki-enterprises.com> ha scritto:

>

> > In general, is it possible to test v14 upgrade scripts before OpenUpgrade is

>

> > available for v14?

>

> yes, you don't need OpenUpgrade for that.


We did some test using a pre-migrate script like the one linked by Lorenzo (*).
The main purpose is to change the name of the module, as well as
rename xmlids, model and tables.

Steps:

1) old_name module installation
2) add/change some data
3) checkout to commit containing new_name module, migration script and
version bumped
4) launch old_name_module update:
./odoo-bin -c etc/odoo14.cfg -d testdb -u old_name_module --stop-after-init

Output:
old_name_module: not installable, skipped

In fact pre-migrate script is not triggered.

We tried this also:
4) launch new_name_module update:
./odoo-bin -c etc/odoo14.cfg -d testdb -u new_name_module --stop-after-init

But it didn't work as well.


The only way (we have found so far) to trigger pre-migrate script is this:

1) old_name module installation
2) add/change some data
3) checkout to commit containing new_name module, migration script and
version bumped
4) execute odoo shell

>>> from openupgradelib import openupgrade

>>> openupgrade.update_module_names(env.cr, [('l10n_it_codici_carica', 'l10n_it_appointment_code'),], merge_modules=False,)

>>> env.cr.commit()
5) launch new_name_module update:
./odoo-bin -c etc/odoo14.cfg -d testdb -u new_name_module --stop-after-init


Do you know a way to trigger the migration script without using odoo shell?

Thanks in advance.
S.


(*) https://github.com/OCA/l10n-italy/blob/0d65b1f7fa23facd9ef52749571a4a18a58f4045/l10n_it_vat_payability/migrations/14.0.1.0.0/pre-migrate.py
      by Sergio Zanchetta - 10:14 - 28 Apr 2021
    • Re: How to test v14 upgrade scripts 
      > In general, is it possible to test v14 upgrade scripts before OpenUpgrade is

> available for v14?

yes, you don't need OpenUpgrade for that.

We lack a good mechanism to test migration scripts, I'm also not sure how I 
would implement such a thing in general. The specific script looks a bit 
pointless to test to me, but you could mock the openupgradelib calls and call 
the function if you're into coverage.


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
      by Holger Brunn - 11:25 - 29 Jan 2021

      1 attachments 1 attachments

      signature.asc
  • Odoo2Odoo

    Dear Community

    According to https://odoo-community.org/groups/contributors-15/contributors-153784?mode=thread&date_begin=&date_end=

    and

    https://odoo-community.org/groups/contributors-15/contributors-84164?mode=thread&date_begin=&date_end=

    the subject has been discussed before...

    Nowadays, could you please give your experience on bidirectional partial replication of Odoo data between 2 databases ?

    Our use case is :

    - Main database on land (accounting, inventory, sales, website...)

    - Secondary database on a boat that loses Internet connexion for several hours (point_of_sale only)

    We already tested https://github.com/JayVora-SerpentCS/SerpentCS_Contributions/tree/13.0/base_synchro it's very slow and have a few issues

    We are going to test bucardo.org with Multi Master Replication but it does not look like the perfect solution

    Would you go to an ESB for such a small use case ?

    Thanks in advance

    Best regards

    -- 
    Cordialement
--------------------------------
Cyril VINH-TUNG
INVITU
Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99
contact@invitu.com
www.invitu.com

    P Please consider the environment before printing this e-mail!

    by Cyril VINH-TUNG - 10:56 - 25 Jan 2021

    1 replies 1 replies

  • Right way to do a new OCA module that depends on EE's LGPL module.
    Dear community,

    Got some questions about licensing.

    There are modules that we want to extend but they are in EE14 --> "approvals", "approvals_purchase".
    Where approvals is a simple module for approving something. And approvals_purchase allow creating purchase order at the end of process.

    They are quite simple. But what we need is to create modules "approvals_purchase_request" and "approvals_hr_expense".

    I have checked that "approvals", although in EE source code, its license is in CE, LGPL.

    What is the right way to deal with this?
    1. Just include approvals in OCA and continue the new module (as it is LGPL, not sure)
    2. We can't use "approvals", and so, we have to first create something similar to it, may be renaming it, add/remove some feature etc. and make it pure OCA module first before continue our needing module.

    Thank you!
    Kitti U.

    by Kitti Upariphutthiphong - 04:31 - 25 Jan 2021

    4 replies 4 replies

    • Re: Right way to do a new OCA module that depends on EE's LGPL module.
      Yes Pedro, "base_tier_validation" will serve us well, will use it with new approvals object (spending request sounds better).

      We want this approvals as a helper window only. End user can request all spending in the same place and at after approval, will create all PR, EX and AV. So, as combined amount, it can go through the right approvals steps (versus smaller documents and get away with) and also for budget check in total amount too.

      I saw, approvals and approvals_purchase, and I think it is intuitive for very end users.

      On Mon, Jan 25, 2021 at 5:27 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
      Kitti, `base_tier_validation` doesn't serve you as base for this?

      Regards.

      El lun, 25 ene 2021 a las 10:27, Kitti Upariphutthiphong (<kittiu@ecosoft.co.th>) escribió:
      Hi Stephane,

      Yes, then I think Odoo just forget it as you say, so it defaults to LGPL. But in any case, I will go with the option 2. Which is to create a new module from the beginning.

      Thanks for your prompt reply.
      Kitti U.

      On Mon, Jan 25, 2021 at 3:47 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      > I have checked that "approvals", although in EE source code, its license is in CE, LGPL.

      Have you checked that with Odoo ? Some EE modules don't have a license key, and when you load them in a database, the license field of ir.module.module defaults to LGPL.
      But last time I reported that to Odoo it was quickly fixed.
      So unless explicitly written otherwise I would assume that all the odoo/enterprise repo is under a proprietary license.

      And you can't create a module that depends on both AGPL and proprietary code.

      In any case adding code that depends on Odoo EE in OCA is not possible because the EE code is not public so we could not run CI, runbot etc.

      Best regards,

      -sbi

      --
      Stéphane Bidoul | @SBidoul
      Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

      On Mon, Jan 25, 2021 at 4:32 AM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
      Dear community,

      Got some questions about licensing.

      There are modules that we want to extend but they are in EE14 --> "approvals", "approvals_purchase".
      Where approvals is a simple module for approving something. And approvals_purchase allow creating purchase order at the end of process.

      They are quite simple. But what we need is to create modules "approvals_purchase_request" and "approvals_hr_expense".

      I have checked that "approvals", although in EE source code, its license is in CE, LGPL.

      What is the right way to deal with this?
      1. Just include approvals in OCA and continue the new module (as it is LGPL, not sure)
      2. We can't use "approvals", and so, we have to first create something similar to it, may be renaming it, add/remove some feature etc. and make it pure OCA module first before continue our needing module.

      Thank you!
      Kitti U.

      _______________________________________________
      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

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

      by Kitti Upariphutthiphong - 12:21 - 25 Jan 2021
    • Re: Right way to do a new OCA module that depends on EE's LGPL module.
      Kitti, `base_tier_validation` doesn't serve you as base for this?

      Regards.

      El lun, 25 ene 2021 a las 10:27, Kitti Upariphutthiphong (<kittiu@ecosoft.co.th>) escribió:
      Hi Stephane,

      Yes, then I think Odoo just forget it as you say, so it defaults to LGPL. But in any case, I will go with the option 2. Which is to create a new module from the beginning.

      Thanks for your prompt reply.
      Kitti U.

      On Mon, Jan 25, 2021 at 3:47 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      > I have checked that "approvals", although in EE source code, its license is in CE, LGPL.

      Have you checked that with Odoo ? Some EE modules don't have a license key, and when you load them in a database, the license field of ir.module.module defaults to LGPL.
      But last time I reported that to Odoo it was quickly fixed.
      So unless explicitly written otherwise I would assume that all the odoo/enterprise repo is under a proprietary license.

      And you can't create a module that depends on both AGPL and proprietary code.

      In any case adding code that depends on Odoo EE in OCA is not possible because the EE code is not public so we could not run CI, runbot etc.

      Best regards,

      -sbi

      --
      Stéphane Bidoul | @SBidoul
      Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

      On Mon, Jan 25, 2021 at 4:32 AM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
      Dear community,

      Got some questions about licensing.

      There are modules that we want to extend but they are in EE14 --> "approvals", "approvals_purchase".
      Where approvals is a simple module for approving something. And approvals_purchase allow creating purchase order at the end of process.

      They are quite simple. But what we need is to create modules "approvals_purchase_request" and "approvals_hr_expense".

      I have checked that "approvals", although in EE source code, its license is in CE, LGPL.

      What is the right way to deal with this?
      1. Just include approvals in OCA and continue the new module (as it is LGPL, not sure)
      2. We can't use "approvals", and so, we have to first create something similar to it, may be renaming it, add/remove some feature etc. and make it pure OCA module first before continue our needing module.

      Thank you!
      Kitti U.

      _______________________________________________
      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 Pedro M. Baeza - 11:25 - 25 Jan 2021
    • Re: Right way to do a new OCA module that depends on EE's LGPL module.
      Hi Stephane,

      Yes, then I think Odoo just forget it as you say, so it defaults to LGPL. But in any case, I will go with the option 2. Which is to create a new module from the beginning.

      Thanks for your prompt reply.
      Kitti U.

      On Mon, Jan 25, 2021 at 3:47 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      > I have checked that "approvals", although in EE source code, its license is in CE, LGPL.

      Have you checked that with Odoo ? Some EE modules don't have a license key, and when you load them in a database, the license field of ir.module.module defaults to LGPL.
      But last time I reported that to Odoo it was quickly fixed.
      So unless explicitly written otherwise I would assume that all the odoo/enterprise repo is under a proprietary license.

      And you can't create a module that depends on both AGPL and proprietary code.

      In any case adding code that depends on Odoo EE in OCA is not possible because the EE code is not public so we could not run CI, runbot etc.

      Best regards,

      -sbi

      --
      Stéphane Bidoul | @SBidoul
      Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

      On Mon, Jan 25, 2021 at 4:32 AM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
      Dear community,

      Got some questions about licensing.

      There are modules that we want to extend but they are in EE14 --> "approvals", "approvals_purchase".
      Where approvals is a simple module for approving something. And approvals_purchase allow creating purchase order at the end of process.

      They are quite simple. But what we need is to create modules "approvals_purchase_request" and "approvals_hr_expense".

      I have checked that "approvals", although in EE source code, its license is in CE, LGPL.

      What is the right way to deal with this?
      1. Just include approvals in OCA and continue the new module (as it is LGPL, not sure)
      2. We can't use "approvals", and so, we have to first create something similar to it, may be renaming it, add/remove some feature etc. and make it pure OCA module first before continue our needing module.

      Thank you!
      Kitti U.

      _______________________________________________
      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 Kitti Upariphutthiphong - 10:26 - 25 Jan 2021
    • Re: Right way to do a new OCA module that depends on EE's LGPL module.
      > I have checked that "approvals", although in EE source code, its license is in CE, LGPL.

      Have you checked that with Odoo ? Some EE modules don't have a license key, and when you load them in a database, the license field of ir.module.module defaults to LGPL.
      But last time I reported that to Odoo it was quickly fixed.
      So unless explicitly written otherwise I would assume that all the odoo/enterprise repo is under a proprietary license.

      And you can't create a module that depends on both AGPL and proprietary code.

      In any case adding code that depends on Odoo EE in OCA is not possible because the EE code is not public so we could not run CI, runbot etc.

      Best regards,

      -sbi

      --
      Stéphane Bidoul | @SBidoul
      Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

      On Mon, Jan 25, 2021 at 4:32 AM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
      Dear community,

      Got some questions about licensing.

      There are modules that we want to extend but they are in EE14 --> "approvals", "approvals_purchase".
      Where approvals is a simple module for approving something. And approvals_purchase allow creating purchase order at the end of process.

      They are quite simple. But what we need is to create modules "approvals_purchase_request" and "approvals_hr_expense".

      I have checked that "approvals", although in EE source code, its license is in CE, LGPL.

      What is the right way to deal with this?
      1. Just include approvals in OCA and continue the new module (as it is LGPL, not sure)
      2. We can't use "approvals", and so, we have to first create something similar to it, may be renaming it, add/remove some feature etc. and make it pure OCA module first before continue our needing module.

      Thank you!
      Kitti U.

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

      by Stéphane Bidoul - 09:46 - 25 Jan 2021
  • Repository for repair module
    Hello, 

    I'll be working on a module to make a procurement from a repair order in the repair module for V14. But I don't know in which repository I can make the PR, I have searched in OCA Shop and I found modules related to repair in field-service and manufacture repositories.

    Where is the best repo to add this module?

    Thanks in advance
    by Jesús Alan Ramos Rodriguez - 09:00 - 20 Jan 2021

    1 replies 1 replies

  • Muli Cloud and Hybrid Cloud for Odoo Solutions
    Hi Contributors,


    I've been 4 months researching about IaC with Terraform for Odoo implementations at multi cloud level.

    I've also been researching in hybrid cloud with kubernetes for Odoo solutions.

    This research is cover by the open source project "TerradooCloud" (https://github.com/TerradooCloud), where I want offer a documentation reference for all the possible deployments scenarios for Odoo on Cloud.

    Recently, Google Cloud launch a course and already have a docs for SAP (https://cloud.google.com/solutions/sap/docs).

    This is like my intends to build for Odoo instead for SAP.

    At this moment, I don't have more time to spend in this research, I only can offer management of GitHub projects and reviews, but due to it is a very big and ambitious project, only can be possible with contributors interested.

    Now, I'm focusing in IoT and electronics, so I continue with microk8s and Odoo for server side of IoT, but my focus will be in electronics side.

    If there are anyone interested in participate in this project is already invited to be a member of the organization, but with external PRs is the best way to participate.

    Thank you very much, I hope this project will be interested to anyone,

    JuanDCG.
    by Juan Del Castillo Gómez - 01:36 - 20 Jan 2021

    2 replies 2 replies

    • Re: Muli Cloud and Hybrid Cloud for Odoo Solutions
      Hi,

      Sorry for the delay, but I've no time for this project.

      Naran, thanks for your feedback, it is great and you are a very early adopter of k8s with odoo.

      But, there are other study cases when k8s is too big, for example an odoo for a freelence.

      I would like cover all study cases from one instance to k8s hosting.

      But now, I don't have time for this and the project is stopped to me.

      I don't know if you are interested in share your experience and know-how at TerradooCloud documentation or you preferred maintain it as private information.

      Cheers,

      Juan.

      El jue, 21 ene 2021 a las 4:12, Naran M (<moturi12@gmail.com>) escribió:
      Hi Juan,

      Thanks for the info. 

      Did you come across an open source Rancher orchestration tool (https://rancher.com/ , now owned by Suse)...? It enables the deployments on K8's with multi-cloud providers. 

      We have been using the Rancher for the last 4+ years to deploy our Odoo productions instances on multi-cloud and the experience is amazing, it made it a lot easier to deploy & manage services.

      For IoT related, they have K3's ( lightweight K8's).

      Cheers,
      Naran

      On Wed, Jan 20, 2021 at 11:37 PM Juan DCG <juandcg314@gmail.com> wrote:
      Hi Contributors,


      I've been 4 months researching about IaC with Terraform for Odoo implementations at multi cloud level.

      I've also been researching in hybrid cloud with kubernetes for Odoo solutions.

      This research is cover by the open source project "TerradooCloud" (https://github.com/TerradooCloud), where I want offer a documentation reference for all the possible deployments scenarios for Odoo on Cloud.

      Recently, Google Cloud launch a course and already have a docs for SAP (https://cloud.google.com/solutions/sap/docs).

      This is like my intends to build for Odoo instead for SAP.

      At this moment, I don't have more time to spend in this research, I only can offer management of GitHub projects and reviews, but due to it is a very big and ambitious project, only can be possible with contributors interested.

      Now, I'm focusing in IoT and electronics, so I continue with microk8s and Odoo for server side of IoT, but my focus will be in electronics side.

      If there are anyone interested in participate in this project is already invited to be a member of the organization, but with external PRs is the best way to participate.

      Thank you very much, I hope this project will be interested to anyone,

      JuanDCG.

      _______________________________________________
      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 Juan Del Castillo Gómez - 06:51 - 1 Feb 2021
    • Re: Muli Cloud and Hybrid Cloud for Odoo Solutions
      Hi Juan,

      Thanks for the info. 

      Did you come across an open source Rancher orchestration tool (https://rancher.com/ , now owned by Suse)...? It enables the deployments on K8's with multi-cloud providers. 

      We have been using the Rancher for the last 4+ years to deploy our Odoo productions instances on multi-cloud and the experience is amazing, it made it a lot easier to deploy & manage services.

      For IoT related, they have K3's ( lightweight K8's).

      Cheers,
      Naran

      On Wed, Jan 20, 2021 at 11:37 PM Juan DCG <juandcg314@gmail.com> wrote:
      Hi Contributors,


      I've been 4 months researching about IaC with Terraform for Odoo implementations at multi cloud level.

      I've also been researching in hybrid cloud with kubernetes for Odoo solutions.

      This research is cover by the open source project "TerradooCloud" (https://github.com/TerradooCloud), where I want offer a documentation reference for all the possible deployments scenarios for Odoo on Cloud.

      Recently, Google Cloud launch a course and already have a docs for SAP (https://cloud.google.com/solutions/sap/docs).

      This is like my intends to build for Odoo instead for SAP.

      At this moment, I don't have more time to spend in this research, I only can offer management of GitHub projects and reviews, but due to it is a very big and ambitious project, only can be possible with contributors interested.

      Now, I'm focusing in IoT and electronics, so I continue with microk8s and Odoo for server side of IoT, but my focus will be in electronics side.

      If there are anyone interested in participate in this project is already invited to be a member of the organization, but with external PRs is the best way to participate.

      Thank you very much, I hope this project will be interested to anyone,

      JuanDCG.

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

      by Naran Moturi - 04:11 - 21 Jan 2021
  • Header sorting in form view
    Dear community,

    I'm looking for an addon or a way to keep user sorting choices.

    As you know, you can click on a One2Many or Many2Many header (of a stored field) to sort the lines but any action in the form (validate something or encoding quantities, etc.) reload it and reset the user sort.

    I don't have a great JS expertise that's why I'm asking here before starting to work on a new module/hook dedicated to this feature.

    Thank you.
    --
    Yann Papouin
    by Yann Papouin - 11:11 - 11 Jan 2021

    4 replies 4 replies