Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • spreadsheet_dashboard_oca's module: Is printing process available?
    Hi everyone,

    I currently use spreadsheet_dashboard_oca v16, which works well. However, I need to print (as PDF report) the content of  a spreadsheet.dashboard. Doesn't seem to be available with the current version of the module that I use.

    Did I miss something? Or is there another way (combination with an existing module, library) to realise that?

    Thanks in advance for your answer,




    --
    SMILE

    7 Boulevard Louis XIV 59800 Lille
    Laurent WEBER
    Développeur


    Twitter Facebook LinkedIn Github


    eco Pour la planète, n'imprimez ce mail que si c'est nécessaire
    by Laurent Weber - 03:36 - 5 Jul 2024

    2 replies 2 replies

  • Bank sync for Societe Generale (France)
    Hello,

    I hope this is not inappropriate for this list.

    I'm seeking for help on configuring the bank sync for Societe Generale.
    I see Saltedge support EBICS connection (with Odoo Enterprise Edition).

    But I'm being asked what format should be used for the bank statement:
    - CFONB 120
    - Swift MT 940
    - camt.053.001.02

    Anyone has gone though this before?

    Thank you!

    --
    DANIEL REIS
    MANAGING PARTNER

    Meet with me.
    M: +351 919 991 307
    E: dreis@OpenSourceIntegrators.com
    A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais

    [Logo OpenSourceIntegrators.com]

    by Daniel Reis - 10:35 - 5 Jul 2024

    6 replies 6 replies

  • New repo web-api-contrib
    Hi all,

    I'm proposing the creation of a new repo.


    Bests

    --
    Simone Orsi

    Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
    by Simone Orsi - 08:51 - 4 Jul 2024

    2 replies 2 replies

    • Re: New repo web-api-contrib 
      +1 too

On 04/07/2024 08:57, Simone Orsi wrote:

> Hi all,

> 

> I'm proposing the creation of a new repo.

> 

> Please check https://github.com/OCA/repo-maintainer-conf/pull/27 

> <https://github.com/OCA/repo-maintainer-conf/pull/27>

> 

> Bests

> 

> -- 

> Simone Orsi

> 

> Full stack Python web developer, Odoo specialist, Odoo Community Board 

> Member, in love with open source.

> 

> _______________________________________________

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

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

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

http://www.camptocamp.com
      by Alexandre Fayolle - 02:43 - 16 Jul 2024
    • Re: New repo web-api-contrib
      It makes sense: +1

      On Thu, Jul 4, 2024 at 8:57 AM Simone Orsi <notifications@odoo-community.org> wrote:
      Hi all,

      I'm proposing the creation of a new repo.


      Bests

      --
      Simone Orsi

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

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

      by Laurent Mignon - 12:36 - 4 Jul 2024
  • ODOO Update versions V.15 to V.17 - Historical data.

    Hello everyone.

     

    I am doing an upgrade project from version 15 to 17, I am not going to migrate historical data, I will leave the historical data in version 15, up to the date of Go Live, and, in version 17 I will start with initial balances and operations from scratch , example: New Purchase Orders, New customer orders, etc.

     

    My questions are: Is there a way to extract information from data that I will leave in version 15, for example: historical sales data, processed purchase orders, historical inventory data, etc.? Is there a connector or application for I can use Power BI to manage this data and be able to do reports, demand analysis, inventory analysis, etc.?

     

    Thank you all in advance for your comments and recommendations.

     

    Regards.

     

    HF

    by Hugo Ferrer - 11:40 - 3 Jul 2024

    3 replies 3 replies

    • Re: ODOO Update versions V.15 to V.17 - Historical data.
      On the contrary, I give more value to old data, and more with all the generative AIs coming. In this case, migrating the instance to v17 with OpenUpgrade (not yet there, but you can wait a bit or do a progressive migration - we do it constantly on our customers -) is the best strategy IMO.

      I introduce another factor on your previous suggestion: you have to maintain the old system. Apart from keeping the resources used by this system, their foundation software, libraries, etc should be also kept, and this is more and more a burden as times pass by. And even worse, both the foundation and the old Odoo version become vulnerable, as they are not updated by their manufacturers at any point, so you have an attack surface that is also a concern due to the RGPD.

      Regards.
      by Pedro M. Baeza - 09:01 - 4 Jul 2024
    • Re: ODOO Update versions V.15 to V.17 - Historical data.

      Hi Hugo,

      i agree with that Graeme said. In most cases where we had such challenges we simply decided to keep a version of the old system running (with the data of the last day in productive use and reset to that every night if necessary). This has 2 advantages

      1.) This is the cheapest approach that you can probably take (at the jost of manually logging on to an old system in the case its needed)

      2.) It literally shows you (either obvserved or measured by monitoring) how infrequently this system is being used.

      Any kind of integration just makes a system more complex and doesn't render the base of decision making better imho

      Best Frederik

      Am 04.07.24 um 00:19 schrieb Graeme Gellatly:
      Not for less than the cost of just migrating the historical data in the first place IMO if it is Odoo. Other historical systems, sometimes (most times) the cost isn't worth it.

      Indeed I have one project like that. A v7 instance still running after nearly 14 years plus 8 historical systems still after 25 years. One of the dumber things I agreed to.

      Any connector I'd do at database level. Most people that use Power BI, Jasper, Crystal or any reporting tools do at db level.

      In any case, consider that the historical data is immutable and devalues quickly. You can probably just produce the historical summary reports / flat tables you need and stick them in tables/views in whatever software you want including Odoo. Maybe override some reports to add Unions on the historical. In fact that is something I'm considering even for instances where all the data is migrated, it sucks waiting minutes for reports when 90% of the information is aggregations of historical data that will never change.



      On Thu, Jul 4, 2024 at 9:42 AM hugo.ferrer <notifications@odoo-community.org> wrote:

      Hello everyone.

       

      I am doing an upgrade project from version 15 to 17, I am not going to migrate historical data, I will leave the historical data in version 15, up to the date of Go Live, and, in version 17 I will start with initial balances and operations from scratch , example: New Purchase Orders, New customer orders, etc.

       

      My questions are: Is there a way to extract information from data that I will leave in version 15, for example: historical sales data, processed purchase orders, historical inventory data, etc.? Is there a connector or application for I can use Power BI to manage this data and be able to do reports, demand analysis, inventory analysis, etc.?

       

      Thank you all in advance for your comments and recommendations.

       

      Regards.

       

      HF

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

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

      -- 
Dr.-Ing. Frederik Kramer
Geschäftsführer

initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.

Tel:   +49 (0) 4181 13503 12
Fax:   +49 (0) 4181 13503 10
Mobil: +49 (0) 179 3901819

Email: frederik.kramer@initos.com
Internet: www.initos.com

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

Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
USt-IdNr.: DE815580155
Steuer-Nr: 15/200/53247
      by Frederik Kramer - 08:36 - 4 Jul 2024
    • Re: ODOO Update versions V.15 to V.17 - Historical data.
      Not for less than the cost of just migrating the historical data in the first place IMO if it is Odoo. Other historical systems, sometimes (most times) the cost isn't worth it.

      Indeed I have one project like that. A v7 instance still running after nearly 14 years plus 8 historical systems still after 25 years. One of the dumber things I agreed to.

      Any connector I'd do at database level. Most people that use Power BI, Jasper, Crystal or any reporting tools do at db level.

      In any case, consider that the historical data is immutable and devalues quickly. You can probably just produce the historical summary reports / flat tables you need and stick them in tables/views in whatever software you want including Odoo. Maybe override some reports to add Unions on the historical. In fact that is something I'm considering even for instances where all the data is migrated, it sucks waiting minutes for reports when 90% of the information is aggregations of historical data that will never change.



      On Thu, Jul 4, 2024 at 9:42 AM hugo.ferrer <notifications@odoo-community.org> wrote:

      Hello everyone.

       

      I am doing an upgrade project from version 15 to 17, I am not going to migrate historical data, I will leave the historical data in version 15, up to the date of Go Live, and, in version 17 I will start with initial balances and operations from scratch , example: New Purchase Orders, New customer orders, etc.

       

      My questions are: Is there a way to extract information from data that I will leave in version 15, for example: historical sales data, processed purchase orders, historical inventory data, etc.? Is there a connector or application for I can use Power BI to manage this data and be able to do reports, demand analysis, inventory analysis, etc.?

       

      Thank you all in advance for your comments and recommendations.

       

      Regards.

       

      HF

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

      by "Graeme Gellatly" <graeme@moahub.nz> - 12:18 - 4 Jul 2024
  • Odoo Community 17 issues

    Good morning,

    I hope you are doing great.

     

    We are starting to work with the Odoo Community platform and we have some situations, such as not being able to delete companies that we created in the system.

    Validation Error

    The operation cannot be completed: another model requires the record being deleted. If possible, archive it instead.

    Model: Picking Type (stock.picking.type)

    Constraint: stock_picking_type_company_id_fkey

     

    Another situation is that one of our employees, when clearing the browser cache, was deleted from the system and was unable to log in again, not even through a new invitation.

     

    I would love to hear from you if there are any solutions for the correct configuration and operation of the Odoo Community 17 system?

    I hope I hear from you soon.

    Thanks in advance!

    Best regards,

     

     

     

    by Dan Vasques - 09:56 - 2 Jul 2024

    7 attachments 7 attachments

    image007.gif
    image006.png
    image005.png
    image004.png
    image003.png
    image002.png
    image001.gif

    4 replies 4 replies

    • RE: Odoo Community 17 issues

      Dear,

       

      When you archived the partners, they stay in your res.partner table as a record. When there is a field with a ‘unique’ constraint, you cannot create another record with the same field value. When this field is not a relational field ( = not a link to another table ), the easiest way is to simply go in the database with pgadmin and change the field in the archived record in for example ‘value_old’. That’s fast and do the trick. Of course, maybe your field don’t need to be ‘unique’. Than you can build a small module and remove the constraint from the field.

       

      Kind regards,

       

      Van Hirtum Johan

       

      Van: Dan Vasques [mailto:notifications@odoo-community.org]
      Verzonden: dinsdag 2 juli 2024 13:57
      Aan: Contributors
      Onderwerp: R      E: Odoo Community 17 issues

       

      Hi everyone,

      I´ve archived the companies but when I try to add a new one, it keeps refusing. It comes up with the notification that it has to have a unique name.
      I believe that it has something to do with the previous ones that were deleted, as they have the same name.
      So, is there a way to really delete the archived ones?

      Thanks in advance for the assistance!

      Dan Vasques

       

      De: Tom Blauwendraat <notifications@odoo-community.org>
      Enviada: 2 de julho de 2024 09:09
      Para: Contributors <contributors@odoo-community.org>
      Assunto: Re: Odoo Community 17 issues

       

      Hi Dan,

      this is normal; deletion of records is tricky if there are already references to it. Archiving would be the best option here.

      This is the same in Odoo Enterprise, btw (Enterprise runs on the same core modules)

      -Tom

      On 7/2/24 09:57, Dan Vasques wrote:

      Good morning,

      I hope you are doing great.

       

      We are starting to work with the Odoo Community platform and we have some situations, such as not being able to delete companies that we created in the system.

      Validation Error

      The operation cannot be completed: another model requires the record being deleted. If possible, archive it instead.

      Model: Picking Type (stock.picking.type)

      Constraint: stock_picking_type_company_id_fkey

       

      Another situation is that one of our employees, when clearing the browser cache, was deleted from the system and was unable to log in again, not even through a new invitation.

       

      I would love to hear from you if there are any solutions for the correct configuration and operation of the Odoo Community 17 system?

      I hope I hear from you soon.

      Thanks in advance!

      Best regards,

       

       

       

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

      by johan - 02:15 - 2 Jul 2024
    • RE: Odoo Community 17 issues

      Hi everyone,

      I´ve archived the companies but when I try to add a new one, it keeps refusing. It comes up with the notification that it has to have a unique name.
      I believe that it has something to do with the previous ones that were deleted, as they have the same name.
      So, is there a way to really delete the archived ones?

      Thanks in advance for the assistance!

      Dan Vasques

       

      De: Tom Blauwendraat <notifications@odoo-community.org>
      Enviada: 2 de julho de 2024 09:09
      Para: Contributors <contributors@odoo-community.org>
      Assunto: Re: Odoo Community 17 issues

       

      Hi Dan,

      this is normal; deletion of records is tricky if there are already references to it. Archiving would be the best option here.

      This is the same in Odoo Enterprise, btw (Enterprise runs on the same core modules)

      -Tom

      On 7/2/24 09:57, Dan Vasques wrote:

      Good morning,

      I hope you are doing great.

       

      We are starting to work with the Odoo Community platform and we have some situations, such as not being able to delete companies that we created in the system.

      Validation Error

      The operation cannot be completed: another model requires the record being deleted. If possible, archive it instead.

      Model: Picking Type (stock.picking.type)

      Constraint: stock_picking_type_company_id_fkey

       

      Another situation is that one of our employees, when clearing the browser cache, was deleted from the system and was unable to log in again, not even through a new invitation.

       

      I would love to hear from you if there are any solutions for the correct configuration and operation of the Odoo Community 17 system?

      I hope I hear from you soon.

      Thanks in advance!

      Best regards,

       

       

       

      by Dan Vasques - 01:56 - 2 Jul 2024
    • RE: Odoo Community 17 issues

      Hi Tom,

      Thank you so much for the quick response.
      I really appreciate your assistance.

       

      Kind regards,

       

       

       

      De: Tom Blauwendraat <notifications@odoo-community.org>
      Enviada: 2 de julho de 2024 09:09
      Para: Contributors <contributors@odoo-community.org>
      Assunto: Re: Odoo Community 17 issues

       

      Hi Dan,

      this is normal; deletion of records is tricky if there are already references to it. Archiving would be the best option here.

      This is the same in Odoo Enterprise, btw (Enterprise runs on the same core modules)

      -Tom

      On 7/2/24 09:57, Dan Vasques wrote:

      Good morning,

      I hope you are doing great.

       

      We are starting to work with the Odoo Community platform and we have some situations, such as not being able to delete companies that we created in the system.

      Validation Error

      The operation cannot be completed: another model requires the record being deleted. If possible, archive it instead.

      Model: Picking Type (stock.picking.type)

      Constraint: stock_picking_type_company_id_fkey

       

      Another situation is that one of our employees, when clearing the browser cache, was deleted from the system and was unable to log in again, not even through a new invitation.

       

      I would love to hear from you if there are any solutions for the correct configuration and operation of the Odoo Community 17 system?

      I hope I hear from you soon.

      Thanks in advance!

      Best regards,

       

       

       

      by Dan Vasques - 10:31 - 2 Jul 2024

      7 attachments 7 attachments

      image007.gif
      image006.png
      image005.png
      image004.png
      image003.png
      image002.png
      image001.gif
    • Re: Odoo Community 17 issues

      Hi Dan,

      this is normal; deletion of records is tricky if there are already references to it. Archiving would be the best option here.

      This is the same in Odoo Enterprise, btw (Enterprise runs on the same core modules)

      -Tom

      On 7/2/24 09:57, Dan Vasques wrote:

      Good morning,

      I hope you are doing great.

       

      We are starting to work with the Odoo Community platform and we have some situations, such as not being able to delete companies that we created in the system.

      Validation Error

      The operation cannot be completed: another model requires the record being deleted. If possible, archive it instead.

      Model: Picking Type (stock.picking.type)

      Constraint: stock_picking_type_company_id_fkey

       

      Another situation is that one of our employees, when clearing the browser cache, was deleted from the system and was unable to log in again, not even through a new invitation.

       

      I would love to hear from you if there are any solutions for the correct configuration and operation of the Odoo Community 17 system?

      I hope I hear from you soon.

      Thanks in advance!

      Best regards,

       

       

       

      _______________________________________________
      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 - 10:02 - 2 Jul 2024
  • v18 early migration work based on master
    Hi everybody,

    We would like to start working on migrating some base modules to v18 before it gets released.

    AFAIR there's no "official" policy for it, if not "do it on your own fork and then open PRs when the release is out".

    From my POV it would be nice to define one.

    For the branch, I see these options:

    1. add a `master` branch that can be used w/ any version
    2. add a `$nextVersion-[master|dev]` branch that can be used w/ odoo master for a specific version
    3. simply have $nextVersion branch and stick to version policy nr 2 (see below)

    For the module version:

    1. append `dev`to the version (eg: 18.0.1.0.0dev)
    2. start w/ a number lesser than 1.0.0 and switch to 1.0.0 only when the release is out (eg: 18.0.0.0.1)

    I'd go for branch opt 3 + mod version opt 2.

    For the test suite: I'm not sure we have a way to run tests against master ATM.

    Am I missing something?

    In general, what do you think?

    --
    Simone Orsi

    Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
    by Simone Orsi - 12:41 - 1 Jul 2024

    9 replies 9 replies

    • Re: Re: v18 early migration work based on master 
      Hallo liebe Leute,

