Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
-
Re: Shopinvader E-Commerce Bugs with odoo 12 docker image
Hello Mohamed !Shopinvader e-commerce has a new version developed in vueJs and NuxtJs and the API on Odoo side also changed a lot (Fast API now) !We still have some costumers using the old stack, but if you are starting from scratch, it would be better to start from the newest stack (available on Odoo 14 and Odoo 16).Here is the template https://github.com/shopinvader/shopinvader-template-nuxtjsBest regards,DoraLe lun. 23 sept. 2024 à 23:38, mohamed alkobrosly <notifications@odoo-community.org> a écrit :Dear community.
One of my customers needs an E-Commerce application that depends on odoo in the backend.
A friend of mine recommended the Shopinvader project to use.
I have read about it, I cloned many of it's repositories.
I tried to follow the documentation and install and run the "getting started" docker-compose app.
It failed to run due to old odoo 12 dependency.
I really need to install and try this project so that if it is useful I can upgrade to version 17 and share it in the community.
Any guidance on how to install and run it without bugs even in version 16 of odoo?
Thanks community_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by "Dora Jurcevic" <dora.jurcevic@akretion.com.br> - 05:06 - 24 Sep 2024 -
Re: [16.0] Reset to Draft button disappear after changed Price on Vendor Bills
Thank You!!! I'll check it out.
On 9/24/24 10:52, María Florencia Frigieri Parma wrote:
El mar, 24 sept 2024 a las 11:22, Rolando Pérez Rebollo (<notifications@odoo-community.org>) escribió:
Hi team, We recently upgrade a client from v13 to v16, and now they are being hit by the infamous "Reset to Draft button disappear after changed Price on Vendor Bills" (https://github.com/odoo/odoo/issues/114732). I have read a lot of code, blog posts, comments on github issues an so on. Because fiscal regulations the customer can't issue credit notes as Odoo officially suggested as workaround. So, has anyone figured out some strategy to solve this problem. I'm a developer, maybe someone could point me to functional steps to in somehow revert or reevaluate the problematic stock.valuation.layers. This customer uses multi currency, so the currency rate variations between product reception and bill confirmation date makes almost every vendor bill gets blocked with no chances to any form of modification. Has anyone come out with a bright solution?
_______________________________________________
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 Ing. Rolando Pérez Rebollo - 05:06 - 24 Sep 2024 -
Re: [16.0] Reset to Draft button disappear after changed Price on Vendor Bills
Hi Rolando,what about the proposed solution in the issue? Simply show the button again by changing the view.RegardsChristianVon: "Rolando Pérez Rebollo" <notifications@odoo-community.org>
An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
Gesendet: Dienstag, 24. September 2024 16:22:00
Betreff: [16.0] Reset to Draft button disappear after changed Price on Vendor BillsHi team, We recently upgrade a client from v13 to v16, and now they are being hit by the infamous "Reset to Draft button disappear after changed Price on Vendor Bills" (https://github.com/odoo/odoo/issues/114732). I have read a lot of code, blog posts, comments on github issues an so on. Because fiscal regulations the customer can't issue credit notes as Odoo officially suggested as workaround. So, has anyone figured out some strategy to solve this problem. I'm a developer, maybe someone could point me to functional steps to in somehow revert or reevaluate the problematic stock.valuation.layers. This customer uses multi currency, so the currency rate variations between product reception and bill confirmation date makes almost every vendor bill gets blocked with no chances to any form of modification. Has anyone come out with a bright solution?
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Christian Zöllner - 04:56 - 24 Sep 2024 -
Re: [16.0] Reset to Draft button disappear after changed Price on Vendor Bills
El mar, 24 sept 2024 a las 11:22, Rolando Pérez Rebollo (<notifications@odoo-community.org>) escribió:Hi team, We recently upgrade a client from v13 to v16, and now they are being hit by the infamous "Reset to Draft button disappear after changed Price on Vendor Bills" (https://github.com/odoo/odoo/issues/114732). I have read a lot of code, blog posts, comments on github issues an so on. Because fiscal regulations the customer can't issue credit notes as Odoo officially suggested as workaround. So, has anyone figured out some strategy to solve this problem. I'm a developer, maybe someone could point me to functional steps to in somehow revert or reevaluate the problematic stock.valuation.layers. This customer uses multi currency, so the currency rate variations between product reception and bill confirmation date makes almost every vendor bill gets blocked with no chances to any form of modification. Has anyone come out with a bright solution?
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Maria Florencia Frigieri Parma - 04:51 - 24 Sep 2024 -
[16.0] Reset to Draft button disappear after changed Price on Vendor Bills
Hi team, We recently upgrade a client from v13 to v16, and now they are being hit by the infamous "Reset to Draft button disappear after changed Price on Vendor Bills" (https://github.com/odoo/odoo/issues/114732). I have read a lot of code, blog posts, comments on github issues an so on. Because fiscal regulations the customer can't issue credit notes as Odoo officially suggested as workaround. So, has anyone figured out some strategy to solve this problem. I'm a developer, maybe someone could point me to functional steps to in somehow revert or reevaluate the problematic stock.valuation.layers. This customer uses multi currency, so the currency rate variations between product reception and bill confirmation date makes almost every vendor bill gets blocked with no chances to any form of modification. Has anyone come out with a bright solution?
by Ing. Rolando Pérez Rebollo - 04:20 - 24 Sep 2024 -
Shopinvader E-Commerce Bugs with odoo 12 docker image
Dear community.
One of my customers needs an E-Commerce application that depends on odoo in the backend.
A friend of mine recommended the Shopinvader project to use.
I have read about it, I cloned many of it's repositories.
I tried to follow the documentation and install and run the "getting started" docker-compose app.
It failed to run due to old odoo 12 dependency.
I really need to install and try this project so that if it is useful I can upgrade to version 17 and share it in the community.
Any guidance on how to install and run it without bugs even in version 16 of odoo?
Thanks community
by Mohamed Alkobrosly - 11:36 - 23 Sep 2024 -
Re: Multiple customers on Purchase Orders
Thanks Holger,
the idea of "consortium" instead of trying to put multiple customers into PO is a good one and also naturally extendable beyond more than 2 companies.
Best regards
Radovan
On pondelok 23. septembra 2024 12:37:45 CEST Holger Brunn wrote:
> > Anyone faced anything similar? I am thinking of using 2 companies to model
> > it and tinkering with visibility in each according to split. Because where
> > there is a split, they want to see the document in both. Where there is
> > not
> > (it belongs to single company), should ony be visible there. However how
> > to
> > model in a best way that there should be 2 customers (maybe more for
> > future
> > extensions) on each document?
>
> I have a customer with a similar requirement the other way around, where
> multiple suppliers invoice the same customer:
> https://github.com/tosccolors/vertical-professional-services/tree/16.0/
> ps_partner_multi_relation
> They solved this by defining a partner relation "consortium", and every time
> an invoice for a consortium partner is posted, this invoice is split by the
> weights ("distribution key") on the consortium relation and new invoices
> are created for the involved partners.
> This concept should extend quite naturally to the purchase side, where you
> split the supplier invoices and deliveries according to the distribution key
> on the partner relation.
> --
> Your partner for the hard Odoo problems
> https://hunki-enterprises.com
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [1]
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [2]
>
>
>
> [1] https://odoo-community.org/groups/contributors-15
> [2] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 02:46 - 23 Sep 2024 -
Re: Multiple customers on Purchase Orders
> Anyone faced anything similar? I am thinking of using 2 companies to model > it and tinkering with visibility in each according to split. Because where > there is a split, they want to see the document in both. Where there is not > (it belongs to single company), should ony be visible there. However how to > model in a best way that there should be 2 customers (maybe more for future > extensions) on each document? I have a customer with a similar requirement the other way around, where multiple suppliers invoice the same customer: https://github.com/tosccolors/vertical-professional-services/tree/16.0/ ps_partner_multi_relation They solved this by defining a partner relation "consortium", and every time an invoice for a consortium partner is posted, this invoice is split by the weights ("distribution key") on the consortium relation and new invoices are created for the involved partners. This concept should extend quite naturally to the purchase side, where you split the supplier invoices and deliveries according to the distribution key on the partner relation. -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 12:32 - 23 Sep 2024 -
Multiple customers on Purchase Orders
Hello,
I am dealing with a scenario where 2 sister companies share parts of their operations and make purchase orders together with split ratio between them. The way they do it is 3-party agreements, where there are 2 customers and 1 supplier and for purchase orders there are instructions for suppliers on how to split the invoicing (i.e. the supplier sends 2 separate invoices - each to individual company according to the split ratio).
Anyone faced anything similar? I am thinking of using 2 companies to model it and tinkering with visibility in each according to split. Because where there is a split, they want to see the document in both. Where there is not (it belongs to single company), should ony be visible there. However how to model in a best way that there should be 2 customers (maybe more for future extensions) on each document?
Any advice is highly welcome. Thank you very much.
Best regards
Radovan Skolnik
by Radovan Skolnik - 12:06 - 23 Sep 2024 -
-
Fwd: Purchase Request inconvinient
---------- Forwarded message ---------
De: Manuel Scarafia <manuelscarafia@gmail.com>
Date: vie, 20 sept 2024 a las 15:38
Subject: Purchase Request inconvinient
To: <support@odoo-community.org>¡Hi! ¿How's going?I was using your Purchase Request module (purchase_request) when I noticed that it didn't let me change the currency on a Purchase Request; I was able to change the currency (from ARS to USD) but when I clicked "Save" it took me back to ARS again. I've also noticed that when I change the currency in the currency field, it doesn't change the currency in the product lines and doesn't let me change it as well.¿Do you have a fix for this problem? ¿Or is there any configuration that I could check?
by Manuel Scarafia - 09:57 - 20 Sep 2024 -
Subject: Welcome to the VentorTech Support!
Hi there,
We're excited to welcome you to the VentorTech Support! This is your one-stop shop for getting help with our products and services.
Here's what you can do in the portal:
- Create and track support requests: Get the help you need, when you need it.
- Access our knowledge base: Find answers to common questions and troubleshoot issues.
- Stay up-to-date: Receive notifications about product updates and announcements.
To get started, simply click the link below to set up your account: sign up link
We're here to help you make the most of our products. If you have any questions, don't hesitate to reach out!
Sincerely,
The VentorTech Team
by "VentorTech Support" <support@ventor.tech> - 02:36 - 20 Sep 2024 -
Re: RFQ for OCA Days 2024 Video Post Production
Hello OCA Contributors,Just a reminder this RFQ closes today.If you have the skills within your company to help us out after the OCA Days, we would love to hear from you.Warm regards,RebeccaOn Wed, 28 Aug 2024 at 23:11, Rebecca Gellatly <rebecca@odoo-community.org> wrote:Hello OCA Contributors,I hope this finds you all well.We are getting the final details ready for OCA Days 2024.If you haven't registered yet, there is still time, you can do so here.I'm sharing the RFQ for Video Post Production of the recorded talks - have you got a digital superstar in your company who could help? Please share it around.Deadline for submission for the RFQ is 18th September 2024.You can find out more on our RFQ process page.If you have any questions please get in touch.Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly (OCA) - 12:21 - 18 Sep 2024 -
Re: OCA Days India - 2024 - 28th September
That's a great news!Thanks for sharing Rebecca :)Thanks Serpent and BizzAppDev :)On Tue, Sep 17, 2024 at 1:52 AM Rebecca Gellatly <rebecca@odoo-community.org> wrote:Hello OCA Contributors.
I hope this email finds you all well.
I wanted to share with you that we have a one day OCA Days India 2024 event in Gandhinagar at the Serpent Consulting Offices from 10am - 5pm on Saturday the 28th September.We had so many visitors at the Odoo Community Days just a couple of weeks ago, our friends at Serpent Consulting and BizzAppDev are keen to help support the community and share the OCA with Odoo supporters in the area.
There are talks to help with contributing, how to use the Indian Localisation and a number of sprint topics. Technical and Functional profiles are warmly encouraged to attend.
You can see the agenda here.You can register here.If you are attending but haven't signed an ICLA, you can find all the details here. Please get on to this quick so I have time to action them before I start travelling from NZ to Belgium late next week for the European OCA Days 2024.If you have any questions please get in touch.Warmest regards,Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
by Simone Orsi - 10:36 - 18 Sep 2024 -
RE: OCA Days India - 2024 - 28th September
Jordan Kinsella reacted to your message:
From: Rebecca Gellatly <rebecca@odoo-community.org>
Sent: Monday, September 16, 2024 11:52:52 PM
To: Contributors <contributors@odoo-community.org>
Subject: OCA Days India - 2024 - 28th SeptemberCaution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, contact your Department Manager
Hello OCA Contributors.
I hope this email finds you all well.
I wanted to share with you that we have a one day OCA Days India 2024 event in Gandhinagar at the Serpent Consulting Offices from 10am - 5pm on Saturday the 28th September.
We had so many visitors at the Odoo Community Days just a couple of weeks ago, our friends at Serpent Consulting and BizzAppDev are keen to help support the community and share the OCA with Odoo supporters in the area.
There are talks to help with contributing, how to use the Indian Localisation and a number of sprint topics. Technical and Functional profiles are warmly encouraged to attend.
You can see the agenda here.You can register here.
If you are attending but haven't signed an ICLA, you can find all the details here. Please get on to this quick so I have time to action them before I start travelling from NZ to Belgium late next week for the European OCA Days 2024.
If you have any questions please get in touch.Warmest regards,Rebecca--
Rebecca GellatlyGeneral SecretaryOdoo Community Association_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Jordan Kinsella - 10:21 - 18 Sep 2024 -
OCA Days India - 2024 - 28th September
Hello OCA Contributors.
I hope this email finds you all well.
I wanted to share with you that we have a one day OCA Days India 2024 event in Gandhinagar at the Serpent Consulting Offices from 10am - 5pm on Saturday the 28th September.We had so many visitors at the Odoo Community Days just a couple of weeks ago, our friends at Serpent Consulting and BizzAppDev are keen to help support the community and share the OCA with Odoo supporters in the area.
There are talks to help with contributing, how to use the Indian Localisation and a number of sprint topics. Technical and Functional profiles are warmly encouraged to attend.
You can see the agenda here.You can register here.If you are attending but haven't signed an ICLA, you can find all the details here. Please get on to this quick so I have time to action them before I start travelling from NZ to Belgium late next week for the European OCA Days 2024.If you have any questions please get in touch.Warmest regards,Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly (OCA) - 01:50 - 17 Sep 2024 -
odoo kernel for web development
Hello Odoo community, I have started to make use of the best of odoo which is the magnificent ORM and OWL.
To simplify I made a special light version of odoo that runs only the base module and it's related logical associated modules.
I took this step as 4 months ago, I have created my company website:This website was built using Flask in the backend and OWL for the frontend.
It was very nice as I found OWL is quite simple and highly efficient as React and Vue.js.
Flask is great to run my website, but if I get a project that needs connection to the database then I have to use opensource ORM library and connect it with Flask, or I can directily use Django.
I am satisfied with Django and comfortable with Flask, but I like too much to make use of odoo ORM.
That is how I got the idea, and I hope I find it helpful in the future.
I also hope that you find my email useful.
Here is the repository for Odoo Kernel:
Thanks all
by Mohamed Alkobrosly - 09:01 - 15 Sep 2024 -
Preparing for Odoo 18
Hi everyone,If history repeats itself, we may have a new Odoo version 3 weeks from now.I created the tracking issue to prepare OCA tooling for Odoo 18, including suggestions for improvements: https://github.com/OCA/maintainer-tools/issues/628Contributions are most welcome, so don't hesitate to chime in if you want to help.Best regards,-Stéphane
by Stéphane Bidoul - 03:41 - 12 Sep 2024 -
Re: Triple discount modules refactor and maturity levels
Hi Akim,Thank you for your hard work on the triple discount module. IMO we should merge the 16.0 branch. By bumping the version to the next major level, the signal is clear that this new version contains breaking changes. I'm often reluctant to introduce such deep changes in a ‘stable’ version. In this case, I feel it's justified by the need to introduce a cleaner/simpler approach and remove hacks made necessary by the complexity of the previous one. This cleaner architecture also provides a better basis for all the modules based on this module. Regarding the maturity level, the default one is beta, I would find it logical to prohibit such changes on a ‘stable’/‘mature’ version, but not on a ‘beta’ version.Regards,lmiOn Tue, Sep 10, 2024 at 7:08 PM Akim Juillerat <notifications@odoo-community.org> wrote:Hello communityA few months ago, I started a big refactor of triple discount modules in v16.0 that ended up with the following PRs:Since this is a BIG breaking change I'm wondering if these should be merged only in v17.0 instead of 16.0.We actually have migration PRs for triple discount modules in 17.0:My feeling is we must probably leverage the maturity levels to define what can be merged in a released version, and avoid such breaking change when the maturity level is stable/mature. But then, if there is no maturity level in manifest, as is the case here, it seems to default to Beta in readme generation. Should we consider this as a rule?Do we then want to move forward with this refactor in 16.0 or keep it for 17.0 and eventually define a stable maturity level for 17.0?Please let me know what do you guys think about it.Best regards.camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSAkim JuilleratBusiness solutionsSoftware architect_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Laurent MignonTechnical lead / Management TeamT: +32 2 8883148Atrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumVal Benoit, Quai Banning 6 | B-4000 Liège | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg
by Laurent Mignon - 08:56 - 11 Sep 2024 -
Triple discount modules refactor and maturity levels
Hello communityA few months ago, I started a big refactor of triple discount modules in v16.0 that ended up with the following PRs:Since this is a BIG breaking change I'm wondering if these should be merged only in v17.0 instead of 16.0.We actually have migration PRs for triple discount modules in 17.0:My feeling is we must probably leverage the maturity levels to define what can be merged in a released version, and avoid such breaking change when the maturity level is stable/mature. But then, if there is no maturity level in manifest, as is the case here, it seems to default to Beta in readme generation. Should we consider this as a rule?Do we then want to move forward with this refactor in 16.0 or keep it for 17.0 and eventually define a stable maturity level for 17.0?Please let me know what do you guys think about it.Best regards.camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSAkim JuilleratBusiness solutionsSoftware architect
by Akim Juillerat - 07:06 - 10 Sep 2024