Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

  • Question regarding the process for check deposit with POS V>=14.0
    Hi everyone,

    Hope it's the proper place to share this question.
    In v12, all the payment mode for POS were journal so that it work perfectly with the check deposit module.
    Getting check in the POS could be used directly in the deposit.

    In v14, pos.payment.mode are not associated to a specific journal so that collected checks in pos ar not available for deposit.

    Is anyone has an advce for this?

    Maybe @legalsylvain @alexis-via ?

    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:00 - 23 Jan 2023

    5 replies 5 replies

  • Supplier invoice suspending 
    Hello,

a customer asks for a functionality to somehow "suspense" supplier invoice 
(payment) until some additional criteria is met - like for example supplier 
providing required documents, etc.

New state would seem ot be a good way to do this but I am a bit hesitant 
adding new state into accounting.

Is there anything else available that would provide clear visibility to 
accountant that although this bill is posted we should not be paying it yet?

Thank you. Best regards

	Radovan Skolnik
    by Radovan Skolnik - 03:10 - 20 Jan 2023

    3 replies 3 replies

    • Re: Supplier invoice suspending
      Hey, Daniel
      We are actually trying to use this module, 
      though we try 15th(the latest) version with odoo 16.
      The problem that we stuck with is that it throws ctx.review.reqested_by is undefinded error when the ‘request validation’ button is pressed.
      Hence i wonder, if you could suggest what could cause that.
      Specifically - could that be caused by version discrepancies?
      And if that’s the case - could you suggest how to migrate  it to 16th or whether there is chance someone will migrate it to 16th sooner?

      Thank you,
      Lena

      On 20 Jan 2023, at 16:22, Daniel Reis <notifications@odoo-community.org> wrote:

      I would do this preventing the Vendor Bill from being confirmed until some criteria is met.
      The Tier Validation module allows implementing this through configurable rules.
      https://odoo-community.org/shop/account-move-tier-validation-5253

      Thanks
      Daniel

      by "lena moshchot" <lena@moshchot.org> - 10:15 - 23 Jan 2023
    • Re: Supplier invoice suspending
      Maybe this can help you

      https://github.com/OCA/account-invoicing/tree/14.0/account_invoice_blocking

      Marks the lines of the invoice as blocked 

      On 20 Jan 2023 15:22, Daniel Reis <notifications@odoo-community.org> wrote:
      I would do this preventing the Vendor Bill from being confirmed until some criteria is met.
      The Tier Validation module allows implementing this through configurable rules.
      https://odoo-community.org/shop/account-move-tier-validation-5253

      Thanks
      Daniel

      On 20/01/23 14:11, Radovan Skolnik wrote:
      Hello,

a customer asks for a functionality to somehow "suspense" supplier invoice 
(payment) until some additional criteria is met - like for example supplier 
providing required documents, etc.

New state would seem ot be a good way to do this but I am a bit hesitant 
adding new state into accounting.

Is there anything else available that would provide clear visibility to 
accountant that although this bill is posted we should not be paying it yet?

Thank you. Best regards

	Radovan Skolnik

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


      --
      DANIEL REIS
      MANAGING DIRECTOR

      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office B, #34

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






      Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
      pueden contener información reservada y/o confidencial, destinada exclusivamente
      para el uso del destinatario o la persona responsable de entregarlo al mismo,
      estando su uso no autorizado prohibido legalmente.
      Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
      salvo ratificación escrita por ambas partes. En caso de su recepción por error,
      rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
      o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
      a su eliminación.
      by Enric Tobella Alomar - 03:51 - 20 Jan 2023
    • Re: Supplier invoice suspending
      I would do this preventing the Vendor Bill from being confirmed until some criteria is met.
      The Tier Validation module allows implementing this through configurable rules.
      https://odoo-community.org/shop/account-move-tier-validation-5253

      Thanks
      Daniel

      On 20/01/23 14:11, Radovan Skolnik wrote:
      Hello,

a customer asks for a functionality to somehow "suspense" supplier invoice 
(payment) until some additional criteria is met - like for example supplier 
providing required documents, etc.

New state would seem ot be a good way to do this but I am a bit hesitant 
adding new state into accounting.

Is there anything else available that would provide clear visibility to 
accountant that although this bill is posted we should not be paying it yet?