Unser Büro ist in der Zeit vom Mo., 5. August bis Mo. 13. August nicht besetzt.

Sobald wir zurück sind, melden wir uns sobald als möglich zurück.

Liebe Grüße und schöne Sommerferien,

Das Team von it-fact

Am 18.07.2024 um 15:02 schrieb David Beal <notifications@odoo-community.org>:


> Hi,

> 

> Allowing a PR on a future version is a good way to go further.

> We are in august, and the new version is in October, then we don't have so much time to move, 

> then the roadmap must be short I suppose.

> 

> Regards

> 

> David BEAL

> Akretion

> Consultant ERP Odoo

> 

> 

> Le jeu. 18 juil. 2024 à 11:47, Stéphane Bidoul <notifications@odoo-community.org> a écrit :

> Hm, I don't have a good feeling with merging stuff that is not proven compatible with the real 18.0, that's going to be confusing.

> Also, all the dependency management relies on merged stuff being available on PyPI.

> 

> But that can still be considered in a second step when we have learned to fly with unmerged PRs first.

> 

> -sbi

> 

> On Thu, Jul 18, 2024 at 11:23 AM Simone Orsi <simahawk@gmail.com> wrote:

> Thanks everybody for the feedback :)

> 

> @Stéphane Bidoul regarding

> 

> I'd also suggest not merging nor pushing to PyPI until the Odoo 18.0 branch has been created, so work only with git PR references in test-requirements.txt for dependencies. 

> So we'd probably need to add protections in the bot to avoid premature merges or pushes to PyPI

> 

> I agree on not pushing to PyPI but we should merge, to not enter a valley of pain later.

> IMO the version of the module should serve as the way to check if it is fully migrated or not and we could update the repo readme generation to make it more visible, same for the module's readme. Maybe a ribbon?

> 

> We could also add a non blocking warning test in the CI.

> 

> WDYT?

>  

> 

> On Tue, Jul 16, 2024 at 3:27 PM Mignon, Laurent <notifications@odoo-community.org> wrote:

> >  I'd go for branch opt 3 + mod version opt 2.

> 

> +1

> 

> On Tue, Jul 16, 2024 at 2:48 PM Alexandre Fayolle <notifications@odoo-community.org> wrote:

> I think this could be nice.

> 

> I would favor Option 2 for branch naming. This could be an indicator for 

> the OCAbot to behave differently about the version numbers when a PR s 

> merged (and we can have option 1 for module version).

> 

> 

> Alexandre

> 

> 

> On 01/07/2024 12:42, Simone Orsi wrote:

> 

> 

> 

> 

> > Hi everybody,

> 

> 

> 

> 

> > 

> 

> 

> 

> 

> > We would like to start working on migrating some base modules to v18 

> 

> 

> 

> 

> > before it gets released.

> 

> 

> 

> 

> > 

> 

> 

> 

> 

> > AFAIR there's no "official" policy for it, if not "do it on your own 

> 

> 

> 

> 

> > fork and then open PRs when the release is out".

> 

> 

> 

> 

> > 

> 

> 

> 

> 

> >  From my POV it would be nice to define one.

> 

> 

> 

> 

> > 

> 

> 

> 

> 

> > For the branch, I see these options:

> 

> 

> 

> 

> > 

> 

> 

> 

> 

> > 1. add a `master` branch that can be used w/ any version

> 

> 

> 

> 

> > 2. add a `$nextVersion-[master|dev]` branch that can be used w/ odoo 

> 

> 

> 

> 

> > master for a specific version

> 

> 

> 

> 

> > 3. simply have $nextVersion branch and stick to version policy nr 2 (see 

> 

> 

> 

> 

> > below)

> 

> 

> 

> 

> > 

> 

> 

> 

> 

> > For the module version:

> 

> 

> 

> 

> > 

> 

> 

> 

> 

> > 1. append `dev`to the version (eg: 18.0.1.0.0dev)

> 

> 

> 

> 

> > 2. start w/ a number lesser than 1.0.0 and switch to 1.0.0 only when the 

> 

> 

> 

> 

> > release is out (eg: 18.0.0.0.1)

> 

> 

> 

> 

> > 

> 

> 

> 

> 

> > I'd go for branch opt 3 + mod version opt 2.

> 

> 

> 

> 

> > 

> 

> 

> 

> 

> > For the test suite: I'm not sure we have a way to run tests against 

> 

> 

> 

> 

> > master ATM.

> 

> 

> 

> 

> > 

> 

> 

> 

> 

> > Am I missing something?

> 

> 

> 

> 

> > 

> 

> 

> 

> 

> > In general, what do you think?

> 

> 

> 

> 

> > 

> 

> 

> 

> 

> > -- 

> 

> 

> 

> 

> > Simone Orsi

> 

> 

> 

> 

> > 

> 

> 

> 

> 

> > Full stack Python web developer, Odoo specialist, Odoo Community Board 

> 

> 

> 

> 

> > Member, in love with open source.

> 

> 

> 

> 

> > 

> 

> 

> 

> 

> > _______________________________________________

> 

> 

> 

> 

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

> 

> 

> 

> 

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

> 

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

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

> 

> 

> -- 

> Simone Orsi

> 

> Full stack Python web developer,

> Odoo specialist,

> Odoo Community Board Member,

> in love with open source.

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

> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe
>
      by Andreas Maurhart - 08:06 - 5 Aug 2024

      1 attachments 1 attachments

      attachment
    • Re: v18 early migration work based on master
      Hi,

      Allowing a PR on a future version is a good way to go further.
      We are in august, and the new version is in October, then we don't have so much time to move, 
      then the roadmap must be short I suppose.

      Regards

      David BEAL
      Consultant ERP Odoo


      Le jeu. 18 juil. 2024 à 11:47, Stéphane Bidoul <notifications@odoo-community.org> a écrit :
      Hm, I don't have a good feeling with merging stuff that is not proven compatible with the real 18.0, that's going to be confusing.
      Also, all the dependency management relies on merged stuff being available on PyPI.

      But that can still be considered in a second step when we have learned to fly with unmerged PRs first.

      -sbi

      On Thu, Jul 18, 2024 at 11:23 AM Simone Orsi <simahawk@gmail.com> wrote:
      Thanks everybody for the feedback :)


      I'd also suggest not merging nor pushing to PyPI until the Odoo 18.0 branch has been created, so work only with git PR references in test-requirements.txt for dependencies.
      So we'd probably need to add protections in the bot to avoid premature merges or pushes to PyPI

      I agree on not pushing to PyPI but we should merge, to not enter a valley of pain later.
      IMO the version of the module should serve as the way to check if it is fully migrated or not and we could update the repo readme generation to make it more visible, same for the module's readme. Maybe a ribbon?

      We could also add a non blocking warning test in the CI.

      WDYT?
       

      On Tue, Jul 16, 2024 at 3:27 PM Mignon, Laurent <notifications@odoo-community.org> wrote:
      >  I'd go for branch opt 3 + mod version opt 2.

      +1

      On Tue, Jul 16, 2024 at 2:48 PM Alexandre Fayolle <notifications@odoo-community.org> wrote:
      I think this could be nice.

I would favor Option 2 for branch naming. This could be an indicator for 
the OCAbot to behave differently about the version numbers when a PR s 
merged (and we can have option 1 for module version).


Alexandre


On 01/07/2024 12:42, Simone Orsi wrote:




> Hi everybody,




> 




> We would like to start working on migrating some base modules to v18 




> before it gets released.




> 




> AFAIR there's no "official" policy for it, if not "do it on your own 




> fork and then open PRs when the release is out".




> 




>  From my POV it would be nice to define one.




> 




> For the branch, I see these options:




> 




> 1. add a `master` branch that can be used w/ any version




> 2. add a `$nextVersion-[master|dev]` branch that can be used w/ odoo 




> master for a specific version




> 3. simply have $nextVersion branch and stick to version policy nr 2 (see 




> below)




> 




> For the module version:




> 




> 1. append `dev`to the version (eg: 18.0.1.0.0dev)




> 2. start w/ a number lesser than 1.0.0 and switch to 1.0.0 only when the 




> release is out (eg: 18.0.0.0.1)




> 




> I'd go for branch opt 3 + mod version opt 2.




> 




> For the test suite: I'm not sure we have a way to run tests against 




> master ATM.




> 




> Am I missing something?




> 




> In general, what do you think?




> 




> -- 




> Simone Orsi




> 




> Full stack Python web developer, Odoo specialist, Odoo Community Board 




> Member, in love with open source.




> 




> _______________________________________________




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




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

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

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



      --
      Simone Orsi

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

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

      by David BEAL - 03:01 - 18 Jul 2024
    • Re: v18 early migration work based on master
      Hm, I don't have a good feeling with merging stuff that is not proven compatible with the real 18.0, that's going to be confusing.
      Also, all the dependency management relies on merged stuff being available on PyPI.

      But that can still be considered in a second step when we have learned to fly with unmerged PRs first.

      -sbi

      On Thu, Jul 18, 2024 at 11:23 AM Simone Orsi <simahawk@gmail.com> wrote:
      Thanks everybody for the feedback :)


      I'd also suggest not merging nor pushing to PyPI until the Odoo 18.0 branch has been created, so work only with git PR references in test-requirements.txt for dependencies.
      So we'd probably need to add protections in the bot to avoid premature merges or pushes to PyPI

      I agree on not pushing to PyPI but we should merge, to not enter a valley of pain later.
      IMO the version of the module should serve as the way to check if it is fully migrated or not and we could update the repo readme generation to make it more visible, same for the module's readme. Maybe a ribbon?

      We could also add a non blocking warning test in the CI.

      WDYT?
       

      On Tue, Jul 16, 2024 at 3:27 PM Mignon, Laurent <notifications@odoo-community.org> wrote:
      >  I'd go for branch opt 3 + mod version opt 2.

      +1

      On Tue, Jul 16, 2024 at 2:48 PM Alexandre Fayolle <notifications@odoo-community.org> wrote:
      I think this could be nice.

I would favor Option 2 for branch naming. This could be an indicator for 
the OCAbot to behave differently about the version numbers when a PR s 
merged (and we can have option 1 for module version).


Alexandre


On 01/07/2024 12:42, Simone Orsi wrote:



> Hi everybody,



> 



> We would like to start working on migrating some base modules to v18 



> before it gets released.



> 



> AFAIR there's no "official" policy for it, if not "do it on your own 



> fork and then open PRs when the release is out".



> 



>  From my POV it would be nice to define one.



> 



> For the branch, I see these options:



> 



> 1. add a `master` branch that can be used w/ any version



> 2. add a `$nextVersion-[master|dev]` branch that can be used w/ odoo 



> master for a specific version



> 3. simply have $nextVersion branch and stick to version policy nr 2 (see 



> below)



> 



> For the module version:



> 



> 1. append `dev`to the version (eg: 18.0.1.0.0dev)



> 2. start w/ a number lesser than 1.0.0 and switch to 1.0.0 only when the 



> release is out (eg: 18.0.0.0.1)



> 



> I'd go for branch opt 3 + mod version opt 2.



> 



> For the test suite: I'm not sure we have a way to run tests against 



> master ATM.



> 



> Am I missing something?



> 



> In general, what do you think?



> 



> -- 



> Simone Orsi



> 



> Full stack Python web developer, Odoo specialist, Odoo Community Board 



> Member, in love with open source.



> 



> _______________________________________________



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



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

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

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



      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
      by Stéphane Bidoul - 11:46 - 18 Jul 2024
    • Re: v18 early migration work based on master
      Thanks everybody for the feedback :)


      I'd also suggest not merging nor pushing to PyPI until the Odoo 18.0 branch has been created, so work only with git PR references in test-requirements.txt for dependencies.
      So we'd probably need to add protections in the bot to avoid premature merges or pushes to PyPI

      I agree on not pushing to PyPI but we should merge, to not enter a valley of pain later.
      IMO the version of the module should serve as the way to check if it is fully migrated or not and we could update the repo readme generation to make it more visible, same for the module's readme. Maybe a ribbon?

      We could also add a non blocking warning test in the CI.

      WDYT?
       

      On Tue, Jul 16, 2024 at 3:27 PM Mignon, Laurent <notifications@odoo-community.org> wrote:
      >  I'd go for branch opt 3 + mod version opt 2.

      +1

      On Tue, Jul 16, 2024 at 2:48 PM Alexandre Fayolle <notifications@odoo-community.org> wrote:
      I think this could be nice.

I would favor Option 2 for branch naming. This could be an indicator for 
the OCAbot to behave differently about the version numbers when a PR s 
merged (and we can have option 1 for module version).


Alexandre


On 01/07/2024 12:42, Simone Orsi wrote:



> Hi everybody,



> 



> We would like to start working on migrating some base modules to v18 



> before it gets released.



> 



> AFAIR there's no "official" policy for it, if not "do it on your own 



