Skip to Content

Contributors

  • Re: OCA BOT can't merge PRs in OCA/l10n-italy branch 11.0

    Il giorno mar 2 mar 2021 alle ore 15:12 Lorenzo Battistini <elbaddy@gmail.com> ha scritto:
    So, the best thing to do is to fix https://github.com/OCA/l10n-italy/issues/1921


    On Tue, 2 Mar 2021 at 12:16, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
    The test failure looks real although it does not appear with each run.

    Regarding the pot file not stabilizing I'm not sure what to do. Maybe trying with python 3.6 ?

    -sbi

    On Tue, Mar 2, 2021 at 11:27 AM Francesco Apruzzese <cescoap@gmail.com> wrote:
    Hi Stéphane.

    Is there anything we need to do in our repo?
     

    Il giorno lun 1 mar 2021 alle ore 17:52 Stéphane Bidoul <stephane.bidoul@acsone.eu> ha scritto:
    Hi Francesco,

    For the second one, the error can be seen on the last commit here:


    So it seems to be a real test error, but one that does not appear during all builds.
    Also, it seems that Odoo's .pot file exporter has difficulties producing a stable result, with several commits updating the same .pot file.

    I'd suggest first trying to understand the test failure, then we can see if the pot file issue needs addressing (maybe by upgrading to python 3.6).

    -sbi



    On Mon, Mar 1, 2021 at 2:21 PM Francesco Apruzzese <cescoap@gmail.com> wrote:
    Can anyone help us to understand why the BOT can't merge this PR


    or this one 


    ?

    Thank you.
    --

    Francesco Apruzzese

    Profilo professionale: http://it.linkedin.com/in/francescoapruzzese

    Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
    This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.

    Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.

    _______________________________________________
    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



    --

    Francesco Apruzzese

    Profilo professionale: http://it.linkedin.com/in/francescoapruzzese

    Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
    This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.

    Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.

    _______________________________________________
    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



    --

    Francesco Apruzzese

    Profilo professionale: http://it.linkedin.com/in/francescoapruzzese

    Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
    This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.

    Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.


    by Francesco Apruzzese - 02:56 - 11 Mar 2021
  • Re: Track sales packaging costs
     A solution could be to use a consumable product with a nominal value e.g. $1.
    Then the warehouse user could add the qty (value) of the packaging in the delivery order.
    The margin report needs then to pick up this extra line. You'll need to customize It.
    Regards






    On Thu, 11 Mar 2021 at 6:22 AM, Daniel Reis <dreis@opensourceintegrators.com> wrote:
    Hello,

    Here is a functional issue I could use some brain sharing.

    A sales order needs packaging to be shipped to the customer.
    But product margins are tight and, depending on the value of the products sold, packaging costs can have a significant impact on the sales margin.
    Adding to the Product cost an extra amount for average packaging costs is not a solution, as the actual packaging costs depend on the sales order composition.

    This looks a bit like "landed costs" but for sales.
    It also looks a bit like "additional carrier shipping costs", but is an inventory expense rather than a vendor bill to be paid.
    There is no hard requirement to include the costs in the COGS, we are more interested in margin analysis.
     
    Thanks for sharing your ideas

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

    --
    Dominique KON-SUN-TACK  [Project Manager]
    Odoo Gold Partner, best Odoo Partner 2014 for APAC

    Mobile: + 65 8502 2399
    Skype: dominique_elico



    by dominique.k - 02:16 - 11 Mar 2021
  • Re: Track sales packaging costs
    I drafted a module lately that would add a line to the sale order when the 
    stock.quant.package used in a picking involved there has a product defined.
    
    Then it's up to the user to invoice that. Is that what you have in mind?
    
    -- 
    Your partner for the hard Odoo problems
    https://hunki-enterprises.com

    by Holger Brunn - 11:51 - 10 Mar 2021
  • Track sales packaging costs
    Hello,

    Here is a functional issue I could use some brain sharing.

    A sales order needs packaging to be shipped to the customer.
    But product margins are tight and, depending on the value of the products sold, packaging costs can have a significant impact on the sales margin.
    Adding to the Product cost an extra amount for average packaging costs is not a solution, as the actual packaging costs depend on the sales order composition.

    This looks a bit like "landed costs" but for sales.
    It also looks a bit like "additional carrier shipping costs", but is an inventory expense rather than a vendor bill to be paid.
    There is no hard requirement to include the costs in the COGS, we are more interested in margin analysis.
     
    Thanks for sharing your ideas

    --
    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 - 10 Mar 2021
  • Re: Proposing moving Pledra product configurator to the OCA
    +++++1

    Regards,
    Vishal Mehra

    cell: (972) 853-1805

    BizAlytics Consulting
    Analyzing Your Business for Success


    On Thu, Mar 4, 2021 at 7:32 AM Thorsten Vocks <thorsten.vocks@big-consulting.net> wrote:
    pledra configurator is really great. +1
    Thorsten Vocks

    openBIG.org
    Dipl. Kaufmann (FH)
    Porscheweg 4-6
    49661 Cloppenburg

    Phone: +49 4471 8409000
    Fax: +49 4471 84090009
    Mail: thorsten.vocks@openbig.org

                  


    Am Mi., 3. März 2021 um 17:02 Uhr schrieb Daniel Reis <dreis@opensourceintegrators.com>:
    Hello all,

    Some of you may be familiar with the Pledra project, proposing an advanced product configurator.
    https://github.com/pledra/odoo-product-configurator

    I don't think there is a comparable project in the OCA, and I would like proposing to move Pledra under the OCA umbrella.
    I contacted the original author, Paul Catinean, and he  is supportive of this move.
    There are quite a few details to get right, and I'm ready to take the role and address them.

    At this point the main question is, from a high level PoV if this sounds like a good idea, and what concerns we should address when moving forward.

    Thank you, and thanks Paul for being onboard with this.

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


    _______________________________________________
    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 Vishal Mehra - 02:06 - 6 Mar 2021
  • Re: partner_revision module?
    Hi Tom,

    I think you need this one

    """
    This module allows you to manage versions for partner addresses.

     
    A list of fields are defined for versioning. These are immutable once set, and force the user to create a new partner
    if they want to change one of these fields.
    """


    I hope it can help you

    Cordialement
    Akretion, créateur de ShopInvader
    https://shopinvader.com



    Le jeu. 4 mars 2021 à 15:12, Daniel Reis <dreis@opensourceintegrators.com> a écrit :
    Maybe this? It is a dependency for sale_order_revision.

    https://github.com/OCA/server-ux/tree/14.0/base_revision


    --daniel


    On 04/03/2021 14:01, Tom Blauwendraat wrote:
    A client wants to keep a history of archived res.partner records lying 
    around, to be able to link invoices to the exact partner record that was 
    used for the invoice at the time (address details, etc).
    
    Is there a module lying around somewhere that does this?
    
    
    

    _______________________________________________
    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


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


    by David BEAL - 09:41 - 4 Mar 2021
  • Re: partner_revision module?
    Maybe this? It is a dependency for sale_order_revision.

    https://github.com/OCA/server-ux/tree/14.0/base_revision


    --daniel


    On 04/03/2021 14:01, Tom Blauwendraat wrote:
    A client wants to keep a history of archived res.partner records lying 
    around, to be able to link invoices to the exact partner record that was 
    used for the invoice at the time (address details, etc).
    
    Is there a module lying around somewhere that does this?
    
    
    

    _______________________________________________
    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 - 03:11 - 4 Mar 2021
  • partner_revision module?
    A client wants to keep a history of archived res.partner records lying 
    around, to be able to link invoices to the exact partner record that was 
    used for the invoice at the time (address details, etc).
    
    Is there a module lying around somewhere that does this?
    
    
    

    by Tom Blauwendraat - 03:00 - 4 Mar 2021
  • Re: Proposing moving Pledra product configurator to the OCA
    pledra configurator is really great. +1
    Thorsten Vocks

    openBIG.org
    Dipl. Kaufmann (FH)
    Porscheweg 4-6
    49661 Cloppenburg

    Phone: +49 4471 8409000
    Fax: +49 4471 84090009
    Mail: thorsten.vocks@openbig.org

                  


    Am Mi., 3. März 2021 um 17:02 Uhr schrieb Daniel Reis <dreis@opensourceintegrators.com>:
    Hello all,

    Some of you may be familiar with the Pledra project, proposing an advanced product configurator.
    https://github.com/pledra/odoo-product-configurator

    I don't think there is a comparable project in the OCA, and I would like proposing to move Pledra under the OCA umbrella.
    I contacted the original author, Paul Catinean, and he  is supportive of this move.
    There are quite a few details to get right, and I'm ready to take the role and address them.

    At this point the main question is, from a high level PoV if this sounds like a good idea, and what concerns we should address when moving forward.

    Thank you, and thanks Paul for being onboard with this.

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


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


    by Thorsten Vocks - 02:31 - 4 Mar 2021
  • Re: Proposing moving Pledra product configurator to the OCA
    +1

    Peter Langenberg
    Senior Odoo Consultant
    Product Owner Odoo
    Volg op twitter via : @mylbco




    Op do 4 mrt. 2021 om 13:56 schreef Paul Catinean <paulcatinean@gmail.com>:
    Hello everyone,

    I'm happy to see there is still great support on this project, both from customers and the community.

    While the initial intent to provide an ever evolving generic app did not go as planned I'm sure under the OCA umbrella it can grow faster and better.

    We have plans to refactor some bits of the architecture already but it's something we can discuss together after the move.

    Regards,
    Paul



    On Thu, Mar 4, 2021 at 11:32 AM Frederik Kramer <frederik.kramer@initos.com> wrote:
    Sounds great
    
    @Daniel: I think we seldomly got more +1 within just two days. Would
    you mind to get in touch with Paul to make the first handover quickly.
    I think -from what we've discussed over the years- he would be more
    than happy to see things evolve like this! And its definitely an added
    value for the OCA ecosystem.
    
    Best Frederik
    
    Am Donnerstag, den 04.03.2021, 09:22 +0000 schrieb
    luc.demeyer@noviat.com:
    
    
    
    > We are running the configurator in production on Odoo 13.
    
    
    
    > 
    
    
    
    > A small couple of PR’s were sufficient for our use case.
    
    
    
    > 
    
    
    
    > I think we can use the current 13.0 code as the base for the OCA repo
    
    
    
    > and do the refactoring in a second stage.
    
    
    
    > 
    
    
    
    >  
    
    
    
    > 
    
    
    
    > Luc
    
    
    
    > 
    
    
    
    >  
    
    
    
    > 
    
    
    
    > From: Richard deMeester <richard.demeester@willdooit.com> 
    
    
    
    > Sent: Thursday, 4 March 2021 10:12
    
    
    
    > To: Contributors <contributors@odoo-community.org>
    
    
    
    > Subject: Re: Proposing moving Pledra product configurator to the OCA
    
    
    
    > 
    
    
    
    >  
    
    
    
    > 
    
    
    
    > Hi,
    
    
    
    > 
    
    
    
    >  
    
    
    
    > 
    
    
    
    > I had much involvement with this repo in v10, and ended up with a
    
    
    
    > multitude of enhancements and patches outside of the configurator.
    
    
    
    > 
    
    
    
    >  
    
    
    
    > 
    
    
    
    > It is an awesome tool, and while at the low end, the Odoo tool can do
    
    
    
    > a lot, at the top end, this is the deal.
    
    
    
    > 
    
    
    
    >  
    
    
    
    > 
    
    
    
    > Unfortunately, I feel that to bring it up to 13/14 needs a
    
    
    
    > considerable rethink in some of the architecture, but in my spare
    
    
    
    > time, I would be very keen to assist in this worthwhile project.
    
    
    
    > 
    
    
    
    >  
    
    
    
    > 
    
    
    
    > Richard
    
    
    
    > 
    
    
    
    >  
    
    
    
    > 
    
    
    
    > 
    
    
    
    > Richard deMeester
    
    
    
    > Senior Development Analyst
    
    
    
    > WilldooIT Pty Ltd
    
    
    
    > E: richard.demeester@willdooit.com
    
    
    
    > M: +61 403 76 76 76
    
    
    
    > P: +61 3 9135 1900
    
    
    
    > A: 10/435 Williamstown Road, Port Melbourne, Vic 3207
    
    
    
    >  
    
    
    
    >  
    
    
    
    > Making growth through technology easy
    
    
    
    >  
    
    
    
    > 
    
    
    
    >  
    
    
    
    > DISCLAIMER | This electronic message together with any attachments is
    
    
    
    > confidential. If you are not the recipient, do not copy, disclose, or
    
    
    
    > use the contents in any way. Please also advise us by e-mail that you
    
    
    
    > have received this message in error and then please destroy this
    
    
    
    > email and any of its attachments. WilldooIT Pty. Ltd. is not
    
    
    
    > responsible for any changes made to this message and/or any
    
    
    
    > attachments after sending by WilldooIT Pty. Ltd. WilldooIT Pty. Ltd.
    
    
    
    > use virus scanning software but exclude all liability for virus or
    
    
    
    > anything similar in this email or attachment.
    
    
    
    >  
    
    
    
    > 
    
    
    
    > From: Daniel Reis <dreis@opensourceintegrators.com>
    
    
    
    > Sent: Thursday, 4 March 2021 3:02 AM
    
    
    
    > To: Contributors <contributors@odoo-community.org>
    
    
    
    > Subject: Proposing moving Pledra product configurator to the OCA
    
    
    
    > 
    
    
    
    >  
    
    
    
    > 
    
    
    
    > Hello all,
    
    
    
    > 
    
    
    
    > Some of you may be familiar with the Pledra project, proposing an
    
    
    
    > advanced product configurator.
    
    
    
    > https://github.com/pledra/odoo-product-configurator
    
    
    
    > 
    
    
    
    > I don't think there is a comparable project in the OCA, and I would
    
    
    
    > like proposing to move Pledra under the OCA umbrella.
    
    
    
    > I contacted the original author, Paul Catinean, and he  is supportive
    
    
    
    > of this move.
    
    
    
    > There are quite a few details to get right, and I'm ready to take the
    
    
    
    > role and address them.
    
    
    
    > 
    
    
    
    > At this point the main question is, from a high level PoV if this
    
    
    
    > sounds like a good idea, and what concerns we should address when
    
    
    
    > moving forward.
    
    
    
    > 
    
    
    
    > Thank you, and thanks Paul for being onboard with this. 
    
    
    
    > 
    
    
    
    > 
    
    
    
    > --
    
    
    
    > 
    
    
    
    > DANIEL REIS
    
    
    
    > MANAGING DIRECTOR
    
    
    
    > 
    
    
    
    > M: +351 919991307
    
    
    
    > E: DReis@OpenSourceIntegrators.com
    
    
    
    > 
    
    
    
    > AV DOUTOR DESIDÉRIO CAMBOURNAC 12 • 2710-553 SINTRA, PORTUGAL
    
    
    
    > 
    
    
    
    >  
    
    
    
    > 
    
    
    
    > 
    
    
    
    > 
    
    
    
    > 
    
    
    
    > 
    
    
    
    > 
    
    
    
    > _______________________________________________
    
    
    
    > 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
    
    
    
    -- 
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    An der Eisenbahn 1
    21224 Rosengarten
            
    Phone:  +49 4105 56156-12
    Fax:    +49 4105 56156-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Rosengarten – Klecken
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155
    
    

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

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


    by Peter Langenberg - 02:21 - 4 Mar 2021
  • Re: Proposing moving Pledra product configurator to the OCA
    Hello everyone,

    I'm happy to see there is still great support on this project, both from customers and the community.

    While the initial intent to provide an ever evolving generic app did not go as planned I'm sure under the OCA umbrella it can grow faster and better.

    We have plans to refactor some bits of the architecture already but it's something we can discuss together after the move.

    Regards,
    Paul



    On Thu, Mar 4, 2021 at 11:32 AM Frederik Kramer <frederik.kramer@initos.com> wrote:
    Sounds great
    
    @Daniel: I think we seldomly got more +1 within just two days. Would
    you mind to get in touch with Paul to make the first handover quickly.
    I think -from what we've discussed over the years- he would be more
    than happy to see things evolve like this! And its definitely an added
    value for the OCA ecosystem.
    
    Best Frederik
    
    Am Donnerstag, den 04.03.2021, 09:22 +0000 schrieb
    luc.demeyer@noviat.com:
    
    
    > We are running the configurator in production on Odoo 13.
    
    
    > 
    
    
    > A small couple of PR’s were sufficient for our use case.
    
    
    > 
    
    
    > I think we can use the current 13.0 code as the base for the OCA repo
    
    
    > and do the refactoring in a second stage.
    
    
    > 
    
    
    >  
    
    
    > 
    
    
    > Luc
    
    
    > 
    
    
    >  
    
    
    > 
    
    
    > From: Richard deMeester <richard.demeester@willdooit.com> 
    
    
    > Sent: Thursday, 4 March 2021 10:12
    
    
    > To: Contributors <contributors@odoo-community.org>
    
    
    > Subject: Re: Proposing moving Pledra product configurator to the OCA
    
    
    > 
    
    
    >  
    
    
    > 
    
    
    > Hi,
    
    
    > 
    
    
    >  
    
    
    > 
    
    
    > I had much involvement with this repo in v10, and ended up with a
    
    
    > multitude of enhancements and patches outside of the configurator.
    
    
    > 
    
    
    >  
    
    
    > 
    
    
    > It is an awesome tool, and while at the low end, the Odoo tool can do
    
    
    > a lot, at the top end, this is the deal.
    
    
    > 
    
    
    >  
    
    
    > 
    
    
    > Unfortunately, I feel that to bring it up to 13/14 needs a
    
    
    > considerable rethink in some of the architecture, but in my spare
    
    
    > time, I would be very keen to assist in this worthwhile project.
    
    
    > 
    
    
    >  
    
    
    > 
    
    
    > Richard
    
    
    > 
    
    
    >  
    
    
    > 
    
    
    > 
    
    
    > Richard deMeester
    
    
    > Senior Development Analyst
    
    
    > WilldooIT Pty Ltd
    
    
    > E: richard.demeester@willdooit.com
    
    
    > M: +61 403 76 76 76
    
    
    > P: +61 3 9135 1900
    
    
    > A: 10/435 Williamstown Road, Port Melbourne, Vic 3207
    
    
    >  
    
    
    >  
    
    
    > Making growth through technology easy
    
    
    >  
    
    
    > 
    
    
    >  
    
    
    > DISCLAIMER | This electronic message together with any attachments is
    
    
    > confidential. If you are not the recipient, do not copy, disclose, or
    
    
    > use the contents in any way. Please also advise us by e-mail that you
    
    
    > have received this message in error and then please destroy this
    
    
    > email and any of its attachments. WilldooIT Pty. Ltd. is not
    
    
    > responsible for any changes made to this message and/or any
    
    
    > attachments after sending by WilldooIT Pty. Ltd. WilldooIT Pty. Ltd.
    
    
    > use virus scanning software but exclude all liability for virus or
    
    
    > anything similar in this email or attachment.
    
    
    >  
    
    
    > 
    
    
    > From: Daniel Reis <dreis@opensourceintegrators.com>
    
    
    > Sent: Thursday, 4 March 2021 3:02 AM
    
    
    > To: Contributors <contributors@odoo-community.org>
    
    
    > Subject: Proposing moving Pledra product configurator to the OCA
    
    
    > 
    
    
    >  
    
    
    > 
    
    
    > Hello all,
    
    
    > 
    
    
    > Some of you may be familiar with the Pledra project, proposing an
    
    
    > advanced product configurator.
    
    
    > https://github.com/pledra/odoo-product-configurator
    
    
    > 
    
    
    > I don't think there is a comparable project in the OCA, and I would
    
    
    > like proposing to move Pledra under the OCA umbrella.
    
    
    > I contacted the original author, Paul Catinean, and he  is supportive
    
    
    > of this move.
    
    
    > There are quite a few details to get right, and I'm ready to take the
    
    
    > role and address them.
    
    
    > 
    
    
    > At this point the main question is, from a high level PoV if this
    
    
    > sounds like a good idea, and what concerns we should address when
    
    
    > moving forward.
    
    
    > 
    
    
    > Thank you, and thanks Paul for being onboard with this. 
    
    
    > 
    
    
    > 
    
    
    > --
    
    
    > 
    
    
    > DANIEL REIS
    
    
    > MANAGING DIRECTOR
    
    
    > 
    
    
    > M: +351 919991307
    
    
    > E: DReis@OpenSourceIntegrators.com
    
    
    > 
    
    
    > AV DOUTOR DESIDÉRIO CAMBOURNAC 12 • 2710-553 SINTRA, PORTUGAL
    
    
    > 
    
    
    >  
    
    
    > 
    
    
    > 
    
    
    > 
    
    
    > 
    
    
    > 
    
    
    > 
    
    
    > _______________________________________________
    
    
    > 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
    
    
    -- 
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    An der Eisenbahn 1
    21224 Rosengarten
            
    Phone:  +49 4105 56156-12
    Fax:    +49 4105 56156-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Rosengarten – Klecken
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155
    
    

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


    by Paul Catinean - 01:55 - 4 Mar 2021
  • Re: Integration of mailing.mailing (Email marketing) templates and webiste pages?
    Simeno, thanx a lot again. Will dive into that.
    
    	Radovan
    
    On štvrtok 4. marca 2021 13:01:47 CET Simone Orsi wrote:
    
    > On Thu, Mar 4, 2021 at 11:27 AM Radovan Skolnik < radovan@skolnik.info [1] >
    
    > wrote: Thank you Simone!
    
    > I was thinking about something exactly like this. How would you propose to
    
    > handle a situation where I want to have a general copy of that email/page -
    
    > for example shared via FB campaign? That is not linked to any specific
    
    > recipient (or is linked to a pseudo one). Should I maybe extend extend the
    
    > mail_browser_view controller to provide something like /campaing/view/
    
    > <string:token> which would render the same content without tracking? Or to
    
    > save removing the tracking elements and create a special version of
    
    > mail.mail to be used in static linking from other websites? Hope I am clear
    
    > :-) I see. Yeah maybe a fake recipient mail record is the easiest way. Then
    
    > to strip out elements on rendering you could rely on query string params.
    
    > Another approach would be to not use mail_browser_view for such case and do
    
    > something custom based on
    
    > https://github.com/OCA/social/blob/13.0/mail_layout_preview/controllers/lay
    
    > out_preview.py [2]  This way you render what you want w/ whatever record you
    
    > want. Best regards
    
    > Radovan
    
    > 
    
    > On štvrtok 4. marca 2021 10:57:46 CET Simone Orsi wrote:
    
    > > Hello,
    
    > > this should address your issue
    
    > > 
    
    > >  https://github.com/OCA/social/tree/11.0/mail_browser_view [3] [1] And if
    
    > >  you> 
    
    > > want to test/dev your templates before sending them w/ real content you
    
    > > can
    
    > > use  https://github.com/OCA/social/tree/13.0/mail_layout_preview [4] [2]
    
    > > HTH, On Thu, Mar 4, 2021 at 9:21 AM Radovan Skolnik < 
    
    > > radovan@skolnik.info [5] [3] > wrote: Hello,
    
    > > let me start in this way. When receiving e-mail campaign mails from
    
    > > various
    
    > > sources, they usually contain a link saying "If you cannot read this email
    
    > > properly, click here to display on web" or something like that for cases
    
    > > when email client forbids loading external content or just cannot render
    
    > > the HTML content properly. The link leads to a webpage where there is
    
    > > basically the same content as in the email.
    
    > > Now I would like to achieve something similar. I.e. to be able to send
    
    > > themed marketing emails and have them contain link to website page as a
    
    > > alternative way of displaying the content. That webpage should be a normal
    
    > > webpage - will be advertised through other means as well (Facebook,
    
    > > Instagram, ...) Now I know I could design/create both email template and
    
    > > website page but that just doubles the work. So I am looking for something
    
    > > like one of these alternatives:
    
    > > *) You design the email and have it render (create) the website page with
    
    > > the same content.
    
    > > *) The same as above but just the other way around. Create webpage and
    
    > > from
    
    > > that have email generated.
    
    > > *) Something else?
    
    > > Can anyone advise anything in this regards? Or am I missing something as
    
    > > usual? ;-)
    
    > > Best regards
    
    > > Radovan Skolnik
    
    > > 
    
    > > 
    
    > > _______________________________________________
    
    > > Mailing-List:  https://odoo-community.org/groups/contributors-15 [6] [4]
    
    > > Post to: mailto:  contributors@odoo-community.org [7] [5]
    
    > > Unsubscribe:  https://odoo-community.org/groups?unsubscribe [8] [6]
    
    > > 
    
    > > --
    
    > > Simone Orsi
    
    > > Full stack Python web developer,
    
    > > Odoo specialist,
    
    > > Odoo Community Board Member,
    
    > > Freelance
    
    > > in love with open source.
    
    > > _______________________________________________
    
    > > Mailing-List:  https://odoo-community.org/groups/contributors-15 [9] [7]
    
    > > Post to: mailto: contributors@odoo-community.org [10]
    
    > > Unsubscribe:  https://odoo-community.org/groups?unsubscribe [11] [8]
    
    > > 
    
    > > 
    
    > > 
    
    > > [1]  https://github.com/OCA/social/tree/11.0/mail_browser_view [12]
    
    > > [2]  https://github.com/OCA/social/tree/13.0/mail_layout_preview [13]
    
    > > [3] mailto: radovan@skolnik.info [14]
    
    > > [4]  https://odoo-community.org/groups/contributors-15 [15]
    
    > > [5] mailto: contributors@odoo-community.org [16]
    
    > > [6]  https://odoo-community.org/groups?unsubscribe [17]
    
    > > [7]  https://odoo-community.org/groups/contributors-15 [18]
    
    > > [8]  https://odoo-community.org/groups?unsubscribe [19]
    
    > 
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 [20]
    
    > Post to: mailto: contributors@odoo-community.org [21]
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe [22]
    
    > 
    
    > --
    
    > Simone Orsi
    
    > Full stack Python web developer,
    
    > Odoo specialist,
    
    > Odoo Community Board Member,
    
    > Freelance
    
    > in love with open source.
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 [23]
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe [24]
    
    > 
    
    > 
    
    > 
    
    > [1] mailto:radovan@skolnik.info
    
    > [2]
    
    > https://github.com/OCA/social/blob/13.0/mail_layout_preview/controllers/lay
    
    > out_preview.py [3] https://github.com/OCA/social/tree/11.0/mail_browser_view
    
    > [4] https://github.com/OCA/social/tree/13.0/mail_layout_preview
    
    > [5] mailto:radovan@skolnik.info
    
    > [6] https://odoo-community.org/groups/contributors-15
    
    > [7] mailto:contributors@odoo-community.org
    
    > [8] https://odoo-community.org/groups?unsubscribe
    
    > [9] https://odoo-community.org/groups/contributors-15
    
    > [10] mailto:contributors@odoo-community.org
    
    > [11] https://odoo-community.org/groups?unsubscribe
    
    > [12] https://github.com/OCA/social/tree/11.0/mail_browser_view
    
    > [13] https://github.com/OCA/social/tree/13.0/mail_layout_preview
    
    > [14] mailto:radovan@skolnik.info
    
    > [15] https://odoo-community.org/groups/contributors-15
    
    > [16] mailto:contributors@odoo-community.org
    
    > [17] https://odoo-community.org/groups?unsubscribe
    
    > [18] https://odoo-community.org/groups/contributors-15
    
    > [19] https://odoo-community.org/groups?unsubscribe
    
    > [20] https://odoo-community.org/groups/contributors-15
    
    > [21] mailto:contributors@odoo-community.org
    
    > [22] https://odoo-community.org/groups?unsubscribe
    
    > [23] https://odoo-community.org/groups/contributors-15
    
    > [24] https://odoo-community.org/groups?unsubscribe
    
    
    
    
    

    by Radovan Skolnik - 01:10 - 4 Mar 2021
  • Re: Integration of mailing.mailing (Email marketing) templates and webiste pages?
    On Thu, Mar 4, 2021 at 11:27 AM Radovan Skolnik <radovan@skolnik.info> wrote:
    Thank you Simone!
    
    I was thinking about something exactly like this. How would you propose to 
    handle a situation where I want to have a general copy of that email/page - 
    for example shared via FB campaign? That is not linked to any specific 
    recipient (or is linked to a pseudo one). Should I maybe extend extend the 
    mail_browser_view controller to provide something like /campaing/view/
    <string:token> which would render the same content without tracking? Or to 
    save removing the tracking elements and create a special version of mail.mail 
    to be used in static linking from other websites? Hope I am clear :-)

    I see. Yeah maybe a fake recipient mail record is the easiest way.
    Then to strip out elements on rendering you could rely on query string params.
    Another approach would be to not use mail_browser_view for such case
    This way you render what you want w/ whatever record you want.
     
    Best regards
    
    	Radovan
    
    On štvrtok 4. marca 2021 10:57:46 CET Simone Orsi wrote:
    
    
    > Hello,
    
    
    > this should address your issue
    
    
    > https://github.com/OCA/social/tree/11.0/mail_browser_view [1] And if you
    
    
    > want to test/dev your templates before sending them w/ real content you can
    
    
    > use https://github.com/OCA/social/tree/13.0/mail_layout_preview [2] HTH,
    
    
    > On Thu, Mar 4, 2021 at 9:21 AM Radovan Skolnik < radovan@skolnik.info [3] >
    
    
    > wrote: Hello,
    
    
    > let me start in this way. When receiving e-mail campaign mails from various
    
    
    > sources, they usually contain a link saying "If you cannot read this email
    
    
    > properly, click here to display on web" or something like that for cases
    
    
    > when email client forbids loading external content or just cannot render
    
    
    > the HTML content properly. The link leads to a webpage where there is
    
    
    > basically the same content as in the email.
    
    
    > Now I would like to achieve something similar. I.e. to be able to send
    
    
    > themed marketing emails and have them contain link to website page as a
    
    
    > alternative way of displaying the content. That webpage should be a normal
    
    
    > webpage - will be advertised through other means as well (Facebook,
    
    
    > Instagram, ...) Now I know I could design/create both email template and
    
    
    > website page but that just doubles the work. So I am looking for something
    
    
    > like one of these alternatives:
    
    
    > *) You design the email and have it render (create) the website page with
    
    
    > the same content.
    
    
    > *) The same as above but just the other way around. Create webpage and from
    
    
    > that have email generated.
    
    
    > *) Something else?
    
    
    > Can anyone advise anything in this regards? Or am I missing something as
    
    
    > usual? ;-)
    
    
    > Best regards
    
    
    > Radovan Skolnik
    
    
    > 
    
    
    > 
    
    
    > _______________________________________________
    
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 [4]
    
    
    > Post to: mailto: contributors@odoo-community.org [5]
    
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe [6]
    
    
    > 
    
    
    > --
    
    
    > Simone Orsi
    
    
    > Full stack Python web developer,
    
    
    > Odoo specialist,
    
    
    > Odoo Community Board Member,
    
    
    > Freelance
    
    
    > in love with open source.
    
    
    > _______________________________________________
    
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 [7]
    
    
    > Post to: mailto:contributors@odoo-community.org
    
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe [8]
    
    
    > 
    
    
    > 
    
    
    > 
    
    
    > [1] https://github.com/OCA/social/tree/11.0/mail_browser_view
    
    
    > [2] https://github.com/OCA/social/tree/13.0/mail_layout_preview
    
    
    > [3] mailto:radovan@skolnik.info
    
    
    > [4] https://odoo-community.org/groups/contributors-15
    
    
    > [5] mailto:contributors@odoo-community.org
    
    
    > [6] https://odoo-community.org/groups?unsubscribe
    
    
    > [7] https://odoo-community.org/groups/contributors-15
    
    
    > [8] 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



    --
    Simone Orsi

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

    by Simone Orsi - 01:00 - 4 Mar 2021
  • Re: Integration of mailing.mailing (Email marketing) templates and webiste pages?
    Thank you Simone!
    
    I was thinking about something exactly like this. How would you propose to 
    handle a situation where I want to have a general copy of that email/page - 
    for example shared via FB campaign? That is not linked to any specific 
    recipient (or is linked to a pseudo one). Should I maybe extend extend the 
    mail_browser_view controller to provide something like /campaing/view/
    <string:token> which would render the same content without tracking? Or to 
    save removing the tracking elements and create a special version of mail.mail 
    to be used in static linking from other websites? Hope I am clear :-)
    
    Best regards
    
    	Radovan
    
    On štvrtok 4. marca 2021 10:57:46 CET Simone Orsi wrote:
    
    > Hello,
    
    > this should address your issue
    
    > https://github.com/OCA/social/tree/11.0/mail_browser_view [1] And if you
    
    > want to test/dev your templates before sending them w/ real content you can
    
    > use https://github.com/OCA/social/tree/13.0/mail_layout_preview [2] HTH,
    
    > On Thu, Mar 4, 2021 at 9:21 AM Radovan Skolnik < radovan@skolnik.info [3] >
    
    > wrote: Hello,
    
    > let me start in this way. When receiving e-mail campaign mails from various
    
    > sources, they usually contain a link saying "If you cannot read this email
    
    > properly, click here to display on web" or something like that for cases
    
    > when email client forbids loading external content or just cannot render
    
    > the HTML content properly. The link leads to a webpage where there is
    
    > basically the same content as in the email.
    
    > Now I would like to achieve something similar. I.e. to be able to send
    
    > themed marketing emails and have them contain link to website page as a
    
    > alternative way of displaying the content. That webpage should be a normal
    
    > webpage - will be advertised through other means as well (Facebook,
    
    > Instagram, ...) Now I know I could design/create both email template and
    
    > website page but that just doubles the work. So I am looking for something
    
    > like one of these alternatives:
    
    > *) You design the email and have it render (create) the website page with
    
    > the same content.
    
    > *) The same as above but just the other way around. Create webpage and from
    
    > that have email generated.
    
    > *) Something else?
    
    > Can anyone advise anything in this regards? Or am I missing something as
    
    > usual? ;-)
    
    > Best regards
    
    > Radovan Skolnik
    
    > 
    
    > 
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 [4]
    
    > Post to: mailto: contributors@odoo-community.org [5]
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe [6]
    
    > 
    
    > --
    
    > Simone Orsi
    
    > Full stack Python web developer,
    
    > Odoo specialist,
    
    > Odoo Community Board Member,
    
    > Freelance
    
    > in love with open source.
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 [7]
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe [8]
    
    > 
    
    > 
    
    > 
    
    > [1] https://github.com/OCA/social/tree/11.0/mail_browser_view
    
    > [2] https://github.com/OCA/social/tree/13.0/mail_layout_preview
    
    > [3] mailto:radovan@skolnik.info
    
    > [4] https://odoo-community.org/groups/contributors-15
    
    > [5] mailto:contributors@odoo-community.org
    
    > [6] https://odoo-community.org/groups?unsubscribe
    
    > [7] https://odoo-community.org/groups/contributors-15
    
    > [8] https://odoo-community.org/groups?unsubscribe
    
    
    
    
    

    by Radovan Skolnik - 11:26 - 4 Mar 2021
  • Re: Partner Hierarchy module
    Contact relation is a tricky thing, takes a lot of insight and thinking as it relates to almost every area of odoo. It's master data, after all. 
    We also looked into the various OCA contact extensions, and they are great, but somtimes they were not enough to fulfill the needs of various customers. Thus we additionally created a contact location extension, contact ++, togheter with contact hierachy.
    In particular this can be helpful if a person is located in a company, but also works in a home office and is associated with a branch office of this organisation that is the regular work location of this contact. Electronic communication (phone/mail, etc) means are likewise related.

    BTW: Besides of 80 other enhancement,  as for 14 we now have developed and included a "studio" product and various shipping connectors into the ITISeasy.business distro. Lauching soon. 


    Von: "Holger Brunn" <mail@hunki-enterprises.com>
    An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
    Gesendet: Mittwoch, 3. März 2021 19:07:28
    Betreff: Re: Partner Hierarchy module

    > No hierarchy in the sense of parent_of though with 
    
    
    > https://github.com/OCA/partner-contact/tree/13.0/partner_multi_relation [1]
    
    
    > Only feedback, in environments with the granularity requested on the
    
    
    > partners, we simultaneously have requests for qualifications of relations
    
    
    > between partners without any parent relations as funders, investors,
    
    
    > administrators ... and partner_multi_relation module is a good complement
    
    when conceiving this originally, I did toy with a `transitive` checkbox, then 
    you could use transitive relations just like parent_of. But as the customer 
    lost interest in this feature, so did I. Maybe Daniel will add it?
    
    OTOH this case sounds more like composite relations: When partner A has 
    relation X with B, and B relation Y with C, then A and C have relation Z. This 
    also sounds like a very useful feature to have, and I think will be much less 
    computationally expensive to implement if you don't just store the transitive 
    closure above.
    
    
    
    -- 
    Your partner for the hard Odoo problems
    https://hunki-enterprises.com

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



    by Joerg Lorenz. - 11:21 - 4 Mar 2021
  • Re: Integration of mailing.mailing (Email marketing) templates and webiste pages?
    Oh, forgot to mention: this won't prevent you to write 2 templates BUT if you use 


    and


    You can get to workable solution w/outing getting insane as you can reuse styles and templates.

    On Thu, Mar 4, 2021 at 10:52 AM Simone Orsi <simahawk@gmail.com> wrote:
    Hello,


    And if you want to test/dev your templates before sending them w/ real content you can use https://github.com/OCA/social/tree/13.0/mail_layout_preview

    HTH,


    On Thu, Mar 4, 2021 at 9:21 AM Radovan Skolnik <radovan@skolnik.info> wrote:
    Hello,
    
    let me start in this way. When receiving e-mail campaign mails from various 
    sources, they usually contain a link saying "If you cannot read this email 
    properly, click here to display on web" or something like that for cases when 
    email client forbids loading external content or just cannot render the HTML 
    content properly. The link leads to a webpage where there is basically the 
    same content as in the email.
    
    Now I would like to achieve something similar. I.e. to be able to send themed 
    marketing emails and have them contain link to website page as a alternative 
    way of displaying the content. That webpage should be a normal webpage - will 
    be advertised through other means as well (Facebook, Instagram, ...)
    
    Now I know I could design/create both email template and website page but that 
    just doubles the work. So I am looking for something like one of these 
    alternatives:
    
    *) You design the email and have it render (create) the website page with the 
    same content.
    *) The same as above but just the other way around. Create webpage and from 
    that have email generated.
    *) Something else?
    
    Can anyone advise anything in this regards? Or am I missing something as 
    usual? ;-)
    
    Best regards
    
    	Radovan Skolnik
    
    
    

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


    --
    Simone Orsi

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

    by Simone Orsi - 10:56 - 4 Mar 2021
  • Re: Integration of mailing.mailing (Email marketing) templates and webiste pages?
    Hello,


    And if you want to test/dev your templates before sending them w/ real content you can use https://github.com/OCA/social/tree/13.0/mail_layout_preview

    HTH,


    On Thu, Mar 4, 2021 at 9:21 AM Radovan Skolnik <radovan@skolnik.info> wrote:
    Hello,
    
    let me start in this way. When receiving e-mail campaign mails from various 
    sources, they usually contain a link saying "If you cannot read this email 
    properly, click here to display on web" or something like that for cases when 
    email client forbids loading external content or just cannot render the HTML 
    content properly. The link leads to a webpage where there is basically the 
    same content as in the email.
    
    Now I would like to achieve something similar. I.e. to be able to send themed 
    marketing emails and have them contain link to website page as a alternative 
    way of displaying the content. That webpage should be a normal webpage - will 
    be advertised through other means as well (Facebook, Instagram, ...)
    
    Now I know I could design/create both email template and website page but that 
    just doubles the work. So I am looking for something like one of these 
    alternatives:
    
    *) You design the email and have it render (create) the website page with the 
    same content.
    *) The same as above but just the other way around. Create webpage and from 
    that have email generated.
    *) Something else?
    
    Can anyone advise anything in this regards? Or am I missing something as 
    usual? ;-)
    
    Best regards
    
    	Radovan Skolnik
    
    
    

    _______________________________________________
    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 - 10:56 - 4 Mar 2021
  • Re: Partner Hierarchy module

    p.s. partner in separate companies was meant to be a separate reply from our branch requirements 🙁 - Should have put a clearer divide....

    Richard deMeester

    Senior Development Analyst

    WilldooIT Pty Ltd

    E: richard.demeester@willdooit.com

    M: +61 403 76 76 76

    P: +61 3 9135 1900

    A: 10/435 Williamstown Road, Port Melbourne, Vic 3207

     

     

    Making growth through technology easy

     

     

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by WilldooIT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.



    From: Daniel Reis <dreis@opensourceintegrators.com>
    Sent: Thursday, 4 March 2021 3:27 AM
    To: Contributors <contributors@odoo-community.org>
    Subject: Partner Hierarchy module
     
    Hello,

    I'm quite sure there was an OCA module to enable multilevel Partner parent/child relations, but I'm not finding it right now.
    Use cases are Partner structures like: Holding company / Company / Branch Office / Contact.

    Am I missing something?

    Thanks!

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


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


    by "Richard deMeester" <richard.demeester@willdooit.com> - 10:30 - 4 Mar 2021
  • Re: Proposing moving Pledra product configurator to the OCA
    Sounds great
    
    @Daniel: I think we seldomly got more +1 within just two days. Would
    you mind to get in touch with Paul to make the first handover quickly.
    I think -from what we've discussed over the years- he would be more
    than happy to see things evolve like this! And its definitely an added
    value for the OCA ecosystem.
    
    Best Frederik
    
    Am Donnerstag, den 04.03.2021, 09:22 +0000 schrieb
    luc.demeyer@noviat.com:
    
    > We are running the configurator in production on Odoo 13.
    
    > 
    
    > A small couple of PR’s were sufficient for our use case.
    
    > 
    
    > I think we can use the current 13.0 code as the base for the OCA repo
    
    > and do the refactoring in a second stage.
    
    > 
    
    >  
    
    > 
    
    > Luc
    
    > 
    
    >  
    
    > 
    
    > From: Richard deMeester <richard.demeester@willdooit.com> 
    
    > Sent: Thursday, 4 March 2021 10:12
    
    > To: Contributors <contributors@odoo-community.org>
    
    > Subject: Re: Proposing moving Pledra product configurator to the OCA
    
    > 
    
    >  
    
    > 
    
    > Hi,
    
    > 
    
    >  
    
    > 
    
    > I had much involvement with this repo in v10, and ended up with a
    
    > multitude of enhancements and patches outside of the configurator.
    
    > 
    
    >  
    
    > 
    
    > It is an awesome tool, and while at the low end, the Odoo tool can do
    
    > a lot, at the top end, this is the deal.
    
    > 
    
    >  
    
    > 
    
    > Unfortunately, I feel that to bring it up to 13/14 needs a
    
    > considerable rethink in some of the architecture, but in my spare
    
    > time, I would be very keen to assist in this worthwhile project.
    
    > 
    
    >  
    
    > 
    
    > Richard
    
    > 
    
    >  
    
    > 
    
    > 
    
    > Richard deMeester
    
    > Senior Development Analyst
    
    > WilldooIT Pty Ltd
    
    > E: richard.demeester@willdooit.com
    
    > M: +61 403 76 76 76
    
    > P: +61 3 9135 1900
    
    > A: 10/435 Williamstown Road, Port Melbourne, Vic 3207
    
    >  
    
    >  
    
    > Making growth through technology easy
    
    >  
    
    > 
    
    >  
    
    > DISCLAIMER | This electronic message together with any attachments is
    
    > confidential. If you are not the recipient, do not copy, disclose, or
    
    > use the contents in any way. Please also advise us by e-mail that you
    
    > have received this message in error and then please destroy this
    
    > email and any of its attachments. WilldooIT Pty. Ltd. is not
    
    > responsible for any changes made to this message and/or any
    
    > attachments after sending by WilldooIT Pty. Ltd. WilldooIT Pty. Ltd.
    
    > use virus scanning software but exclude all liability for virus or
    
    > anything similar in this email or attachment.
    
    >  
    
    > 
    
    > From: Daniel Reis <dreis@opensourceintegrators.com>
    
    > Sent: Thursday, 4 March 2021 3:02 AM
    
    > To: Contributors <contributors@odoo-community.org>
    
    > Subject: Proposing moving Pledra product configurator to the OCA
    
    > 
    
    >  
    
    > 
    
    > Hello all,
    
    > 
    
    > Some of you may be familiar with the Pledra project, proposing an
    
    > advanced product configurator.
    
    > https://github.com/pledra/odoo-product-configurator
    
    > 
    
    > I don't think there is a comparable project in the OCA, and I would
    
    > like proposing to move Pledra under the OCA umbrella.
    
    > I contacted the original author, Paul Catinean, and he  is supportive
    
    > of this move.
    
    > There are quite a few details to get right, and I'm ready to take the
    
    > role and address them.
    
    > 
    
    > At this point the main question is, from a high level PoV if this
    
    > sounds like a good idea, and what concerns we should address when
    
    > moving forward.
    
    > 
    
    > Thank you, and thanks Paul for being onboard with this. 
    
    > 
    
    > 
    
    > --
    
    > 
    
    > DANIEL REIS
    
    > MANAGING DIRECTOR
    
    > 
    
    > M: +351 919991307
    
    > E: DReis@OpenSourceIntegrators.com
    
    > 
    
    > AV DOUTOR DESIDÉRIO CAMBOURNAC 12 • 2710-553 SINTRA, PORTUGAL
    
    > 
    
    >  
    
    > 
    
    > 
    
    > 
    
    > 
    
    > 
    
    > 
    
    > _______________________________________________
    
    > 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
    
    -- 
    Dr.-Ing. Frederik Kramer
    Geschäftsführer
            
    initOS GmbH
    An der Eisenbahn 1
    21224 Rosengarten
            
    Phone:  +49 4105 56156-12
    Fax:    +49 4105 56156-10
    Mobil:  +49 179 3901819
            
    Email: frederik.kramer@initos.com
    Web:   www.initos.com
            
    Geschäftsführung:
    Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
    
    Sitz der Gesellschaft: Rosengarten – Klecken
    Amtsgericht Tostedt, HRB 205226
    Steuer-Nr: 15/200/53247
    USt-IdNr.: DE815580155
    
    

    by Frederik Kramer - 10:30 - 4 Mar 2021
  • Re: Partner Hierarchy module

    Morning,

    Slightly off topic, but not entirely, we are looking at migrating the contact in several companies to v14, and it is not on the to be migrated list, does anyone know why?

    Internally, we have created a "holding compamy" module, but would be interested in an OCA inspired solution.

    We have a link between "branch" and "holding company", and then they can obvioulsy have their standard contacts beneath.  The nice things we added are:

    Check boxes on "does the invoice accumulate with the branch or the holding company", "statements go to branch / holding company" (some franchises want them to behave differently) , meaning on a case by case basis the call can be made to send the invoice up the chain or to the holding company.  We also have mods in the purchasing side to allow holding companies to have purchase prices, and when a PO goes to a branch, it uses the holding company's pricelist to buy.

    This has real use when dealing with "stores" from one chain, or "franchises".  These are common structures where two "company" entities need to be associated with each other.

    Richard



    Richard deMeester

    Senior Development Analyst

    WilldooIT Pty Ltd

    E: richard.demeester@willdooit.com

    M: +61 403 76 76 76

    P: +61 3 9135 1900

    A: 10/435 Williamstown Road, Port Melbourne, Vic 3207

     

     

    Making growth through technology easy

     

     

    DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by WilldooIT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.



    From: Holger Brunn <mail@hunki-enterprises.com>
    Sent: Thursday, 4 March 2021 5:07 AM
    To: Contributors <contributors@odoo-community.org>
    Subject: Re: Partner Hierarchy module
     
    > No hierarchy in the sense of parent_of though with 
    
    > https://github.com/OCA/partner-contact/tree/13.0/partner_multi_relation [1]
    
    > Only feedback, in environments with the granularity requested on the
    
    > partners, we simultaneously have requests for qualifications of relations
    
    > between partners without any parent relations as funders, investors,
    
    > administrators ... and partner_multi_relation module is a good complement
    
    when conceiving this originally, I did toy with a `transitive` checkbox, then 
    you could use transitive relations just like parent_of. But as the customer 
    lost interest in this feature, so did I. Maybe Daniel will add it?
    
    OTOH this case sounds more like composite relations: When partner A has 
    relation X with B, and B relation Y with C, then A and C have relation Z. This 
    also sounds like a very useful feature to have, and I think will be much less 
    computationally expensive to implement if you don't just store the transitive 
    closure above.
    
    
    -- 
    Your partner for the hard Odoo problems
    https://hunki-enterprises.com

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


    by "Richard deMeester" <richard.demeester@willdooit.com> - 10:30 - 4 Mar 2021