Thank you. Best regards

	Radovan Skolnik

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


      --
      DANIEL REIS
      MANAGING DIRECTOR

      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office B, #34

      by Daniel Reis - 03:21 - 20 Jan 2023
  • Weblate - use po file download/upload - revisions
    Hi, 
    I did some translation on translation.odoo-community.org using the web interface.
    Now I desire to have an overall view of a repository translation and fix some imprecisions I did, expecially for common and repeated strings.
    I see that I can download the repo's POs file but the Weblate option to upload them isn't enabled.
    If isn't possible to enable the upload, there is a way to go around this (i.e. sending the fixed files to someone)? Or the only solution is the web interface?

    Second question, on Transifex for Odoo project there is the revision option enabled that grant a better quality of the translations.
    Do you think that it can be activate on OCA Weblate too?

    Thanks for attention.
     
    PS: I hope to had use the right mailing list for this questions. 


    Stefano Consolaro
    www.mymage.it
    by Stefano Consolaro - 10:26 - 20 Jan 2023

    21 replies 21 replies

    • Re: odoo accounting and IFRS posting, reporting, rules and regulations
      Hi Joe,

      This is an interesting question. My (limited) knowledge on reporting standards, leads me to believe that having a generic IFRS compliance is asking too much to odoo.There is SO much in IFRS, that i don't see how you can have that. Having seen several SME oriented accounting software, I would say that odoo is likewise, well equipped, for simple processes; but beware of complicated processes. e.g. (but not limited to):
      - Recognition of work in progress (for MRP, or for long run services e.g. audit, or in the construction industry, or in the travel industry)
      - Everything related to consolidated figures (investment in other companies etc..)

      and this is just what I have in mind..
      So, it strongly depends on the industry, and i believe that in other standalone software, a lot of schedules are kept in Excel, and the entries are manually passed. Odoo is not worse, and at least some could be automated (customisation)

      My 2 cents,
      Dominique


      On Thu, 13 Jul 2023 at 01:48, Joerg Lorenz <notifications@odoo-community.org> wrote:
      Dear Community, 

      we are currently investigating the possibility of support of odoo community for accounting with IFRS rules and regulations. Best would be, if we would see a layered chart of accounts and accounting rules dependent on the books to reflect.
      There are various applications for layered charts of accounts,  like tax related books, valuation of stock and deprecation of inventory,  in several countries in Italy,etc. 

      On IFRS: 
      Our current findings are that Vauxoo has done a module formerly, but this is for up to V8 and addresses the matter of reporting only, it appears.

      What we do not know is if the invoicing rules, inventory deprecation and other postings and acounting posting templates are present to support a full fledged usage of odoo (community) with IFRS.
      It would be very helpful if we could get a couple of practical experience reports like "we have done it, it worked on version XY"

      It would be terrific if we could connect our client with one of your clients for exchange of experience, where we would be happy to sign an NDA as well.  Also - if appreciated - we would like to turn this job over to an experiences partner, but this could be step 2. 

      First we need to convince the client, that odoo-  and in particular the OCA - is stronger and better than the proprietary competing solutions out there. 

      Appreciate the power of out community here. Any comment welcome

      Thanks, Joe


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

      by dominique.k - 08:36 - 13 Jul 2023
    • odoo accounting and IFRS posting, reporting, rules and regulations
      Dear Community, 

      we are currently investigating the possibility of support of odoo community for accounting with IFRS rules and regulations. Best would be, if we would see a layered chart of accounts and accounting rules dependent on the books to reflect.
      There are various applications for layered charts of accounts,  like tax related books, valuation of stock and deprecation of inventory,  in several countries in Italy,etc. 

      On IFRS: 
      Our current findings are that Vauxoo has done a module formerly, but this is for up to V8 and addresses the matter of reporting only, it appears.

      What we do not know is if the invoicing rules, inventory deprecation and other postings and acounting posting templates are present to support a full fledged usage of odoo (community) with IFRS.
      It would be very helpful if we could get a couple of practical experience reports like "we have done it, it worked on version XY"

      It would be terrific if we could connect our client with one of your clients for exchange of experience, where we would be happy to sign an NDA as well.  Also - if appreciated - we would like to turn this job over to an experiences partner, but this could be step 2. 

      First we need to convince the client, that odoo-  and in particular the OCA - is stronger and better than the proprietary competing solutions out there. 

      Appreciate the power of out community here. Any comment welcome

      Thanks, Joe


      by Joerg Lorenz. - 07:48 - 12 Jul 2023
    • Re: [FIX]:Weblate - use po file download/upload - revisions
      Hi Rémi,

      Thanks for your investigation.

      Asking support from weblate is a good idea. The board agrees to free up a small budget to get specialized support and put us on the right track.

      I'll PM you with the details.

      Best regards,

      -Stéphane

      On Thu, Jun 29, 2023 at 2:12 PM Rémi CAZENAVE - Le Filament <notifications@odoo-community.org> wrote:

      Hi Stéphane, all,

      I have been looking into the best way to integrate OCA repos inside Weblate but could not figure it out by myself. I have found a few promising things however :

      I have also looked in Transifex and was able to export glossary and translation memory used by Odoo (so that OCA modules translations are as much as possible coherent with Odoo ones). Next step would be to import those in Weblate (I am working on French ones for now).


      As you mentioned, from my point of view, before going more in details on what we could do on Weblate, we would need to question the organization of projects / components. I have tried to figure out what is the best way to implement those based on Weblate documentation, but with not much findings. I think the best way-forward would be to ask support from Weblate directly to ask them what would be the most efficient way to do so.

      I have discussed this point internally at Le Filament and we would be OK to pay for a few hours of support from Weblate engineers on this OCA topic.


      Basically, I would like to present them :

      • what OCA has to translate (GitHub repos, with branches and modules inside),
      • OCA processes regarding translations (pot file generated by odoobot and pushed to Weblate, Weblate pushes translations back to repo)
      • (the way we implemented it in Weblate)
      • the languages we use

      And ask them the following :

      • What would be the best way to integrate OCA modules to ease translation while keeping automatic workflows ?
      • Also, I would like to ask them whether it is possible to merge redundant languages (for instance is it necessary to keep both fr and fr_FR translations) ?
      • What is according to them the best path towards automatic translations (keeping only review / correction / validation by translation teams before pushing to OCA repos)


      I am not sure how to get approval from OCA to perform the above (maybe even whether I should seek approval) ? Let me know if this should be granted by OCA board or if I could go forward if noone is against it (please tell me if you do object with the approach) ?

      Let me know also if you see other questions that we could ask them ?


      Best Regards,

      Rémi

      Le 22/06/2023 à 18:16, Stéphane Bidoul a écrit :
      A DeepL integration in weblate would be great. If the budget is reasonable we may even imagine that OCA could cover the DeepL cost.

      I suspect however that a prerequisite to make that work is the better organization of the projects and glossaries that I mentioned before.

      -sbi


      On Thu, Jun 22, 2023 at 5:52 PM Rémi CAZENAVE - Le Filament <notifications@odoo-community.org> wrote:

      Hi Stefano,

      We also had discussions for French translations earlier today (not really to add validation layers / access rights but rather to improve the number of translated modules) and we are about to test translating with DeepL using Traduction Memory and Glossaries to see how good it gets and if it can improve a lot contributing with French translation.

      (For now we will test it outside Weblate and import translations manually in Weblate, but it is also possible to directly interface Weblate with DeepL to get automatic translations or suggestions, maybe we could go into that direction if it really helps !)


      Also, I had a few spare minutes so I unlocked all the repositories you listed below in Weblate.

      It seems that this could be scripted but I would have needed access to the server which I do not have so I did it manually, one by one.

      As for why they were locked I cannot say, the only thing I see is that these were locked because of error, but I could not find the error...


      Best Regards,

      Rémi


      --X-BM-SIGNATURE--
      Le 22/06/2023 à 08:31, Stefano Consolaro a écrit :
      Hi Stéphane,
      you are not alone with a lot a things to do and the my reply time to your answer prove it ;-)

      We (italian members) have talked a bit and will probably install a test server after the summer to test configuration options and functionalities.
      After that we will share results and some ideas on how to rules the translations.

      In the meantime I ask you the favour to unlock some modules listed below (but there are many more).
      But, why some modules are locked?
      Is there a way to unlock all at once or do you have to do them one at a time?
      Thanks

      Modules locked
      agreement-16.0-agreement
      bank-payment-16-0-account_payment_mode
      connector-16-0-test_component
      contract-16-0-contract
      crm-16.0-crm_claim
      currency-16.0-currency_rate_update
      data-protection-16-0/data-protection-16-0-privacy
      fleet-16.0-fleet_vehicle_fuel_type_ethanol
      helpdesk-16.0-helpdesk_mgmt
      hr-16.0-hr_employee_firstname
      iot-16.0-iot_oca
      l10n-italy-16.0-l10n_it_rea
      management-system-16.0-mgmtsystem
      manufacture-16.0-mrp_warehouse_calendar
      project-16.0-project_type
      purchase-workflow-16.0-purchase_discount
      report-print-send-15-0-base_report_to_printer
      report-print-send-16-0-base_report_to_printer
      server-backend-16.0-base_user_role
      server-backend-16-0-base_user_role
      server-env-16-0-server_environment
      vertical-association-16-0-membership_extension
      vertical-hotel-15.0-hotel_reservation
      Da "Stéphane Bidoul" notifications@odoo-community.org
      Cc
      Data Sat, 10 Jun 2023 12:32:03 -0000
      Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions

      Hi Stefano,

      I also support the idea, obviously ;)

      Unfortunately that alone will not help get things moving as I have several other priorities with OCA infrastructure and tooling that already barely fit in the time I can allocate to it.
      For instance, just preventing weblate to bring down the OCA server swallowed several hours already, recently (and there is still more to do).

      I'm happy to tweak any configuration you propose but I'd need precise indications of what to do with links to the weblate documentation.
      The process part also needs to be elaborated. The high level principle you mentioned sound good but how do we concretely do that in practice? For instance, when one asks to get translation access how will Rebecca know which role to give them? What is the process to accept a new reviewer for a given language? Can we have languages with reviewers and other without? Do we need to publish who has reviewer rights? What does all that imply in terms of weblate configuration?

      Regarding glossaries and translation memories there are also important questions to be investigated. For instance, we now have one project per repo and branch. Is it possible to share glossaries across these? If not, should we / can we group them? Who should have permissions to manage glossaries, etc.

      So there is quite a bit of research to do that, as far as I know, as not been done by anyone yet.

      As I don't think these can be easily experimented live on the OCA instance (I may be wrong about that), I'd recommend anyone who would like to dive in that to setup a test weblate on their local machine and play with that to come up with a proposal or a plan. I'm happy to help with that too.

      Best regards,

      -Stéphane

      On Thu, Jun 8, 2023 at 10:01 PM Stefano Consolaro <notifications@odoo-community.org> wrote:
      Hi Stéphane,
      did you give a look to mine and Sergio replies (i attached them below)?

      Last month, as italian community, we had the Odoo Italia Days in Milan. We talked with other people interested in setting up a better way to manage translations, at least for italian language.

      We met Simone Orsi, OCA member, that support this idea.

      In fact we think that what we are looking for could be useful for all language teams.

      If you, or someone else, can invest some time to configure Weblate to activate the requested features, we can test it and give a fast feedback.

      Obviously, we welcome all people willing to join the project.

      Thanks for your time and help.

      Stefano


      Da "Stefano Consolaro" stefano.consolaro@mymage.it
      Cc
      Data Mon, 23 Jan 2023 08:40:30 +0100
      Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions

      I give my reply for italian language/community:
       
      > Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?
      As far I know we don't have problems of a misuse of the tool. What we noticed is that the "need" and the "hurry" to have the translations, or a lack in the definition of a glossary for common terms, or the contributions of a new entry (like in part I am), goes to some incorrect  or not so pertinent translations.
       
      > What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.
      Hm, here I don't know what to say, can't be done in the "same way" that PSC are nominated for repository in GitHub?
       
      > How to make sure translation proposals are not stuck for too long waiting for review?
      Yes, this is a weakness. I don't know if it can be done and how, but I'd like to have a system in which the reviewed terms can be changed only by reviewers and other terms can be changed (and then loaded) by anyone (view *).
       > Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.
      Absolutely yes: the lack of resources is a problem and (*) I prefer that a thing is done now than perfect never. So the activation of the review process should be decided by each community.

      Thanks for expanding the discussion, I hope others will join.



      Da "Sergio Zanchetta" notifications@odoo-community.org
      Cc
      Data Mon, 23 Jan 2023 10:36:56 -0000
      Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions

      Il giorno dom 22 gen 2023 alle ore 11:27 Stéphane Bidoul <notifications@odoo-community.org> ha scritto:
      We discussed a translation review mechanism before, I think, but IIRC we concluded we need a process first.

      Yes, you are right. :-)

      Below, as italian community in addition to Stefano answers, you can find a proposal.

      Here are a few questions that come to mind. There might be more.

      - Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?

      The second one. Incorrect/low level translations, not only new, that don't follow current community guidelines and glossaries (language specific).

       
      - What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.
      - How to make sure translation proposals are not stuck for too long waiting for review?

      I would replicate Transifex structure or similar, if possible. Here is a proposal:
      - Anyone can be accepted as translator, strings are pushed as soon as translated. (or on a periodic basis)
      - There is a reviewer role, reviewed strings are freezed and can't be changed by translators.
      -  The coordinator role has reviewer power and can appoint translators as reviewers.

      The coordinator could be nominated by each localization repository PSC. (l10n-*)
      He would be in charge of appointing reviewers evaluating the quality of their translations over time, based on guidelines/glossary compliance.

      - Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.

      Sure, I add that not all communities have translation guidelines. [*]

      [*] e.g. italian guidelines (and glossaries) https://www.odoo-italia.org/documentazione/14.0/traduzioni.html







      Da "Stéphane Bidoul" notifications@odoo-community.org
      Cc
      Data Sun, 22 Jan 2023 10:27:40 -0000
      Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions

      We discussed a translation review mechanism before, I think, but IIRC we concluded we need a process first.

      Here are a few questions that come to mind. There might be more.

      - Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?
      - What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.
      - How to make sure translation proposals are not stuck for too long waiting for review?
      - Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.

      Best regards,

      -sbi

      _______________________________________________
      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



      Stefano Consolaro

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

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

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

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

      by Stéphane Bidoul - 11:05 - 30 Jun 2023
    • Re: [FIX]:Weblate - use po file download/upload - revisions
      Yes, let's do at least the move of sharing glossaries and TM.

      Regards.
      by Pedro M. Baeza - 09:01 - 30 Jun 2023
    • Re: [FIX]:Weblate - use po file download/upload - revisions
      Hi Rémi,

      Thank you for your work on this topic. The proposed approach seems very coherent and offers the opportunity for significant improvements in translation processes and quality. Automating translation by using a tool like deepl seems to me to be better in most cases than no translation at all. If the process for correcting inconsistent translations is simplified, this will undoubtedly encourage more people to correct these cases. Being able to share glossaries and translation memories between projects should also increase consistency in translating the same terms across different repos. Let's see what others think.

      Regards,

      Laurent

      On Thu, Jun 29, 2023 at 2:47 PM Stefano Consolaro <notifications@odoo-community.org> wrote:
      Hi Rémi,
      thanks for your work.

      Regardless what the OCA Board will decide to do with different functionalities of Weblate, I think that know how it can works is a good things.

      We (Italian community) are a bit suspicious on automatic translations. Suggestion can be a good thing, but auto-fill the translation is a bit risky.

      What we desire much is the implementation of the review process, that has to be only tested on Weblate and then organized by OCA.

      Keep share here the news to stay all together up-to-date.

      Ciao
      Stefano

      Da "Rémi CAZENAVE - Le Filament" notifications@odoo-community.org
      Cc
      Data Thu, 29 Jun 2023 12:12:00 -0000
      Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions

      Hi Stéphane, all,

      I have been looking into the best way to integrate OCA repos inside Weblate but could not figure it out by myself. I have found a few promising things however :

      I have also looked in Transifex and was able to export glossary and translation memory used by Odoo (so that OCA modules translations are as much as possible coherent with Odoo ones). Next step would be to import those in Weblate (I am working on French ones for now).


      As you mentioned, from my point of view, before going more in details on what we could do on Weblate, we would need to question the organization of projects / components. I have tried to figure out what is the best way to implement those based on Weblate documentation, but with not much findings. I think the best way-forward would be to ask support from Weblate directly to ask them what would be the most efficient way to do so.

      I have discussed this point internally at Le Filament and we would be OK to pay for a few hours of support from Weblate engineers on this OCA topic.


      Basically, I would like to present them :

      • what OCA has to translate (GitHub repos, with branches and modules inside),
      • OCA processes regarding translations (pot file generated by odoobot and pushed to Weblate, Weblate pushes translations back to repo)
      • (the way we implemented it in Weblate)
      • the languages we use

      And ask them the following :

      • What would be the best way to integrate OCA modules to ease translation while keeping automatic workflows ?
      • Also, I would like to ask them whether it is possible to merge redundant languages (for instance is it necessary to keep both fr and fr_FR translations) ?
      • What is according to them the best path towards automatic translations (keeping only review / correction / validation by translation teams before pushing to OCA repos)


      I am not sure how to get approval from OCA to perform the above (maybe even whether I should seek approval) ? Let me know if this should be granted by OCA board or if I could go forward if noone is against it (please tell me if you do object with the approach) ?

      Let me know also if you see other questions that we could ask them ?


      Best Regards,

      Rémi

      Le 22/06/2023 à 18:16, Stéphane Bidoul a écrit :
      A DeepL integration in weblate would be great. If the budget is reasonable we may even imagine that OCA could cover the DeepL cost.

      I suspect however that a prerequisite to make that work is the better organization of the projects and glossaries that I mentioned before.

      -sbi


      On Thu, Jun 22, 2023 at 5:52 PM Rémi CAZENAVE - Le Filament <notifications@odoo-community.org> wrote:

      Hi Stefano,

      We also had discussions for French translations earlier today (not really to add validation layers / access rights but rather to improve the number of translated modules) and we are about to test translating with DeepL using Traduction Memory and Glossaries to see how good it gets and if it can improve a lot contributing with French translation.

      (For now we will test it outside Weblate and import translations manually in Weblate, but it is also possible to directly interface Weblate with DeepL to get automatic translations or suggestions, maybe we could go into that direction if it really helps !)


      Also, I had a few spare minutes so I unlocked all the repositories you listed below in Weblate.

      It seems that this could be scripted but I would have needed access to the server which I do not have so I did it manually, one by one.

      As for why they were locked I cannot say, the only thing I see is that these were locked because of error, but I could not find the error...


      Best Regards,

      Rémi


      --X-BM-SIGNATURE--
      Le 22/06/2023 à 08:31, Stefano Consolaro a écrit :
      Hi Stéphane,
      you are not alone with a lot a things to do and the my reply time to your answer prove it ;-)

      We (italian members) have talked a bit and will probably install a test server after the summer to test configuration options and functionalities.
      After that we will share results and some ideas on how to rules the translations.

      In the meantime I ask you the favour to unlock some modules listed below (but there are many more).
      But, why some modules are locked?
      Is there a way to unlock all at once or do you have to do them one at a time?
      Thanks

      Modules locked
      agreement-16.0-agreement
      bank-payment-16-0-account_payment_mode
      connector-16-0-test_component
      contract-16-0-contract
      crm-16.0-crm_claim
      currency-16.0-currency_rate_update
      data-protection-16-0/data-protection-16-0-privacy
      fleet-16.0-fleet_vehicle_fuel_type_ethanol
      helpdesk-16.0-helpdesk_mgmt
      hr-16.0-hr_employee_firstname
      iot-16.0-iot_oca
      l10n-italy-16.0-l10n_it_rea
      management-system-16.0-mgmtsystem
      manufacture-16.0-mrp_warehouse_calendar
      project-16.0-project_type
      purchase-workflow-16.0-purchase_discount
      report-print-send-15-0-base_report_to_printer
      report-print-send-16-0-base_report_to_printer
      server-backend-16.0-base_user_role
      server-backend-16-0-base_user_role
      server-env-16-0-server_environment
      vertical-association-16-0-membership_extension
      vertical-hotel-15.0-hotel_reservation
      Da "Stéphane Bidoul" notifications@odoo-community.org
      Cc
      Data Sat, 10 Jun 2023 12:32:03 -0000
      Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions

      Hi Stefano,

      I also support the idea, obviously ;)

      Unfortunately that alone will not help get things moving as I have several other priorities with OCA infrastructure and tooling that already barely fit in the time I can allocate to it.
      For instance, just preventing weblate to bring down the OCA server swallowed several hours already, recently (and there is still more to do).

      I'm happy to tweak any configuration you propose but I'd need precise indications of what to do with links to the weblate documentation.
      The process part also needs to be elaborated. The high level principle you mentioned sound good but how do we concretely do that in practice? For instance, when one asks to get translation access how will Rebecca know which role to give them? What is the process to accept a new reviewer for a given language? Can we have languages with reviewers and other without? Do we need to publish who has reviewer rights? What does all that imply in terms of weblate configuration?

      Regarding glossaries and translation memories there are also important questions to be investigated. For instance, we now have one project per repo and branch. Is it possible to share glossaries across these? If not, should we / can we group them? Who should have permissions to manage glossaries, etc.

      So there is quite a bit of research to do that, as far as I know, as not been done by anyone yet.

      As I don't think these can be easily experimented live on the OCA instance (I may be wrong about that), I'd recommend anyone who would like to dive in that to setup a test weblate on their local machine and play with that to come up with a proposal or a plan. I'm happy to help with that too.

      Best regards,

      -Stéphane

      On Thu, Jun 8, 2023 at 10:01 PM Stefano Consolaro <notifications@odoo-community.org> wrote:
      Hi Stéphane,
      did you give a look to mine and Sergio replies (i attached them below)?

      Last month, as italian community, we had the Odoo Italia Days in Milan. We talked with other people interested in setting up a better way to manage translations, at least for italian language.

      We met Simone Orsi, OCA member, that support this idea.

      In fact we think that what we are looking for could be useful for all language teams.

      If you, or someone else, can invest some time to configure Weblate to activate the requested features, we can test it and give a fast feedback.

      Obviously, we welcome all people willing to join the project.

      Thanks for your time and help.

      Stefano


      Da "Stefano Consolaro" stefano.consolaro@mymage.it
      Cc
      Data Mon, 23 Jan 2023 08:40:30 +0100
      Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions

      I give my reply for italian language/community:
       
      > Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?
      As far I know we don't have problems of a misuse of the tool. What we noticed is that the "need" and the "hurry" to have the translations, or a lack in the definition of a glossary for common terms, or the contributions of a new entry (like in part I am), goes to some incorrect  or not so pertinent translations.
       
      > What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.
      Hm, here I don't know what to say, can't be done in the "same way" that PSC are nominated for repository in GitHub?
       
      > How to make sure translation proposals are not stuck for too long waiting for review?
      Yes, this is a weakness. I don't know if it can be done and how, but I'd like to have a system in which the reviewed terms can be changed only by reviewers and other terms can be changed (and then loaded) by anyone (view *).
       > Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.
      Absolutely yes: the lack of resources is a problem and (*) I prefer that a thing is done now than perfect never. So the activation of the review process should be decided by each community.

      Thanks for expanding the discussion, I hope others will join.



      Da "Sergio Zanchetta" notifications@odoo-community.org
      Cc
      Data Mon, 23 Jan 2023 10:36:56 -0000
      Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions

      Il giorno dom 22 gen 2023 alle ore 11:27 Stéphane Bidoul <notifications@odoo-community.org> ha scritto:
      We discussed a translation review mechanism before, I think, but IIRC we concluded we need a process first.

      Yes, you are right. :-)

      Below, as italian community in addition to Stefano answers, you can find a proposal.

      Here are a few questions that come to mind. There might be more.

      - Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?

      The second one. Incorrect/low level translations, not only new, that don't follow current community guidelines and glossaries (language specific).

       
      - What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.
      - How to make sure translation proposals are not stuck for too long waiting for review?

      I would replicate Transifex structure or similar, if possible. Here is a proposal:
      - Anyone can be accepted as translator, strings are pushed as soon as translated. (or on a periodic basis)
      - There is a reviewer role, reviewed strings are freezed and can't be changed by translators.
      -  The coordinator role has reviewer power and can appoint translators as reviewers.

      The coordinator could be nominated by each localization repository PSC. (l10n-*)
      He would be in charge of appointing reviewers evaluating the quality of their translations over time, based on guidelines/glossary compliance.

      - Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.

      Sure, I add that not all communities have translation guidelines. [*]

      [*] e.g. italian guidelines (and glossaries) https://www.odoo-italia.org/documentazione/14.0/traduzioni.html







      Da "Stéphane Bidoul" notifications@odoo-community.org
      Cc
      Data Sun, 22 Jan 2023 10:27:40 -0000
      Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions

      We discussed a translation review mechanism before, I think, but IIRC we concluded we need a process first.

      Here are a few questions that come to mind. There might be more.

      - Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?
      - What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.
      - How to make sure translation proposals are not stuck for too long waiting for review?
      - Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.

      Best regards,

      -sbi

      _______________________________________________
      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



      Stefano Consolaro

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

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

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

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



      Stefano Consolaro

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



      --
      Laurent Mignon
      Senior software engineer
      T: +32 2 8883148


      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

      by Laurent Mignon - 08:55 - 30 Jun 2023

  • Sorry, i'm not familiar with git
    Hi everyone, I am discovering git/github/Pull Requests and I am receiving this error. 

    Basically I wanted to ask how can I fix this, but most importantly I want to excuse because I think that I forced pushed while trying to fix it. 

    Not sure if force pushing can really cause problems in protected branches, but I have read it's a really bad practice. 

    I suddenly panicked like I never did, of course, and immediately cancelled PR and made it new. But the error is still here. Not sure about the error, what could I do in this situation? 


    Invalid title for commit: ' [FIX] product: add explicit copy arg to property_product_pricelist'
    Thanks in advance,
    Francesco Ballerini
    by Francesco Ballerini - 12:56 - 19 Jan 2023

    8 replies 8 replies

    • Re: Sorry, i'm not familiar with git
      Thanks for the feedback Holger, is good to have some reliable indications on the right documentation to follow. For now i'll just save the link but this should go in my to-do list : )
      I just managed to solve the issue on the commit name, thanks everyone for the patience and advices.

      Il giorno gio 19 gen 2023 alle ore 23:47 Holger Brunn <notifications@odoo-community.org> ha scritto:
      > Hi Martin I made a small research and I'd like to make a try but at the same