> fork and then open PRs when the release is out".



> 



>  From my POV it would be nice to define one.



> 



> For the branch, I see these options:



> 



> 1. add a `master` branch that can be used w/ any version



> 2. add a `$nextVersion-[master|dev]` branch that can be used w/ odoo 



> master for a specific version



> 3. simply have $nextVersion branch and stick to version policy nr 2 (see 



> below)



> 



> For the module version:



> 



> 1. append `dev`to the version (eg: 18.0.1.0.0dev)



> 2. start w/ a number lesser than 1.0.0 and switch to 1.0.0 only when the 



> release is out (eg: 18.0.0.0.1)



> 



> I'd go for branch opt 3 + mod version opt 2.



> 



> For the test suite: I'm not sure we have a way to run tests against 



> master ATM.



> 



> Am I missing something?



> 



> In general, what do you think?



> 



> -- 



> Simone Orsi



> 



> Full stack Python web developer, Odoo specialist, Odoo Community Board 



> Member, in love with open source.



> 



> _______________________________________________



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



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

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

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



      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
      by Simone Orsi - 11:25 - 18 Jul 2024
    • Re: v18 early migration work based on master
      >  I'd go for branch opt 3 + mod version opt 2.

      +1

      On Tue, Jul 16, 2024 at 2:48 PM Alexandre Fayolle <notifications@odoo-community.org> wrote:
      I think this could be nice.

I would favor Option 2 for branch naming. This could be an indicator for 
the OCAbot to behave differently about the version numbers when a PR s 
merged (and we can have option 1 for module version).


Alexandre


On 01/07/2024 12:42, Simone Orsi wrote:


> Hi everybody,


> 


> We would like to start working on migrating some base modules to v18 


> before it gets released.


> 


> AFAIR there's no "official" policy for it, if not "do it on your own 


> fork and then open PRs when the release is out".


> 


>  From my POV it would be nice to define one.


> 


> For the branch, I see these options:


> 


> 1. add a `master` branch that can be used w/ any version


> 2. add a `$nextVersion-[master|dev]` branch that can be used w/ odoo 


> master for a specific version


> 3. simply have $nextVersion branch and stick to version policy nr 2 (see 


> below)


> 


> For the module version:


> 


> 1. append `dev`to the version (eg: 18.0.1.0.0dev)


> 2. start w/ a number lesser than 1.0.0 and switch to 1.0.0 only when the 


> release is out (eg: 18.0.0.0.1)


> 


> I'd go for branch opt 3 + mod version opt 2.


> 


> For the test suite: I'm not sure we have a way to run tests against 


> master ATM.


> 


> Am I missing something?


> 


> In general, what do you think?


> 


> -- 


> Simone Orsi


> 


> Full stack Python web developer, Odoo specialist, Odoo Community Board 


> Member, in love with open source.


> 


> _______________________________________________


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


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

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

      by Laurent Mignon - 03:26 - 16 Jul 2024

  • Sensitive information fields - controlled access, encryption, display, ...

    Hello,


    I am dealing with a scenario where some personal data needs to be handled in a special way. Unprivileged users should not see them at all or only see their encrypted/hashed/garbled versions. Privileged users should have a way to display the data ideally after some additional step which would be logged. Ideally the sensitive data should be encrypted at database level.


    Has anyone has similar requirements? Is there any module providing foundation / ideas for such thing? Setup of employee classes (hr.employee, hr.employee.base and hr.employee.public) and groups seems could be somewhat an inspiration to this.


    Any ideas / pointers are welcome. Thank you very much.


    Best regards


        Radovan Skolnik

    by Radovan Skolnik - 11:46 - 1 Jul 2024

    1 replies 1 replies

  • [17.0]Website : How to switch display from B2B to B2c
    Hi everyone,

    Hope you're doing well,

    Is anyone know how to toogle the display between b2b and b2c on the web site for a v17 ?

    Any tips/advice will be appreciated,

    Regards

    Vertical seprator

    Florent THOMAS

    ☎ +33 972 457 755
    ✉ florent.thomas@mind-and-go.com

    Mind & Go
    14, Rue Pierre Cartelet | 66000 PERPIGNAN

    Logo Mind And Go Facebook Mind And Go Twitter Mind And Go LinkedIn Mind And Go
    by Florent THOMAS - 10:46 - 1 Jul 2024

    8 replies 8 replies

    • Re: Re: [17.0]Website : How to switch display from B2B to B2c 
      Hallo liebe Leute,

Unser Büro ist in der Zeit vom Mo., 5. August bis Mo. 13. August nicht besetzt.

Sobald wir zurück sind, melden wir uns sobald als möglich zurück.

Liebe Grüße und schöne Sommerferien,

Das Team von it-fact

Am 01.07.2024 um 15:12 schrieb Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT <notifications@odoo-community.org>:


> Hey radovan,

> Thanks for the hint. I’ll have a look. In that particular case I would stick to the setup, as we have some products published on b2b and not on b2c and the other way around.

> But for the future… 

> 

> Many thanks 

> 

> Von: Radovan Skolnik <notifications@odoo-community.org>

> Gesendet: Monday, July 1, 2024 3:02:00 PM

> An: Contributors <contributors@odoo-community.org>

> Betreff: Re: [17.0]Website : How to switch display from B2B to B2c

>  

> 

> ACHTUNG! Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist. 

> Nils,

> 

> check out this one: https://github.com/OCA/e-commerce/tree/15.0/website_sale_b2x_alt_price

> 

> Best regards

> 

>     Radovan

> 

> On pondelok 1. júla 2024 14:17:28 CEST Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT wrote:

> > Just to let you know… when I tried showing b2b and b2c orices on the same

> > page, there has been some side effects when calculating the price. I ended

> > up to have one site for b2b and one for b2c with fixed settings concerning

> > tax display. This helped me to sort out  the wrong calculation when

> > switching back and forth between b2b  and b2c.

> > 

> > Cheers nils

> > 

> > 

> > 

> > *Von:* Florent Thomas <notifications@odoo-community.org>

> > *Gesendet:* Monday, July 1, 2024 12:37:03 PM

> > *An:* Contributors <contributors@odoo-community.org>

> > *Betreff:* Re: [17.0]Website : How to switch display from B2B to B2c

> > 

> > 

> > 

> > 

> > 

> > *ACHTUNG!* Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie

> > nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den

> > Absender und wissen, dass der Inhalt sicher ist.

> > 

> > 

> > 

> > 

> > Hi,

> > 

> > 

> > Great thanks for this tips.

> > 

> > We're gonna hook the display of this fioeld to be able to let the end user

> > toggle between B2C and B2B views

> > 

> > 

> > regards

> > 

> > 

> > 

> > 

> > 

> > Florent THOMAS*

> > ☎ +33 972 457 755

> > ✉

> > florent.thomas@mind-and-go.com [1]

> > 

> > 

> > *Mind & Go*

> > 14, Rue Pierre Cartelet | 66000 PERPIGNAN

> > None [2]

> > [3]

> > None [4]

> > [5]

> > 

> > 

> > 

> > 

> > 

> > *De: *"Radovan Skolnik" <notifications@odoo-community.org>

> > *À: *"contributors" <contributors@odoo-community.org>

> > *Envoyé: *Lundi 1 Juillet 2024 11:52:23

> > *Objet: *Re: [17.0]Website : How to switch display from B2B to B2c

> > 

> > 

> > 

> > Hi,

> > 

> > there is a option in Website configuration on whether to show prices with

> > (B2C) or without (B2B) taxes:

> > 

> > 

> > Then there is a configuration snippet on checkout page that allows to

> > display B2B fields:

> > 

> > 

> > Best regards

> > 

> > Radovan Skolnik

> > 

> > On pondelok 1. júla 2024 10:48:00 CEST Florent Thomas wrote:

> > > Hi everyone,

> > > Hope you're doing well,

> > > Is anyone know how to toogle the display between b2b and b2c on the web

> > > site for a v17 ? Any tips/advice will be appreciated,

> > > Regards

> > > Florent THOMAS*

> > > ☎ +33 972 457 755

> > > ✉ florent.thomas@mind-and-go.com [1]

> > > *Mind & Go*

> > > 14, Rue Pierre Cartelet | 66000 PERPIGNAN

> > > [2]  None [3]   [4]   [5]

> > > _______________________________________________

> > > Mailing-List: https://odoo-community.org/groups/contributors-15 [6]

> > > Post to: mailto:contributors@odoo-community.org

> > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [7]

> > > 

> > > 

> > > 

> > > [1] mailto:florent.thomas@mind-and-go.com

> > > [2] https://mind-and-go.com/

> > > [3] https://www.facebook.com/Mind-And-Go-296462057466508/

> > > [4] https://twitter.com/MindAndGo

> > > [5] https://www.linkedin.com/company/mind-and-go

> > > [6] https://odoo-community.org/groups/contributors-15

> > > [7] https://odoo-community.org/groups?unsubscribe

> > 

> > _______________________________________________

> > Mailing-List:

> > https://odoo-community.org/groups/contributors-15 [6]

> > Post to: mailto:contributors@odoo-community.org

> > Unsubscribe:

> > https://odoo-community.org/groups?unsubscribe [7]

> > 

> > 

> > 

> > 

> > _______________________________________________

> > Mailing-List:

> > https://odoo-community.org/groups/contributors-15 [8]

> > Post to: mailto:contributors@odoo-community.org

> > Unsubscribe:

> > https://odoo-community.org/groups?unsubscribe [9]

> > 

> > 

> > 

> > 

> > _______________________________________________

> > Mailing-List: https://odoo-community.org/groups/contributors-15 [10]

> > Post to: mailto:contributors@odoo-community.org

> > Unsubscribe: https://odoo-community.org/groups?unsubscribe [11]

> > 

> > 

> > 

> > [1] mailto:florent.thomas@mind-and-go.com

> > [2] https://mind-and-go.com/

> > [3] https://www.facebook.com/Mind-And-Go-296462057466508/

> > [4] https://twitter.com/MindAndGo

> > [5] https://www.linkedin.com/company/mind-and-go

> > [6] https://odoo-community.org/groups/contributors-15

> > [7] https://odoo-community.org/groups?unsubscribe

> > [8] https://odoo-community.org/groups/contributors-15

> > [9] https://odoo-community.org/groups?unsubscribe

> > [10] https://odoo-community.org/groups/contributors-15

> > [11] 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 Andreas Maurhart - 08:21 - 5 Aug 2024

      1 attachments 1 attachments

      attachment
    • Re: Re: [17.0]Website : How to switch display from B2B to B2c 
      Hallo liebe Leute,

Unser Büro ist in der Zeit vom Mo., 5. August bis Mo. 13. August nicht besetzt.

Sobald wir zurück sind, melden wir uns sobald als möglich zurück.

Liebe Grüße und schöne Sommerferien,

Das Team von it-fact

Am 01.07.2024 um 15:02 schrieb Radovan Skolnik <notifications@odoo-community.org>:


> Nils,

> 

> check out this one: https://github.com/OCA/e-commerce/tree/15.0/website_sale_b2x_alt_price

> 

> Best regards

> 

>     Radovan

> 

> On pondelok 1. júla 2024 14:17:28 CEST Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT wrote:

> > Just to let you know… when I tried showing b2b and b2c orices on the same

> > page, there has been some side effects when calculating the price. I ended

> > up to have one site for b2b and one for b2c with fixed settings concerning

> > tax display. This helped me to sort out  the wrong calculation when

> > switching back and forth between b2b  and b2c.

> > 

> > Cheers nils

> > 

> > 

> > 

> > *Von:* Florent Thomas <notifications@odoo-community.org>

> > *Gesendet:* Monday, July 1, 2024 12:37:03 PM

> > *An:* Contributors <contributors@odoo-community.org>

> > *Betreff:* Re: [17.0]Website : How to switch display from B2B to B2c

> > 

> > 

> > 

> > 

> > 

> > *ACHTUNG!* Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie

> > nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den

> > Absender und wissen, dass der Inhalt sicher ist.

> > 

> > 

> > 

> > 

> > Hi,

> > 

> > 

> > Great thanks for this tips.

> > 

> > We're gonna hook the display of this fioeld to be able to let the end user

> > toggle between B2C and B2B views

> > 

> > 

> > regards

> > 

> > 

> > 

> > 

> > 

> > Florent THOMAS*

> > ☎ +33 972 457 755

> > ✉

> > florent.thomas@mind-and-go.com [1]

> > 

> > 

> > *Mind & Go*

> > 14, Rue Pierre Cartelet | 66000 PERPIGNAN

> > None [2]

> > [3]

> > None [4]

> > [5]

> > 

> > 

> > 

> > 

> > 

> > *De: *"Radovan Skolnik" <notifications@odoo-community.org>

> > *À: *"contributors" <contributors@odoo-community.org>

> > *Envoyé: *Lundi 1 Juillet 2024 11:52:23

> > *Objet: *Re: [17.0]Website : How to switch display from B2B to B2c

> > 

> > 

> > 

> > Hi,

> > 

> > there is a option in Website configuration on whether to show prices with

> > (B2C) or without (B2B) taxes:

> > 

> > 

> > Then there is a configuration snippet on checkout page that allows to

> > display B2B fields:

> > 

> > 

> > Best regards

> > 

> > Radovan Skolnik

> > 

> > On pondelok 1. júla 2024 10:48:00 CEST Florent Thomas wrote:

> > > Hi everyone,

> > > Hope you're doing well,

> > > Is anyone know how to toogle the display between b2b and b2c on the web

> > > site for a v17 ? Any tips/advice will be appreciated,

> > > Regards

> > > Florent THOMAS*

> > > ☎ +33 972 457 755

> > > ✉ florent.thomas@mind-and-go.com [1]

> > > *Mind & Go*

> > > 14, Rue Pierre Cartelet | 66000 PERPIGNAN

> > > [2]  None [3]   [4]   [5]

> > > _______________________________________________

> > > Mailing-List: https://odoo-community.org/groups/contributors-15 [6]

> > > Post to: mailto:contributors@odoo-community.org

> > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [7]

> > > 

> > > 

> > > 

> > > [1] mailto:florent.thomas@mind-and-go.com

> > > [2] https://mind-and-go.com/

> > > [3] https://www.facebook.com/Mind-And-Go-296462057466508/

> > > [4] https://twitter.com/MindAndGo

> > > [5] https://www.linkedin.com/company/mind-and-go

> > > [6] https://odoo-community.org/groups/contributors-15

> > > [7] https://odoo-community.org/groups?unsubscribe

> > 

> > _______________________________________________

> > Mailing-List:

> > https://odoo-community.org/groups/contributors-15 [6]

> > Post to: mailto:contributors@odoo-community.org

> > Unsubscribe:

> > https://odoo-community.org/groups?unsubscribe [7]

> > 

> > 

> > 

> > 

> > _______________________________________________

> > Mailing-List:

> > https://odoo-community.org/groups/contributors-15 [8]

> > Post to: mailto:contributors@odoo-community.org

> > Unsubscribe:

> > https://odoo-community.org/groups?unsubscribe [9]

> > 

> > 

> > 

> > 

> > _______________________________________________

> > Mailing-List: https://odoo-community.org/groups/contributors-15 [10]

> > Post to: mailto:contributors@odoo-community.org

> > Unsubscribe: https://odoo-community.org/groups?unsubscribe [11]

> > 

> > 

> > 

> > [1] mailto:florent.thomas@mind-and-go.com

> > [2] https://mind-and-go.com/

> > [3] https://www.facebook.com/Mind-And-Go-296462057466508/

> > [4] https://twitter.com/MindAndGo

> > [5] https://www.linkedin.com/company/mind-and-go

> > [6] https://odoo-community.org/groups/contributors-15

> > [7] https://odoo-community.org/groups?unsubscribe

> > [8] https://odoo-community.org/groups/contributors-15

> > [9] https://odoo-community.org/groups?unsubscribe

> > [10] https://odoo-community.org/groups/contributors-15

> > [11] 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 Andreas Maurhart - 08:21 - 5 Aug 2024

      1 attachments 1 attachments

      attachment
    • Re: Re: [17.0]Website : How to switch display from B2B to B2c 
      Hallo liebe Leute,

Unser Büro ist in der Zeit vom Mo., 5. August bis Mo. 13. August nicht besetzt.

Sobald wir zurück sind, melden wir uns sobald als möglich zurück.

Liebe Grüße und schöne Sommerferien,

Das Team von it-fact

Am 01.07.2024 um 11:52 schrieb Radovan Skolnik <notifications@odoo-community.org>:


> Hi,

> 

> there is a option in Website configuration on whether to show prices with (B2C) or without (B2B) taxes:
      by Andreas Maurhart - 08:21 - 5 Aug 2024

      5 attachments 5 attachments

      attachment
      attachment
      attachment
      attachment
      attachment
    • Re: [17.0]Website : How to switch display from B2B to B2c
      Hey radovan,
      Thanks for the hint. I’ll have a look. In that particular case I would stick to the setup, as we have some products published on b2b and not on b2c and the other way around.
      But for the future… 

      Many thanks 
      Von: Radovan Skolnik <notifications@odoo-community.org>
      Gesendet: Monday, July 1, 2024 3:02:00 PM
      An: Contributors <contributors@odoo-community.org>
      Betreff: Re: [17.0]Website : How to switch display from B2B to B2c
       

      ACHTUNG! Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.

      Nils,


      check out this one: https://github.com/OCA/e-commerce/tree/15.0/website_sale_b2x_alt_price


      Best regards


          Radovan


      On pondelok 1. júla 2024 14:17:28 CEST Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT wrote:

      > Just to let you know… when I tried showing b2b and b2c orices on the same

      > page, there has been some side effects when calculating the price. I ended

      > up to have one site for b2b and one for b2c with fixed settings concerning

      > tax display. This helped me to sort out  the wrong calculation when

      > switching back and forth between b2b  and b2c.

      >

      > Cheers nils

      >

      >

      >

      > *Von:* Florent Thomas <notifications@odoo-community.org>

      > *Gesendet:* Monday, July 1, 2024 12:37:03 PM

      > *An:* Contributors <contributors@odoo-community.org>

      > *Betreff:* Re: [17.0]Website : How to switch display from B2B to B2c

      >

      >

      >

      >

      >

      > *ACHTUNG!* Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie

      > nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den

      > Absender und wissen, dass der Inhalt sicher ist.

      >

      >

      >

      >

      > Hi,

      >

      >

      > Great thanks for this tips.

      >

      > We're gonna hook the display of this fioeld to be able to let the end user

      > toggle between B2C and B2B views

      >

      >

      > regards

      >

      >

      >

      >

      >

      > Florent THOMAS*

      > ☎ +33 972 457 755

      > ✉

      > florent.thomas@mind-and-go.com [1]

      >

      >

      > *Mind & Go*

      > 14, Rue Pierre Cartelet | 66000 PERPIGNAN

      > None [2]

      > [3]

      > None [4]

      > [5]

      >

      >

      >

      >

      >

      > *De: *"Radovan Skolnik" <notifications@odoo-community.org>

      > *À: *"contributors" <contributors@odoo-community.org>

      > *Envoyé: *Lundi 1 Juillet 2024 11:52:23

      > *Objet: *Re: [17.0]Website : How to switch display from B2B to B2c

      >

      >

      >

      > Hi,

      >

      > there is a option in Website configuration on whether to show prices with

      > (B2C) or without (B2B) taxes:

      >

      >

      > Then there is a configuration snippet on checkout page that allows to

      > display B2B fields:

      >

      >

      > Best regards

      >

      > Radovan Skolnik

      >

      > On pondelok 1. júla 2024 10:48:00 CEST Florent Thomas wrote:

      > > Hi everyone,

      > > Hope you're doing well,

      > > Is anyone know how to toogle the display between b2b and b2c on the web

      > > site for a v17 ? Any tips/advice will be appreciated,

      > > Regards

      > > Florent THOMAS*

      > > ☎ +33 972 457 755

      > > ✉ florent.thomas@mind-and-go.com [1]

      > > *Mind & Go*

      > > 14, Rue Pierre Cartelet | 66000 PERPIGNAN

      > > [2]  None [3]   [4]   [5]

      > > _______________________________________________

      > > Mailing-List: https://odoo-community.org/groups/contributors-15 [6]

      > > Post to: mailto:contributors@odoo-community.org

      > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [7]

      > >

      > >

      > >

      > > [1] mailto:florent.thomas@mind-and-go.com

      > > [2] https://mind-and-go.com/

      > > [3] https://www.facebook.com/Mind-And-Go-296462057466508/

      > > [4] https://twitter.com/MindAndGo

      > > [5] https://www.linkedin.com/company/mind-and-go

      > > [6] https://odoo-community.org/groups/contributors-15

      > > [7] https://odoo-community.org/groups?unsubscribe

      >

      > _______________________________________________

      > Mailing-List:

      > https://odoo-community.org/groups/contributors-15 [6]

      > Post to: mailto:contributors@odoo-community.org

      > Unsubscribe:

      > https://odoo-community.org/groups?unsubscribe [7]

      >

      >

      >

      >

      > _______________________________________________

      > Mailing-List:

      > https://odoo-community.org/groups/contributors-15 [8]

      > Post to: mailto:contributors@odoo-community.org

      > Unsubscribe:

      > https://odoo-community.org/groups?unsubscribe [9]

      >

      >

      >

      >

      > _______________________________________________

      > Mailing-List: https://odoo-community.org/groups/contributors-15 [10]

      > Post to: mailto:contributors@odoo-community.org

      > Unsubscribe: https://odoo-community.org/groups?unsubscribe [11]

      >

      >

      >

      > [1] mailto:florent.thomas@mind-and-go.com

      > [2] https://mind-and-go.com/

      > [3] https://www.facebook.com/Mind-And-Go-296462057466508/

      > [4] https://twitter.com/MindAndGo

      > [5] https://www.linkedin.com/company/mind-and-go

      > [6] https://odoo-community.org/groups/contributors-15

      > [7] https://odoo-community.org/groups?unsubscribe

      > [8] https://odoo-community.org/groups/contributors-15

      > [9] https://odoo-community.org/groups?unsubscribe

      > [10] https://odoo-community.org/groups/contributors-15

      > [11] 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 Nils Coenen - 03:11 - 1 Jul 2024
    • Re: [17.0]Website : How to switch display from B2B to B2c

      Nils,


      check out this one: https://github.com/OCA/e-commerce/tree/15.0/website_sale_b2x_alt_price


      Best regards


          Radovan


      On pondelok 1. júla 2024 14:17:28 CEST Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT wrote:

      > Just to let you know… when I tried showing b2b and b2c orices on the same

      > page, there has been some side effects when calculating the price. I ended

      > up to have one site for b2b and one for b2c with fixed settings concerning

      > tax display. This helped me to sort out  the wrong calculation when

      > switching back and forth between b2b  and b2c.

      >

      > Cheers nils

      >

      >

      >

      > *Von:* Florent Thomas <notifications@odoo-community.org>

      > *Gesendet:* Monday, July 1, 2024 12:37:03 PM

      > *An:* Contributors <contributors@odoo-community.org>

      > *Betreff:* Re: [17.0]Website : How to switch display from B2B to B2c

      >

      >

      >

      >

      >

      > *ACHTUNG!* Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie

      > nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den

      > Absender und wissen, dass der Inhalt sicher ist.

      >

      >

      >

      >

      > Hi,

      >

      >

      > Great thanks for this tips.

      >

      > We're gonna hook the display of this fioeld to be able to let the end user

      > toggle between B2C and B2B views

      >

      >

      > regards

      >

      >

      >

      >

      >

      > Florent THOMAS*

      > ☎ +33 972 457 755

      > ✉

      > florent.thomas@mind-and-go.com [1]

      >

      >

      > *Mind & Go*

      > 14, Rue Pierre Cartelet | 66000 PERPIGNAN

      > None [2]

      > [3]

      > None [4]

      > [5]

      >

      >

      >

      >

      >

      > *De: *"Radovan Skolnik" <notifications@odoo-community.org>

      > *À: *"contributors" <contributors@odoo-community.org>

      > *Envoyé: *Lundi 1 Juillet 2024 11:52:23

      > *Objet: *Re: [17.0]Website : How to switch display from B2B to B2c

      >

      >

      >

      > Hi,

      >

      > there is a option in Website configuration on whether to show prices with

      > (B2C) or without (B2B) taxes:

      >

      >

      > Then there is a configuration snippet on checkout page that allows to

      > display B2B fields:

      >

      >

      > Best regards

      >

      > Radovan Skolnik

      >

      > On pondelok 1. júla 2024 10:48:00 CEST Florent Thomas wrote:

      > > Hi everyone,

      > > Hope you're doing well,

      > > Is anyone know how to toogle the display between b2b and b2c on the web

      > > site for a v17 ? Any tips/advice will be appreciated,

      > > Regards

      > > Florent THOMAS*

      > > ☎ +33 972 457 755

      > > ✉ florent.thomas@mind-and-go.com [1]

      > > *Mind & Go*

      > > 14, Rue Pierre Cartelet | 66000 PERPIGNAN

      > > [2]  None [3]   [4]   [5]

      > > _______________________________________________

      > > Mailing-List: https://odoo-community.org/groups/contributors-15 [6]

      > > Post to: mailto:contributors@odoo-community.org

      > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [7]

      > >

      > >

      > >

      > > [1] mailto:florent.thomas@mind-and-go.com

      > > [2] https://mind-and-go.com/

      > > [3] https://www.facebook.com/Mind-And-Go-296462057466508/

      > > [4] https://twitter.com/MindAndGo

      > > [5] https://www.linkedin.com/company/mind-and-go

      > > [6] https://odoo-community.org/groups/contributors-15

      > > [7] https://odoo-community.org/groups?unsubscribe

      >

      > _______________________________________________

      > Mailing-List:

      > https://odoo-community.org/groups/contributors-15 [6]

      > Post to: mailto:contributors@odoo-community.org

      > Unsubscribe:

      > https://odoo-community.org/groups?unsubscribe [7]

      >

      >

      >

      >

      > _______________________________________________

      > Mailing-List:

      > https://odoo-community.org/groups/contributors-15 [8]

      > Post to: mailto:contributors@odoo-community.org

      > Unsubscribe:

      > https://odoo-community.org/groups?unsubscribe [9]

      >

      >

      >

      >

      > _______________________________________________

      > Mailing-List: https://odoo-community.org/groups/contributors-15 [10]

      > Post to: mailto:contributors@odoo-community.org

      > Unsubscribe: https://odoo-community.org/groups?unsubscribe [11]

      >

      >

      >

      > [1] mailto:florent.thomas@mind-and-go.com

      > [2] https://mind-and-go.com/

      > [3] https://www.facebook.com/Mind-And-Go-296462057466508/

      > [4] https://twitter.com/MindAndGo

      > [5] https://www.linkedin.com/company/mind-and-go

      > [6] https://odoo-community.org/groups/contributors-15

      > [7] https://odoo-community.org/groups?unsubscribe

      > [8] https://odoo-community.org/groups/contributors-15

      > [9] https://odoo-community.org/groups?unsubscribe

      > [10] https://odoo-community.org/groups/contributors-15

      > [11] https://odoo-community.org/groups?unsubscribe



      by Radovan Skolnik - 02:56 - 1 Jul 2024

  • Weblate locked components
    Hi everyone,

    Over time a bunch of Weblate components became locked.

    This typically happens when there is a merge conflict between the Weblate copy of the git repo and GitHub. This in turns happens 1/ when there is a force-push to a main branch 2/ when a .po file is pushed to GitHub via a PR and a translation is in progress at the same time in Weblate. 

    There may be other reasons but these seem to be the most common according to the sampling I did.

    This automatic locking mechanism is a protection, to prevent further drift between translations and the git repo.

    To mitigate this problem. Please don't do 1/, and if you have to do 2/, check in Weblate after a little while that the corresponding components have not been locked.

    If you detect locked components, please send an email to transbot@odoo-community.org with the full URL of the components to unlock.

    You'll find below the list of components that I have unlocked today, by resetting the Weblate copy of the git repos. Note that pending translations for these branches may have been lost.

    Best regards,

    -Stéphane

    account-invoice-reporting-16-0,account-invoice-reporting-16-0-account_invoice_report_grouped_by_picking
    bank-statement-import-15-0,bank-statement-import-15-0-account_bank_statement_clear_partner
    bank-statement-import-15-0,bank-statement-import-15-0-account_bank_statement_import_move_line
    bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import
    bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_base
    bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_camt
    bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_camt54
    bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_file_reconciliation_widget
    bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_move_line
    bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_ofx
    bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_online
    bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_online_gocardless
    bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_online_paypal
    bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_online_ponto
    bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_paypal
    bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_txt_xlsx
    calendar-15-0,calendar-15-0-resource_booking
    connector-cmis-16-0,connector-cmis-16-0-cmis
    credit-control-15-0,credit-control-15-0-account_credit_control
    credit-control-15-0,credit-control-15-0-account_financial_risk
    credit-control-15-0,credit-control-15-0-account_invoice_overdue_reminder
    credit-control-15-0,credit-control-15-0-account_payment_return_financial_risk
    credit-control-15-0,credit-control-15-0-partner_risk_insurance
    credit-control-15-0,credit-control-15-0-sale_financial_risk
    credit-control-15-0,credit-control-15-0-sale_financial_risk_info
    credit-control-15-0,credit-control-15-0-sale_payment_sheet_financial_risk
    delivery-carrier-16-0,delivery-carrier-16-0-delivery_package_number
    hr-holidays-16-0,hr-holidays-16-0-hr_holidays_public
    l10n-brazil-15-0,l10n-brazil-15-0-l10n_br_base
    l10n-croatia-16-0,l10n-croatia-16-0-currency_rate_update_hr_hnb
    l10n-ecuador-15-0,l10n-ecuador-15-0-l10n_ec_base
    l10n-germany-15-0,l10n-germany-15-0-l10n_de_holidays
    l10n-iran-16-0,l10n-iran-16-0-l10n_ir_states
    l10n-japan-15-0,l10n-japan-15-0-l10n_jp_address_layout
    l10n-japan-16-0,l10n-japan-16-0-l10n_jp_partner_title_qweb
    l10n-luxemburg-14-0,l10n-luxemburg-14-0-l10n_lu_intrastat_product
    l10n-netherlands-16-0,l10n-netherlands-16-0-l10n_nl_bsn
    l10n-portugal-16-0,l10n-portugal-16-0-l10n_pt_vat
    l10n-romania-16-0,l10n-romania-16-0-l10n_ro_vat_on_payment
    l10n-spain-13-0,l10n-spain-13-0-account_promissory_note_bankia
    l10n-spain-13-0,l10n-spain-13-0-account_promissory_note_caixabank
    l10n-spain-13-0,l10n-spain-13-0-account_promissory_note_santander
    l10n-spain-13-0,l10n-spain-13-0-delivery_dhl_parcel
    l10n-spain-13-0,l10n-spain-13-0-delivery_gls_asm
    l10n-spain-13-0,l10n-spain-13-0-delivery_seur
    l10n-spain-13-0,l10n-spain-13-0-ecoembes
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_account_asset
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_account_banking_sepa_fsdd
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_account_bank_statement_import_n43
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod111
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod115
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod123
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod190
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod216
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod296
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod303
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod303_oss
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod347
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod349
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod390
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod390_oss
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_sii_match
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_sii_oca
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_sii_oss
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_vat_prorrate
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_vat_prorrate_asset
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_dua
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_dua_sii
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_dua_ticketbai_batuz
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_facturae
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_facturae_efact
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_facturae_face
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_intrastat_report
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_irnr
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_mis_report
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_partner
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_partner_mercantil
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_pos
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_ticketbai
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_ticketbai_api
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_ticketbai_api_batuz
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_ticketbai_batuz
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_ticketbai_pos
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_toponyms
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_vat_book
    l10n-spain-13-0,l10n-spain-13-0-l10n_es_vat_book_oss
    l10n-spain-13-0,l10n-spain-13-0-payment_redsys
    l10n-spain-17-0,l10n-spain-17-0-l10n_ca_cnae
    l10n-spain-17-0,l10n-spain-17-0-l10n_ca_es_cnae
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_account_asset
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_account_banking_sepa_fsdd
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_account_statement_import_n43
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod111
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod115
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod123
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod303
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod303_vat_prorate
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod347
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod349
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod390
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_atc
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_cnae
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_partner
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_partner_mercantil
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_toponyms
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_vat_book
    l10n-spain-17-0,l10n-spain-17-0-l10n_es_vat_prorate
    l10n-spain-17-0,l10n-spain-17-0-payment_redsys
    l10n-spain-6-0,l10n-spain-6-0-l10n_es_aeat_mod340
    l10n-switzerland-15-0,l10n-switzerland-15-0-l10n_ch_invoice_reports
    l10n-usa-16-0,l10n-usa-16-0-l10n_us_form_1099
    management-system-17-0,management-system-17-0-document_page_procedure
    management-system-17-0,management-system-17-0-mgmtsystem
    mis-builder-contrib-16-0,mis-builder-contrib-16-0-mis_builder_total_committed_purchase
    multi-company-16-0,multi-company-16-0-product_tax_multicompany_default
    odoo-pim-12-0,odoo-pim-12-0-product_attribute_set_completeness
    operating-unit-16-0,operating-unit-16-0-operating_unit
    payroll-15-0,payroll-15-0-payroll
    product-pack-16-0,product-pack-16-0-product_pack
    product-variant-16-0,product-variant-16-0-product_variant_default_code
    reporting-engine-16-0,reporting-engine-16-0-report_xml
    rest-framework-16-0,rest-framework-16-0-graphql_demo
    sale-promotion-15-0,sale-promotion-15-0-coupon_chatter
    sale-reporting-16-0,sale-reporting-16-0-sale_order_line_position
    server-auth-16-0,server-auth-16-0-auth_api_key
    server-brand-16-0,server-brand-16-0-disable_odoo_online
    server-tools-16-0,server-tools-16-0-upgrade_analysis
    server-ux-15-0,server-ux-15-0-announcement
    server-ux-15-0,server-ux-15-0-barcode_action
    server-ux-15-0,server-ux-15-0-base_archive_date
    server-ux-15-0,server-ux-15-0-base_cancel_confirm
    server-ux-15-0,server-ux-15-0-base_duplicate_security_group
    server-ux-15-0,server-ux-15-0-base_export_manager
    server-ux-15-0,server-ux-15-0-base_field_deprecated
    server-ux-15-0,server-ux-15-0-base_import_security_group
    server-ux-15-0,server-ux-15-0-base_menu_visibility_restriction
    server-ux-15-0,server-ux-15-0-base_optional_quick_create
    server-ux-15-0,server-ux-15-0-base_recurrence
    server-ux-15-0,server-ux-15-0-base_revision
    server-ux-15-0,server-ux-15-0-base_search_custom_field_filter
    server-ux-15-0,server-ux-15-0-base_substate
    server-ux-15-0,server-ux-15-0-base_technical_features
    server-ux-15-0,server-ux-15-0-base_tier_validation
    server-ux-15-0,server-ux-15-0-base_tier_validation_formula
    server-ux-15-0,server-ux-15-0-base_tier_validation_forward
    server-ux-15-0,server-ux-15-0-base_tier_validation_report
    server-ux-15-0,server-ux-15-0-base_tier_validation_server_action
    server-ux-15-0,server-ux-15-0-chained_swapper
    server-ux-15-0,server-ux-15-0-date_range
    server-ux-15-0,server-ux-15-0-default_multi_user
    server-ux-15-0,server-ux-15-0-document_quick_access
    server-ux-15-0,server-ux-15-0-document_quick_access_folder_auto_classification
    server-ux-15-0,server-ux-15-0-filter_multi_user
    server-ux-15-0,server-ux-15-0-mass_editing
    server-ux-15-0,server-ux-15-0-multi_step_wizard
    server-ux-15-0,server-ux-15-0-sequence_reset_period
    server-ux-15-0,server-ux-15-0-web_archive_date
    social-17-0,social-17-0-base_search_mail_content
    social-17-0,social-17-0-mail_outbound_static
    social-17-0,social-17-0-mail_partner_forwarding
    social-17-0,social-17-0-mail_send_confirmation
    stock-logistics-reporting-16-0,stock-logistics-reporting-16-0-delivery_line_sale_line_position
    stock-logistics-warehouse-16-0,stock-logistics-warehouse-16-0-stock_mts_mto_rule
    stock-logistics-workflow-16-0,stock-logistics-workflow-16-0-stock_putaway_hook
    survey-15-0,survey-15-0-partner_survey
    web-api-15-0,web-api-15-0-webservice
    by Stéphane Bidoul - 06:06 - 30 Jun 2024

    2 replies 2 replies

    • Re: Weblate locked components 
      Yes, a really good job.

