Archives
Contributors
-
Re: Purchasing "packaging-like" products
Hi Radovan
I had to deal with a similar situation for a supermarket, where an external database had to be imported as products in the system. It had a lot of similar examples like "package of 6 eggs" or "crate of 20 bottles" whereby the purchase and sales units are different.
I ended up creating separate "uom" records for each, which correspond to a certain number of another "uom". So a "12 pack" is 12 times a "unit". You can then decide to purchase in a different unit and sell in another unit. Odoo also has some documentation on it:
Maybe this could help
-Tom
On 3/1/24 20:36, Radovan Skolnik wrote:
Hello, I am dealing with a situation where the customer purchases many products that are like this: "Flora Margarine 8x1kg" It is not packaging, because it is not possible to buy just 1kg. This is quite confusing for the customer and I am trying to make it easier for them to manage. One of the problems is that they perceive that the UoM here should be kg (because they just see it there in the name). This can be handled by product_secondary_unit and stock_secondary_unit to get the amount in kgs. What I think could help is this: when ordering 1 unit of that product somehow turn in into 8 units of virtual "Flora Margarine 1kg" I am trying to wrap my head around this with no success. I have considered these modules but none seem to be doing what I would like to: * product_supplierinfo_qty_multiplier * purchase_only_by_packaging * product_pack Any ideas on how to approach this? Thank you very much. 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
by Tom Blauwendraat - 10:11 - 1 Mar 2024 -
Purchasing "packaging-like" products
Hello, I am dealing with a situation where the customer purchases many products that are like this: "Flora Margarine 8x1kg" It is not packaging, because it is not possible to buy just 1kg. This is quite confusing for the customer and I am trying to make it easier for them to manage. One of the problems is that they perceive that the UoM here should be kg (because they just see it there in the name). This can be handled by product_secondary_unit and stock_secondary_unit to get the amount in kgs. What I think could help is this: when ordering 1 unit of that product somehow turn in into 8 units of virtual "Flora Margarine 1kg" I am trying to wrap my head around this with no success. I have considered these modules but none seem to be doing what I would like to: * product_supplierinfo_qty_multiplier * purchase_only_by_packaging * product_pack Any ideas on how to approach this? Thank you very much. Best regards Radovan Skolnik
by Radovan Skolnik - 08:36 - 1 Mar 2024 -
Re: [PSA] mail template editor group, mass mailing user group
> I think a security repository sounds like a great idea. I am less > enthusiastic about auto-installation, as its use is a bit contentious and > has spawned modules like module_change_auto_install [1] . but exactly that repository would be for people who want an installation that is, well, for however we define it 'secure by default'. There I'd find it a feature that if you have the repo, and install some module from core that does things violating our idea of 'secure by default', you get the module that squelches that violation immediately. If we don't have the auto install, every integrator will have to depend on those modules explicitly, which I will do anyways for my customers, so for me it doesn't really matter. Still I think it will be more convenient for most people to just pull this repo into however they do their deployment, and then the magic happens. But I agree, much less modules than authors think are a good idea to auto install in the general case. -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 07:31 - 29 Feb 2024 -
Re: [PSA] mail template editor group, mass mailing user group
> Did you report this vulnerability to Odoo SA? > https://www.odoo.com/security-report [1] yes, but I learned this was a choice they made. You're supposed to click the 'restrict mail templates' flag in the general settings if you disagree. (which still doesn't change the fact that everyone is a mail template editor as soon as you install mass_mailing) Seems a different philosophy, I want secure by default, they want easy. Actually, I was a bit frightened about this being a conscious choice so now I'm sifting through other core modules if I find similar choices. If so, a secure-by-default oca repo might be in order, where we collect modules like the ones I propose above, and set them to auto install. -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 05:51 - 29 Feb 2024 -
[PSA] mail template editor group, mass mailing user group
Hi all, today I got aware that Odoo by default (and by design) assigns the mail template editor group to all backend users. Sounds harmless, but being a member of this group allows you to run code, and when you can run code you can do all kinds of nefarious things in the database. Given I'm busy with Odoo for a very long time, I'm a little ashamed that this is news for me, but as a few colleagues I asked were also not aware of this, it seems a good idea to me to spread awareness. On https://github.com/OCA/social/pull/1319 you find a module that helps you removing this potentially dangerous group from your users. A very similar issue is mass_mailing with the mass mailing user group, the above PR also contains a module to address that. My (and my customers') expectation is: Nobody can run code unless being added to some high privilege group like mass mailing user explicitly, and those modules help implementing this. Best regards, Holger -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 04:41 - 29 Feb 2024 -
Re: Question regarding the Community Discuss functionnality
Hi everyone,First I would like to share our experience regarding déployment of the Odoo discuss via RTC.We installed a coturn server and setup TURN server in the ICE servers in the Odoo backend.I works mostly like a charm! We share links with customers etc...We still having some issues and we've been monitoring :- network and logs of the coturn server
- network and logs on the odoo server
- browser console during communication
In the console we still having some unavailable ICE server . After many tests we're suspecting that the websocket Odoo conf could help https://github.com/odoo/odoo/blob/16.0/odoo/tools/config.py#L81 because issues seems to be raised by the websocket_worker_bundle that receiving and passing the payload of ice connexions.We're running out of ideas and wondering if anybody already had used this with 20-50 users ?Any feedback would be welcomed,RegardsFlorent THOMAS
☎ +33 972 457 755
✉ florent.thomas@mind-and-go.comMind & Go
14, Rue Pierre Cartelet | 66000 PERPIGNANDe: "Florent Thomas" <florent.thomas@mind-and-go.com>
À: "contributors" <contributors@odoo-community.org>
Envoyé: Vendredi 23 Juin 2023 09:08:36
Objet: Re: Question regarding the Community Discuss functionnalityHi @David,A great thanks for your answer !RegardsFlorent THOMAS
☎ +33 972 457 755
✉ florent.thomas@mind-and-go.comMind & Go
14, Rue Pierre Cartelet | 66000 PERPIGNANDe: "David Vidal" <notifications@odoo-community.org>
À: "contributors" <contributors@odoo-community.org>
Envoyé: Mardi 20 Juin 2023 09:06:50
Objet: Re: Question regarding the Community Discuss functionnalityThat's it. It uses the technology available in the browser itself which is widely supported https://caniuse.com/rtcpeerconnectionEl lun, 19 jun 2023 a las 15:42, Florent Thomas (<notifications@odoo-community.org>) escribió:Thanks for your answer David,So from your point of view, everything i/ users ?s embedded in the community version and don't use external services ?RegardsFlorent THOMAS
☎ +33 972 457 755
✉ florent.thomas@mind-and-go.comMind & Go
14, Rue Pierre Cartelet | 66000 PERPIGNANDe: "David Vidal" <notifications@odoo-community.org>
À: "contributors" <contributors@odoo-community.org>
Envoyé: Lundi 19 Juin 2023 09:36:54
Objet: Re: Question regarding the Community Discuss functionnalityEl dom, 18 jun 2023 a las 18:48, Florent Thomas (<notifications@odoo-community.org>) escribió:Hi Community,I'm running v16 community version and I'm wondering what is the technology hiding behind the live discuss feature :I didn't succeed to find out if it relies on an external dependency or ant IAP service.Any feedback will be appreciated,RegardsFlorent THOMAS
☎ +33 972 457 755
✉ florent.thomas@mind-and-go.comMind & Go
14, Rue Pierre Cartelet | 66000 PERPIGNAN_______________________________________________
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 Florent THOMAS - 04:35 - 27 Feb 2024 - network and logs of the coturn server
-
Re: Status of different branches and reasoning to choose
More on this:First about stability: as Pedro explained today there is no difference in stability between pair and odd versions. The thing is there is a resonance happening where pair versions are a bit more popular among skilled integrators and have more OCA modules. This can be observed by looking at the number of modules OCA by version in the attachment.Usually in the 1st year after the release around 90 modules per month are migrated in the OCA and it slows down after some 3 years. For some reason, the situation with v17 isn't as good today yet the version is reputed "stable". Note that this is only "merged" modules, there are a lot more modules with a valid migration Pull Request proposition that is just not merged yet (there a lot of such PRs for v17).I would add: you can choose a recent version both for large and small projects because small projects will need just a few modules and large ones might have money to migrate whatever is required. Mid sized projects however might be tricky if you choose a version that is too recent like version 17 today.On Thu, Feb 22, 2024 at 9:37 AM Pedro M. Baeza <notifications@odoo-community.org> wrote:Good summary from Xavier. Just one clarification: the question about even versions being more stable is a myth propagated by some interested parties. You may find the same number of problems in even or odd versions (as in any software), and nowadays, they have been reduced a lot thanks to the maturity the software has. Anyway, any just released version is expected to have some of them, requiring a bit of time to get the proper coverage. But I also want to distinguish here the scope of these bugs: most of the time they are really edge cases or special use cases that are uncovered or not tested when a refactoring is done, and only after someone faces such use case, it's discovered and fixed. We are now discovering some of them in 15.0 2 years after their release with a special case with stock packages while having dozens of customers without problem because they don't use that specific flow with the packages.You have to analyze the cust omer requirements, and see the gap between them and:- Odoo core features in that version.- Already migrated OCA modules to that version.and always trying to push to the latest version if possible, as it can be considered always the best version released. Only if the gap can be covered with a lot of OCA modules that are not migrated, then you may think about putting a prior version, but I invite you to reverse the thing: dedicate a bit of budget to migrate that modules to the latest version, and you will save having a lot of features including by Odoo S. A. itself in that version (they have more than 300 developers investing their full time each year to improve the product).Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Raphaël ValyiFounder and consultant
by "Raphaël Valyi" <rvalyi@akretion.com> - 05:35 - 22 Feb 2024 -
Re: Status of different branches and reasoning to choose
Good summary from Xavier. Just one clarification: the question about even versions being more stable is a myth propagated by some interested parties. You may find the same number of problems in even or odd versions (as in any software), and nowadays, they have been reduced a lot thanks to the maturity the software has. Anyway, any just released version is expected to have some of them, requiring a bit of time to get the proper coverage. But I also want to distinguish here the scope of these bugs: most of the time they are really edge cases or special use cases that are uncovered or not tested when a refactoring is done, and only after someone faces such use case, it's discovered and fixed. We are now discovering some of them in 15.0 2 years after their release with a special case with stock packages while having dozens of customers without problem because they don't use that specific flow with the packages.You have to analyze the customer requirements, and see the gap between them and:- Odoo core features in that version.- Already migrated OCA modules to that version.and always trying to push to the latest version if possible, as it can be considered always the best version released. Only if the gap can be covered with a lot of OCA modules that are not migrated, then you may think about putting a prior version, but I invite you to reverse the thing: dedicate a bit of budget to migrate that modules to the latest version, and you will save having a lot of features including by Odoo S. A. itself in that version (they have more than 300 developers investing their full time each year to improve the product).Regards.
by Pedro M. Baeza - 01:36 - 22 Feb 2024 -
Re: Empty SQL argument and ANY operator
Looks like a bug indeed, in 14.0 and lower. In 15.0 the code seems refactored.
>>> env.cr.execute("select count(1) from res_users where id != any(%s)", (([1,],)))
>>> env.cr.query
b'select count(1) from res_users where id != any(ARRAY[1])'
>>> env.cr.fetchall()
[(248,)]
>>> env.cr.execute("select count(1) from res_users where id != any(%s)", (([],)))
>>> env.cr.query
b"select count(1) from res_users where id != any('{}')"
>>> env.cr.fetchall()
[(0,)]
Probably the Odoo programmers misinterpreted what kind of query psycopg would generate in such a case.
On 2/21/24 15:22, Yann Papouin wrote:
I forgot again that this OCA's mailing-list bug is not fixed (if someone interested: https://github.com/decgroupe/odoo-ocb/commit/5d07dba81e05d44fdbd593017e13de5c22a1c46e)
You can see the image here: https://odoo-community.org/groups/contributors-15/contributors-1702031?mode=thread&date_begin=&date_end=The relevant code is: https://github.com/odoo/odoo/blob/b7777c50d40cc56e094f43d8f35753d713e17f77/addons/mail/models/mail_thread.py#L2523-L2541
--
Yann PAPOUIN, Ingénieur R&D | DEC
Le mer. 21 févr. 2024 à 15:12, Tom Blauwendraat <notifications@odoo-community.org> a écrit :
For some reason I can't see the image, can you maybe send it as attachment?
Also, can you provide a link to the relevant part of the Odoo source code that defines "except_partner"?
On 2/21/24 12:52, Yann Papouin wrote:
Hello everyone,
I'm trying to debug Odoo 14.0 to understand why some emails received on one of our public channel are not forwarded to all members of the list.
The SQL query is made to retrieve all partners members of a channel that will be notified with a copy of the received email
I tracked down the issue to the fact that an empty list (except_partner) is converted to '{}' (empty array literal) when used as an argument in the SQL query and the result of the query with this condition is always empty.
I'm pretty sure that it is something tricky around the SQL language but as I'm not an expert on this, I don't know how to fix it.My current dirty fix is to add except_partner.append(0) to have a valid query but I would prefer to have the real SQL fix.
Any idea ?
--
Yann PAPOUIN, Ingénieur R&D | DEC_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Tom Blauwendraat - 07:51 - 21 Feb 2024 -
Re: Empty SQL argument and ANY operator
I forgot again that this OCA's mailing-list bug is not fixed (if someone interested: https://github.com/decgroupe/odoo-ocb/commit/5d07dba81e05d44fdbd593017e13de5c22a1c46e)You can see the image here: https://odoo-community.org/groups/contributors-15/contributors-1702031?mode=thread&date_begin=&date_end=The relevant code is: https://github.com/odoo/odoo/blob/b7777c50d40cc56e094f43d8f35753d713e17f77/addons/mail/models/mail_thread.py#L2523-L2541--
Yann PAPOUIN, Ingénieur R&D | DECLe mer. 21 févr. 2024 à 15:12, Tom Blauwendraat <notifications@odoo-community.org> a écrit :For some reason I can't see the image, can you maybe send it as attachment?
Also, can you provide a link to the relevant part of the Odoo source code that defines "except_partner"?
On 2/21/24 12:52, Yann Papouin wrote:
Hello everyone,
I'm trying to debug Odoo 14.0 to understand why some emails received on one of our public channel are not forwarded to all members of the list.
The SQL query is made to retrieve all partners members of a channel that will be notified with a copy of the received email
I tracked down the issue to the fact that an empty list (except_partner) is converted to '{}' (empty array literal) when used as an argument in the SQL query and the result of the query with this condition is always empty.
I'm pretty sure that it is something tricky around the SQL language but as I'm not an expert on this, I don't know how to fix it.My current dirty fix is to add except_partner.append(0) to have a valid query but I would prefer to have the real SQL fix.
Any idea ?
--
Yann PAPOUIN, Ingénieur R&D | DEC_______________________________________________
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 Yann Papouin - 03:21 - 21 Feb 2024 -
Re: Empty SQL argument and ANY operator
For some reason I can't see the image, can you maybe send it as attachment?
Also, can you provide a link to the relevant part of the Odoo source code that defines "except_partner"?
On 2/21/24 12:52, Yann Papouin wrote:
Hello everyone,
I'm trying to debug Odoo 14.0 to understand why some emails received on one of our public channel are not forwarded to all members of the list.
The SQL query is made to retrieve all partners members of a channel that will be notified with a copy of the received email
I tracked down the issue to the fact that an empty list (except_partner) is converted to '{}' (empty array literal) when used as an argument in the SQL query and the result of the query with this condition is always empty.
I'm pretty sure that it is something tricky around the SQL language but as I'm not an expert on this, I don't know how to fix it.My current dirty fix is to add except_partner.append(0) to have a valid query but I would prefer to have the real SQL fix.
Any idea ?
--
Yann PAPOUIN, Ingénieur R&D | DEC_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Tom Blauwendraat - 03:10 - 21 Feb 2024 -
Empty SQL argument and ANY operator
Hello everyone,I'm trying to debug Odoo 14.0 to understand why some emails received on one of our public channel are not forwarded to all members of the list.The SQL query is made to retrieve all partners members of a channel that will be notified with a copy of the received emailI tracked down the issue to the fact that an empty list (except_partner) is converted to '{}' (empty array literal) when used as an argument in the SQL query and the result of the query with this condition is always empty.I'm pretty sure that it is something tricky around the SQL language but as I'm not an expert on this, I don't know how to fix it.My current dirty fix is to add except_partner.append(0) to have a valid query but I would prefer to have the real SQL fix.
Any idea ?--
Yann PAPOUIN, Ingénieur R&D | DEC
by Yann Papouin - 12:52 - 21 Feb 2024 -
Status of different branches and reasoning to choose
Hi, oca hosts a lot of repositories whith branches for the different versions of odoo (..14,16,17). What's missing for me is a big picture of the overall state of the different versions... Is community still most complete/stable on 14, 16 oder 17 (or maybe even 12)? What version would you suggest to start with? What's also missing for me is a good big picture on the difference in code/features beetween odoo enterprise, odoo open-source and oca on the different versions. thx for any feedback, Peter
by Peter Niederlag - 01:16 - 18 Feb 2024 -
Re: Concurrency write check
> I guess it's easy to (re)build this as an OCA module, although instances that install it will probably also run into the problems that made Odoo ditch it.
I agree, a less impacting solution should be better.
Il giorno ven 16 feb 2024 alle ore 15:12 David Vidal <notifications@odoo-community.org> ha scritto:> From my pov, a simple advice, on the UI with a js, should be enough to point out the fact.In the web_editor there's a kind of concurrence protection: https://github.com/OCA/OCB/blob/15.0/addons/web_editor/controllers/main.py#L32-L39Interesting, but it's only implemented for collaborative pages on web (events? I couldn't find where).Sergio CoratoEl vie, 16 feb 2024 a las 14:32, Sergio Corato (<notifications@odoo-community.org>) escribió:From my pov, a simple advice, on the UI with a js, should be enough to point out the fact.Sergio CoratoIl giorno ven 16 feb 2024 alle ore 10:32 Ronald Portier <notifications@odoo-community.org> ha scritto:So basically Odoo has no longer any mechanism to prevent the changes of one user undoing the changes of another user.
In applications traditionally two mechanisms existed that intended to prevent this problem, respectively pessimistic and optimistic locking.
In pessimistic locking anybody touching a record with the potential to update it, would establish a lock on the record, other users would be prevented from reading the same record for update. This has the potential for lots of access problems, especially as databases and transactions became more complicated and would no longer involve single records but whole networks of records.
Optimistic locking would, as Odoo does, timestamp all records. The idea that most reads that have a potential to update a record, mostly would not be updating anything. But when updating, the timestamp of the record read would be compared with the current timestamp and any previous change would result in an Exception.
An alternative method for optimistic locking, not depending on timestamps, would be to save the original record image and compare with the actual record image just before the actual update.
Missing either pessimistic locking or optimistic locking, for some applications it might be needed to implement a mechanism where a user must specifically claim a main application object for change, before being allowed to update it. A claim made preventing other users from making the same claim, before the application object being released. A main application object could be a Customer, an Order or a Helpdesk Ticket. Such a claim would work like a "check out" in document management systems, or a kind of Semaphore on OS level.
On 15-02-2024 23:11, Tom Blauwendraat wrote:
Closest I could come in finding some info about it is this:
https://github.com/odoo/odoo/pull/87756
Apparently it caused problems and was already long ago removed from the frontend, and by 16.0 they killed the backend part as well.
On 2/15/24 19:07, Sergio Corato wrote:
The logic isn't implemented/enabled in any version that I checked, this seems at least strange (I saw this function working in other softwares decades ago).Debugging didn't help, the context is never passed with the field '__last_update'.
However it's not a requested function, I'll give up for now ;)
Thanks
Sergio Corato
Il giorno gio 15 feb 2024 alle ore 17:07 Tom Blauwendraat <notifications@odoo-community.org> ha scritto:
I also looked for unit tests and didn't find, and also saw this function was deleted in 16.0 (but maybe renamed). I think debugging is the only way to find out! pdb to the rescue
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Sergio Corato - 04:11 - 16 Feb 2024