> time I always doubt about the action I'm planning to do on git.  For


> example in this case I have read in this article

if you keep reading recipes about isolated issues you'll always doubt what 
you're doing. I recommend reading
https://git-scm.com/book/en/v2
(skip 4 and stop after 9)
and then you'll be confident on all git related actions



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

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

      by Francesco Ballerini - 12:20 - 20 Jan 2023
    • Re: Sorry, i'm not familiar with git 
      > Hi Martin I made a small research and I'd like to make a try but at the same

> time I always doubt about the action I'm planning to do on git.  For

> example in this case I have read in this article

if you keep reading recipes about isolated issues you'll always doubt what 
you're doing. I recommend reading
https://git-scm.com/book/en/v2
(skip 4 and stop after 9)
and then you'll be confident on all git related actions


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
      by Holger Brunn - 11:46 - 19 Jan 2023

      1 attachments 1 attachments

      signature.asc
    • Re: Sorry, i'm not familiar with git

      Hi Franscesco,

      In this case, you seams to force-push on a branch that you own, and no body else is working on it. So, nobody will get trouble with you force push and you don't risk to destroy works of other as you are the only one working on your branch.

      It seams to be a good practice to use '--force-with-lease' when a force push is needed. If it fails it means you have to look closer of what your doing and why the push did work by looking at the history of the local and the remote branch. Common failing cases are that you try to push on the wrong remote branch or your going to delete commits from others. For the last case you need to pull and rebase and then push again.

      As you said, you're not familiar with the basic concept of git. When using such a tool, its very recommended to understand some concept so that it reveals to you the magic behind and you will fly from your own. There are lots of tutorials on the web, choose the one that you prefer. It will saves you lots of time. :)

      See you on PR's one the OCA repository. :)

      Regards,

      Le 19 janvier 2023 18:57:25 GMT+01:00, Francesco Ballerini <notifications@odoo-community.org> a écrit :
      Hi Martin I made a small research and I'd like to make a try but at the same time I always doubt about the action I'm planning to do on git. 
      For example in this case I have read in this article https://www.educative.io/answers/how-to-change-a-git-commit-message-after-a-push that I could use:

      git commit --amend -m "New message" 
      git push --force-with-lease repository-name branch-name

      but I am not sure about the 'force' or --force-with-lease which seems a less intrusive option. What I don't understand is, if --force 'which will destroy any changes someone else has pushed to the branch' as I read in the article, and --force-with-lease will "abort if there was an upstream change to the repository", is for me enough to fetch the origin before the amend/push to make a safe amend (I am not even sure this sentence makes sense eheh) or maybe it is an alternative way that I don't know? 

      Thanks,
      Francesco 

       

      Il giorno gio 19 gen 2023 alle ore 09:27 Francesco Ballerini <francescobl.lavoro@gmail.com> ha scritto:
      Thanks, I would appreciate that a lot, if it's easy to solve for you. I was a little bit tired yesterday and don't wanna make even more trouble eheh ... : )

      Thank you,
      Francesco

      Il giorno gio 19 gen 2023 alle ore 08:32 Martin Trigaux (mat) <notifications@odoo-community.org> ha scritto:
      On 19/01/2023 00:57, Francesco Ballerini wrote:
      Invalid title for commit: ' [FIX] product: add explicit copy arg to property_product_pricelist'

      Hello,

      This one is because you have a space in the beginning of the commit message, " [FIX]" instead of "[FIX]" ;-)
      But don't worry about it if you are not sure how to amend your commit, we can handle it for you if needed.

      Martin

      _______________________________________________
      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

      --
      Rémy Taymans
      Coop IT Easy
      https://coopiteasy.be
      by Rémy Taymans - 09:01 - 19 Jan 2023
    • Re: Sorry, i'm not familiar with git
      Hi Martin I made a small research and I'd like to make a try but at the same time I always doubt about the action I'm planning to do on git. 
      For example in this case I have read in this article https://www.educative.io/answers/how-to-change-a-git-commit-message-after-a-push that I could use:

      git commit --amend -m "New message" 
      git push --force-with-lease repository-name branch-name

      but I am not sure about the 'force' or --force-with-lease which seems a less intrusive option. What I don't understand is, if --force 'which will destroy any changes someone else has pushed to the branch' as I read in the article, and --force-with-lease will "abort if there was an upstream change to the repository", is for me enough to fetch the origin before the amend/push to make a safe amend (I am not even sure this sentence makes sense eheh) or maybe it is an alternative way that I don't know? 

      Thanks,
      Francesco 

       

      Il giorno gio 19 gen 2023 alle ore 09:27 Francesco Ballerini <francescobl.lavoro@gmail.com> ha scritto:
      Thanks, I would appreciate that a lot, if it's easy to solve for you. I was a little bit tired yesterday and don't wanna make even more trouble eheh ... : )

      Thank you,
      Francesco

      Il giorno gio 19 gen 2023 alle ore 08:32 Martin Trigaux (mat) <notifications@odoo-community.org> ha scritto:
      On 19/01/2023 00:57, Francesco Ballerini wrote:
      Invalid title for commit: ' [FIX] product: add explicit copy arg to property_product_pricelist'

      Hello,

      This one is because you have a space in the beginning of the commit message, " [FIX]" instead of "[FIX]" ;-)
      But don't worry about it if you are not sure how to amend your commit, we can handle it for you if needed.

      Martin

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

      by Francesco Ballerini - 06:56 - 19 Jan 2023
    • Re: Sorry, i'm not familiar with git
      Thanks, I would appreciate that a lot, if it's easy to solve for you. I was a little bit tired yesterday and don't wanna make even more trouble eheh ... : )

      Thank you,
      Francesco

      Il giorno gio 19 gen 2023 alle ore 08:32 Martin Trigaux (mat) <notifications@odoo-community.org> ha scritto:
      On 19/01/2023 00:57, Francesco Ballerini wrote:
      Invalid title for commit: ' [FIX] product: add explicit copy arg to property_product_pricelist'

      Hello,

      This one is because you have a space in the beginning of the commit message, " [FIX]" instead of "[FIX]" ;-)
      But don't worry about it if you are not sure how to amend your commit, we can handle it for you if needed.

      Martin

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

      by Francesco Ballerini - 09:30 - 19 Jan 2023

  • Multi-company > one default bank account
    Dear Contributors,
     
    We are a young distributed devops coop, part of Bar Kayma  - a nonprofit cooperative cultural fiscal hosting consortium from Jerusalem - and a fresh member of OCA, very looking forward to becoming a contributing party to the commons. 

    Recently we started the project of implementing our fiscal hosting frameworks on self hosted  Odoo with the end-goal of developing  our vertical solution of fiscal sponsorship and self management for Non-Profit Projects for social economy peers (basically an Odoo-based OpenCollective.com equivalent) to be shared with the OCA. 

    To our understanding using Multi-Company logic is the best fit for our purposes, including the need of inter-company billing, however as a fiscal host we must be able to set one default bank account (of the main/parent company) for all the children companies.

    So with a lot of inspiration from OCA/Cooperative we started customising and extending Accounting to our needs and for V16 - but still can’t figure out how to make it work properly.

    We tried to set it as a default attribute from inherited account.move model & form, & res.partner.bank, and also muted restriction in res.bank to allow different companies have the same bank account. This however doesn’t seem to work.

    We also tried to set a default bank account value in payment mode, but we couldn’t make the parent's mode be accessible for daughter companies.

    Are we using a wrong approach to the problem?  Or deprecated methods? Had someone already ported any relevant parts of the vertical cooperative  accounting to  v16?

    We would appreciate any help, advice, suggestions, or working examples on how to add this feature without reinventing the wheel.

    Thank you in advance,
    Lena & Talia

    Moshchot Coop
    A DISTRIBUTED OPEN SOURCE COOPERATIVE



    by "Moshchot Coop" <tali@moshchot.org> - 04:10 - 18 Jan 2023

    1 attachments 1 attachments

    PastedGraphic-3.tiff

    4 replies 4 replies

    • Re: Multi-company > one default bank account
      Thank you so much for your welcoming  feedback Holger and Sylvain:)

      Indeed the French CAE accounting example (shared Journals, account, taxes ) seems to be exactly what we need - and we can use all the help we can get to port it from v12 to v16 as quickly as possible, with the goal of proposing and maintaining it as a 16 vertical cooperative fiscal host branch to the OCA/cooperative.

      We have some funds (nonprofit scale though) to start spearheading the verticalization we need and we want to invest it in helping sylvain porting  the 4 base modules to start with, or in any simpler solution with same accounting functions:
      We already have 3 other nonprofit hosts in pipeline and we’re convinced that the need for such structure is growing exponentially everywhere, not only in our cultural and activism domains but in all sorts of open source communities. Many of the most groundbreaking OS projects from allover the world are forced to use opencollective and such, and the OCA seems to be the most logical environment to offer a decentralized and mutualized alternative to them.

      Thanks in advance for any feedback and/or pointers on how to achieve that as swiftly and sustainable as possible,
      Lena && Tali

      > To our understanding using Multi-Company logic is the best fit for our