David BEAL
Akretion
Consultant ERP Odoo

Le lun. 1 juil. 2024 à 09:46, Stefano Consolaro
<notifications@odoo-community.org> a écrit :

>

> Super! Thank you Stéphane for this fantastic work!

>

> Da "Stéphane Bidoul" notifications@odoo-community.org

> A "Contributors" contributors@odoo-community.org

> Cc

> Data Sun, 30 Jun 2024 16:07:29 -0000

> Oggetto Weblate locked components

>

> Hi everyone,

>

> Over time a bunch of Weblate components became locked.

>

> This typically happens when there is a merge conflict between the Weblate copy of the git repo and GitHub. This in turns happens 1/ when there is a force-push to a main branch 2/ when a .po file is pushed to GitHub via a PR and a translation is in progress at the same time in Weblate.

>

> There may be other reasons but these seem to be the most common according to the sampling I did.

>

> This automatic locking mechanism is a protection, to prevent further drift between translations and the git repo.

>

> To mitigate this problem. Please don't do 1/, and if you have to do 2/, check in Weblate after a little while that the corresponding components have not been locked.

>

> If you detect locked components, please send an email to transbot@odoo-community.org with the full URL of the components to unlock.

>

> You'll find below the list of components that I have unlocked today, by resetting the Weblate copy of the git repos. Note that pending translations for these branches may have been lost.

>

> Best regards,

>

> -Stéphane

>

> account-invoice-reporting-16-0,account-invoice-reporting-16-0-account_invoice_report_grouped_by_picking

> bank-statement-import-15-0,bank-statement-import-15-0-account_bank_statement_clear_partner

> bank-statement-import-15-0,bank-statement-import-15-0-account_bank_statement_import_move_line

> bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import

> bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_base

> bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_camt

> bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_camt54

> bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_file_reconciliation_widget

> bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_move_line

> bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_ofx

> bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_online

> bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_online_gocardless

> bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_online_paypal

> bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_online_ponto

> bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_paypal

> bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_txt_xlsx

> calendar-15-0,calendar-15-0-resource_booking

> connector-cmis-16-0,connector-cmis-16-0-cmis

> credit-control-15-0,credit-control-15-0-account_credit_control

> credit-control-15-0,credit-control-15-0-account_financial_risk

> credit-control-15-0,credit-control-15-0-account_invoice_overdue_reminder

> credit-control-15-0,credit-control-15-0-account_payment_return_financial_risk

> credit-control-15-0,credit-control-15-0-partner_risk_insurance

> credit-control-15-0,credit-control-15-0-sale_financial_risk

> credit-control-15-0,credit-control-15-0-sale_financial_risk_info

> credit-control-15-0,credit-control-15-0-sale_payment_sheet_financial_risk

> delivery-carrier-16-0,delivery-carrier-16-0-delivery_package_number

> hr-holidays-16-0,hr-holidays-16-0-hr_holidays_public

> l10n-brazil-15-0,l10n-brazil-15-0-l10n_br_base

> l10n-croatia-16-0,l10n-croatia-16-0-currency_rate_update_hr_hnb

> l10n-ecuador-15-0,l10n-ecuador-15-0-l10n_ec_base

> l10n-germany-15-0,l10n-germany-15-0-l10n_de_holidays

> l10n-iran-16-0,l10n-iran-16-0-l10n_ir_states

> l10n-japan-15-0,l10n-japan-15-0-l10n_jp_address_layout

> l10n-japan-16-0,l10n-japan-16-0-l10n_jp_partner_title_qweb

> l10n-luxemburg-14-0,l10n-luxemburg-14-0-l10n_lu_intrastat_product

> l10n-netherlands-16-0,l10n-netherlands-16-0-l10n_nl_bsn

> l10n-portugal-16-0,l10n-portugal-16-0-l10n_pt_vat

> l10n-romania-16-0,l10n-romania-16-0-l10n_ro_vat_on_payment

> l10n-spain-13-0,l10n-spain-13-0-account_promissory_note_bankia

> l10n-spain-13-0,l10n-spain-13-0-account_promissory_note_caixabank

> l10n-spain-13-0,l10n-spain-13-0-account_promissory_note_santander

> l10n-spain-13-0,l10n-spain-13-0-delivery_dhl_parcel

> l10n-spain-13-0,l10n-spain-13-0-delivery_gls_asm

> l10n-spain-13-0,l10n-spain-13-0-delivery_seur

> l10n-spain-13-0,l10n-spain-13-0-ecoembes

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_account_asset

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_account_banking_sepa_fsdd

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_account_bank_statement_import_n43

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod111

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod115

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod123

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod190

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod216

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod296

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod303

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod303_oss

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod347

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod349

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod390

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod390_oss

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_sii_match

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_sii_oca

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_sii_oss

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_vat_prorrate

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_vat_prorrate_asset

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_dua

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_dua_sii

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_dua_ticketbai_batuz

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_facturae

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_facturae_efact

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_facturae_face

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_intrastat_report

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_irnr

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_mis_report

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_partner

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_partner_mercantil

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_pos

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_ticketbai

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_ticketbai_api

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_ticketbai_api_batuz

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_ticketbai_batuz

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_ticketbai_pos

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_toponyms

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_vat_book

> l10n-spain-13-0,l10n-spain-13-0-l10n_es_vat_book_oss

> l10n-spain-13-0,l10n-spain-13-0-payment_redsys

> l10n-spain-17-0,l10n-spain-17-0-l10n_ca_cnae

> l10n-spain-17-0,l10n-spain-17-0-l10n_ca_es_cnae

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_account_asset

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_account_banking_sepa_fsdd

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_account_statement_import_n43

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod111

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod115

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod123

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod303

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod303_vat_prorate

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod347

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod349

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod390

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_atc

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_cnae

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_partner

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_partner_mercantil

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_toponyms

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_vat_book

> l10n-spain-17-0,l10n-spain-17-0-l10n_es_vat_prorate

> l10n-spain-17-0,l10n-spain-17-0-payment_redsys

> l10n-spain-6-0,l10n-spain-6-0-l10n_es_aeat_mod340

> l10n-switzerland-15-0,l10n-switzerland-15-0-l10n_ch_invoice_reports

> l10n-usa-16-0,l10n-usa-16-0-l10n_us_form_1099

> management-system-17-0,management-system-17-0-document_page_procedure

> management-system-17-0,management-system-17-0-mgmtsystem

> mis-builder-contrib-16-0,mis-builder-contrib-16-0-mis_builder_total_committed_purchase

> multi-company-16-0,multi-company-16-0-product_tax_multicompany_default

> odoo-pim-12-0,odoo-pim-12-0-product_attribute_set_completeness

> operating-unit-16-0,operating-unit-16-0-operating_unit

> payroll-15-0,payroll-15-0-payroll

> product-pack-16-0,product-pack-16-0-product_pack

> product-variant-16-0,product-variant-16-0-product_variant_default_code

> reporting-engine-16-0,reporting-engine-16-0-report_xml

> rest-framework-16-0,rest-framework-16-0-graphql_demo

> sale-promotion-15-0,sale-promotion-15-0-coupon_chatter

> sale-reporting-16-0,sale-reporting-16-0-sale_order_line_position

> server-auth-16-0,server-auth-16-0-auth_api_key

> server-brand-16-0,server-brand-16-0-disable_odoo_online

> server-tools-16-0,server-tools-16-0-upgrade_analysis

> server-ux-15-0,server-ux-15-0-announcement

> server-ux-15-0,server-ux-15-0-barcode_action

> server-ux-15-0,server-ux-15-0-base_archive_date

> server-ux-15-0,server-ux-15-0-base_cancel_confirm

