Archives
Contributors
-
Re: OCA Codesprint - around FOSDEM - are you keen?
Hello there,is there is any chance we hang up online,we would love to attend in person, but it’s nearly impossible to flight up there.On Fri, 29 Nov 2024 at 1:52 PM Ibrahim Alsaman <notifications@odoo-community.org> wrote:Hello,I will make sure to join remotely. However, if there is a way for me to travel to Brussels, I would be happy to attend in person.Note: I reside outside the EU.On Fri, 29 Nov 2024, 12:07 Michel Stroom, <notifications@odoo-community.org> wrote:Is it possible to join remote or do you have to be in Brussels?
On 26 Nov 2024, at 01:28, Rebecca Gellatly <notifications@odoo-community.org> wrote:Hello OCA Contributors,You may have seen on our social media that we are weighing up if there is enough interest to organise an OCA Codesprint around the FOSDEM event next year.
If this is something that is of interest to you, please let us know on our survey here. Depending on interest we will make a decision about what to do.The FOSDEM event is on the 1st and 2nd of February in Brussels. We are considering a sprint a day or two on either side.Have a great week.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
_______________________________________________
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 عمر ابو ضيف - 12:01 - 29 Nov 2024 -
Re: OCA Codesprint - around FOSDEM - are you keen?
Hello,I will make sure to join remotely. However, if there is a way for me to travel to Brussels, I would be happy to attend in person.Note: I reside outside the EU.On Fri, 29 Nov 2024, 12:07 Michel Stroom, <notifications@odoo-community.org> wrote:
Is it possible to join remote or do you have to be in Brussels?
On 26 Nov 2024, at 01:28, Rebecca Gellatly <notifications@odoo-community.org> wrote:Hello OCA Contributors,You may have seen on our social media that we are weighing up if there is enough interest to organise an OCA Codesprint around the FOSDEM event next year.
If this is something that is of interest to you, please let us know on our survey here. Depending on interest we will make a decision about what to do.The FOSDEM event is on the 1st and 2nd of February in Brussels. We are considering a sprint a day or two on either side.Have a great week.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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Ibrahim Alsaman - 11:51 - 29 Nov 2024 -
Re: OCA Codesprint - around FOSDEM - are you keen?
Is it possible to join remote or do you have to be in Brussels?
On 26 Nov 2024, at 01:28, Rebecca Gellatly <notifications@odoo-community.org> wrote:Hello OCA Contributors,You may have seen on our social media that we are weighing up if there is enough interest to organise an OCA Codesprint around the FOSDEM event next year.
If this is something that is of interest to you, please let us know on our survey here. Depending on interest we will make a decision about what to do.The FOSDEM event is on the 1st and 2nd of February in Brussels. We are considering a sprint a day or two on either side.Have a great week.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 Michel Stroom - 11:06 - 29 Nov 2024 -
Re: Clarification on merge/squash the commits generated by bots or weblate
Thank U, Christopher.
\Rebollo
On 11/29/24 03:28, Christopher Rogos wrote:
When you migrate a module from 16 to 17, you create a new branch “17.0-mig-my_module” based on the 17.0 branch.
Then you transfer all commits from my_module to the new branch.
When you are working on branch “17.0-mig-my_module” you can use “git rebase -i origin/17.0” to rebase the transferred commits on your branch, and clean them up by squashing some.
From: Rolando Pérez Rebollo <notifications@odoo-community.org>
Sent: Freitag, 29. November 2024 00:13
To: Contributors <contributors@odoo-community.org>
Subject: Clarification on merge/squash the commits generated by bots or weblateWhen reviewing this guide, it states:
"In order to squash these administrative commits, use
git rebase -i origin/x, wherexis the Odoo version (14.0, 15.0, 16.0,...). Don't forget first to dogit fetch origin xto get the latest remote information."In the context of migrating a module, this step is recommended after applying the patches and running pre-commit.
My question is: regarding the
xbranch mentioned above—does it refer to the source version or the target version for the migration?_______________________________________________
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 - 10:26 - 29 Nov 2024 -
RE: Clarification on merge/squash the commits generated by bots or weblate
When you migrate a module from 16 to 17, you create a new branch “17.0-mig-my_module” based on the 17.0 branch.
Then you transfer all commits from my_module to the new branch.
When you are working on branch “17.0-mig-my_module” you can use “git rebase -i origin/17.0” to rebase the transferred commits on your branch, and clean them up by squashing some.
From: Rolando Pérez Rebollo <notifications@odoo-community.org>
Sent: Freitag, 29. November 2024 00:13
To: Contributors <contributors@odoo-community.org>
Subject: Clarification on merge/squash the commits generated by bots or weblateWhen reviewing this guide, it states:
"In order to squash these administrative commits, use
git rebase -i origin/x, wherexis the Odoo version (14.0, 15.0, 16.0,...). Don't forget first to dogit fetch origin xto get the latest remote information."In the context of migrating a module, this step is recommended after applying the patches and running pre-commit.
My question is: regarding the
xbranch mentioned above—does it refer to the source version or the target version for the migration?_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Christopher Rogos - 09:26 - 29 Nov 2024 -
Clarification on merge/squash the commits generated by bots or weblate
When reviewing this guide, it states:
"In order to squash these administrative commits, use
git rebase -i origin/x, wherexis the Odoo version (14.0, 15.0, 16.0,...). Don't forget first to dogit fetch origin xto get the latest remote information."In the context of migrating a module, this step is recommended after applying the patches and running pre-commit.
My question is: regarding the
xbranch mentioned above—does it refer to the source version or the target version for the migration?
by Ing. Rolando Pérez Rebollo - 12:11 - 29 Nov 2024 -
Re: Vertical support
Hey Joel,I am interested in getting the agriculture vertical forward as well.I already did a lot of work with a total different approach then the modules available there. More focused on the different disciplines of agriculture and especially the reporting part. Stil a lot of work. But I have good connections to the food agriculture section, which gives great input on how it should work.
So if there is something coming up...please let me know...
Cheers Nils
Von: Joel Patrick <notifications@odoo-community.org>
Gesendet: Wednesday, November 27, 2024 1:13:08 PM
An: Contributors <contributors@odoo-community.org>
Betreff: Vertical supportACHTUNG! Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.
Hello,
I am interested in exploring the support of the Vertical Agriculture project.I also like to understand if it would be possible to initiate and lead a project for Commercial Horticulture. There is already a version 1 available to initiate this project.
Joel PatrickPartner
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Nils Coenen - 02:06 - 27 Nov 2024 -
Re: [Odoo CE 17.0] Help needed with client search on budgets
Hi @Redes Sociales JLBBERPI didn't noticed at first but indeed you're right, thank you for pointing that out.The fact that you see those info about VAT and address is basically due to the field context (defined in XML field definition) which contains key values like 'show_vat': 1. That context is propagated to the python context which will be evaluated in odoo 17 _compute_display_name method.The code I gave you was totally overriding that context evaluation but this issue can be easily avoided by extending the _get_complete_name() hook instead, which is called in the first lines of _compute_display_name and can be extended to add values without overriding the context evaluation part. So I suggest to remove the _compute_display_name() override and replace it with the followingx_cliente_interno = fields.Integer() # use a standard field for consistencydef _get_complete_name(self):"""@override: add `x_cliente_interno` field to the complete name"""complete_name = super()._get_complete_name()cliente_interno = f"[{self.x_cliente_interno}] " if self.x_cliente_interno else ""complete_name_add_cliente_interno = cliente_interno + complete_namereturn complete_name_add_cliente_internoI made a quick test locally and this should be able to fix the issueKindly regards--FrancescoIl giorno mar 26 nov 2024 alle ore 09:47 Redes Sociales JLBBERP <notifications@odoo-community.org> ha scritto:Hello everyone,after making a custom module with Francescos' code and fixing the search function, I came across a problem related to how the partner is displayed at the sales order form:When searching for a customer, they are displayed with the following format: "[x_cliente_interno] + customer name", which is the exact format I needed. But the problem is that when I select any customer, it doesn't show it's address and neither it's VAT below the customer anymore.Here I send my version of the code from Francesco:from odoo import models, fields, api
class ResPartner(models.Model):_inherit = “res.partner”
x_cliente_interno = fields.Integer() # use a standard field for consistency
@api.depends(“name”, “x_cliente_interno”)def _compute_display_name(self):“""Show reference code before partner name""”super()._compute_display_name()for partner in self:name = partner.name or “unknown”cliente_interno = f"[{partner.x_cliente_interno}] " if partner.x_cliente_interno else ""# !! Disclaimer !!# If you copy this code and change it DO NOT ASSIGN the value of partner.name,# that would compromise your datas. Only re-assign partner.display_namepartner.display_name = cliente_interno + name # It's replacing the whole field
@api.modeldef _name_search(self, name, domain=None, operator='ilike', limit=None, order=None):“""Add custom field `cliente_interno` to the search domain""”domain = domain or []if name:domain += ['|', '|', ('name', operator, name),('email', operator, name),('x_cliente_interno', '=', name)]return self._search(domain, limit=limit, order=order)I tried fixing it by myself, and even if I wasn't able to, I discovered the field "partner.display_name" is the one causing this problem.Thanks in advance for the help.El 20/11/2024 9:21 CET Redes Sociales JLBBERP <redes_sociales@jlbberp.com> escribió:Hello Francesco,
I have seen your message right now, and I would like to thank you so much for not only your answer, but also for you writing the code I should do. I do not know how could I pay you back this favor that you have done for me.I rely on the community because I am in my beginnings and because of everything that my company JLBB ERP has given me through good collaboration, I am now checking it out. Do not doubt that everything I can contribute, you will find me here.Thank you Francesco for the help.Salutations to the community.El 20/11/2024 0:02 CET Francesco Ballerini <notifications@odoo-community.org> escribió:I apologize, it is now clear to me also that you need both the search from a custom field and the way the name is displayed, but the search is indeed prioritized.As Daniel and Xavier pointed out, in Odoo 17.0 you can already submit the "ref" field (field label on GUI is "Reference") and get the right record. E.g. if you have a contact named John Doe with Reference set on "ab-001" and you search for "ab-001" in the contacts search or dropdown you will fetch John Doe.You could migrate your "x_cliente_interno" data into the "ref" field, and this would automatically unlock the search feature. However if you need to keep this data in a specific custom field you will need to override _name_search() method.In every case you will also need to override _compute_display_name if you want to also show the code before the field. I provided a couple of snippet below (just as an example, especially the _name_search override needs to be refined).Let me point out another thing: from the field name I assume you are using a field defined from GUI, unfortunately it's not recommended to use those kind of fields in python methods as it will easily lead to inconsistencies and bugs (e.g. if you delete field from db and not remove it from python methods..). This means that if you want to use a custom field in _name_search() override you should migrate data to a standard field aniway.
This is an example of what you might do on a custom module. As you can see the _name_search() implementation has to be refined while the_compute_display_name method will work as is.If you decide to migrate data into the "ref" field you can only implement _compute_display_name by replacing "cliente_interno" with "ref" and you do not need to implement _name_search() in this case.from odoo import models, fields, apifrom odoo.osv import expression
class ResPartner(models.Model):_inherit = "res.partner"
cliente_interno = fields.Char() # use a standard field for consistency
@api.depends("name", "cliente_interno")def _compute_display_name(self):"""Show reference code before partner name"""super()._compute_display_name()for partner in self:name = partner.name or "unknown"cliente_interno = f"[{partner.cliente_interno}] " if partner.cliente_interno else ""# !! Disclaimer !!#I f you copy this code and change it DO NOT ASSIGN the value of partner.name,# that would compromise your datas. Only re-assign partner.display_namepartner.display_name = cliente_interno + name
@api.modeldef _name_search(self, name, domain=None, operator='ilike', limit=None, order=None):"""Add custom field `cliente_interno` to the search domain"""domain = expression.OR([domain or [], [("cliente_interno", operator, name)]])# this doesn't work properly, it seems like the domain we pass gets overridden,# might take this as example and adjust by debugging/find more examples on source codereturn super()._name_search(name, domain=domain, operator=operator, limit=limit, order=order)Regards--FrancescoIl giorno mar 19 nov 2024 alle ore 14:13 Daniel Reis <notifications@odoo-community.org> ha scritto:From your description, it feels like this is already available in standard Odoo:
The "ref" field is to be used for Client codes
The code is no longer presented in front of the name.
I think an OCA module is needed to bring that feature back.
/Daniel
On 19/11/2024 09:22, Redes Sociales JLBBERP wrote:Hello everyone,I am writing this message because I need assistance with modifying how searching a client while doing a budget works.What I am trying to do is, instead of searching just by the name, I want it to work like the following: I made a custom field called "x_cliente_interno", which is a number to identify the client, and I would like to make the search work like how product search works: If you write either the product's ID or the product's name, it will show you both fields merged from the data you wrote. Something like this:And when you select it, it shows the data like this:To sum up, what I am trying to do is that when you search a client, the search shows you the field "x_cliente_interno" behind the client name, like this: "[x_cliente_interno] client name" and it should also stay like in the second image when selected.Thanks in advance for the help._______________________________________________
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 PARTNER>> Schedule time on my calendar.
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais![[Logo OpenSourceIntegrators.com]](https://www.opensourceintegrators.com/images/opensource-logo-2022.svg)
_______________________________________________
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 Francesco Ballerini - 02:01 - 27 Nov 2024 -
Vertical support
Hello,I am interested in exploring the support of the Vertical Agriculture project.I also like to understand if it would be possible to initiate and lead a project for Commercial Horticulture. There is already a version 1 available to initiate this project.Joel PatrickPartner
by Joël PATRICK - 01:11 - 27 Nov 2024 -
Re: [Odoo CE 17.0] Help needed with client search on budgets
Hello everyone,after making a custom module with Francescos' code and fixing the search function, I came across a problem related to how the partner is displayed at the sales order form:When searching for a customer, they are displayed with the following format: "[x_cliente_interno] + customer name", which is the exact format I needed. But the problem is that when I select any customer, it doesn't show it's address and neither it's VAT below the customer anymore.Here I send my version of the code from Francesco:from odoo import models, fields, api
class ResPartner(models.Model):_inherit = “res.partner”
x_cliente_interno = fields.Integer() # use a standard field for consistency
@api.depends(“name”, “x_cliente_interno”)def _compute_display_name(self):“""Show reference code before partner name""”super()._compute_display_name()for partner in self:name = partner.name or “unknown”cliente_interno = f"[{partner.x_cliente_interno}] " if partner.x_cliente_interno else ""# !! Disclaimer !!# If you copy this code and change it DO NOT ASSIGN the value of partner.name,# that would compromise your datas. Only re-assign partner.display_namepartner.display_name = cliente_interno + name # It's replacing the whole field
@api.modeldef _name_search(self, name, domain=None, operator='ilike', limit=None, order=None):“""Add custom field `cliente_interno` to the search domain""”domain = domain or []if name:domain += ['|', '|', ('name', operator, name),('email', operator, name),('x_cliente_interno', '=', name)]return self._search(domain, limit=limit, order=order)I tried fixing it by myself, and even if I wasn't able to, I discovered the field "partner.display_name" is the one causing this problem.Thanks in advance for the help.El 20/11/2024 9:21 CET Redes Sociales JLBBERP <redes_sociales@jlbberp.com> escribió:Hello Francesco,
I have seen your message right now, and I would like to thank you so much for not only your answer, but also for you writing the code I should do. I do not know how could I pay you back this favor that you have done for me.I rely on the community because I am in my beginnings and because of everything that my company JLBB ERP has given me through good collaboration, I am now checking it out. Do not doubt that everything I can contribute, you will find me here.Thank you Francesco for the help.Salutations to the community.El 20/11/2024 0:02 CET Francesco Ballerini <notifications@odoo-community.org> escribió:I apologize, it is now clear to me also that you need both the search from a custom field and the way the name is displayed, but the search is indeed prioritized.As Daniel and Xavier pointed out, in Odoo 17.0 you can already submit the "ref" field (field label on GUI is "Reference") and get the right record. E.g. if you have a contact named John Doe with Reference set on "ab-001" and you search for "ab-001" in the contacts search or dropdown you will fetch John Doe.You could migrate your "x_cliente_interno" data into the "ref" field, and this would automatically unlock the search feature. However if you need to keep this data in a specific custom field you will need to override _name_search() method.In every case you will also need to override _compute_display_name if you want to also show the code before the field. I provided a couple of snippet below (just as an example, especially the _name_search override needs to be refined).Let me point out another thing: from the field name I assume you are using a field defined from GUI, unfortunately it's not recommended to use those kind of fields in python methods as it will easily lead to inconsistencies and bugs (e.g. if you delete field from db and not remove it from python methods..). This means that if you want to use a custom field in _name_search() override you should migrate data to a standard field aniway.
This is an example of what you might do on a custom module. As you can see the _name_search() implementation has to be refined while the_compute_display_name method will work as is.If you decide to migrate data into the "ref" field you can only implement _compute_display_name by replacing "cliente_interno" with "ref" and you do not need to implement _name_search() in this case.from odoo import models, fields, apifrom odoo.osv import expression
class ResPartner(models.Model):_inherit = "res.partner"
cliente_interno = fields.Char() # use a standard field for consistency
@api.depends("name", "cliente_interno")def _compute_display_name(self):"""Show reference code before partner name"""super()._compute_display_name()for partner in self:name = partner.name or "unknown"cliente_interno = f"[{partner.cliente_interno}] " if partner.cliente_interno else ""# !! Disclaimer !!#I f you copy this code and change it DO NOT ASSIGN the value of partner.name,# that would compromise your datas. Only re-assign partner.display_namepartner.display_name = cliente_interno + name
@api.modeldef _name_search(self, name, domain=None, operator='ilike', limit=None, order=None):"""Add custom field `cliente_interno` to the search domain"""domain = expression.OR([domain or [], [("cliente_interno", operator, name)]])# this doesn't work properly, it seems like the domain we pass gets overridden,# might take this as example and adjust by debugging/find more examples on source codereturn super()._name_search(name, domain=domain, operator=operator, limit=limit, order=order)Regards--FrancescoIl giorno mar 19 nov 2024 alle ore 14:13 Daniel Reis <notifications@odoo-community.org> ha scritto:From your description, it feels like this is already available in standard Odoo:
The "ref" field is to be used for Client codes
The code is no longer presented in front of the name.
I think an OCA module is needed to bring that feature back.
/Daniel
On 19/11/2024 09:22, Redes Sociales JLBBERP wrote:Hello everyone,I am writing this message because I need assistance with modifying how searching a client while doing a budget works.What I am trying to do is, instead of searching just by the name, I want it to work like the following: I made a custom field called "x_cliente_interno", which is a number to identify the client, and I would like to make the search work like how product search works: If you write either the product's ID or the product's name, it will show you both fields merged from the data you wrote. Something like this:And when you select it, it shows the data like this:To sum up, what I am trying to do is that when you search a client, the search shows you the field "x_cliente_interno" behind the client name, like this: "[x_cliente_interno] client name" and it should also stay like in the second image when selected.Thanks in advance for the help._______________________________________________
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 PARTNER>> Schedule time on my calendar.
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais _______________________________________________
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 Alejandro Párraga Alcázar - 09:46 - 26 Nov 2024 -
OCA Codesprint - around FOSDEM - are you keen?
Hello OCA Contributors,You may have seen on our social media that we are weighing up if there is enough interest to organise an OCA Codesprint around the FOSDEM event next year.
If this is something that is of interest to you, please let us know on our survey here. Depending on interest we will make a decision about what to do.The FOSDEM event is on the 1st and 2nd of February in Brussels. We are considering a sprint a day or two on either side.Have a great week.Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly - 01:26 - 26 Nov 2024 -
Re: Partner Types: refactor partner_firstname and introduce partner_type_base
Touching to have that 3 level hierarchy is not recommended, as other things depend on that hierarchy, and you won't obtain the desired partner on the corresponding parts.Regards.El dom, 24 nov 2024 a las 16:26, Christopher Rogos (<notifications@odoo-community.org>) escribió:Hi Pedro,
I understand your intension regarding a partner_name_split module, but I am not sure if merging partner_firstname, partner_second_lastname, partner_middlename into one module would make the module to complex. The partner_firstname tests are already complex. Adding more configurable cases could make the module very complex in development, if there is not a very clear definition how the splitting should work in each case.
Maybe we could add a partner_name_split module, which adds some configuration options and controls the installation of these existing modules?
But this is all going a lot further than the change I like to make at this point. I just want to add different address types like “partner_address” (contact with firstname/lastname but editable address) order “service” (only name and no editable address). The idea is to have better filter options and more control, when we have firstname/lastname and when we have only name.
There is also a lot of inconsistencies in Odoo. e.g. you can add a subcontact to a individual, but you cannot select an individual as a parent. Therefore another attribute like “can_be_parent” would be nice, because we use “other address” to track addresses of offices, and want to add the employees to each office. But therefore “other_address” needs to be selectable in “parent_id”, but currently only is_company is selectable in standard.
Best Regards
From: Pedro M. Baeza <notifications@odoo-community.org>
Sent: Montag, 18. November 2024 12:24
To: Contributors <contributors@odoo-community.org>
Subject: Re: Partner Types: refactor partner_firstname and introduce partner_type_baseYeah, I also feel that we should refactor into a "contact name splitting" module, for parameterizing which fields to show and with which goal. For example, having first name and second name, initials, and so on. This can depend on the country or other. I think this also fits with your use case.
Regards.
_______________________________________________
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 Pedro M. Baeza - 08:16 - 25 Nov 2024 -
RE: Partner Types: refactor partner_firstname and introduce partner_type_base
Hi Pedro,
I understand your intension regarding a partner_name_split module, but I am not sure if merging partner_firstname, partner_second_lastname, partner_middlename into one module would make the module to complex. The partner_firstname tests are already complex. Adding more configurable cases could make the module very complex in development, if there is not a very clear definition how the splitting should work in each case.
Maybe we could add a partner_name_split module, which adds some configuration options and controls the installation of these existing modules?
But this is all going a lot further than the change I like to make at this point. I just want to add different address types like “partner_address” (contact with firstname/lastname but editable address) order “service” (only name and no editable address). The idea is to have better filter options and more control, when we have firstname/lastname and when we have only name.
There is also a lot of inconsistencies in Odoo. e.g. you can add a subcontact to a individual, but you cannot select an individual as a parent. Therefore another attribute like “can_be_parent” would be nice, because we use “other address” to track addresses of offices, and want to add the employees to each office. But therefore “other_address” needs to be selectable in “parent_id”, but currently only is_company is selectable in standard.
Best Regards
From: Pedro M. Baeza <notifications@odoo-community.org>
Sent: Montag, 18. November 2024 12:24
To: Contributors <contributors@odoo-community.org>
Subject: Re: Partner Types: refactor partner_firstname and introduce partner_type_baseYeah, I also feel that we should refactor into a "contact name splitting" module, for parameterizing which fields to show and with which goal. For example, having first name and second name, initials, and so on. This can depend on the country or other. I think this also fits with your use case.
Regards.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Christopher Rogos - 04:25 - 24 Nov 2024 -
Re: [odoo16 ce] deploy doodba instance on portainer
Thank you Enric, I didn't customize the image yet as I'm still exploring the Doodba environment in my spare time and thus progressing gradually with this task :-)I’ll definitely keep your suggestion in mind. Once again, thank you all for the support.Cheers--FrancescoIl giorno lun 18 nov 2024 alle ore 00:02 Enric Tobella Alomar <notifications@odoo-community.org> ha scritto:On the creation of the doodba, you were able to set where to store the image.Just use copier update to reset the values and set it to a registry of your own choice.Kind regards,El dom, 17 nov 2024 a las 23:22, Francesco Ballerini (<notifications@odoo-community.org>) escribió:Oh.. right, after I read your answer I feel like I made a dumb question, well, it is neither the first nor the last time ; )As a developer who is starting to explore the world of deployment, I find your advice very helpful, thanks Graeme.--FrancescoIl giorno dom 17 nov 2024 alle ore 22:27 Graeme Gellatly <notifications@odoo-community.org> ha scritto:It makes no sense to build in a production compose file (note, this is not to say Doodba is wrong, as it needs instructions to make a production build, but that in a real prod environment you wouldn't). You are just pulling an image. Provided you link to your already built image you don't need any of that. Your CI will have the build instructions, tag the image etc, and then you are just pulling it.On Mon, Nov 18, 2024 at 10:02 AM Francesco Ballerini <notifications@odoo-community.org> wrote:Hi,few days ago I managed to set up a basic doodba instance. We're running this as "prod env" but we're actually just testing it at the moment. The instance is running well, but I've been asked to run this configuration from Portainer if possible.I'm trying to make some adaptations in order to make it work on portainer, I merged the `common.yaml` and `prod.yaml` in a single compose, added the result in the stack web editor, with some additional adjustments. However I am not sure how to solve this.```build:
context: ./odoo
args:
DB_VERSION: "15"
ODOO_VERSION: "16.0"
UID: "${UID:-1000}"
GID: "${GID:-1000}"```when I try to deploy it says that "build" is an unsupported option. Is there any way to adapt this?I would also like to ask if someone has to link an example on github or any other platform, I havent find any yet.Thank you--Francesco_______________________________________________
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
--Enric Tobella AlomarCEO & Founder_______________________________________________
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:46 - 21 Nov 2024 -
Re: Store large Size videos
Dear Hed Shefer,
If you need an ultimate solution you can have mine solution to deal with very big files.
I have been storing large videos outside of YouTube and displaying them in odoo blog.
You are my brother
Best
On Thu, Nov 21, 2024, 18:49 mohamed alkobrosly <alkobroslymohamed@gmail.com> wrote:Dear Graeme,
If you need an ultimate solution you can have mine solution to deal with very big files.
I have been storing large videos outside of YouTube and displaying them in odoo blog.
You are my brother
Best
On Wed, Nov 20, 2024, 23:38 Graeme Gellatly <notifications@odoo-community.org> wrote:Very interesting. So the issue isn't actually s3 per se, it is Odoo's file handling which seems to at least be on the radar/partially addressed by the OCA/storage team. Will watch with interest.On Thu, Nov 21, 2024 at 9:02 AM Axel Mendoza <notifications@odoo-community.org> wrote:I have used attachment_s3 and other approaches in the past and they aren't good options for handling big files. Every time you give a big file to Odoo it's a bad experience. No streaming, high memory usage, slow manipulation. I have even implemented an streaming google drive file type to avoid odoo issues with big files and it's better but too complex solution because of all routes that need to create to handle everything and not as good as directly upload and download from S3 buckets without giving the files to OdooMsc. Axel Mendoza PupoOn Wed, Nov 20, 2024 at 1:47 PM Graeme Gellatly <notifications@odoo-community.org> wrote:Hi,Why go to all that trouble? What advantage does doing all that give over the commonly used attachment_s3?On Thu, Nov 21, 2024 at 7:52 AM Axel Mendoza <notifications@odoo-community.org> wrote:It's a combination of deployment strategies where the odoo filestore is mounted into the local filesystem as FUSE. The attachment is created empty in Odoo to get the store_fname location into the S3 Bucket and then the upload action is pre-signed to allow the user upload the files directly into S3 uri location and all the operations that involve the usage of the file is also pre-signed so the user will be able to view it, download and even edit it using online tools for some file types like using google docs or microsoft office online. For Odoo the file lives in the filestore but the filestore is remote in an S3 bucketMsc. Axel Mendoza PupoOn Wed, Nov 20, 2024 at 11:57 AM Hed Shefer <notifications@odoo-community.org> wrote:Great!And how was the integration after loading to aws S3? Did you fetch the files to the odoo website page without issues?בתאריך יום ד׳, 20 בנוב׳ 2024, 19:38, מאת Axel Mendoza <notifications@odoo-community.org>:HelloI have experience directly uploading big files to AWS S3 and also integrated with Odoo. You should avoid at all cost to give Odoo the file since it will load it completely in memory and it will be very slow and could easily crash for big filesMsc. Axel Mendoza PupoOn Wed, Nov 20, 2024 at 11:27 AM Roussel, Denis <notifications@odoo-community.org> wrote:Hi Hed,I suggest you to check fs_storage module: https://github.com/OCA/storage/tree/16.0/fs_storage
It supports external storages as S3, ...Regards,On Wed, Nov 20, 2024 at 2:42 PM Hed Shefer <notifications@odoo-community.org> wrote:Hi everyone,
Does anyone have experience with storing very large video files (e.g., 1-hour-long, few GB) in the Odoo file system or an external drive?
Our use case involves an Odoo website with Videos, and we're trying to avoid embedding videos from external platforms like YouTube.
Thanks_______________________________________________
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
_______________________________________________
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 Mohamed Alkobrosly - 04:56 - 21 Nov 2024 -
Re: Store large Size videos
Dear Graeme,
If you need an ultimate solution you can have mine solution to deal with very big files.
I have been storing large videos outside of YouTube and displaying them in odoo blog.
You are my brother
Best
On Wed, Nov 20, 2024, 23:38 Graeme Gellatly <notifications@odoo-community.org> wrote:Very interesting. So the issue isn't actually s3 per se, it is Odoo's file handling which seems to at least be on the radar/partially addressed by the OCA/storage team. Will watch with interest.On Thu, Nov 21, 2024 at 9:02 AM Axel Mendoza <notifications@odoo-community.org> wrote:I have used attachment_s3 and other approaches in the past and they aren't good options for handling big files. Every time you give a big file to Odoo it's a bad experience. No streaming, high memory usage, slow manipulation. I have even implemented an streaming google drive file type to avoid odoo issues with big files and it's better but too complex solution because of all routes that need to create to handle everything and not as good as directly upload and download from S3 buckets without giving the files to OdooMsc. Axel Mendoza PupoOn Wed, Nov 20, 2024 at 1:47 PM Graeme Gellatly <notifications@odoo-community.org> wrote:Hi,Why go to all that trouble? What advantage does doing all that give over the commonly used attachment_s3?On Thu, Nov 21, 2024 at 7:52 AM Axel Mendoza <notifications@odoo-community.org> wrote:It's a combination of deployment strategies where the odoo filestore is mounted into the local filesystem as FUSE. The attachment is created empty in Odoo to get the store_fname location into the S3 Bucket and then the upload action is pre-signed to allow the user upload the files directly into S3 uri location and all the operations that involve the usage of the file is also pre-signed so the user will be able to view it, download and even edit it using online tools for some file types like using google docs or microsoft office online. For Odoo the file lives in the filestore but the filestore is remote in an S3 bucketMsc. Axel Mendoza PupoOn Wed, Nov 20, 2024 at 11:57 AM Hed Shefer <notifications@odoo-community.org> wrote:Great!And how was the integration after loading to aws S3? Did you fetch the files to the odoo website page without issues?בתאריך יום ד׳, 20 בנוב׳ 2024, 19:38, מאת Axel Mendoza <notifications@odoo-community.org>:HelloI have experience directly uploading big files to AWS S3 and also integrated with Odoo. You should avoid at all cost to give Odoo the file since it will load it completely in memory and it will be very slow and could easily crash for big filesMsc. Axel Mendoza PupoOn Wed, Nov 20, 2024 at 11:27 AM Roussel, Denis <notifications@odoo-community.org> wrote:Hi Hed,I suggest you to check fs_storage module: https://github.com/OCA/storage/tree/16.0/fs_storage
It supports external storages as S3, ...Regards,On Wed, Nov 20, 2024 at 2:42 PM Hed Shefer <notifications@odoo-community.org> wrote:Hi everyone,
Does anyone have experience with storing very large video files (e.g., 1-hour-long, few GB) in the Odoo file system or an external drive?
Our use case involves an Odoo website with Videos, and we're trying to avoid embedding videos from external platforms like YouTube.
Thanks_______________________________________________
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
_______________________________________________
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 Mohamed Alkobrosly - 04:51 - 21 Nov 2024 -
Re: [NEWS] oca-port: a new version has been released!
thank U sebastian, I'm already thinking in some use cases at hand. I'll checkout the talks.
On 11/20/24 11:32, Sebastien Alix wrote:
Yes exactly it is a helper, but it won't do everything automatically sadly :)
When it comes to migrate a module, it'll play the usual "git format-patch" command and pre-commit for you, and will print the next steps (and the link of the OCA migration guide you just provided).
But its main strength is to compare two different git history (e.g. 14.0 and 16.0) for a module already migrated but which evolved overtime in 14.0, and list missing commits from 14.0 in 16.0, and "help" you to port them, example here some ports for the module 'account_invoice_section_sale_order', one branch after another:
- 14.0 to 15.0: https://github.com/OCA/account-invoicing/pull/1802
- 15.0 to 16.0: https://github.com/OCA/account-invoicing/pull/1803
- 16.0 to 17.0: https://github.com/OCA/account-invoicing/pull/1804
Basically it's mostly a helper to forward-port and backport (switch the branches!) commits from one branch/repo to another.
Here are talks that were made about this tool:
- 2022: https://www.youtube.com/watch?v=idGLkQiJ5N0&pp=ygUIb2NhLXBvcnQ%3D
- 2023: https://www.youtube.com/watch?v=eCXJMvV_EhM&pp=ygUIb2NhLXBvcnQ%3D
Yes, I'm not good to promote things, will try to improve that!
Le 20/11/2024 à 15:52, Rolando Pérez Rebollo a écrit :
Wow, are there any OCA talks or similar about this? I've just discovered. From the readme looks like could assist in the migration of addons. Is It a helper that replace manual work when doing stuff like https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-16.0?
On 11/20/24 06:13, Mignon, Laurent wrote:
Thank you Sébastion for this useful and powerful tool!
On Wed, Nov 20, 2024 at 11:47 AM David Vidal <notifications@odoo-community.org> wrote:
Thanks for the great work!
El mié, 20 nov 2024 a las 11:38, Sebastien Alix (<notifications@odoo-community.org>) escribió:
Hello there!
A new version of oca-port has been released:
- CHANGELOG: https://github.com/OCA/oca-port/releases/tag/v0.16
(+ https://github.com/OCA/oca-port/releases/tag/v0.17
- fix)
- GitHub: https://github.com/OCA/oca-port
- PyPI: https://pypi.org/project/oca-port/
This new version changed the CLI parameters, and now allows to migrate modules or port commits from one repository to another thanks to the new syntax.
Let's say that origin remote is for OCA/social, and mail remote for the newly created OCA/mail repository, to check if mail_tracking is migrated or have commits to port from 16.0 to 18.0:
$ cd ~/OCA/social $ git remote add mail git@github.com:OCA/mail.git $ oca-port origin/16.0 mail/18.0 mail_tracking --verbose --fetch --dry-run
Output:
Source: origin/16.0, remote origin git@github.com:OCA/social.git Target: mail/18.0, remote mail git@github.com:OCA/mail.git Fetch origin/16.0 from git@github.com:OCA/social.git Fetch mail/18.0 from git@github.com:OCA/mail.git ⚠️ Migration of mail_tracking seems handled in this PR: https://github.com/OCA/mail/pull/1 (by trisdoan) We invite you to review this PR instead of opening a new one. Thank you! ℹ️ mail_tracking can be migrated from 16.0 to 18.0.
Seems there is already a PR open on OCA/mail to migrate this module, better to review this one before opening a new one!
Otherwise, by removing the --dry-run flag (with an optional --destination) we could handle the migration, following OCA migration guide.
If a module is already migrated, the list of missing commits (if any) grouped by PR will be listed, up to the user to port or to blacklist them if they are not relevant.
This new version also allows you to migrate modules located in a subfolder instead of the root directory, useful for private project repositories for instance.
ROADMAP:
- integrate odoo-module-migrator to automatically upgrade code when migrating a module (WIP)
- register/handle renamed modules
Ideas, bugfixes and improvements are welcome.
Have a good day,
-- Sébastien Alix Business Solutions Odoo Developer Camptocamp France SA https://www.camptocamp.com/
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
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
-- Sébastien Alix Business Solutions Odoo Developer Camptocamp France SA https://www.camptocamp.com/
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Ing. Rolando Pérez Rebollo - 12:06 - 21 Nov 2024 -
Re: Store large Size videos
Very interesting. So the issue isn't actually s3 per se, it is Odoo's file handling which seems to at least be on the radar/partially addressed by the OCA/storage team. Will watch with interest.On Thu, Nov 21, 2024 at 9:02 AM Axel Mendoza <notifications@odoo-community.org> wrote:I have used attachment_s3 and other approaches in the past and they aren't good options for handling big files. Every time you give a big file to Odoo it's a bad experience. No streaming, high memory usage, slow manipulation. I have even implemented an streaming google drive file type to avoid odoo issues with big files and it's better but too complex solution because of all routes that need to create to handle everything and not as good as directly upload and download from S3 buckets without giving the files to OdooMsc. Axel Mendoza PupoOn Wed, Nov 20, 2024 at 1:47 PM Graeme Gellatly <notifications@odoo-community.org> wrote:Hi,Why go to all that trouble? What advantage does doing all that give over the commonly used attachment_s3?On Thu, Nov 21, 2024 at 7:52 AM Axel Mendoza <notifications@odoo-community.org> wrote:It's a combination of deployment strategies where the odoo filestore is mounted into the local filesystem as FUSE. The attachment is created empty in Odoo to get the store_fname location into the S3 Bucket and then the upload action is pre-signed to allow the user upload the files directly into S3 uri location and all the operations that involve the usage of the file is also pre-signed so the user will be able to view it, download and even edit it using online tools for some file types like using google docs or microsoft office online. For Odoo the file lives in the filestore but the filestore is remote in an S3 bucketMsc. Axel Mendoza PupoOn Wed, Nov 20, 2024 at 11:57 AM Hed Shefer <notifications@odoo-community.org> wrote:Great!And how was the integration after loading to aws S3? Did you fetch the files to the odoo website page without issues?בתאריך יום ד׳, 20 בנוב׳ 2024, 19:38, מאת Axel Mendoza <notifications@odoo-community.org>:HelloI have experience directly uploading big files to AWS S3 and also integrated with Odoo. You should avoid at all cost to give Odoo the file since it will load it completely in memory and it will be very slow and could easily crash for big filesMsc. Axel Mendoza PupoOn Wed, Nov 20, 2024 at 11:27 AM Roussel, Denis <notifications@odoo-community.org> wrote:Hi Hed,I suggest you to check fs_storage module: https://github.com/OCA/storage/tree/16.0/fs_storage
It supports external storages as S3, ...Regards,On Wed, Nov 20, 2024 at 2:42 PM Hed Shefer <notifications@odoo-community.org> wrote:Hi everyone,
Does anyone have experience with storing very large video files (e.g., 1-hour-long, few GB) in the Odoo file system or an external drive?
Our use case involves an Odoo website with Videos, and we're trying to avoid embedding videos from external platforms like YouTube.
Thanks_______________________________________________
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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Graeme Gellatly - 09:36 - 20 Nov 2024 -
Re: Store large Size videos
I have used attachment_s3 and other approaches in the past and they aren't good options for handling big files. Every time you give a big file to Odoo it's a bad experience. No streaming, high memory usage, slow manipulation. I have even implemented an streaming google drive file type to avoid odoo issues with big files and it's better but too complex solution because of all routes that need to create to handle everything and not as good as directly upload and download from S3 buckets without giving the files to OdooMsc. Axel Mendoza PupoOn Wed, Nov 20, 2024 at 1:47 PM Graeme Gellatly <notifications@odoo-community.org> wrote:Hi,Why go to all that trouble? What advantage does doing all that give over the commonly used attachment_s3?On Thu, Nov 21, 2024 at 7:52 AM Axel Mendoza <notifications@odoo-community.org> wrote:It's a combination of deployment strategies where the odoo filestore is mounted into the local filesystem as FUSE. The attachment is created empty in Odoo to get the store_fname location into the S3 Bucket and then the upload action is pre-signed to allow the user upload the files directly into S3 uri location and all the operations that involve the usage of the file is also pre-signed so the user will be able to view it, download and even edit it using online tools for some file types like using google docs or microsoft office online. For Odoo the file lives in the filestore but the filestore is remote in an S3 bucketMsc. Axel Mendoza PupoOn Wed, Nov 20, 2024 at 11:57 AM Hed Shefer <notifications@odoo-community.org> wrote:Great!And how was the integration after loading to aws S3? Did you fetch the files to the odoo website page without issues?בתאריך יום ד׳, 20 בנוב׳ 2024, 19:38, מאת Axel Mendoza <notifications@odoo-community.org>:HelloI have experience directly uploading big files to AWS S3 and also integrated with Odoo. You should avoid at all cost to give Odoo the file since it will load it completely in memory and it will be very slow and could easily crash for big filesMsc. Axel Mendoza PupoOn Wed, Nov 20, 2024 at 11:27 AM Roussel, Denis <notifications@odoo-community.org> wrote:Hi Hed,I suggest you to check fs_storage module: https://github.com/OCA/storage/tree/16.0/fs_storage
It supports external storages as S3, ...Regards,On Wed, Nov 20, 2024 at 2:42 PM Hed Shefer <notifications@odoo-community.org> wrote:Hi everyone,
Does anyone have experience with storing very large video files (e.g., 1-hour-long, few GB) in the Odoo file system or an external drive?
Our use case involves an Odoo website with Videos, and we're trying to avoid embedding videos from external platforms like YouTube.
Thanks_______________________________________________
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 Axel Mendoza - 09:01 - 20 Nov 2024