> purposes, including the need of inter-company billing, however as a fiscal

> host we must be able to set one default bank account (of the main/parent

> company) for all the children companies.

note that multicompany separates entities to some degree, but as soon as you 
allow any user of the child companies access to the configuration, they can 
undo all of this. The same if you install modules that allow users to run 
code.


> We tried to set it as a default attribute from inherited account.move model

> & form, & res.partner.bank, and also muted restriction in res.bank to allow

> different companies have the same bank account. This however doesn’t seem

> to work.

links to code are much more helpful than verbal descriptions
 

> We also tried to set a default bank account value in payment mode, but we

> couldn’t make the parent's mode be accessible for daughter companies.

did you change
https://github.com/OCA/bank-payment/blob/16.0/account_payment_mode/security/
account_payment_mode.xml#L7
?


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



      Moshchot Coop
      A DISTRIBUTED OPEN SOURCE COOPERATIVE



      by "Moshchot Coop" <tali@moshchot.org> - 11:10 - 20 Jan 2023

      3 attachments 3 attachments

      PastedGraphic-3.tiff
      signature.asc
      PastedGraphic-1.png
    • Fwd: ***SPAM*** Re: Multi-company > one default bank account
      Thank you so much for your welcoming  feedback Holger and Sylvain:)

      Indeed the French CAE accounting example (shared Journals, account, taxes ) seems to be exactly what we need - and we can use all the help we can get to port it from v12 to v16 as quickly as possible, with the goal of proposing and maintaining it as a 16 vertical cooperative fiscal host branch to the OCA/cooperative.

      We have some funds (nonprofit scale though) to start spearheading the verticalization we need and we want to invest it in helping sylvain porting  the 4 base modules to start with, or in any simpler solution with same accounting functions:
      We already have 3 other nonprofit hosts in pipeline and we’re convinced that the need for such structure is growing exponentially everywhere, not only in our cultural and activism domains but in all sorts of open source communities. Many of the most groundbreaking OS projects from allover the world are forced to use opencollective and such, and the OCA seems to be the most logical environment to offer a decentralized and mutualized alternative to them.

      Thanks in advance for any feedback and/or pointers on how to achieve that as swiftly and sustainable as possible,
      Lena && Tali

      > To our understanding using Multi-Company logic is the best fit for our