> server-ux-15-0,server-ux-15-0-base_duplicate_security_group

> server-ux-15-0,server-ux-15-0-base_export_manager

> server-ux-15-0,server-ux-15-0-base_field_deprecated

> server-ux-15-0,server-ux-15-0-base_import_security_group

> server-ux-15-0,server-ux-15-0-base_menu_visibility_restriction

> server-ux-15-0,server-ux-15-0-base_optional_quick_create

> server-ux-15-0,server-ux-15-0-base_recurrence

> server-ux-15-0,server-ux-15-0-base_revision

> server-ux-15-0,server-ux-15-0-base_search_custom_field_filter

> server-ux-15-0,server-ux-15-0-base_substate

> server-ux-15-0,server-ux-15-0-base_technical_features

> server-ux-15-0,server-ux-15-0-base_tier_validation

> server-ux-15-0,server-ux-15-0-base_tier_validation_formula

> server-ux-15-0,server-ux-15-0-base_tier_validation_forward

> server-ux-15-0,server-ux-15-0-base_tier_validation_report

> server-ux-15-0,server-ux-15-0-base_tier_validation_server_action

> server-ux-15-0,server-ux-15-0-chained_swapper

> server-ux-15-0,server-ux-15-0-date_range

> server-ux-15-0,server-ux-15-0-default_multi_user

> server-ux-15-0,server-ux-15-0-document_quick_access

> server-ux-15-0,server-ux-15-0-document_quick_access_folder_auto_classification

> server-ux-15-0,server-ux-15-0-filter_multi_user

> server-ux-15-0,server-ux-15-0-mass_editing

> server-ux-15-0,server-ux-15-0-multi_step_wizard

> server-ux-15-0,server-ux-15-0-sequence_reset_period

> server-ux-15-0,server-ux-15-0-web_archive_date

> social-17-0,social-17-0-base_search_mail_content

> social-17-0,social-17-0-mail_outbound_static

> social-17-0,social-17-0-mail_partner_forwarding

> social-17-0,social-17-0-mail_send_confirmation

> stock-logistics-reporting-16-0,stock-logistics-reporting-16-0-delivery_line_sale_line_position

> stock-logistics-warehouse-16-0,stock-logistics-warehouse-16-0-stock_mts_mto_rule

> stock-logistics-workflow-16-0,stock-logistics-workflow-16-0-stock_putaway_hook

> survey-15-0,survey-15-0-partner_survey

> web-api-15-0,web-api-15-0-webservice

>

> _______________________________________________

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

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe

>

>

>

> Stefano Consolaro

> www.mymage.it

>

> _______________________________________________

> 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 - 10:00 - 1 Jul 2024
    • Re:Weblate locked components
      Super! Thank you Stéphane for this fantastic work!

      Da "Stéphane Bidoul" notifications@odoo-community.org
      A "Contributors" contributors@odoo-community.org
      Cc
      Data Sun, 30 Jun 2024 16:07:29 -0000
      Oggetto Weblate locked components

      Hi everyone,

      Over time a bunch of Weblate components became locked.

      This typically happens when there is a merge conflict between the Weblate copy of the git repo and GitHub. This in turns happens 1/ when there is a force-push to a main branch 2/ when a .po file is pushed to GitHub via a PR and a translation is in progress at the same time in Weblate. 

      There may be other reasons but these seem to be the most common according to the sampling I did.

      This automatic locking mechanism is a protection, to prevent further drift between translations and the git repo.

      To mitigate this problem. Please don't do 1/, and if you have to do 2/, check in Weblate after a little while that the corresponding components have not been locked.

      If you detect locked components, please send an email to transbot@odoo-community.org with the full URL of the components to unlock.

      You'll find below the list of components that I have unlocked today, by resetting the Weblate copy of the git repos. Note that pending translations for these branches may have been lost.

      Best regards,

      -Stéphane

      account-invoice-reporting-16-0,account-invoice-reporting-16-0-account_invoice_report_grouped_by_picking
      bank-statement-import-15-0,bank-statement-import-15-0-account_bank_statement_clear_partner
      bank-statement-import-15-0,bank-statement-import-15-0-account_bank_statement_import_move_line
      bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import
      bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_base
      bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_camt
      bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_camt54
      bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_file_reconciliation_widget
      bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_move_line
      bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_ofx
      bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_online
      bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_online_gocardless
      bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_online_paypal
      bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_online_ponto
      bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_paypal
      bank-statement-import-15-0,bank-statement-import-15-0-account_statement_import_txt_xlsx
      calendar-15-0,calendar-15-0-resource_booking
      connector-cmis-16-0,connector-cmis-16-0-cmis
      credit-control-15-0,credit-control-15-0-account_credit_control
      credit-control-15-0,credit-control-15-0-account_financial_risk
      credit-control-15-0,credit-control-15-0-account_invoice_overdue_reminder
      credit-control-15-0,credit-control-15-0-account_payment_return_financial_risk
      credit-control-15-0,credit-control-15-0-partner_risk_insurance
      credit-control-15-0,credit-control-15-0-sale_financial_risk
      credit-control-15-0,credit-control-15-0-sale_financial_risk_info
      credit-control-15-0,credit-control-15-0-sale_payment_sheet_financial_risk
      delivery-carrier-16-0,delivery-carrier-16-0-delivery_package_number
      hr-holidays-16-0,hr-holidays-16-0-hr_holidays_public
      l10n-brazil-15-0,l10n-brazil-15-0-l10n_br_base
      l10n-croatia-16-0,l10n-croatia-16-0-currency_rate_update_hr_hnb
      l10n-ecuador-15-0,l10n-ecuador-15-0-l10n_ec_base
      l10n-germany-15-0,l10n-germany-15-0-l10n_de_holidays
      l10n-iran-16-0,l10n-iran-16-0-l10n_ir_states
      l10n-japan-15-0,l10n-japan-15-0-l10n_jp_address_layout
      l10n-japan-16-0,l10n-japan-16-0-l10n_jp_partner_title_qweb
      l10n-luxemburg-14-0,l10n-luxemburg-14-0-l10n_lu_intrastat_product
      l10n-netherlands-16-0,l10n-netherlands-16-0-l10n_nl_bsn
      l10n-portugal-16-0,l10n-portugal-16-0-l10n_pt_vat
      l10n-romania-16-0,l10n-romania-16-0-l10n_ro_vat_on_payment
      l10n-spain-13-0,l10n-spain-13-0-account_promissory_note_bankia
      l10n-spain-13-0,l10n-spain-13-0-account_promissory_note_caixabank
      l10n-spain-13-0,l10n-spain-13-0-account_promissory_note_santander
      l10n-spain-13-0,l10n-spain-13-0-delivery_dhl_parcel
      l10n-spain-13-0,l10n-spain-13-0-delivery_gls_asm
      l10n-spain-13-0,l10n-spain-13-0-delivery_seur
      l10n-spain-13-0,l10n-spain-13-0-ecoembes
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_account_asset
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_account_banking_sepa_fsdd
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_account_bank_statement_import_n43
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod111
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod115
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod123
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod190
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod216
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod296
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod303
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod303_oss
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod347
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod349
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod390
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_mod390_oss
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_sii_match
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_sii_oca
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_sii_oss
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_vat_prorrate
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_aeat_vat_prorrate_asset
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_dua
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_dua_sii
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_dua_ticketbai_batuz
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_facturae
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_facturae_efact
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_facturae_face
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_intrastat_report
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_irnr
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_mis_report
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_partner
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_partner_mercantil
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_pos
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_ticketbai
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_ticketbai_api
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_ticketbai_api_batuz
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_ticketbai_batuz
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_ticketbai_pos
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_toponyms
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_vat_book
      l10n-spain-13-0,l10n-spain-13-0-l10n_es_vat_book_oss
      l10n-spain-13-0,l10n-spain-13-0-payment_redsys
      l10n-spain-17-0,l10n-spain-17-0-l10n_ca_cnae
      l10n-spain-17-0,l10n-spain-17-0-l10n_ca_es_cnae
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_account_asset
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_account_banking_sepa_fsdd
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_account_statement_import_n43
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod111
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod115
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod123
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod303
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod303_vat_prorate
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod347
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod349
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_aeat_mod390
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_atc
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_cnae
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_partner
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_partner_mercantil
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_toponyms
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_vat_book
      l10n-spain-17-0,l10n-spain-17-0-l10n_es_vat_prorate
      l10n-spain-17-0,l10n-spain-17-0-payment_redsys
      l10n-spain-6-0,l10n-spain-6-0-l10n_es_aeat_mod340
      l10n-switzerland-15-0,l10n-switzerland-15-0-l10n_ch_invoice_reports
      l10n-usa-16-0,l10n-usa-16-0-l10n_us_form_1099
      management-system-17-0,management-system-17-0-document_page_procedure
      management-system-17-0,management-system-17-0-mgmtsystem
      mis-builder-contrib-16-0,mis-builder-contrib-16-0-mis_builder_total_committed_purchase
      multi-company-16-0,multi-company-16-0-product_tax_multicompany_default
      odoo-pim-12-0,odoo-pim-12-0-product_attribute_set_completeness
      operating-unit-16-0,operating-unit-16-0-operating_unit
      payroll-15-0,payroll-15-0-payroll
      product-pack-16-0,product-pack-16-0-product_pack
      product-variant-16-0,product-variant-16-0-product_variant_default_code
      reporting-engine-16-0,reporting-engine-16-0-report_xml
      rest-framework-16-0,rest-framework-16-0-graphql_demo
      sale-promotion-15-0,sale-promotion-15-0-coupon_chatter
      sale-reporting-16-0,sale-reporting-16-0-sale_order_line_position
      server-auth-16-0,server-auth-16-0-auth_api_key
      server-brand-16-0,server-brand-16-0-disable_odoo_online
      server-tools-16-0,server-tools-16-0-upgrade_analysis
      server-ux-15-0,server-ux-15-0-announcement
      server-ux-15-0,server-ux-15-0-barcode_action
      server-ux-15-0,server-ux-15-0-base_archive_date
      server-ux-15-0,server-ux-15-0-base_cancel_confirm
      server-ux-15-0,server-ux-15-0-base_duplicate_security_group
      server-ux-15-0,server-ux-15-0-base_export_manager
      server-ux-15-0,server-ux-15-0-base_field_deprecated
      server-ux-15-0,server-ux-15-0-base_import_security_group
      server-ux-15-0,server-ux-15-0-base_menu_visibility_restriction
      server-ux-15-0,server-ux-15-0-base_optional_quick_create
      server-ux-15-0,server-ux-15-0-base_recurrence
      server-ux-15-0,server-ux-15-0-base_revision
      server-ux-15-0,server-ux-15-0-base_search_custom_field_filter
      server-ux-15-0,server-ux-15-0-base_substate
      server-ux-15-0,server-ux-15-0-base_technical_features
      server-ux-15-0,server-ux-15-0-base_tier_validation
      server-ux-15-0,server-ux-15-0-base_tier_validation_formula
      server-ux-15-0,server-ux-15-0-base_tier_validation_forward
      server-ux-15-0,server-ux-15-0-base_tier_validation_report
      server-ux-15-0,server-ux-15-0-base_tier_validation_server_action
      server-ux-15-0,server-ux-15-0-chained_swapper
      server-ux-15-0,server-ux-15-0-date_range
      server-ux-15-0,server-ux-15-0-default_multi_user
      server-ux-15-0,server-ux-15-0-document_quick_access
      server-ux-15-0,server-ux-15-0-document_quick_access_folder_auto_classification
      server-ux-15-0,server-ux-15-0-filter_multi_user
      server-ux-15-0,server-ux-15-0-mass_editing
      server-ux-15-0,server-ux-15-0-multi_step_wizard
      server-ux-15-0,server-ux-15-0-sequence_reset_period
      server-ux-15-0,server-ux-15-0-web_archive_date
      social-17-0,social-17-0-base_search_mail_content
      social-17-0,social-17-0-mail_outbound_static
      social-17-0,social-17-0-mail_partner_forwarding
      social-17-0,social-17-0-mail_send_confirmation
      stock-logistics-reporting-16-0,stock-logistics-reporting-16-0-delivery_line_sale_line_position
      stock-logistics-warehouse-16-0,stock-logistics-warehouse-16-0-stock_mts_mto_rule
      stock-logistics-workflow-16-0,stock-logistics-workflow-16-0-stock_putaway_hook
      survey-15-0,survey-15-0-partner_survey
      web-api-15-0,web-api-15-0-webservice

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



      Stefano Consolaro
      www.mymage.it
      by Stefano Consolaro - 09:41 - 1 Jul 2024
  • proposing myself as team member on infrastructure-maintainer
    Hi,

    We're planning multiple developpment in this repo with my team in the next monts, like OOVH connector, server description link with products etc...

    I'm wondering if I could be added as a maintainer/team member of this repo.
    Not sure what it implies but really want to contribute.

    Regards

    Vertical seprator

    Florent THOMAS

    ☎ +33 972 457 755
    ✉ florent.thomas@mind-and-go.com

    Mind & Go
    14, Rue Pierre Cartelet | 66000 PERPIGNAN

    Logo Mind And Go Facebook Mind And Go Twitter Mind And Go LinkedIn Mind And Go
    by Florent THOMAS - 05:26 - 29 Jun 2024
  • Odoo 14 translation no longer at Transifex 
    

Is there an active community in translating Odoo 14?
I now found a bad translation in Swedish in core-odoo/base. If I can 
translate at the source more people can use it.

Is OCA hosting this translation?

regards,

// jakob





-- 
Med vänlig hälsning / Best regards/ 顺祝商祺,
Jakob Krabbe

VERTEL AB | Jakob Krabbe | jakob.krabbe@vertel.se
+46 (0)13 99 19 480 | +46 (0) 709 24 54 75 | vertel.se
    by Jakob Krabbe - 01:40 - 28 Jun 2024

    2 replies 2 replies

    • Re: Odoo 14 translation no longer at Transifex
      No, there isn't any. The effort is too much for little value. You should look ahead and move ASAP to newer versions.

      Only OCB can receive patches via PRs if there's a bad keyword translation that provokes a crash.

      Regards.
      by Pedro M. Baeza - 02:01 - 28 Jun 2024
    • Re: Odoo 14 translation no longer at Transifex 
      
I enclose an image describing the problem that I can solve myself in 
Odoo 15 and above!

How do I solve it in Odoo 14!?

regards,


// jakob

Den 2024-06-28 kl. 13:32, skrev Jakob Krabbe:

> 

> 

> 

> Is there an active community in translating Odoo 14?

> I now found a bad translation in Swedish in core-odoo/base. If I can 

> translate at the source more people can use it.

> 

> Is OCA hosting this translation?

> 

> regards,

> 

> // jakob

> 

> 

> 

> 


-- 
Med vänlig hälsning / Best regards/ 顺祝商祺,
Jakob Krabbe