> purposes, including the need of inter-company billing, however as a fiscal

> host we must be able to set one default bank account (of the main/parent

> company) for all the children companies.

note that multicompany separates entities to some degree, but as soon as you 
allow any user of the child companies access to the configuration, they can 
undo all of this. The same if you install modules that allow users to run 
code.


> We tried to set it as a default attribute from inherited account.move model

> & form, & res.partner.bank, and also muted restriction in res.bank to allow

> different companies have the same bank account. This however doesn’t seem

> to work.

links to code are much more helpful than verbal descriptions
 

> We also tried to set a default bank account value in payment mode, but we

> couldn’t make the parent's mode be accessible for daughter companies.

did you change
https://github.com/OCA/bank-payment/blob/16.0/account_payment_mode/security/
account_payment_mode.xml#L7
?


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



      Moshchot Coop
      A DISTRIBUTED OPEN SOURCE COOPERATIVE



      by "Moshchot Coop" <tali@moshchot.org> - 10:55 - 20 Jan 2023

      3 attachments 3 attachments

      PastedGraphic-3.tiff
      signature.asc
      PastedGraphic-1.png
    • Re: Multi-company > one default bank account


      Le 18/01/2023 à 16:12, Moshchot Coop a écrit :
      Dear Contributors,
       
      We are a young distributed devops coop, part of Bar Kayma  - a nonprofit cooperative cultural fiscal hosting consortium from Jerusalem - and a fresh member of OCA, very looking forward to becoming a contributing party to the commons. 

      Recently we started the project of implementing our fiscal hosting frameworks on self hosted  Odoo with the end-goal of developing  our vertical solution of fiscal sponsorship and self management for Non-Profit Projects for social economy peers (basically an Odoo-based OpenCollective.com equivalent) to be shared with the OCA. 

      To our understanding using Multi-Company logic is the best fit for our purposes, including the need of inter-company billing, however as a fiscal host we must be able to set one default bank account (of the main/parent company) for all the children companies.

      Hi. do you mean that your child companies share the same accounting configuration ? Journals, account, taxes ? If yes, I developped in my company (GRAP) a verticalization for that purpose. (the name is CAE in France) You can take a look here and send me a message if you think that it could be mutualized. https://github.com/grap/odoo-addons-cae

      Regards.

      So with a lot of inspiration from OCA/Cooperative we started customising and extending Accounting to our needs and for V16 - but still can’t figure out how to make it work properly.

      We tried to set it as a default attribute from inherited account.move model & form, & res.partner.bank, and also muted restriction in res.bank to allow different companies have the same bank account. This however doesn’t seem to work.

      We also tried to set a default bank account value in payment mode, but we couldn’t make the parent's mode be accessible for daughter companies.

      Are we using a wrong approach to the problem?  Or deprecated methods? Had someone already ported any relevant parts of the vertical cooperative  accounting to  v16?

      We would appreciate any help, advice, suggestions, or working examples on how to add this feature without reinventing the wheel.

      Thank you in advance,
      Lena & Talia

      Moshchot Coop
      A DISTRIBUTED OPEN SOURCE COOPERATIVE



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

      -- 
Sylvain LE GAL
- GRAP, service informatique
- 3 Grande rue des Feuillants 69001 LYON, 09.72.32.33.17
- Astreinte : 06.81.85.61.43 // informatique@grap.coop
      by Sylvain LE GAL - 05:05 - 18 Jan 2023
    • Re: Multi-company > one default bank account 
      > To our understanding using Multi-Company logic is the best fit for our

> purposes, including the need of inter-company billing, however as a fiscal

> host we must be able to set one default bank account (of the main/parent

> company) for all the children companies.

note that multicompany separates entities to some degree, but as soon as you 
allow any user of the child companies access to the configuration, they can 
undo all of this. The same if you install modules that allow users to run 
code.


> We tried to set it as a default attribute from inherited account.move model

> & form, & res.partner.bank, and also muted restriction in res.bank to allow

> different companies have the same bank account. This however doesn’t seem

> to work.

links to code are much more helpful than verbal descriptions
 

> We also tried to set a default bank account value in payment mode, but we

> couldn’t make the parent's mode be accessible for daughter companies.