VERTEL AB | Jakob Krabbe | jakob.krabbe@vertel.se
+46 (0)13 99 19 480 | +46 (0) 709 24 54 75 | vertel.se
      by Jakob Krabbe - 01:55 - 28 Jun 2024

      1 attachments 1 attachments

      parent and child.png
  • Weblate: "Your request was rejected..." 
    

Hello!
Some other person wrote about this feature quite recently! However, I 
can´t find that thread.

When working with such a fancy speed, "unexpected error occurs"!

The pink field says "Your request was rejected because you have 
performed too many operations recently. You have been logged out, please 
log in and try again later."

Would it be possible to change that lower limit to something less low?

regards,

// jakob




-- 
Med vänlig hälsning / Best regards/ 顺祝商祺,
Jakob Krabbe

VERTEL AB | Jakob Krabbe | jakob.krabbe@vertel.se
+46 (0)13 99 19 480 | +46 (0) 709 24 54 75 | vertel.se
    by Jakob Krabbe - 04:31 - 26 Jun 2024

    2 attachments 2 attachments

    weblate working limit 2.png
    weblate working limit 1.png

    2 replies 2 replies

  • Auto-send confirmation email
    Hi,

    what could be a solution to automatically send SO/PO/Invoice email once the document is confirmed?

    Thanks, 

    --

    Francesco Foresti
    Sicurpharma Srl
    +39 333 8123 790
    by Francesco Foresti - 12:11 - 26 Jun 2024

    2 replies 2 replies

  • Configuring Incoming Mail Server in OdooV12 with Outlook

    Hello,

    Should I follow the instructions in this article to set up the incoming mail server in OdooV12? https://ventor.tech/guides/how-to-configure-emails-to-work-with-office-365-and-odoo#2

    According to this link https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online, it seems that OAuth 2.0 is now required for IMAP. 

    Does anyone know the latest method to set up the incoming mail server in OdooV12 using Outlook?"  

    by Tatsuki Kanda - 12:51 - 25 Jun 2024

    3 replies 3 replies

  • Pull manufacturing stock from sublocations 
    Hi,

on an Odoo 14 instance the following is configured:

- Manufacturing operations type that pulls from "MyCompany/Pre-production"
- Pull rule that is configured to always pull stock from 
"MyCompany/Stock" to resupply Pre-production.

Now some stock is in "MyCompany/Stock/001".

How to configure the Pull rule such that it also pulls stock from any 
sublocations which has Qty on hand available?

-Tom
    by Tom Blauwendraat - 10:19 - 25 Jun 2024
  • Backup module for S3-like (Wasabi)

    Hello,

     

    Dear Colleagues,

     

    Have any of you work or have develop for Odoo EE 16.0 a module for automatic backup that use Wasabi?

     

    Wasabi - https://wasabi.com/

     

    I was looking for the modules from Webkul and Cybrosis, one of them uses AWS S3, but we want to use Wasabi, that is S3 compatible. Have you use Wasabi or any other S3-like service with those modules published in Odoo’s apps?

     

    If you have the module ready, please contact me back with the details!

     

    Thanks in advanced,

     

    Regards,

     

    Shape Description automatically generated with low confidence

    Daniel Guerrero

    General Manager

    Nelmix Solutions

    signature_3198377742

    +1 (809) 870-7092

    signature_1151551968

    daniel@nelmix.com

    signature_2672572751

    https://nelmix.com/

    signature_3688296172

    C/ Francisco Prats Ramírez #565, Santo Domingo, Rep. Dom.

     

    by daniel - 10:41 - 24 Jun 2024

    5 attachments 5 attachments

    image005.png
    image004.png
    image003.png
    image002.png
    image001.gif

    3 replies 3 replies

    • Re: Backup module for S3-like (Wasabi)

      Hello Frederik, Graeme.

       

      Thanks for your time. I will try with Duplicity I even found a guide for Wasabi. I didn’t know of Duplicity.

       

      Best Daniel!

       

      From: Frederik Kramer <notifications@odoo-community.org>
      Date: Monday, 24 June 2024 at 5:42       PM
      To: Contributors <contributors@odoo-community.org>
      Subject: Re: Backup module for S3-like (Wasabi)

      Yeah really duplicity does a great job. No need for an Odoo Module.

      Best Frederik

       

      Am 24. Juni 2024 23:12:11 MESZ schrieb Graeme Gellatly <notifications@odoo-community.org>:

      Backup is pretty straightforward. I wouldn't use an Odoo module for it. There are much easier and more appropriate ways.

       

      Personally I use restic in a multi destination configuration, for me it just feels the right way to do backups, but for simple stuff and even not so simple Duplicity is popular. Both of these support pre actions like taking a db dump. They also support 100's of different backends and if not using upstream lifecycle rules also support lifecycle management.

       

      On Tue, Jun 25, 2024 at 8:42 AM Daniel Guerrero <notifications@odoo-community.org> wrote:

      Hello,

       

      Dear Colleagues,

       

      Have any of you work or have develop for Odoo EE 16.0 a module for automatic backup that use Wasabi?

       

      Wasabi - https://wasabi.com/

       

      I was looking for the modules from Webkul and Cybrosis, one of them uses AWS S3, but we want to use Wasabi, that is S3 compatible. Have you use Wasabi or any other S3-like service with those modules published in Odoo’s apps?

       

      If you have the module ready, please contact me back with the details!

       

      Thanks in advanced,

       

      Regards,

       

      Shape Description automatically generated with low confidence

      Daniel Guerrero

      General Manager

      Nelmix Solutions

      signature_3198377742

      +1 (809) 870-7092

      signature_1151551968

      daniel@nelmix.com

      signature_2672572751

      https://nelmix.com/

      signature_3688296172

      C/ Francisco Prats Ramírez #565, Santo Domingo, Rep. Dom.

       

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

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

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

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

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

      by daniel - 06:16 - 25 Jun 2024
    • Re: Backup module for S3-like (Wasabi)
      Yeah really duplicity does a great job. No need for an Odoo Module.

      Best Frederik


      Am 24. Juni 2024 23:12:11 MESZ schrieb Graeme Gellatly <notifications@odoo-community.org>:
      Backup is pretty straightforward. I wouldn't use an Odoo module for it. There are much easier and more appropriate ways.

      Personally I use restic in a multi destination configuration, for me it just feels the right way to do backups, but for simple stuff and even not so simple Duplicity is popular. Both of these support pre actions like taking a db dump. They also support 100's of different backends and if not using upstream lifecycle rules also support lifecycle management.

      On Tue, Jun 25, 2024 at 8:42 AM Daniel Guerrero <notifications@odoo-community.org> wrote:

      Hello,

       

      Dear Colleagues,

       

      Have any of you work or have develop for Odoo EE 16.0 a module for automatic backup that use Wasabi?

       

      Wasabi - https://wasabi.com/

       

      I was looking for the modules from Webkul and Cybrosis, one of them uses AWS S3, but we want to use Wasabi, that is S3 compatible. Have you use Wasabi or any other S3-like service with those modules published in Odoo’s apps?

       

      If you have the module ready, please contact me back with the details!

       

      Thanks in advanced,

       

      Regards,

       

      Shape Description automatically generated with low confidence

      Daniel Guerrero

      General Manager

      Nelmix Solutions

      signature_3198377742

      +1 (809) 870-7092

      signature_1151551968

      daniel@nelmix.com

      signature_2672572751

      https://nelmix.com/

      signature_3688296172

      C/ Francisco Prats Ramírez #565, Santo Domingo, Rep. Dom.

       

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

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

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

      Sitz der Gesellschaft: Buchholz i.d.N.
      Amtsgericht Tostedt, HRB 205226
      Steuer-Nr: 15/200/53247
      USt-IdNr.: DE815580155
      by Frederik Kramer - 11:41 - 24 Jun 2024
    • Re: Backup module for S3-like (Wasabi)
      Backup is pretty straightforward. I wouldn't use an Odoo module for it. There are much easier and more appropriate ways.

      Personally I use restic in a multi destination configuration, for me it just feels the right way to do backups, but for simple stuff and even not so simple Duplicity is popular. Both of these support pre actions like taking a db dump. They also support 100's of different backends and if not using upstream lifecycle rules also support lifecycle management.

      On Tue, Jun 25, 2024 at 8:42 AM Daniel Guerrero <notifications@odoo-community.org> wrote:

      Hello,

       

      Dear Colleagues,

       

      Have any of you work or have develop for Odoo EE 16.0 a module for automatic backup that use Wasabi?

       

      Wasabi - https://wasabi.com/

       

      I was looking for the modules from Webkul and Cybrosis, one of them uses AWS S3, but we want to use Wasabi, that is S3 compatible. Have you use Wasabi or any other S3-like service with those modules published in Odoo’s apps?

       

      If you have the module ready, please contact me back with the details!

       

      Thanks in advanced,

       

      Regards,

       

      Shape Description automatically generated with low confidence

      Daniel Guerrero

      General Manager

      Nelmix Solutions

      signature_3198377742

      +1 (809) 870-7092

      signature_1151551968

      daniel@nelmix.com

      signature_2672572751

      https://nelmix.com/

      signature_3688296172

      C/ Francisco Prats Ramírez #565, Santo Domingo, Rep. Dom.

       

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

      by "Graeme Gellatly" <graeme@moahub.nz> - 11:11 - 24 Jun 2024
  • ledger
    Dear Colleagues,
    We try to install ledger in odoo comunity version 17, but the modules involved in it aren't compatible someone would know how, or if you could give us some indications,  about  compatibilize the module account_asset_management module, from v16 to v17?
     
    Thanks in advance
    Best Regards,
     
    Angel Luis García-Junco Lora (Departamento de Software)
     
    SOFTWARE Y SERVICIOS TECNOLÓGICOS desde 1984Calle Democracia nº5 | San José de la Rinconada
     
    41300 LA RINCONADA ( ANDALUCÍA) - ESPAÑA Teléfono Centralita :(+34)955 085 361 Móvil Telegram y WhatsApp : (+34)601325581 Email:software@jlbberp.com NORMATIVA LEGAL DEL TRATAMIENTO DE LOS DATOS APLICABLE: EN RELACIÓN A LA APLICACIÓN DEL NUEVO REGLAMENTO (UE) 2016/679 DEL PARLAMENTO EUROPEO Y DEL CONSEJO, DE 27 DE ABRIL DE 2016, RELATIVO A LA PROTECCIÓN DE LAS PERSONAS FÍSICAS EN LO QUE RESPECTA AL TRATAMIENTO DE DATOS PERSONALES Y A LA LIBRE CIRCULACIÓN DE ESTOS DATOS, SE LE INFORMA Y CONSIENTE EXPRESAMENTE DE LOS SIGUIENTES EXTREMOS: "QUE, JOSE LUIS BAÑOS CONSULTING Y LA PLATAFORMA DE SERVICIOS TECNOLÓGICOS PMTK BUSINESS IN THE CLOUD, SON LOS RESPONSABLES DEL TRATAMIENTO DE SUS DATOS CON SEDE SOCIAL EN C/. DEMOCRACIA NÚM. 5 - SAN JOSE DE LA RINCONADA | 41300 LA RINCONADA ANDALUCIA ; CUYA FINALIDAD SE BASA EN UNA RELACIÓN CONTRACTUAL Y LEGAL Y, QUE LOS MISMOS, PUEDEN SER CEDIDOS A LOS SOLOS EFECTOS CONTRACTUALES; QUE LA EMPRESA LE BRINDA PODER EJERCR LOS DERECHOS A.R.C.O. Y OTROS (EL ACCESO A LOS DATOS PERSONALES RELATIVOS AL INTERESADO, Y SU RECTIFICACIÓN O SUPRESIÓN, O LA LIMITACIÓN DE SU TRATAMIENTO, O A OPONERSE AL TRATAMIENTO, ASÍ COMO EL DERECHO A LA PORTABILIDAD DE LOS DATOS); ANTE NUESTRO DELEGADO DE PROTECCIÓN DE DATOS, CUYO RESPONSABLE ES D. JOSÉ LUIS BAÑOS BELLIDO NIF 30412908P, TENIENDO COMO CANAL DE COMUNICACIÓN EL CORREO: CONSULTORIA@JLBBERP.COM
    by odoo17trydevelop - 08:16 - 24 Jun 2024

    1 attachments 1 attachments

    attachment

    2 replies 2 replies

    • Re: ledger
      Hello,

      The module account_asset_management is available in version 17 here:

      Regarding translations issues, first you need to find the module where the term to translate comes from (make sure it's an OCA module) and if something prevents you from translating them in Weblate, you can contact the email address showed on this page:

      I'm note sure if you are trying to change terms on a local database or in the OCA translation files related to OCA accounting modules, when reading your question. If it's the second option, what I just told you is relevant.

      Have a nice day,
      Virginie Dewulf
      Executive Director
      +32 477 64 17 20


      Le mer. 3 juil. 2024 à 11:55, Angel García-Junco Lora <notifications@odoo-community.org> a écrit :
      Dear colleages,
      we installed the accounting modules for the Ledgers,
      but when we try to lranaslate the ledger terms, General Ledger and Partner Ledger, these items arent don't translate
      Some one know what do  we can to trabslate these terms of the Contabilidad Menu?
      Thanks in advance
       
      El 24/06/2024 20:14 CEST Angel García-Junco Lora <software@jlbberp.com> escribió:
       
       
      Dear Colleagues,
      We try to install ledger in odoo comunity version 17, but the modules involved in it aren't compatible someone would know how, or if you could give us some indications,  about  compatibilize the module account_asset_management module, from v16 to v17?
       
      Thanks in advance
      Best Regards,
       
      Angel Luis García-Junco Lora (Departamento de Software)
       
      SOFTWARE Y SERVICIOS TECNOLÓGICOS desde 1984Calle Democracia nº5 | San José de la Rinconada
       
      41300 LA RINCONADA ( ANDALUCÍA) - ESPAÑA Teléfono Centralita :(+34)955 085 361 Móvil Telegram y WhatsApp : (+34)601325581 Email:software@jlbberp.com NORMATIVA LEGAL DEL TRATAMIENTO DE LOS DATOS APLICABLE: EN RELACIÓN A LA APLICACIÓN DEL NUEVO REGLAMENTO (UE) 2016/679 DEL PARLAMENTO EUROPEO Y DEL CONSEJO, DE 27 DE ABRIL DE 2016, RELATIVO A LA PROTECCIÓN DE LAS PERSONAS FÍSICAS EN LO QUE RESPECTA AL TRATAMIENTO DE DATOS PERSONALES Y A LA LIBRE CIRCULACIÓN DE ESTOS DATOS, SE LE INFORMA Y CONSIENTE EXPRESAMENTE DE LOS SIGUIENTES EXTREMOS: "QUE, JOSE LUIS BAÑOS CONSULTING Y LA PLATAFORMA DE SERVICIOS TECNOLÓGICOS PMTK BUSINESS IN THE CLOUD, SON LOS RESPONSABLES DEL TRATAMIENTO DE SUS DATOS CON SEDE SOCIAL EN C/. DEMOCRACIA NÚM. 5 - SAN JOSE DE LA RINCONADA | 41300 LA RINCONADA ANDALUCIA ; CUYA FINALIDAD SE BASA EN UNA RELACIÓN CONTRACTUAL Y LEGAL Y, QUE LOS MISMOS, PUEDEN SER CEDIDOS A LOS SOLOS EFECTOS CONTRACTUALES; QUE LA EMPRESA LE BRINDA PODER EJERCR LOS DERECHOS A.R.C.O. Y OTROS (EL ACCESO A LOS DATOS PERSONALES RELATIVOS AL INTERESADO, Y SU RECTIFICACIÓN O SUPRESIÓN, O LA LIMITACIÓN DE SU TRATAMIENTO, O A OPONERSE AL TRATAMIENTO, ASÍ COMO EL DERECHO A LA PORTABILIDAD DE LOS DATOS); ANTE NUESTRO DELEGADO DE PROTECCIÓN DE DATOS, CUYO RESPONSABLE ES D. JOSÉ LUIS BAÑOS BELLIDO NIF 30412908P, TENIENDO COMO CANAL DE COMUNICACIÓN EL CORREO: CONSULTORIA@JLBBERP.COM
       
      Atentamente,
       
      Angel Luis García-Junco Lora (Departamento de Software)
       
      SOFTWARE Y SERVICIOS TECNOLÓGICOS desde 1984Calle Democracia nº5 | San José de la Rinconada
       
      41300 LA RINCONADA ( ANDALUCÍA) - ESPAÑA Teléfono Centralita :(+34)955 085 361 Móvil Telegram y WhatsApp : (+34)601325581 Email:software@jlbberp.com NORMATIVA LEGAL DEL TRATAMIENTO DE LOS DATOS APLICABLE: EN RELACIÓN A LA APLICACIÓN DEL NUEVO REGLAMENTO (UE) 2016/679 DEL PARLAMENTO EUROPEO Y DEL CONSEJO, DE 27 DE ABRIL DE 2016, RELATIVO A LA PROTECCIÓN DE LAS PERSONAS FÍSICAS EN LO QUE RESPECTA AL TRATAMIENTO DE DATOS PERSONALES Y A LA LIBRE CIRCULACIÓN DE ESTOS DATOS, SE LE INFORMA Y CONSIENTE EXPRESAMENTE DE LOS SIGUIENTES EXTREMOS: "QUE, JOSE LUIS BAÑOS CONSULTING Y LA PLATAFORMA DE SERVICIOS TECNOLÓGICOS PMTK BUSINESS IN THE CLOUD, SON LOS RESPONSABLES DEL TRATAMIENTO DE SUS DATOS CON SEDE SOCIAL EN C/. DEMOCRACIA NÚM. 5 - SAN JOSE DE LA RINCONADA | 41300 LA RINCONADA ANDALUCIA ; CUYA FINALIDAD SE BASA EN UNA RELACIÓN CONTRACTUAL Y LEGAL Y, QUE LOS MISMOS, PUEDEN SER CEDIDOS A LOS SOLOS EFECTOS CONTRACTUALES; QUE LA EMPRESA LE BRINDA PODER EJERCR LOS DERECHOS A.R.C.O. Y OTROS (EL ACCESO A LOS DATOS PERSONALES RELATIVOS AL INTERESADO, Y SU RECTIFICACIÓN O SUPRESIÓN, O LA LIMITACIÓN DE SU TRATAMIENTO, O A OPONERSE AL TRATAMIENTO, ASÍ COMO EL DERECHO A LA PORTABILIDAD DE LOS DATOS); ANTE NUESTRO DELEGADO DE PROTECCIÓN DE DATOS, CUYO RESPONSABLE ES D. JOSÉ LUIS BAÑOS BELLIDO NIF 30412908P, TENIENDO COMO CANAL DE COMUNICACIÓN EL CORREO: CONSULTORIA@JLBBERP.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 Virginie Dewulf - 12:15 - 26 Jul 2024
    • Re: ledger
      Dear colleages,
      we installed the accounting modules for the Ledgers,
      but when we try to lranaslate the ledger terms, General Ledger and Partner Ledger, these items arent don't translate
      Some one know what do  we can to trabslate these terms of the Contabilidad Menu?
      Thanks in advance
       
      El 24/06/2024 20:14 CEST Angel García-Junco Lora <software@jlbberp.com> escribió:
       
       
      Dear Colleagues,
      We try to install ledger in odoo comunity version 17, but the modules involved in it aren't compatible someone would know how, or if you could give us some indications,  about  compatibilize the module account_asset_management module, from v16 to v17?
       
      Thanks in advance
      Best Regards,
       
      Angel Luis García-Junco Lora (Departamento de Software)
       
      SOFTWARE Y SERVICIOS TECNOLÓGICOS desde 1984Calle Democracia nº5 | San José de la Rinconada
       
      41300 LA RINCONADA ( ANDALUCÍA) - ESPAÑA Teléfono Centralita :(+34)955 085 361 Móvil Telegram y WhatsApp : (+34)601325581 Email:software@jlbberp.com NORMATIVA LEGAL DEL TRATAMIENTO DE LOS DATOS APLICABLE: EN RELACIÓN A LA APLICACIÓN DEL NUEVO REGLAMENTO (UE) 2016/679 DEL PARLAMENTO EUROPEO Y DEL CONSEJO, DE 27 DE ABRIL DE 2016, RELATIVO A LA PROTECCIÓN DE LAS PERSONAS FÍSICAS EN LO QUE RESPECTA AL TRATAMIENTO DE DATOS PERSONALES Y A LA LIBRE CIRCULACIÓN DE ESTOS DATOS, SE LE INFORMA Y CONSIENTE EXPRESAMENTE DE LOS SIGUIENTES EXTREMOS: "QUE, JOSE LUIS BAÑOS CONSULTING Y LA PLATAFORMA DE SERVICIOS TECNOLÓGICOS PMTK BUSINESS IN THE CLOUD, SON LOS RESPONSABLES DEL TRATAMIENTO DE SUS DATOS CON SEDE SOCIAL EN C/. DEMOCRACIA NÚM. 5 - SAN JOSE DE LA RINCONADA | 41300 LA RINCONADA ANDALUCIA ; CUYA FINALIDAD SE BASA EN UNA RELACIÓN CONTRACTUAL Y LEGAL Y, QUE LOS MISMOS, PUEDEN SER CEDIDOS A LOS SOLOS EFECTOS CONTRACTUALES; QUE LA EMPRESA LE BRINDA PODER EJERCR LOS DERECHOS A.R.C.O. Y OTROS (EL ACCESO A LOS DATOS PERSONALES RELATIVOS AL INTERESADO, Y SU RECTIFICACIÓN O SUPRESIÓN, O LA LIMITACIÓN DE SU TRATAMIENTO, O A OPONERSE AL TRATAMIENTO, ASÍ COMO EL DERECHO A LA PORTABILIDAD DE LOS DATOS); ANTE NUESTRO DELEGADO DE PROTECCIÓN DE DATOS, CUYO RESPONSABLE ES D. JOSÉ LUIS BAÑOS BELLIDO NIF 30412908P, TENIENDO COMO CANAL DE COMUNICACIÓN EL CORREO: CONSULTORIA@JLBBERP.COM
       
      Atentamente,
       
      Angel Luis García-Junco Lora (Departamento de Software)
       
      SOFTWARE Y SERVICIOS TECNOLÓGICOS desde 1984Calle Democracia nº5 | San José de la Rinconada
       
      41300 LA RINCONADA ( ANDALUCÍA) - ESPAÑA Teléfono Centralita :(+34)955 085 361 Móvil Telegram y WhatsApp : (+34)601325581 Email:software@jlbberp.com NORMATIVA LEGAL DEL TRATAMIENTO DE LOS DATOS APLICABLE: EN RELACIÓN A LA APLICACIÓN DEL NUEVO REGLAMENTO (UE) 2016/679 DEL PARLAMENTO EUROPEO Y DEL CONSEJO, DE 27 DE ABRIL DE 2016, RELATIVO A LA PROTECCIÓN DE LAS PERSONAS FÍSICAS EN LO QUE RESPECTA AL TRATAMIENTO DE DATOS PERSONALES Y A LA LIBRE CIRCULACIÓN DE ESTOS DATOS, SE LE INFORMA Y CONSIENTE EXPRESAMENTE DE LOS SIGUIENTES EXTREMOS: "QUE, JOSE LUIS BAÑOS CONSULTING Y LA PLATAFORMA DE SERVICIOS TECNOLÓGICOS PMTK BUSINESS IN THE CLOUD, SON LOS RESPONSABLES DEL TRATAMIENTO DE SUS DATOS CON SEDE SOCIAL EN C/. DEMOCRACIA NÚM. 5 - SAN JOSE DE LA RINCONADA | 41300 LA RINCONADA ANDALUCIA ; CUYA FINALIDAD SE BASA EN UNA RELACIÓN CONTRACTUAL Y LEGAL Y, QUE LOS MISMOS, PUEDEN SER CEDIDOS A LOS SOLOS EFECTOS CONTRACTUALES; QUE LA EMPRESA LE BRINDA PODER EJERCR LOS DERECHOS A.R.C.O. Y OTROS (EL ACCESO A LOS DATOS PERSONALES RELATIVOS AL INTERESADO, Y SU RECTIFICACIÓN O SUPRESIÓN, O LA LIMITACIÓN DE SU TRATAMIENTO, O A OPONERSE AL TRATAMIENTO, ASÍ COMO EL DERECHO A LA PORTABILIDAD DE LOS DATOS); ANTE NUESTRO DELEGADO DE PROTECCIÓN DE DATOS, CUYO RESPONSABLE ES D. JOSÉ LUIS BAÑOS BELLIDO NIF 30412908P, TENIENDO COMO CANAL DE COMUNICACIÓN EL CORREO: CONSULTORIA@JLBBERP.COM
      by odoo17trydevelop - 11:42 - 3 Jul 2024

      3 attachments 3 attachments

      Part_1.png
      image.png
      attachment
  • unsubscribe 
    Sorry all to bother you but I have tried to unsubscribe and always got 
but when I click the received link I get a message: The address 
stijn.vanhandsaeme@team.nubo.coop is already unsubscribed or was never 
subscribed to the mailing list, you may want to check that the address 
was correct.

I also wrote this message to support@odoo... but nothing changed.

I am out on sick leave and would appreciate being unsubscribed.


-- 
Stijn Vanhandsaeme

NUBO cvba-so | scrl-fs
rue Van Elewyck | van elewijckstraat 35
1050 Brussel | Bruxelles
BE 0719.680.909 RPM Bruxelles | RPR Brussel
    by Stijn Vanhandsaeme - 09:56 - 24 Jun 2024

    2 replies 2 replies

    • Re: unsubscribe
      Hi guys,

      I will look further into this for you tomorrow and try and sort it out.
      I'll be in touch with you individually.

      Take care,
      Rebecca

      On Mon, 24 Jun 2024 at 20:22, Tobias Quiter <notifications@odoo-community.org> wrote:
      It's the same for me, I would also like to unsubscribe, but it says, I already unsubscribe my address.

      Mit freundlichen Grüßen / Kind Regards,


      Tobias Quiter
       

      Von: Stijn Vanhandsaeme <notifications@odoo-community.org>
      Gesendet: Montag, 24. Juni 2024 09:58
      An: Contributors <contributors@odoo-community.org>
      Betreff: unsubscribe
       
      Sorry all to bother you but I have tried to unsubscribe and always got 
but when I click the received link I get a message: The address 
stijn.vanhandsaeme@team.nubo.coop is already unsubscribed or was never 
subscribed to the mailing list, you may want to check that the address 
was correct.

I also wrote this message to support@odoo... but nothing changed.

I am out on sick leave and would appreciate being unsubscribed.



-- 
Stijn Vanhandsaeme

NUBO cvba-so | scrl-fs
rue Van Elewyck | van elewijckstraat 35
1050 Brussel | Bruxelles
BE 0719.680.909 RPM Bruxelles | RPR Brussel

      _______________________________________________
      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



      --
      Rebecca Gellatly
      General Secretary
      Odoo Community Association
      by Rebecca Gellatly - 10:56 - 24 Jun 2024
    • AW: unsubscribe
      It's the same for me, I would also like to unsubscribe, but it says, I already unsubscribe my address.

      Mit freundlichen Grüßen / Kind Regards,


      Tobias Quiter
       

      Von: Stijn Vanhandsaeme <notifications@odoo-community.org>
      Gesendet: Montag, 24. Juni 2024 09:58
      An: Contributors <contributors@odoo-community.org>
      Betreff: unsubscribe
       
      Sorry all to bother you but I have tried to unsubscribe and always got 
but when I click the received link I get a message: The address 
stijn.vanhandsaeme@team.nubo.coop is already unsubscribed or was never 
subscribed to the mailing list, you may want to check that the address 
was correct.

I also wrote this message to support@odoo... but nothing changed.

I am out on sick leave and would appreciate being unsubscribed.


-- 
Stijn Vanhandsaeme

NUBO cvba-so | scrl-fs
rue Van Elewyck | van elewijckstraat 35
1050 Brussel | Bruxelles
BE 0719.680.909 RPM Bruxelles | RPR Brussel

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

      by Tobias Quiter - 10:21 - 24 Jun 2024
  • OCA Days 2024 - Early-Bird Tickets closing 30th June
    Hello OCA Contributors,

    I hope this finds you all well.

    I just wanted to remind you that our early-bird tickets for 2024 members close on the 30th June. The discounted price is €125, after this member's full price tickets are €175.
    If you aren't already a member, you can become one for the rest of the year for just €50.

    If you don't wish to become a member we still want to see you at the OCA Days 2024 - the ticket price for non-members is €190 at any time.

    Our call for speakers is open till the 16th of August, we already have some amazing proposals coming through and would love to see more.

    Any questions, please just get in touch.
    Rebecca
    OCA Days 2024 - Logo Horizontal City Tagline Dark@512.png


    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly (OCA) - 06:56 - 24 Jun 2024

    1 attachments 1 attachments

    OCA Days 2024 - Logo Horizontal City Tagline Dark@512.png
  • Is there a module...? :) 
    G'day to all!

Prior to jumping into making a new module, maybe someone solved the following somehow:

"Document Generator". 
 - a document part (component) with variants and per-variant versions
 - can be attached to a a document (e.g. product) via a dynamic "no-code" field
 - to be used in a report generation through that field.
 - wizard that kicks in before the report generation to set the actual "variant value" to that dynamic field.

Use-case: Statement of Work generation, proposal generation.

Kind regards,
Alexey
    by Alexey Pelykh - 05:06 - 21 Jun 2024