did you change
https://github.com/OCA/bank-payment/blob/16.0/account_payment_mode/security/
account_payment_mode.xml#L7
?


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
      by Holger Brunn - 04:55 - 18 Jan 2023

      1 attachments 1 attachments

      signature.asc
  • booking of resources

    hello, dear contributors!

    one of our clients needs a solution for managing bookings of rooms in a building (for events like conferences, parties, etc.). they have several rooms that can be booked, and each booking can have options involving objects or people, like a video projector, waiters, tables, chairs, plates and cutlery,…

    some objects are identified individually (like video projectors), while others can be considered as always available in infinite quantity (like tables, chairs, plates and cutlery) and only the amount matters.

    bookings would be created manually (on the back-end side) by our client after communicating with their customers (by e-mail, telephone,…). for each booking, a sale order should be made, and the price should depend on the room, the duration and the chosen options. the bookings (and thus availability) of each room, person, and individually identified object (like a video projector) should be visible in a calendar, and booking conflicts must be avoided.

    do you have any advice on how to implement this without reinventing the wheel?

    we looked into the resource_booking module, which seems mostly great overall, but quickly faced a constraint: a resource.booking can only book one resource.booking.combination. a combination is a fixed list of resources, and combinations must be created manually. i’m not sure how it’s supposed to be used.

    if only one resource.booking is created for a customer booking, this means that the booking and all its options must be represented by one combination. for example, if there are 4 rooms, 3 video projectors and 5 people that can be combined freely, 96 combinations (including the “no video projector” and “no waiter” choice) must be created (and each of them must be added to at least one resource.booking.type to be selectable). moreover, the client would need to search through all of these to find the desired one. and what if there could be multiple waiters? this feels awkward. also, availability is only visible per combination, not per resource, so it is not very useful. however, it seems that availability conflicts are checked per resource, but in case of conflict, no information is given about which resource is not available.

    another option is to create one combination per resource, and create multiple resource.bookings (with the same date and the same partner) for one customer booking. this is more flexible, but there are no direct links between all of these bookings. what if the customer wants to change the date or cancel the booking?

    for billing, sale_resource_booking allows to link a product to a resource.booking.combination, so one product is needed for each combination. it also allows to generate a sale order from a resource booking type (so combination and dates must be selected afterwards), but i didn’t find a way to do it from a booking, which would be more useful.

    i understand why using combinations can be useful (as a compound for common use cases), and this is maybe a good technical decision (because it can avoid duplication), but i think that as they are, it seems that, in many cases, they get in the way instead of helping. am i maybe missing something obvious?

    here are some possibilities i’m currently considering:

    1. use one resource.booking per booking, but hide the combinations from the user (using a wizard, for example). the user would select all desired resources, and a matching combination would be used if one exists, or one would be created on the fly.
    2. use multiple resource.bookings per booking (one for each resource), create one combination per resource, and find a way to link resource.bookings together.
    3. extend resource.booking by allowing multiple combinations to be booked per booking (instead of only one), and create one combination per resource.
    4. extend resource.booking by allowing multiple resources to be booked directly per booking (instead of a combination), and don’t use combinations.

    for objects considered as always available, use a product, and extend resource.booking by allowing multiple products (with a quantity) to be linked to a booking, or simply add them directly to the generated sale order.

    i’m pretty sure that this resource booking use case is quite common, and having a generic solution that works for most cases would be useful. do you have any ideas about all this?

    cheers,

    hugues de keyzer
    coop it easy

    by hugues - 08:55 - 17 Jan 2023

    4 replies 4 replies

    • Re: booking of resources

      hello,

      thank you, pedro, olaf, and jairo, for your answers.

      what we ended up doing is creating a module (resource_booking_auto_create) that adds a wizard that allows to select resources by category, and create resource combinations on the fly. it is available in oca/calendar#83. reviews welcome.

      while this solution works, it feels to me like a big workaround. i realized too late into the development process (our budget on this was too limited) that a better solution would be to split the resource_booking module into multiple parts, because it handles too many independent things:

      • resource_booking would be the base module which defines the resource.booking model and allows to book resources directly (m2m relationship to resource.resource) and handle the availability of resources.
      • resource_booking_type would depend on resource_booking and define the resource.booking.type model.
      • resource_booking_combination would depend on resource_booking_type and define the resource.booking.combination model.

      installing resource_booking_combination would result in the same behavior as is currently the case with resource_booking. in our case, we would depend only on resource_booking instead of creating useless combinations under the hood.

      what do you think of this refactoring?

      we also needed to be able to link a resource booking to a sale order. the sale_resource_booking module (which has not yet been migrated to 14.0) allows this but works in the opposite way of what we needed: it allows to schedule a booking from an existing sale order, while we wanted to create a sale order from a scheduled booking.

      we ended up creating a new module resource_booking_sale that creates a sale order for each resource booking and displays (and allows to edit) the sale order lines directly on the resource booking form. it also allow to link a product to a resource booking type and to a resource and generates the sale order lines based on this. it is available here. what do you think? reviews welcome.

      for the module containing the wizard, we had to define a resource.category model. we did it in another module (resource_category) (oca/calendar#83 adds several modules). it is a really simple addition (just a simple resource.category model with a name and m2m relationship between it and resource.resource), but i think that it should not belong in oca/calendar. i think that we are missing an oca/resource repository for modules handling resources.

      what do you think?

      cheers,

      hugues
      coop it easy

      by hugues - 11:40 - 22 Feb 2023
    • Re: booking of resources
      Hi Hughes!

      El mar, 17 de ene de 2023 a las 19:56:59 PM, hugues de keyzer <notifications@odoo-community.org> escribiĆ³:
      if there are 4 rooms, 3 video projectors and 5 people that can be combined freely, 96 combinations (including the ā€œno video projectorā€ and ā€œno waiterā€ choice) must be created (and each of them must be added to at least one resource.booking.type to be selectable). moreover, the client would need to search through all of these to find the desired one. and what if there could be multiple waiters? this feels awkward

      Although you might feel like the combinations design is weird, the use case you're proposing here is actually a good reason why it exists.

      Are customers able to do a single booking of 2 projectors? That's unlikely. Or 1 projector and 2 rooms? Also very unlikely. 1 projector, 1 room and 2 waiters? That could be. 1 projector and no waiters or rooms? Depends on the case. Are all projectors available in all rooms? Or some rooms have a projector installed statically that can't be booked for another room? Are all rooms in the same building, or are they in different buildings? Are all buildings in the same country? Are there big rooms that cannot be handled by just 1 waiter?

      The amount of possible combinations (and more important: the impossible combinations) justifies the existence of resource.booking.combination.

      So IMHO the best approach would be to simplify the usage of resource.booking.combination, instead of replacing it. Some ideas:

      1. Add a button "Generate combinations". The button opens a wizard that will help you create combinations massively.
      2. When the user is selecting the combination, improve the UX making them available to pick resources individually. The engine would then select the appropriate combination under the hood.
      3. Add an option to the type: "Allow all possible combinations". Then, when customer selects the combination, resource by resource (idea 2), if it doesn't exist, it will be created on demand.
      Other than that, it seems to me like the use case you described fits perfectly in the resource_booking collection, so you'll probably be better improving them than reinventing them.
      by Jairo Llopis - 09:46 - 19 Jan 2023
    • Re: booking of resources

      On 17 Jan 2023, at 20:56, hugues de keyzer wrote:

      hello, dear contributors!

      one of our clients needs a solution for managing bookings of rooms in a building (for events like conferences, parties, etc.). they have several rooms that can be booked, and each booking can have options involving objects or people, like a video projector, waiters, tables, chairs, plates and cutlery,…

      some objects are identified individually (like video projectors), while others can be considered as always available in infinite quantity (like tables, chairs, plates and cutlery) and only the amount matters.

      bookings would be created manually (on the back-end side) by our client after communicating with their customers (by e-mail, telephone,…). for each booking, a sale order should be made, and the price should depend on the room, the duration and the chosen options. the bookings (and thus availability) of each room, person, and individually identified object (like a video projector) should be visible in a calendar, and booking conflicts must be avoided.

      do you have any advice on how to implement this without reinventing the wheel?

      we looked into the resource_booking module, which seems mostly great overall, but quickly faced a constraint: a resource.booking can only book one resource.booking.combination. a combination is a fixed list of resources, and combinations must be created manually. i’m not sure how it’s supposed to be used.

      if only one resource.booking is created for a customer booking, this means that the booking and all its options must be represented by one combination. for example, if there are 4 rooms, 3 video projectors and 5 people that can be combined freely, 96 combinations (including the “no video projector” and “no waiter” choice) must be created (and each of them must be added to at least one resource.booking.type to be selectable). moreover, the client would need to search through all of these to find the desired one. and what if there could be multiple waiters? this feels awkward. also, availability is only visible per combination, not per resource, so it is not very useful. however, it seems that availability conflicts are checked per resource, but in case of conflict, no information is given about which resource is not available.

      another option is to create one combination per resource, and create multiple resource.bookings (with the same date and the same partner) for one customer booking. this is more flexible, but there are no direct links between all of these bookings. what if the customer wants to change the date or cancel the booking?

      for billing, sale_resource_booking allows to link a product to a resource.booking.combination, so one product is needed for each combination. it also allows to generate a sale order from a resource booking type (so combination and dates must be selected afterwards), but i didn’t find a way to do it from a booking, which would be more useful.

      i understand why using combinations can be useful (as a compound for common use cases), and this is maybe a good technical decision (because it can avoid duplication), but i think that as they are, it seems that, in many cases, they get in the way instead of helping. am i maybe missing something obvious?

      here are some possibilities i’m currently considering:

      1. use one resource.booking per booking, but hide the combinations from the user (using a wizard, for example). the user would select all desired resources, and a matching combination would be used if one exists, or one would be created on the fly.
      2. use multiple resource.bookings per booking (one for each resource), create one combination per resource, and find a way to link resource.bookings together.
      3. extend resource.booking by allowing multiple combinations to be booked per booking (instead of only one), and create one combination per resource.
      4. extend resource.booking by allowing multiple resources to be booked directly per booking (instead of a combination), and don’t use combinations.

      for objects considered as always available, use a product, and extend resource.booking by allowing multiple products (with a quantity) to be linked to a booking, or simply add them directly to the generated sale order.

      i’m pretty sure that this resource booking use case is quite common, and having a generic solution that works for most cases would be useful. do you have any ideas about all this?

      cheers,

      hugues de keyzer
      coop it easy

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

      Another option besides resource.booking would be to just use the rental modules
      and add all rooms and individual objects as products in Odoo.
      You can then use products packs and product sets to create combinations or
      standard offers of the base products.

      Olaf
      --
      Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com
      Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
      Geschäftsführer: Olaf Wagner | Sitz: Berlin
      Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194

      by Olaf Wagner - 09:51 - 18 Jan 2023
    • Re: booking of resources
      Hi, Hugues,

      You can expand current resource_booking for adding the concept of "quantity of a resource" for not having to declare each of them individually, and also add a resource type. Then, both can be added to the resource combination for not needing to declare such an amount of combinations. I think it's not so hard to plug both features into the current module and will prevent you from reinventing the wheel.

      Regards.
      by Pedro M. Baeza - 09:26 - 18 Jan 2023
  • OCA Module to visualize attachment in tree view

    hi all,

    I'd like to have the possibility to display a column in a tree view with the number of attachment related to the item.

    something like that :

    Ideally, I'd like

    - to have the attachment quantity field stored to have the possibility to filter items with attachment(s)

    - to have a widget="attachment" to have the possibility to open quickly the attachment(s) with a minimal number of click.

    do you know if such feature exists in OCA ?

    Thanks !


    -- 
Sylvain LE GAL
- GRAP, service informatique
- 3 Grande rue des Feuillants 69001 LYON, 09.72.32.33.17
- Astreinte : 06.81.85.61.43 // informatique@grap.coop
    by Sylvain LE GAL - 05:25 - 13 Jan 2023

    1 attachments 1 attachments

    zxjbXiQ0iaB8o07j.png

    1 replies 1 replies

  • Proposing PSC l10n-thailand
    Hello everyone,

    I was one of the developers of l10n-thailand repository. I would like to propose myself as a PSC l10n-thailand for improving and migrating.

    My github account: Saran440 

    Thank you,
    Saran Lim.
    by saranl - 07:25 - 11 Jan 2023

    5 replies 5 replies

  • Packaging management repository
    Hi all,


    I'm questioning about a repository for packaging management as some have added great modules to enhance experience at that level but splitted in several repos (warehouse/workflow/wms)

    Currently, we inherited an historical repository which is under-used due to its weird naming 'stock-logistics-tracking'. As Odoo in early versions named Packages as 'stock.tracking' : https://github.com/odoo/odoo/blob/6.1/addons/stock/stock.py#L474

    I see several approaches but I wanted the advice of wise people:

    - Rename 'stock-logistics-tracking' repository into 'stock-logistics-packaging' (which is not as easy as it seems to be, I suppose).
    - Create the new repository
    - Keeping the old one, adding all the stuff to be clearer : better README, better repo description, ... (easiest one).


    Thanks for your feedback

    --

    Denis Roussel
    Software Engineer
    T    : +32 2 888 31 49
    M : +32 472 22 00 57


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg
    by Denis Roussel. - 09:36 - 10 Jan 2023

    2 replies 2 replies

    • Re: Packaging management repository
      product pack is not related.

      Here, it is packaging management for warehouse operations (the box you put products into). 'Put in pack' related operations.

      On Tue, Jan 10, 2023 at 10:31 AM Daniel Reis <notifications@odoo-community.org> wrote:
      There is also this:
      https://github.com/OCA/product-pack

      To assist contributors finding the right repo, they need a good README description stating their scope, and listing "neighbor" repos that are candidates for modules that are close but out of scope.

      Thanks
      Daniel

      On 10/01/23 08:37, Roussel, Denis wrote:
      Hi all,


      I'm questioning about a repository for packaging management as some have added great modules to enhance experience at that level but splitted in several repos (warehouse/workflow/wms)

      Currently, we inherited an historical repository which is under-used due to its weird naming 'stock-logistics-tracking'. As Odoo in early versions named Packages as 'stock.tracking' : https://github.com/odoo/odoo/blob/6.1/addons/stock/stock.py#L474

      I see several approaches but I wanted the advice of wise people:

      - Rename 'stock-logistics-tracking' repository into 'stock-logistics-packaging' (which is not as easy as it seems to be, I suppose).
      - Create the new repository
      - Keeping the old one, adding all the stuff to be clearer : better README, better repo description, ... (easiest one).


      Thanks for your feedback

      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57

      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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


      --
      DANIEL REIS
      MANAGING DIRECTOR

      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office B, #34

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



      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg
      by Denis Roussel. - 10:36 - 10 Jan 2023
    • Re: Packaging management repository
      There is also this:
      https://github.com/OCA/product-pack

      To assist contributors finding the right repo, they need a good README description stating their scope, and listing "neighbor" repos that are candidates for modules that are close but out of scope.

      Thanks
      Daniel

      On 10/01/23 08:37, Roussel, Denis wrote:
      Hi all,


      I'm questioning about a repository for packaging management as some have added great modules to enhance experience at that level but splitted in several repos (warehouse/workflow/wms)

      Currently, we inherited an historical repository which is under-used due to its weird naming 'stock-logistics-tracking'. As Odoo in early versions named Packages as 'stock.tracking' : https://github.com/odoo/odoo/blob/6.1/addons/stock/stock.py#L474

      I see several approaches but I wanted the advice of wise people:

      - Rename 'stock-logistics-tracking' repository into 'stock-logistics-packaging' (which is not as easy as it seems to be, I suppose).
      - Create the new repository
      - Keeping the old one, adding all the stuff to be clearer : better README, better repo description, ... (easiest one).


      Thanks for your feedback

      --

      Denis Roussel
      Software Engineer
      T    : +32 2 888 31 49
      M : +32 472 22 00 57

      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

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


      --
      DANIEL REIS
      MANAGING DIRECTOR

      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office B, #34

      by Daniel Reis - 10:30 - 10 Jan 2023
  • vertical-agriculture
    Hi all,

    I would like to apply as PSC on


    I can maintain the repo


    Thanks

    Regards
    by David BEAL - 01:06 - 6 Jan 2023

    9 replies 9 replies

  • Financial Factoring
    Hello everyone and Happy New Year!

    I am looking for a solution that would allow a company to manage financial factoring with Odoo?


    I have never seen any module to support this but maybe I missed something.

    Thank you.

    Max
    by Maxime Chambreuil - 10:56 - 4 Jan 2023

    5 replies 5 replies

  • Wake up Manufacture and Maintenance repos
    Hi all,
    I'm porting some module to v16.0: i started with something for managemetnt-system and maintenance filling holes on 15.0 and 14.0 (13.0 if necessary), and I'm interested to Manufacture repo too.
    But I saw that there isn't much activity here in recent time.
    There are someone (PSC I think) that can assist me in this work? Mainly to approve and merge PRs but sometime to help me in strange (for me) errors?
    The same for Maintenance repo.
     
    Thanks 

    Stefano Consolaro
    mymage.it
    by Stefano Consolaro - 05:30 - 22 Dec 2022

    1 replies 1 replies

    • Re: Wake up Manufacture and Maintenance repos
      I've been doing some work there and can help.
      You can ping me with @dreispt

      Thanks
      Daniel

      On 22/12/22 16:31, Stefano Consolaro wrote:
      Hi all,
      I'm porting some module to v16.0: i started with something for managemetnt-system and maintenance filling holes on 15.0 and 14.0 (13.0 if necessary), and I'm interested to Manufacture repo too.
      But I saw that there isn't much activity here in recent time.
      There are someone (PSC I think) that can assist me in this work? Mainly to approve and merge PRs but sometime to help me in strange (for me) errors?
      The same for Maintenance repo.
       
      Thanks 

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


      --
      DANIEL REIS
      MANAGING DIRECTOR

      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office B, #34

      by Daniel Reis - 05:41 - 22 Dec 2022
  • Bank Account Security
    Hi all,

    During an evaluation of OCA payment order module we discovered a critical default security issue in Odoo. (Note this is V14, but I doubt Odoo did anything)

    Fundamentally, anybody with Contact Creation rights has unfettered access to bank accounts (res.partner.bank). Of course the issue here is with payment orders or any sort of manual/automatic payment upload where the account comes from Odoo as anyone with those rights can just change the account of a large supplier, get paid, move to Caymans.

    On the other hand, where an account does not exist it is created during reconciliation.

    My gut feel is I want to create a simple security addon which just restricts who can Edit/Delete bank accounts. Maybe create too if I can find the creates and work around them.

    So some questions
    Is it a good idea?
    Does it already exist?
    Which repo?
    For create as well?
    For advisor rights (I think nearly all with advisor rights will be members of professional accounting bodies and bound to professional standards OR a business principal) or a new group?
    Only for automated payment scenarios or by default? my gut says actually this is a big issue and should be default.
    by Graeme Gellatly - 10:56 - 19 Dec 2022

    14 replies 14 replies

  • Javascript Debug
    Hello you,

    when debuggin js with chrome in v16 and v15 the js/css is located in a non named subfolder.
    In v14, it is not the case. There it looks more right. (See attached images.)
    I could believe, thats why I can not debug inside Intellij, because the path mapping does not work correctly.

    Has anyone here an idea ?

    Thank you all.

     












    has got anyone an idea why the javascript/scss/... sources are not located under the running domain
    Vielen Dank und viele Grüße

    Stefan Wild
    Geschäftsführer
    sewisoft.de - Logo

    sewisoft GmbH
    Örtleinsweg 39
    96148 Baunach

    info@sewisoft.de
    Tel. +49 (0) 160 / 99 11 25 69
    www.sewisoft.de

    Sitz der Gesellschaft: Baunach
    Registergericht: Amtsgericht Bamberg, HRB 8508
    Geschäftsführer: Günter Selbert, Stefan Wild



    by Stefan Wild - 02:26 - 17 Dec 2022

    4 attachments 4 attachments

    0hvOlSVhbsBSzX2j.jpeg
    ydu4R3ustUZAmNcy.png
    fMfcjII9OBS9VQMQ.png
    F22m81qcEoka8yji.png

    2 replies 2 replies

    • Re: Javascript Debug 
      > when debuggin js with chrome in v16 and v15 the js/css is located in a non

> named subfolder. In v14, it is not the case. There it looks more right.

> (See attached images.) I could believe, thats why I can not debug inside

> Intellij, because the path mapping does not work correctly.

> 

> Has anyone here an idea ?

the files in the source map those versions generate have leading slashes. Given 
this is a non-standard by google, I'd figure whatever chrome does is correct 
and the fact that firefox handles this more gracefully is a fluke.

You might try to remove leading slashes in
https://github.com/odoo/odoo/blob/16.0/odoo/tools/sourcemap_generator.py#L95
and see if this fixes your problem.


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
      by Holger Brunn - 09:16 - 18 Dec 2022

      1 attachments 1 attachments

      signature.asc
    • Re: Javascript Debug 
      > when debuggin js with chrome in v16 and v15 the js/css is located in a non

> named subfolder. In v14, it is not the case. There it looks more right.

> (See attached images.) I could believe, thats why I can not debug inside

> Intellij, because the path mapping does not work correctly.

> 

> Has anyone here an idea ?

the files in the source map those versions generate have leading slashes. Given 
this is a non-standard by google, I'd figure whatever chrome does is correct 
and the fact that firefox handles this more gracefully is a fluke.

You might try to remove leading slashes in
https://github.com/odoo/odoo/blob/16.0/odoo/tools/sourcemap_generator.py#L95
and see if this fixes your problem.


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
      by "Holger Brunn" <mail@hunki-enterprises.nl> - 09:16 - 18 Dec 2022

      1 attachments 1 attachments

      signature.asc
  • Weblate project is locked
    Hi,

    This project https://translation.odoo-community.org/projects/commission-15-0/commission-15-0-account_commission/ seems to have been locked since the module https://github.com/OCA/commission/tree/15.0/account_commission was added on 5 December, and we have not been able to work on the translation on it.

    The lock seems to have been done due to the following alert:

    > No file mask matches.
    >   This component set up is incomplete, as it lacks any translations.
    > * Starting new translations directly in Weblate is possible, and creates files based on the file mask.
    > * Check whether the file mask account_commission/i18n/*.po matches files in your version control system repository.

    This is a brand new module, and therefore there is no *.po file yet.


    Questions:

    1. Is this (i.e. the project gets locked for new modules with no translation) how Weblate projects are supposed to behave?

    2. How can we unlock such projects?

    Thank you.

    -- 
    Yoshi Tashiro

    by Yoshi Tashiro - 03:01 - 16 Dec 2022

    3 replies 3 replies

    • Re: Weblate project is locked
      > I guess there is no concrete plans on this at this point.

      Indeed :)

      Please send the reports to transbot@odoo-community.org. I monitor that one and will handle the requests.
      If there are enough of them I guess that will motivate me to dig deeper :)

      -sbi

      On Mon, Dec 19, 2022 at 2:52 PM Yoshi Tashiro <notifications@odoo-community.org> wrote:
      Thank you very much, Stephane.

      > We could broaden repository maintenance access but probably not to all translators.

      I guess there is no concrete plans on this at this point.  I may bring up this topic when the problem starts bugging me, but until then please allow us to report individual issues here if this is the proper channel.

      Thanks again.
      -- 
      Yoshi Tashiro



      On Mon, Dec 19, 2022 at 8:22 PM Stéphane Bidoul <notifications@odoo-community.org> wrote:
      Hi Yoshi,

      On Fri, Dec 16, 2022 at 3:02 PM Yoshi Tashiro <notifications@odoo-community.org> wrote:
      1. Is this (i.e. the project gets locked for new modules with no translation) how Weblate projects are supposed to behave?

      No. Unfortunately I don't know exactly why it happens yet. 
      It sometimes happen when there are git sync issues but it was not the case here.

      2. How can we unlock such projects?

      I unlocked it just now.

      We could broaden repository maintenance access but probably not to all translators.

      Best regards,

      -sbi

      _______________________________________________
      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 Stéphane Bidoul - 03:41 - 19 Dec 2022
    • Re: Weblate project is locked
      Thank you very much, Stephane.

      > We could broaden repository maintenance access but probably not to all translators.

      I guess there is no concrete plans on this at this point.  I may bring up this topic when the problem starts bugging me, but until then please allow us to report individual issues here if this is the proper channel.

      Thanks again.
      -- 
      Yoshi Tashiro



      On Mon, Dec 19, 2022 at 8:22 PM Stéphane Bidoul <notifications@odoo-community.org> wrote:
      Hi Yoshi,

      On Fri, Dec 16, 2022 at 3:02 PM Yoshi Tashiro <notifications@odoo-community.org> wrote:
      1. Is this (i.e. the project gets locked for new modules with no translation) how Weblate projects are supposed to behave?

      No. Unfortunately I don't know exactly why it happens yet. 
      It sometimes happen when there are git sync issues but it was not the case here.

      2. How can we unlock such projects?

      I unlocked it just now.

      We could broaden repository maintenance access but probably not to all translators.

      Best regards,

      -sbi

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

      by Yoshi Tashiro - 02:51 - 19 Dec 2022
    • Re: Weblate project is locked
      Hi Yoshi,

      On Fri, Dec 16, 2022 at 3:02 PM Yoshi Tashiro <notifications@odoo-community.org> wrote:
      1. Is this (i.e. the project gets locked for new modules with no translation) how Weblate projects are supposed to behave?

      No. Unfortunately I don't know exactly why it happens yet. 
      It sometimes happen when there are git sync issues but it was not the case here.

      2. How can we unlock such projects?

      I unlocked it just now.

      We could broaden repository maintenance access but probably not to all translators.

      Best regards,

      -sbi
      by Stéphane Bidoul - 12:21 - 19 Dec 2022
  • M14 Accounting for French 'Collectivités locales'
    Dear french OCA contributors,

    I am actually working on a RFQ for accounting software of a French Polynesia City Hall. It works the same as in France due to the regulations.
    We need M14 implementation (Budgets and Accounting) and PES (Protocole d'échanges standards)

    RFQ deadline is before january 4th 2023
    Launching production is planned april 2023

    If someone interested in answering with us for RFQ and developing modules, please contact me

    Best regards
    by Cyril VINH-TUNG - 07:01 - 15 Dec 2022
  • OCA - Github - Switch brach by default

    Hello!

     

    I would like to know as PSC if I can change the default branch of a repository and how 😊

     

    For example, by default account-financial-reporting is v13, It should be v15. Isn’t it?

     

    https://github.com/OCA/account-financial-reporting

     

    More branches by default are v14, etc.

     

    Thanks

    Regards

    Rafael

     

    by "Rafael Blasco" <rblasco@rbnpro.com> - 03:26 - 14 Dec 2022

    3 replies 3 replies

  • Translation for Odoo core<=12.0
    Hi all,

    as Odoo deletes translation ability for versions not supported, is it possible to create a project in weblate for these versions?

    As an alternative, I'll do PRs for every term to translate, perhaps not the better way (an user without git knowledge will find it hard to do).

    Thanks,
    Sergio Corato
    by Sergio Corato - 12:05 - 14 Dec 2022

    4 replies 4 replies

  • Re: pre-commit changes
    > The idea of the first pre-commit set is to store the automatic changes

    Well, I was coming from a place where I'd separate aesthetic changes (automatic or not) vs. functional changes, but thanks for clarifing that.

    I'll squash my intermediate commit into the Migration one.

    Have a nice day.
    by Marco Colombo - 02:10 - 6 Dec 2022

    2 replies 2 replies

    • Re: pre-commit changes
      Daniel, the question is not related to the pre-commit config, but the changes that pre-commit does on your code.

      Regards.
      by Pedro M. Baeza - 04:25 - 9 Dec 2022
    • Re: pre-commit changes
      Actually, pre-commit config updates should be on their own commit, so that they don't contaminate the module history.

      You may want to also create a separate PR cherry-picking that particular commit, that can be fat tracked by maintainers.
      That will avoid the risk of someone else proposing a different commit to update pre-commit config, that will cause you merge conflicts.

      Thanks
      Daniel

      On 06/12/22 13:11, Marco Colombo wrote:
      > The idea of the first pre-commit set is to store the automatic changes

      Well, I was coming from a place where I'd separate aesthetic changes (automatic or not) vs. functional changes, but thanks for clarifing that.

      I'll squash my intermediate commit into the Migration one.

      Have a nice day.

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


      --
      DANIEL REIS
      MANAGING DIRECTOR

      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office B, #34

      by Daniel Reis - 10:35 - 9 Dec 2022
  • Migration 12.0 -> 13.0 and field collision
    Hi,

    I'm starting a migration process for a copy of our production database and it fails on the following error (detailed log attached):

    ERROR mig_9008 odoo.sql_db: bad query:
                UPDATE ir_model_fields
                SET name = 'notified_partner_ids'
                WHERE name = 'needaction_partner_ids'
                    AND model = 'mail.message'

    ERROR: duplicate key value violates unique constraint "ir_model_fields_name_unique"
    DETAIL:  Key (model, name)=(mail.message, notified_partner_ids) already exists.
     
    ERROR mig_9008 OpenUpgrade: mail: error in migration script mail/migrations/13.0.1.0/pre-migration.py: duplicate key value violates unique constraint "ir_model_fields_name_unique"

    I tracked down the issue and I found out that the `notified_partner_ids` field was an existing field added in 7.0 but deleted in 9.0.
    Maybe this field should have been dropped or renamed to `openupgrade_legacy_xxx`, I don't know if it should be the case or if I made a mistake in my original upgrade path, but this field still exists in our database even if not referenced in any files.

    Whatever, if you are in my case, I made a PR to identify and remove orphaned fields (for the database_cleanup module):

    For the record, we have more than 1000 orphaned fields (list attached) in our production database (updated from 6.1 -> 7.0 -> 8.0 -> 9.0 -> 10.0 -> 11.0 in october 2020)

    by Yann Papouin - 11:46 - 6 Dec 2022

    2 attachments 2 attachments

    cleanup.purge.line.field.xls
    migration_log.txt