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
-
db not yet committed when overriding create/update.
Hello,I send a webhook when an event occurs in Odoo.The problem I have is that when overriding create/update; and triggering my webhook, the data is not yet committed in the db.(the external system is sending in it's response that the record is not found in the case of create and get the old field value -before changes- for an update).I tried to use env.cr.flush() and/or env.cr.commit() both in my automated action and in my code before the webhook but nothing seems to work.Any other way I could check?Thank you--Yves Goldberg--
by Yves Goldberg - 11:46 - 21 Jun 2024-
Re: db not yet committed when overriding create/update.
Hi Yves,
flush wouldn't work, but commit should do it! But I wonder if the automated action is using the same cursor as the main process.
Maybe a nice way could be to install OCA's "queue_job" and in your automated action, call the webhook in a separate function that you call using .with_delay().some_function()
Then it will be executed as a queue.job, and you are sure that whenever it's picked up the original action will already have finished (or if it failed, and the cr is rolled back, then the webhook won't be called at all since the queue job record will also not have been created, which is also a feature you won't have if you call the webhook directly)
cheers
On 6/21/24 11:48, Yves Goldberg wrote:
Hello,
I send a webhook when an event occurs in Odoo.
The problem I have is that when overriding create/update; and triggering my webhook, the data is not yet committed in the db.
(the external system is sending in it's response that the record is not found in the case of create and get the old field value -before changes- for an update).
I tried to use env.cr.flush() and/or env.cr.commit() both in my automated action and in my code before the webhook but nothing seems to work.
Any other way I could check?
Thank you
--
Yves Goldberg
--
_______________________________________________
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 - 11:56 - 21 Jun 2024 -
Re: db not yet committed when overriding create/update.
You can send your webhook using a callback on the postcommit callback.Check in the Odoo code for the use of the decorator @self.env.cr.postcommit.addclass BaseCursor:
""" Base class for cursors that manage pre/post commit hooks. """
def __init__(self):
self.precommit = tools.Callbacks()
self.postcommit = tools.Callbacks()
self.prerollback = tools.Callbacks()
self.postrollback = tools.Callbacks()--
Yann PAPOUIN, Ingénieur R&D | DECLe ven. 21 juin 2024 à 11:48, Yves Goldberg <notifications@odoo-community.org> a écrit :Hello,I send a webhook when an event occurs in Odoo.The problem I have is that when overriding create/update; and triggering my webhook, the data is not yet committed in the db.(the external system is sending in it's response that the record is not found in the case of create and get the old field value -before changes- for an update).I tried to use env.cr.flush() and/or env.cr.commit() both in my automated action and in my code before the webhook but nothing seems to work.Any other way I could check?Thank you--Yves Goldberg--_______________________________________________
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 - 11:56 - 21 Jun 2024
-
-
Tree view with preview - is it possible?
Hello,
is there some view or widget or a way to display something like a split screen where one part would be holding a tree view of objects and second part would having a form view (read only is sufficient) of selected (clicked) record from the first part?
I seem to remember seeing something like that somewhere but cannot remember where. Any hints / pointers are greatly welcome.
Best regards
Radovan Skolnik
by Radovan Skolnik - 11:21 - 21 Jun 2024-
Re: Tree view with preview - is it possible?
Enric,
that's where I have seen it! Thanks a lot. I will check it.
Best regards
Radovan
On piatok 21. júna 2024 19:22:30 CEST Enric Tobella Alomar wrote:
> Account reconcile OCA combines a kanban view with a preview form.
> On Fri, 21 Jun 2024, 17:08 Radovan Skolnik, <
> notifications@odoo-community.org [1] > wrote: Alexandre,
>
> that's exactly what I was looking for. A bit pity it's closed source and I'd
> also need it for 14 but great find. I think something like this could be
> part of Odoo itself or at least a very worthy OCA module.
>
> Best regards
>
> Radovan
>
> On piatok 21. júna 2024 16:57:32 CEST Alexandre Fayolle wrote:
> > There's a closed source addon on the app store which seems to do that:
> > rmt_advance_list_form
> > Alexandre
> >
> > On 21/06/2024 11:22, Radovan Skolnik wrote:
> > > Hello,
> > >
> > >
> > > is there some view or widget or a way to display something like a split
> > > screen where one part would be holding a tree view of objects and second
> > > part would having a form view (read only is sufficient) of selected
> > > (clicked) record from the first part?
> > >
> > >
> > > I seem to remember seeing something like that somewhere but cannot
> > > remember where. Any hints / pointers are greatly welcome.
> > >
> > >
> > > Best regards
> > >
> > >
> > > Radovan Skolnik
> > >
> > > _______________________________________________
> > > Mailing-List: https://odoo-community.org/groups/contributors-15 [2]
> > > < https://odoo-community.org/groups/contributors-15 [3] >
> > > Post to: mailto: contributors@odoo-community.org [4]
> > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [5]
> > > < https://odoo-community.org/groups?unsubscribe [6] >
> >
> > --
> > Alexandre Fayolle
> > Senior Software Engineer
> > Tel : +33 4 58 48 20 30
> > Camptocamp France SAS
> > 18 rue du Lac Saint André
> > 73 370 Le Bourget-du-Lac
> > France
> > http://www.camptocamp.com [7]
> >
> > _______________________________________________
> > Mailing-List: https://odoo-community.org/groups/contributors-15 [8] [1]
> > Post to: mailto: contributors@odoo-community.org [9]
> > Unsubscribe: https://odoo-community.org/groups?unsubscribe [10] [2]
> >
> >
> >
> > [1] https://odoo-community.org/groups/contributors-15 [11]
> > [2] https://odoo-community.org/groups?unsubscribe [12]
>
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [13]
> Post to: mailto: contributors@odoo-community.org [14]
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [15]
>
>
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [16]
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [17]
>
>
>
> [1] mailto:notifications@odoo-community.org
> [2] https://odoo-community.org/groups/contributors-15
> [3] https://odoo-community.org/groups/contributors-15
> [4] mailto:contributors@odoo-community.org
> [5] https://odoo-community.org/groups?unsubscribe
> [6] https://odoo-community.org/groups?unsubscribe
> [7] http://www.camptocamp.com
> [8] https://odoo-community.org/groups/contributors-15
> [9] mailto:contributors@odoo-community.org
> [10] https://odoo-community.org/groups?unsubscribe
> [11] https://odoo-community.org/groups/contributors-15
> [12] https://odoo-community.org/groups?unsubscribe
> [13] https://odoo-community.org/groups/contributors-15
> [14] mailto:contributors@odoo-community.org
> [15] https://odoo-community.org/groups?unsubscribe
> [16] https://odoo-community.org/groups/contributors-15
> [17] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 09:06 - 21 Jun 2024 -
Re: Tree view with preview - is it possible?
Account reconcile OCA combines a kanban view with a preview form.On Fri, 21 Jun 2024, 17:08 Radovan Skolnik, <notifications@odoo-community.org> wrote:Alexandre,
that's exactly what I was looking for. A bit pity it's closed source and I'd also need it for 14 but great find. I think something like this could be part of Odoo itself or at least a very worthy OCA module.
Best regards
Radovan
On piatok 21. júna 2024 16:57:32 CEST Alexandre Fayolle wrote:
> There's a closed source addon on the app store which seems to do that:
> rmt_advance_list_form
> Alexandre
>
> On 21/06/2024 11:22, Radovan Skolnik wrote:
> > Hello,
> >
> >
> > is there some view or widget or a way to display something like a split
> > screen where one part would be holding a tree view of objects and second
> > part would having a form view (read only is sufficient) of selected
> > (clicked) record from the first part?
> >
> >
> > I seem to remember seeing something like that somewhere but cannot
> > remember where. Any hints / pointers are greatly welcome.
> >
> >
> > Best regards
> >
> >
> > Radovan Skolnik
> >
> > _______________________________________________
> > Mailing-List: https://odoo-community.org/groups/contributors-15
> > <https://odoo-community.org/groups/contributors-15>
> > Post to: mailto:contributors@odoo-community.org
> > Unsubscribe: https://odoo-community.org/groups?unsubscribe
> > <https://odoo-community.org/groups?unsubscribe>
>
> --
> Alexandre Fayolle
> Senior Software Engineer
> Tel : +33 4 58 48 20 30
> Camptocamp France SAS
> 18 rue du Lac Saint André
> 73 370 Le Bourget-du-Lac
> France
>
> _______________________________________________
> 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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Enric Tobella Alomar - 07:21 - 21 Jun 2024 -
Re: Tree view with preview - is it possible?
Alexandre,
that's exactly what I was looking for. A bit pity it's closed source and I'd also need it for 14 but great find. I think something like this could be part of Odoo itself or at least a very worthy OCA module.
Best regards
Radovan
On piatok 21. júna 2024 16:57:32 CEST Alexandre Fayolle wrote:
> There's a closed source addon on the app store which seems to do that:
> rmt_advance_list_form
> Alexandre
>
> On 21/06/2024 11:22, Radovan Skolnik wrote:
> > Hello,
> >
> >
> > is there some view or widget or a way to display something like a split
> > screen where one part would be holding a tree view of objects and second
> > part would having a form view (read only is sufficient) of selected
> > (clicked) record from the first part?
> >
> >
> > I seem to remember seeing something like that somewhere but cannot
> > remember where. Any hints / pointers are greatly welcome.
> >
> >
> > Best regards
> >
> >
> > Radovan Skolnik
> >
> > _______________________________________________
> > Mailing-List: https://odoo-community.org/groups/contributors-15
> > <https://odoo-community.org/groups/contributors-15>
> > Post to: mailto:contributors@odoo-community.org
> > Unsubscribe: https://odoo-community.org/groups?unsubscribe
> > <https://odoo-community.org/groups?unsubscribe>
>
> --
> Alexandre Fayolle
> Senior Software Engineer
> Tel : +33 4 58 48 20 30
> Camptocamp France SAS
> 18 rue du Lac Saint André
> 73 370 Le Bourget-du-Lac
> France
> http://www.camptocamp.com
>
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [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 - 05:06 - 21 Jun 2024 -
Re: Tree view with preview - is it possible?
There's a closed source addon on the app store which seems to do that: rmt_advance_list_form Alexandre On 21/06/2024 11:22, Radovan Skolnik wrote: > Hello, > > > is there some view or widget or a way to display something like a split > screen where one part would be holding a tree view of objects and second > part would having a form view (read only is sufficient) of selected > (clicked) record from the first part? > > > I seem to remember seeing something like that somewhere but cannot > remember where. Any hints / pointers are greatly welcome. > > > Best regards > > > Radovan Skolnik > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
by Alexandre Fayolle - 04:56 - 21 Jun 2024 -
Re: Tree view with preview - is it possible?
That's not what I aim for. Imagine having split screen where on left side you have list of Sale Orders and when you click on one it is displayed in the right side.
Radovan
On piatok 21. júna 2024 11:48:25 CEST Tom Blauwendraat wrote:
> Dashboards?
>
> _______________________________________________
> 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 - 12:05 - 21 Jun 2024
-
-
x2many fields vertical scrollbar?
Hi,
I am managing a situation where we often have a lot of lines on some main apps x2many fields (sale, picking, invoice, purchase..).
It's not really handy when we are in a range of 60-200 lines, I just discovered that I could permanently increase the "limit" attribute on the tree-view.
That would partially solve the problem, but in my opinion another part of the issue is that if you increase the "pager limit" to contain all lines, all the elements after the field will be pushed down in the view.
It would be nice to have a vertical scrolling so that we can let's say set a limit of 500 lines (so they will all be loaded in the same pager) then have a limited height and be able to vertically scroll through the lines.
Do you know any way to achieve this? Maybe someone already made a module for that?
Have a nice day,Francesco Ballerini
by Francesco Ballerini - 10:06 - 21 Jun 2024-
Re: x2many fields vertical scrollbar?
I'm sorry for bottom posting, just wanted to notify that adding.table-responsive {
overflow: visible;}actually made the overflow-x always visible as well. I didn't notice because I didn't have enough fields in the view while checking for it.Regards,Francesco Ballerini
by Francesco Ballerini - 02:46 - 21 Jun 2024 -
Re: x2many fields vertical scrollbar?
Hi David, the module you've suggested actually makes the x2m listview header sticky !As there were few scss lines I've tested them one by one, realized that you also need to add these lines in order to actually apply this web responsive code which makes list-view header sticky to x2m list as wellI don't have a good perception or particular skills in scss/css so I am not sure why these lines are required to apply the "position:sticky" thing, but I guess we made it 😁.table-responsive {
overflow: visible;
}The footer issue remains as it's still only visible when scrolling to the bottom, but the sticky header was more important. Thanks for all the advice!Regards,Francesco BalleriniIl giorno ven 21 giu 2024 alle ore 12:32 David Beal <notifications@odoo-community.org> ha scritto:Hi all, Consider using https://github.com/CybroOdoo/CybroAddons/tree/16.0/list_view_sticky_header for this use case. It works very well. It might be nice if Cybrosys would consider bringing this module under the OCA umbrella. CybroAddons repo is very huge, it could be an advantage to move it to a smaller one. Regards David BEAL Akretion Consultant ERP Odoo Le ven. 21 juin 2024 à 11:27, Francesco Ballerini <notifications@odoo-community.org> a écrit : > > Hi Yann, > > > I'm really grateful for the feedback, your approach is working. I only have couple of issues with: > > > - sticky header/footer, I have web responsive installed and I verified that this web responsive code is also applying to the x2m list views by changing some colours : ) . But for some reason header and footer will not actually be when adding vertical scrolling to x2m list > > > - overflow-x: useful when we have a decent number of fields in the x2m listview, at the moment I only see it when I reach the bottom of scroll-Y. > > I need it always visible though > > > Do you have additional suggestions to cover this? > > > Thank you > > -- > > Francesco Ballerini > > > Il giorno ven 21 giu 2024 alle ore 10:53 Yann Papouin <notifications@odoo-community.org> ha scritto: > > This should be enough: > > .o_form_view .o_field_widget .o_list_view { > overflow-y: scroll; > max-height: 600px; > } > > Add it using a custom module > > -- > Yann PAPOUIN, Ingénieur R&D | DEC > > > Le ven. 21 juin 2024 à 10:09, Francesco Ballerini <notifications@odoo-community.org> a écrit : > > Hi, > > > I am managing a situation where we often have a lot of lines on some main apps x2many fields (sale, picking, invoice, purchase..). > > > It's not really handy when we are in a range of 60-200 lines, I just discovered that I could permanently increase the "limit" attribute on the tree-view. > > > That would partially solve the problem, but in my opinion another part of the issue is that if you increase the "pager limit" to contain all lines, all the elements after the field will be pushed down in the view. > > It would be nice to have a vertical scrolling so that we can let's say set a limit of 500 lines (so they will all be loaded in the same pager) then have a limited height and be able to vertically scroll through the lines. > > > Do you know any way to achieve this? Maybe someone already made a module for that? > > > Have a nice day, > Francesco Ballerini > > _______________________________________________ > 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 Francesco Ballerini - 02:31 - 21 Jun 2024 -
Re: x2many fields vertical scrollbar?
Hi all, Consider using https://github.com/CybroOdoo/CybroAddons/tree/16.0/list_view_sticky_header for this use case. It works very well. It might be nice if Cybrosys would consider bringing this module under the OCA umbrella. CybroAddons repo is very huge, it could be an advantage to move it to a smaller one. Regards David BEAL Akretion Consultant ERP Odoo Le ven. 21 juin 2024 à 11:27, Francesco Ballerini <notifications@odoo-community.org> a écrit : > > Hi Yann, > > > I'm really grateful for the feedback, your approach is working. I only have couple of issues with: > > > - sticky header/footer, I have web responsive installed and I verified that this web responsive code is also applying to the x2m list views by changing some colours : ) . But for some reason header and footer will not actually be when adding vertical scrolling to x2m list > > > - overflow-x: useful when we have a decent number of fields in the x2m listview, at the moment I only see it when I reach the bottom of scroll-Y. > > I need it always visible though > > > Do you have additional suggestions to cover this? > > > Thank you > > -- > > Francesco Ballerini > > > Il giorno ven 21 giu 2024 alle ore 10:53 Yann Papouin <notifications@odoo-community.org> ha scritto: > > This should be enough: > > .o_form_view .o_field_widget .o_list_view { > overflow-y: scroll; > max-height: 600px; > } > > Add it using a custom module > > -- > Yann PAPOUIN, Ingénieur R&D | DEC > > > Le ven. 21 juin 2024 à 10:09, Francesco Ballerini <notifications@odoo-community.org> a écrit : > > Hi, > > > I am managing a situation where we often have a lot of lines on some main apps x2many fields (sale, picking, invoice, purchase..). > > > It's not really handy when we are in a range of 60-200 lines, I just discovered that I could permanently increase the "limit" attribute on the tree-view. > > > That would partially solve the problem, but in my opinion another part of the issue is that if you increase the "pager limit" to contain all lines, all the elements after the field will be pushed down in the view. > > It would be nice to have a vertical scrolling so that we can let's say set a limit of 500 lines (so they will all be loaded in the same pager) then have a limited height and be able to vertically scroll through the lines. > > > Do you know any way to achieve this? Maybe someone already made a module for that? > > > Have a nice day, > Francesco Ballerini > > _______________________________________________ > 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 David BEAL - 12:31 - 21 Jun 2024 -
Re: x2many fields vertical scrollbar?
Hi Yann,
I'm really grateful for the feedback, your approach is working. I only have couple of issues with:
- sticky header/footer, I have web responsive installed and I verified that this web responsive code is also applying to the x2m list views by changing some colours : ) . But for some reason header and footer will not actually be when adding vertical scrolling to x2m list
- overflow-x: useful when we have a decent number of fields in the x2m listview, at the moment I only see it when I reach the bottom of scroll-Y.
I need it always visible though
Do you have additional suggestions to cover this?
Thank you
--
Francesco Ballerini
Il giorno ven 21 giu 2024 alle ore 10:53 Yann Papouin <notifications@odoo-community.org> ha scritto:This should be enough:.o_form_view .o_field_widget .o_list_view {
overflow-y: scroll;
max-height: 600px;}Add it using a custom module--
Yann PAPOUIN, Ingénieur R&D | DECLe ven. 21 juin 2024 à 10:09, Francesco Ballerini <notifications@odoo-community.org> a écrit :Hi,
I am managing a situation where we often have a lot of lines on some main apps x2many fields (sale, picking, invoice, purchase..).
It's not really handy when we are in a range of 60-200 lines, I just discovered that I could permanently increase the "limit" attribute on the tree-view.
That would partially solve the problem, but in my opinion another part of the issue is that if you increase the "pager limit" to contain all lines, all the elements after the field will be pushed down in the view.
It would be nice to have a vertical scrolling so that we can let's say set a limit of 500 lines (so they will all be loaded in the same pager) then have a limited height and be able to vertically scroll through the lines.
Do you know any way to achieve this? Maybe someone already made a module for that?
Have a nice day,Francesco Ballerini_______________________________________________
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 - 11:26 - 21 Jun 2024 -
Re: x2many fields vertical scrollbar?
This should be enough:.o_form_view .o_field_widget .o_list_view {
overflow-y: scroll;
max-height: 600px;}Add it using a custom module--
Yann PAPOUIN, Ingénieur R&D | DECLe ven. 21 juin 2024 à 10:09, Francesco Ballerini <notifications@odoo-community.org> a écrit :Hi,
I am managing a situation where we often have a lot of lines on some main apps x2many fields (sale, picking, invoice, purchase..).
It's not really handy when we are in a range of 60-200 lines, I just discovered that I could permanently increase the "limit" attribute on the tree-view.
That would partially solve the problem, but in my opinion another part of the issue is that if you increase the "pager limit" to contain all lines, all the elements after the field will be pushed down in the view.
It would be nice to have a vertical scrolling so that we can let's say set a limit of 500 lines (so they will all be loaded in the same pager) then have a limited height and be able to vertically scroll through the lines.
Do you know any way to achieve this? Maybe someone already made a module for that?
Have a nice day,Francesco Ballerini_______________________________________________
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 - 10:46 - 21 Jun 2024
-
-
Technical Question: Restart Odoo process after res.partner model change
Hello Odoo contributors, I am developing, deploying and fixing Odoo for a while and there is one issue I haven't bothered enough to come up with a proper solution or strategy. The problem is simple: I have an Odoo instance running with a module that extends the res.partner model. The res.partner code of this module is updated with a new field. The Odoo server is restarted and exits with a "column does not exist" error. The same procedure works for modules that extend other models than res.partner or res.user. As I understand the res.partner (and other) tables are queried when the Odoo process starts. The SQL queries fail, because the model code does not match the database schema. The solution to the problem seems obvious, before starting the Odoo server with the new code you install module (odoo-bin -i ...). However, automating this step in a deployment pipeline is difficult as you don't know which module needs to be updated. Always updating the base module seems like an overkill. Do you know this problem? Have you solved this problem? I would be glad to hear from you. Regards, Janik Here is a guide to reproduce the issue with https://odoo.build/: 1. Init a new datbase and start the Odoo server: `task start db; task init-db; task start native` 2. Install the contacts module: `task install-module contacts` 3. Stop the Odoo process. 4. Add a new field to the res.partner code: `vi odoo/odoo/addons/base/models/res_partner.py` ```python xy = fields.Char() ``` 5. Start the Odoo server: `task start native` It fails with: ``` ... psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist LINE 1: ..."message_bounce", "res_partner"."name" AS "name", "res_partn... ``` ^ -- We are hiring: https://www.mint-system.ch/jobs Send application to: jobs@mint-system.ch CTO Mint System GmbH Tel: +41 44 244 7222
by Janik von Rotz - 05:22 - 20 Jun 2024-
Re: Technical Question: Restart Odoo process after res.partner model change
Hi Janik,
On 6/21/24 14:02, Janik von Rotz wrote:
A simple solution is probably a fixed list of modules that should always be updated (from the cli) after the code change and before restarting the Odoo container.
This is indeed the more crude solution that we generally use for our clients - either figure out by hand which modules to update if you're in a hurry, or just `-u base`.
But the two solutions mentioned are smarter in that sense because they figure out from the code change what to update.
Cheers
by Tom Blauwendraat - 02:31 - 21 Jun 2024 -
Re: Technical Question: Restart Odoo process after res.partner model change
Hi Pedro, Thanks for your reply. Yes exactly, access to res.partner/res.user is done before I can act. Updating the module with the cli works (but you have to know the module name). As I understand click-odoo-update works similar to module_auto_update, but can update all changed modules from a separate Odoo process. A simple solution is probably a fixed list of modules that should always be updated (from the cli) after the code change and before restarting the Odoo container. Regards, Janik On 6/21/24 11:52, Pedro M. Baeza wrote: > Maybe the problem is that you want to update from the UI, and in that > case, an access to res.partner/res.users is done before you can act. > You should do it in the command line with the -u argument (or > click-odoo-update), or with a parallel run (in Docker environments), > or similar. > > Regards. > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > -- We are hiring: https://www.mint-system.ch/jobs Send application to: jobs@mint-system.ch CTO Mint System GmbH Tel: +41 44 244 7222
by Janik von Rotz - 02:01 - 21 Jun 2024 -
Re: Technical Question: Restart Odoo process after res.partner model change
Maybe the problem is that you want to update from the UI, and in that case, an access to res.partner/res.users is done before you can act. You should do it in the command line with the -u argument (or click-odoo-update), or with a parallel run (in Docker environments), or similar.Regards.
by Pedro M. Baeza - 11:51 - 21 Jun 2024 -
Re: Technical Question: Restart Odoo process after res.partner model change
Do you define the database in the command with -d <database_name> beside the -u argument?I had some effects when the -d was missing.
Von: Janik von Rotz <notifications@odoo-community.org>
Gesendet: Friday, June 21, 2024 8:50:04 AM
An: Contributors <contributors@odoo-community.org>
Betreff: Re: Technical Question: Restart Odoo process after res.partner model changeACHTUNG! Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.
Hi Graeme,
there is no own code so there is no bug. I am pretty sure what I described is reproducible with any Odoo setup.
As I understand updating the database schema for a running Odoo process without restarting the process is simply not possible.
I assume Odoo has an internal state of the field defined in the module code. Only if the process is restarted the state is updated.
Regards,
Janik
On 6/20/24 22:02, Graeme Gellatly wrote:
Then that is a bug in your own code, or you have not also restarted another running odoo process with the old info. -u has worked forever.
On Fri, Jun 21, 2024 at 6:45 AM Janik von Rotz <notifications@odoo-community.org> wrote:
Hi Tom
Thanks for the reply.
I did another test with the same results.
The Odoo log tells that it updated the tables for the module, but it didn't.
Cheers,
Janik
Init Odoo database with the required modules:
```
task start
docker-odoo-install -d 16.0 -i partner_fax,contacts,module_auto_update
```
Then clicked *Apps > Auto-Upgrade Modules*.
Getting the hash for `partner_fax`: `d1db56b45a4c5baa9a6cb0c571c37b0c394d8840`
Then changing the file:
```
cd oca/partner-contact
vi partner_fax/models/res_partner.py
```
By adding:
```python
xy = fields.Char()
```
Then clicked *Apps > Auto-Upgrade Modules*.
The Odoo log:
```
2024-06-20 18:32:03,665 1 INFO 16.0 odoo.modules.registry: module partner_fax: creating or updating database tables
```
Getting the hash for `partner_fax`: `b8236a3734e752fa62b669674afaa1db750f031d`
When doing a restart.
```
task restart
```
I still get this message:
```
psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
LINE 1: ...e" AS "write_date", "res_partner"."fax" AS "fax", "res_partn...
^
```
The issue can be resolved by installing the module:
```
docker-odoo-install -d 16.0 -i partner_fax
```
On 6/20/24 19:57, Tom Blauwendraat wrote:
Hi Janik
-i is wrong anyway, it installs, -u is what you need
I dont know why the field update does not trigger, it should - did you restart odoo beforehand?
20 jun. 2024 18:58:18 Janik von Rotz <notifications@odoo-community.org>:
Hi Tom
I tested this module and like it! However, it seems its only doing an update and not an install, which does not update the database schema.
Cheers, Janik
Here is how I tested the module with https://odoo.build/:
Init Odoo database with the required modules.
```
task start
docker-odoo-install -d 16.0 -i partner_fax,contacts,module_auto_update
```
Checking the hash: `"partner_fax": "b8236a3734e752fa62b669674afaa1db750f031d"`
Then changing a module file.
```
vi oca/partner-contact/partner_fax/models/res_partner.py
```
Adding:
```python
xy = fields.Char()
```
Then clicked *Apps > Auto-Upgrade Modules*.When doing a restart.
```
task restart
```
I still get this message:
```
psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist
LINE 1: ...e" AS "write_date", "res_partner"."fax" AS "fax", "res_partn...
^
```Resolving the issue by installing the module:
```
docker-odoo-install -d 16.0 -i partner_fax
```
On 6/20/24 17:42, Tom Blauwendraat wrote:
module_auto_update
20 jun. 2024 17:22:17 Janik von Rotz <notifications@odoo-community.org>:
Hello Odoo contributors, I am developing, deploying and fixing Odoo for a while and there is one issue I haven't bothered enough to come up with a proper solution or strategy. The problem is simple: I have an Odoo instance running with a module that extends the res.partner model. The res.partner code of this module is updated with a new field. The Odoo server is restarted and exits with a "column does not exist" error. The same procedure works for modules that extend other models than res.partner or res.user. As I understand the res.partner (and other) tables are queried when the Odoo process starts. The SQL queries fail, because the model code does not match the database schema. The solution to the problem seems obvious, before starting the Odoo server with the new code you install module (odoo-bin -i ...). However, automating this step in a deployment pipeline is difficult as you don't know which module needs to be updated. Always updating the base module seems like an overkill. Do you know this problem? Have you solved this problem? I would be glad to hear from you. Regards, Janik Here is a guide to reproduce the issue with https://odoo.build/: 1. Init a new datbase and start the Odoo server: `task start db; task init-db; task start native` 2. Install the contacts module: `task install-module contacts` 3. Stop the Odoo process. 4. Add a new field to the res.partner code: `vi odoo/odoo/addons/base/models/res_partner.py` ```python xy = fields.Char() ``` 5. Start the Odoo server: `task start native` It fails with: ``` ... psycopg2.errors.UndefinedColumn: column res_partner.xy does not exist LINE 1: ..."message_bounce", "res_partner"."name" AS "name", "res_partn... ``` ^ -- We are hiring: https://www.mint-system.ch/jobs Send application to: jobs@mint-system.ch CTO Mint System GmbH Tel: +41 44 244 7222
_______________________________________________
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
-- We are hiring: https://www.mint-system.ch/jobs Send application to: jobs@mint-system.ch CTO Mint System GmbH Tel: +41 44 244 7222
_______________________________________________
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
-- We are hiring: https://www.mint-system.ch/jobs Send application to: jobs@mint-system.ch CTO Mint System GmbH Tel: +41 44 244 7222
_______________________________________________
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
-- We are hiring: https://www.mint-system.ch/jobs Send application to: jobs@mint-system.ch CTO Mint System GmbH Tel: +41 44 244 7222
_______________________________________________
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 - 10:32 - 21 Jun 2024 -
Re: Technical Question: Restart Odoo process after res.partner model change
Hi Pedro, I did not want to offend anyone and have also tried to do justice to your expertise. Reading your answer tells me I asked the wrong questions. Regads, Janik On 6/21/24 09:03, Pedro M. Baeza wrote: > Janik, I'm afraid your deployment process is not correct, not an Odo > bug, as both updating or installing changes DB schema, but obviously > the Python code should be reloaded for this to happen (aka, the > service should be restarted). Questioning an expert like Graeme with a > lot of years of experience in such basic things is not a good practice > IMO. > > Regards. > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > -- We are hiring: https://www.mint-system.ch/jobs Send application to: jobs@mint-system.ch CTO Mint System GmbH Tel: +41 44 244 7222
by Janik von Rotz - 09:47 - 21 Jun 2024
-
-
16.0 translations
Hi guys,
We do have a customer which would like to translate a term used in a python method in a odoo module.
I know translations have changed a lot in 16.0, that and now field translations are stored as jsonb values.
To give you more context, here's a bit of code https://github.com/odoo/odoo/blob/16.0/addons/l10n_din5008_sale/models/sale.py#L12-L32
Our customer isn't happy with the german translation of "Salesperson", which is "Vertriebsmitarbeiter", and would like "Kundenberater" instead.
In the previous versions of odoo, it was possible to create a `l10n_extra` folder, and drop a new translation for the term, and that's it.
Now it's not possible anymore, and I'm looking for ways of doing it.
For instance, if some python code is raising an exception with some translated text that you're unhappy with, you cannot change it.
I noticed there was a few issues on this matter on github.com/odoo/odoo- https://github.com/odoo/odoo/issues/157815
- https://github.com/odoo/odoo/issues/168098
- https://github.com/odoo/odoo/issues/164736
- https://github.com/odoo/odoo/issues/124124
- ...
I'm guessing that we aren't near close of having a solution from Odoo, and was wondering if there was anything in OCA about this?
Thanks!
---
Matthieu Méquignon
by Matthieu Méquignon - 04:04 - 20 Jun 2024-
Re: 16.0 translations
Exactly. Alternatively it can be done in the language settings by updating and overwriting the language.
Best regards
ChristianVon: "Holger Brunn" <notifications@odoo-community.org>
An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
Gesendet: Donnerstag, 20. Juni 2024 23:42:15
Betreff: Re: 16.0 translationsthe i18n_extra mechanism still works exactly as it used to. That includes that translations are only overwritten on the first init of a module, or with -u $module --i18n-overwrite. -- Your partner for the hard Odoo problems https://hunki-enterprises.com_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Christian Zöllner - 09:25 - 21 Jun 2024 -
Re: 16.0 translations
Our customer isn't happy with the german translation of "Salesperson", which is "Vertriebsmitarbeiter", and would like "Kundenberater" instead.
Hi Matthieu, in case this helps, if your pain point is about the QWeb report: https://github.com/OCA/server-ux/tree/16.0/template_content_swapperOn Fri, Jun 21, 2024 at 6:42 AM Holger Brunn <notifications@odoo-community.org> wrote:the i18n_extra mechanism still works exactly as it used to. That includes that translations are only overwritten on the first init of a module, or with -u $module --i18n-overwrite. -- Your partner for the hard Odoo problems https://hunki-enterprises.com_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Yoshi Tashiro. - 02:56 - 21 Jun 2024 -
Re: 16.0 translations
the i18n_extra mechanism still works exactly as it used to. That includes that translations are only overwritten on the first init of a module, or with -u $module --i18n-overwrite. -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 11:41 - 20 Jun 2024 -
RE: 16.0 translations
Hi,
I total share your pain with the German translation in that point and also on “Credit Note” where we need to replace “Gutschrift” with “Rechnungskorrektur”.
For these two values I’ve solved it this way, because I could not find another solution. It removes the original value and adds a new.
You need to translate “Salesperson” in your custom module the same as it is translated in Odoo, and then add a new key/value pair to the collection.
from odoo import _, models
class SaleOrder(models.Model):
_inherit = "sale.order"
def _compute_l10n_din5008_template_data(self):
result = super()._compute_l10n_din5008_template_data()
for record in self:
values = record.l10n_din5008_template_data
# replace salesperson from list
sales_person_label = _("Salesperson")
values = [x for x in values if x[0] != sales_person_label]
if record.user_id:
values.append((_("Contact Person"), record.user_id.name))
record.l10n_din5008_template_data = values
return result
I know this is a very poor solution and would be happy for other, more generic suggestions.
Best Regards,
Christopher
From: Matthieu Mequignon <notifications@odoo-community.org>
Sent: Donnerstag, 20. Juni 2024 16:11
To: Contributors <contributors@odoo-community.org>
Subject: 16.0 translationsHi guys,
We do have a customer which would like to translate a term used in a python method in a odoo module.
I know translations have changed a lot in 16.0, that and now field translations are stored as jsonb values.
To give you more context, here's a bit of code https://github.com/odoo/odoo/blob/16.0/addons/l10n_din5008_sale/models/sale.py#L12-L32
Our customer isn't happy with the german translation of "Salesperson", which is "Vertriebsmitarbeiter", and would like "Kundenberater" instead.
In the previous versions of odoo, it was possible to create a `l10n_extra` folder, and drop a new translation for the term, and that's it.
Now it's not possible anymore, and I'm looking for ways of doing it.
For instance, if some python code is raising an exception with some translated text that you're unhappy with, you cannot change it.
I noticed there was a few issues on this matter on github.com/odoo/odoo- https://github.com/odoo/odoo/issues/157815
- https://github.com/odoo/odoo/issues/168098
- https://github.com/odoo/odoo/issues/164736
- https://github.com/odoo/odoo/issues/124124
- ...
I'm guessing that we aren't near close of having a solution from Odoo, and was wondering if there was anything in OCA about this?
Thanks!---
Matthieu Méquignon_______________________________________________
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 - 10:26 - 20 Jun 2024
-
Create New Sale Order from Picking Backorder
Hello, I need exactly this modulebut for Odoo version 14. Do we have something similar?Regards,Francesco Ballerini
by Francesco Ballerini - 11:03 - 20 Jun 2024 -
OCA Mailing-list and Weblate rate limit issue
Hello everyone,First, this message has already been posted on transbot@odoo-community.org but after looking on https://odoo-community.org/groups, it looks like there is only 1 mailing-list now ? all others are dropped ?Secondly, did you know that you can login on https://odoo-community.org with admin/admin ?So I'm reposting here my message:I started working on translating some modules in the maintenance repository.But now I'm stuck (10 min cooldown ) when I want to add a new FR translation with this error:Your request was rejected because you have performed too many operations recently. You have been signed out, please sign in and try again later.
Technically, only 8 translations have been created this morning (17 jun 2023) before this auto-signout appears, and it looks like it is related to this rate limits:I can create 2 translations every 5 minutes ... that's too long but the lockout period (10 minutes) is worse because it looks like it is reset after each attempt ...Could you decrease this rate (RATELIMIT_LANGUAGE_ATTEMPTS) to the minimum or at least 1 minute ? because this step is recurrent and it is really frustrating to be locked out when so many modules needs translating for a few wordsThank you,
--
Yann PAPOUIN
Ingénieur R&D





WWW.DECGROUPE.COM
02 43 21 65 50 poste 51
02 43 39 30 78 
ypa@decgroupe.com
3 r Champ du Verger
72700 ALLONNES
by Yann Papouin - 11:14 - 18 Jun 2024-
Re: OCA Mailing-list and Weblate rate limit issue
--On Tue, Jun 18, 2024 at 11:14 AM Yann Papouin <notifications@odoo-community.org> wrote:Secondly, did you know that you can login on https://odoo-community.org with admin/admin ?I've checked. Some fun boy registered a spam user as "admin/admin" but is NOT the admin user of our instance (which has a different login). I deleted it.Thanks for reporting!Just one recommendation: next time, please, report possible security issue via security@odoo-community.orgBestsSimone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
by Simone Orsi - 09:06 - 27 Jun 2024 -
Re: OCA Mailing-list and Weblate rate limit issue
Hello Yann,transbot@odoo-community.org is the correct email for OCA translation support. It's not a mailing list, though.I answered there.Best regards,-StéphaneOn Tue, Jun 18, 2024 at 1:55 PM Jakob Krabbe <notifications@odoo-community.org> wrote:Hello! To solve this, the same is for me with Swedish... press BACK in your browser and reload the page and do the same again and then it works. I don't remember the exact procedure, it was a while ago, but do some clicking to solve the error and to continue where you left off. > > *Your request was rejected because you have performed too many > operations recently. You have been signed out, please sign in and try > again later. * > > -- Med vänlig hälsning / Best regards/ 顺祝商祺, Jakob Krabbe VERTEL AB | Jakob Krabbe | jakob.krabbe@vertel.se +46 (0)13 99 19 480 | +46 (0) 709 24 54 75 | vertel.se
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Stéphane Bidoul - 11:31 - 25 Jun 2024 -
Re: OCA Mailing-list and Weblate rate limit issue
Hello! To solve this, the same is for me with Swedish... press BACK in your browser and reload the page and do the same again and then it works. I don't remember the exact procedure, it was a while ago, but do some clicking to solve the error and to continue where you left off. > > *Your request was rejected because you have performed too many > operations recently. You have been signed out, please sign in and try > again later. * > > -- Med vänlig hälsning / Best regards/ 顺祝商祺, Jakob Krabbe VERTEL AB | Jakob Krabbe | jakob.krabbe@vertel.se +46 (0)13 99 19 480 | +46 (0) 709 24 54 75 | vertel.se
by Jakob Krabbe - 01:54 - 18 Jun 2024
-
-
OCA apps lift to 17.0
Hi!I would like to know if you are planning on lifting below apps to 17.0.I have a customer that is using them and they will upgrade to 17.0 very soon. So I need to know if these apps will be lifted by OCA or not. Thanks.stock_move_change_source_locationproduct_net_weight
product_pricelist_simulation
product_pricelist_simulation_marginaccount_statement_import_camtaccount_statement_import_camt54
stock_move_locationcrm_phonecallVänliga hälsningar / Kind RegardsCathrine NiklassonPhone: +46 737146240
by Linserv Consulting AB - 09:08 - 18 Jun 2024-
Re: OCA apps lift to 17.0
What Frederik says, I usually explain it to our customers like this "The first partner with a paying migration customer pays for the upgrade".
So your customer can either fund it, or wait a bit with the upgrade until more of these modules are migrated by others.
Naturally everyone will be happy if, when you fund someone to do the migration, the upgraded module gets contributed back to OCA.
-Tom
On 6/18/24 09:52, Frederik Kramer wrote:
Hi Chathrine,
Generally spoken OCA or basically its contributors will work on migrating modules if there is a direct need to (by one of their customers) AND somebody (normally the customer) is willing to fund their work. Its generally perceived a good habit, to contribute
not only with code but also with funds and ideas, especially if one had a substantial benefit in the first place (by using what was already there in older versions). So what you may do as an well estabilshed Odoo Partner taking advantage of these modules, is contact the PSC for
each of the modules repositories and ask the primary contributors of the module if and how you may support them to prioritize the migration of the module.
Usually redirecting some of the funds of your customer to those contributors will naturally speed up the process enormously for the benefit of all parties.
I hope this helps
Best Frederik
Am 18.06.24 um 09:08 schrieb Cathrine Niklasson:
Hi!
I would like to know if you are planning on lifting below apps to 17.0.
I have a customer that is using them and they will upgrade to 17.0 very soon. So I need to know if these apps will be lifted by OCA or not. Thanks.
stock_move_change_source_locationproduct_net_weight
product_pricelist_simulation
product_pricelist_simulation_marginaccount_statement_import_camtaccount_statement_import_camt54
stock_move_locationcrm_phonecall
Vänliga hälsningar / Kind RegardsCathrine Niklasson
Phone: +46 737146240
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
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 - 11:00 - 18 Jun 2024 -
Re: OCA apps lift to 17.0
Hi Chathrine,
Generally spoken OCA or basically its contributors will work on migrating modules if there is a direct need to (by one of their customers) AND somebody (normally the customer) is willing to fund their work. Its generally perceived a good habit, to contribute
not only with code but also with funds and ideas, especially if one had a substantial benefit in the first place (by using what was already there in older versions). So what you may do as an well estabilshed Odoo Partner taking advantage of these modules, is contact the PSC for
each of the modules repositories and ask the primary contributors of the module if and how you may support them to prioritize the migration of the module.
Usually redirecting some of the funds of your customer to those contributors will naturally speed up the process enormously for the benefit of all parties.
I hope this helps
Best Frederik
Am 18.06.24 um 09:08 schrieb Cathrine Niklasson:
Hi!
I would like to know if you are planning on lifting below apps to 17.0.
I have a customer that is using them and they will upgrade to 17.0 very soon. So I need to know if these apps will be lifted by OCA or not. Thanks.
stock_move_change_source_locationproduct_net_weight
product_pricelist_simulation
product_pricelist_simulation_marginaccount_statement_import_camtaccount_statement_import_camt54
stock_move_locationcrm_phonecall
Vänliga hälsningar / Kind RegardsCathrine Niklasson
Phone: +46 737146240
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
by Frederik Kramer - 09:51 - 18 Jun 2024
-
-
One email address for sales, another for invoices
Hi,has anyone implemented a solution for the following use case:Customer1 should receive quotation/SO emails at purchases@customer1.com, and invoice emails at accounting@customer1.comI didn't find something for this on partner-contact or accountingThanks!
by Francesco Foresti - 03:26 - 17 Jun 2024-
Re: One email address for sales, another for invoices
Thank you!Years and years and I'm still confused about odoo contacts structure...FrancescoIl giorno lun 17 giu 2024 alle ore 15:42 Frederik Kramer <notifications@odoo-community.org> ha scritto:+1
Am 17.06.24 um 15:32 schrieb Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT:
Activate customer addresses in settings and define invoice contact for the customer with the appropriate details.
Von: Francesco Foresti <notifications@odoo-community.org>
Gesendet: Monday, June 17, 2024 3:27:28 PM
An: Contributors <contributors@odoo-community.org>
Betreff: One email address for sales, another for invoices
ACHTUNG! Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.
Hi,
has anyone implemented a solution for the following use case:
Customer1 should receive quotation/SO emails at purchases@customer1.com, and invoice emails at accounting@customer1.com
I didn't find something for this on partner-contact or accounting
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
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
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 Foresti - 04:16 - 17 Jun 2024 -
Re: One email address for sales, another for invoices
+1
Am 17.06.24 um 15:32 schrieb Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT:
Activate customer addresses in settings and define invoice contact for the customer with the appropriate details.
Von: Francesco Foresti <notifications@odoo-community.org>
Gesendet: Monday, June 17, 2024 3:27:28 PM
An: Contributors <contributors@odoo-community.org>
Betreff: One email address for sales, another for invoices
ACHTUNG! Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.
Hi,
has anyone implemented a solution for the following use case:
Customer1 should receive quotation/SO emails at purchases@customer1.com, and invoice emails at accounting@customer1.com
I didn't find something for this on partner-contact or accounting
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
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
by Frederik Kramer - 03:41 - 17 Jun 2024 -
Re: One email address for sales, another for invoices
Activate customer addresses in settings and define invoice contact for the customer with the appropriate details.
Von: Francesco Foresti <notifications@odoo-community.org>
Gesendet: Monday, June 17, 2024 3:27:28 PM
An: Contributors <contributors@odoo-community.org>
Betreff: One email address for sales, another for invoicesACHTUNG! Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.
Hi,
has anyone implemented a solution for the following use case:
Customer1 should receive quotation/SO emails at purchases@customer1.com, and invoice emails at accounting@customer1.com
I didn't find something for this on partner-contact or accounting
Thanks!
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Nils Coenen - 03:31 - 17 Jun 2024
-
-
Please share your thoughts on the use of `x_` prefix for custom fields in Odoo
Hello Odoo contributors,
I'd love to hear your opinion on whether or not one should consistently prefix custom fields and models with `x_`. While there are valid reasons to do so, this convention is either not general or often overlooked in the community. Please share your insights on ir ir when it is required and why it may be missing from some guidelines (e.g., https://www.odoo.com/documentation/17.0/contributing/development/coding_guidelines.html#). I'd really love discuss this topic to enhance our common understanding and best practices in the Odoo ecosystem. Thank you for sharing your opinions
Best regards,
Frederik
Hint: Daniel Reis for instance claims "The field name field entry must start with the
x_prefix. This is mandatory for models and fields created from the developer tools. Customizations made through addon modules don't have this limitation." in https://subscription.packtpub.com/book/business-and-other/9781800200067/2/ch02lvl1sec09/adding-a-custom-field-to-a-model and Odoo itself pretends "Custom model names must start withx_." in https://www.odoo.com/documentation/17.0/developer/reference/external_api.html but leaves the convention unaddressed in https://www.odoo.com/documentation/17.0/contributing/development/coding_guidelines.html#For whom it may concern: SAP is requiring similar prefixes since very early versions of its ABAP programming and costumization iterface https://help.sap.com/doc/saphelp_snc700_ehp01/7.0.1/en-US/c5/e4ade6453d11d189430000e829fbbd/content.htm?no_cache=true
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
by Frederik Kramer - 12:16 - 17 Jun 2024-
Re: Please share your thoughts on the use of `x_` prefix for custom fields in Odoo
Now we reach the veterans talk and remembering. Time flies lads !My two cents on this topic. I confirm what Daniel and Graeme said. The reason behind was to quickly find back the custom fields and models added by the interface and avoid searching in the code for the field and model definition.Anyway such modifications should be banned for the sake of the project and the mental health 😉Regards,HoussineLe mer. 19 juin 2024, 08:08, Graeme Gellatly <notifications@odoo-community.org> a écrit :On Wed, Jun 19, 2024 at 5:57 PM Graeme Gellatly <graeme@moahub.nz> wrote:Yes but it is still exactly the same case. A model or field that is not part of a module. There is zero technical difference between creating a field via RPC and via UI. Afterall the UI is just sending the same RPC calls to the server. It absolutely does not apply to community developed modules in any way whatsoever, and it is absolutely required for any field created outside of a module (such that it gets ignored rather than removed in certain operations, it is essentially treated as data). And yes it existed in v5, and it was a major feature. This was the times of OpenBravo taking primacy with their dynamic low code DDL java thing, and OpenERP had a precursor to Studio in it. They even had a website openerp.tv dedicated to tutorials on how to do it.On Wed, Jun 19, 2024 at 5:41 PM Frederik Kramer <notifications@odoo-community.org> wrote:Well, this is not the only instance of that magical x_ I came across this (at least if I remember well) already in times of OpenERP Version 5 or so. Here for instance it again seems to be more related to backend UI changes and some reasoning is also provided by Ray
https://www.odoo.com/forum/help-1/fixing-a-custom-field-and-database-implications-90794Am 18. Juni 2024 23:32:27 MESZ schrieb Graeme Gellatly <notifications@odoo-community.org>:I took a quick read and yes it is a misunderstanding of the documentation. If reading a specific section about creating custom models over RPC calls, do not try and apply it to module development in general. All the documentation is correct as is Daniel's statement. Just a misread.On Wed, Jun 19, 2024 at 9:19 AM Graeme Gellatly <graeme@moahub.nz> wrote:Before Odoo studio, there was another frontend editor, like way back in v5. But it is only for fields created through the UI, not modules. Never modules, it would be a nonsense. The only time you would use in a module is if it contained dynamic field creation, e.g. like studio, or you have some kind of variable dynamic model like say custom field service worksheets. I think this is simply a misunderstanding of the documentation.On Tue, Jun 18, 2024 at 12:16 AM Frederik Kramer <notifications@odoo-community.org> wrote:Thanks Pedro, thanks Christian and Francesco for your comments, i think the first appearance of that magical "x_" was long before Odoo Studio even existed but i do definitely agree that backend UI changes done with Odoo Studio (or earlier through Developer Tools and Plain BE functions) should be avoided in any production grade DB. However, technically forbid to use that "methods" is not all too simple (if the customer pretends to have certain rights on his landscape) or comes from an origin where nobody even told them ;-) To me it seems (i.e. would be my conclusion) that Odoo S.A. always wanted to have that "x_" prefix and the community mostly ignored it (if i remember well, i have occassionaly seen app store modules that followed this 'requirement'). Now what bothers me most is that Odoo S.A. isn't consistent either on the matter and obviously never forced to comply (would have been easily possible). So probably we we better follow the "wisdom of the crowd" altogether and continue to ignore that "magic convention". Best Frederik Am 17.06.24 um 13:43 schrieb Pedro M. Baeza: > IMO, that prefix must only apply to fields created through UI / Odoo > Studio, not on community modules. And if you have to maintain that DB, > I advise you to forbid both Odoo Studio and manual field creation. > > Regards. > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Dr.-Ing. Frederik Kramer
Geschäftsführer
initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.
Phone: +49 4181 13503-12
Fax: +49 4181 13503-10
Mobil: +49 179 3901819
Email: frederik.kramer@initos.com
Web: www.initos.com
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Houssine BAKKALI - 10:00 - 19 Jun 2024 -
Re: Please share your thoughts on the use of `x_` prefix for custom fields in Odoo
On Wed, Jun 19, 2024 at 5:57 PM Graeme Gellatly <graeme@moahub.nz> wrote:Yes but it is still exactly the same case. A model or field that is not part of a module. There is zero technical difference between creating a field via RPC and via UI. Afterall the UI is just sending the same RPC calls to the server. It absolutely does not apply to community developed modules in any way whatsoever, and it is absolutely required for any field created outside of a module (such that it gets ignored rather than removed in certain operations, it is essentially treated as data). And yes it existed in v5, and it was a major feature. This was the times of OpenBravo taking primacy with their dynamic low code DDL java thing, and OpenERP had a precursor to Studio in it. They even had a website openerp.tv dedicated to tutorials on how to do it.On Wed, Jun 19, 2024 at 5:41 PM Frederik Kramer <notifications@odoo-community.org> wrote:Well, this is not the only instance of that magical x_ I came across this (at least if I remember well) already in times of OpenERP Version 5 or so. Here for instance it again seems to be more related to backend UI changes and some reasoning is also provided by Ray
https://www.odoo.com/forum/help-1/fixing-a-custom-field-and-database-implications-90794Am 18. Juni 2024 23:32:27 MESZ schrieb Graeme Gellatly <notifications@odoo-community.org>:I took a quick read and yes it is a misunderstanding of the documentation. If reading a specific section about creating custom models over RPC calls, do not try and apply it to module development in general. All the documentation is correct as is Daniel's statement. Just a misread.On Wed, Jun 19, 2024 at 9:19 AM Graeme Gellatly <graeme@moahub.nz> wrote:Before Odoo studio, there was another frontend editor, like way back in v5. But it is only for fields created through the UI, not modules. Never modules, it would be a nonsense. The only time you would use in a module is if it contained dynamic field creation, e.g. like studio, or you have some kind of variable dynamic model like say custom field service worksheets. I think this is simply a misunderstanding of the documentation.On Tue, Jun 18, 2024 at 12:16 AM Frederik Kramer <notifications@odoo-community.org> wrote:Thanks Pedro, thanks Christian and Francesco for your comments, i think the first appearance of that magical "x_" was long before Odoo Studio even existed but i do definitely agree that backend UI changes done with Odoo Studio (or earlier through Developer Tools and Plain BE functions) should be avoided in any production grade DB. However, technically forbid to use that "methods" is not all too simple (if the customer pretends to have certain rights on his landscape) or comes from an origin where nobody even told them ;-) To me it seems (i.e. would be my conclusion) that Odoo S.A. always wanted to have that "x_" prefix and the community mostly ignored it (if i remember well, i have occassionaly seen app store modules that followed this 'requirement'). Now what bothers me most is that Odoo S.A. isn't consistent either on the matter and obviously never forced to comply (would have been easily possible). So probably we we better follow the "wisdom of the crowd" altogether and continue to ignore that "magic convention". Best Frederik Am 17.06.24 um 13:43 schrieb Pedro M. Baeza: > IMO, that prefix must only apply to fields created through UI / Odoo > Studio, not on community modules. And if you have to maintain that DB, > I advise you to forbid both Odoo Studio and manual field creation. > > Regards. > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Dr.-Ing. Frederik Kramer
Geschäftsführer
initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.
Phone: +49 4181 13503-12
Fax: +49 4181 13503-10
Mobil: +49 179 3901819
Email: frederik.kramer@initos.com
Web: www.initos.com
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by "Graeme Gellatly" <graeme@moahub.nz> - 08:08 - 19 Jun 2024 -
Re: Please share your thoughts on the use of `x_` prefix for custom fields in Odoo
Yes but it is still exactly the same case. A model or field that is not part of a module. There is zero technical difference between creating a field via RPC and via UI. Afterall the UI is just sending the same RPC calls to the server. It absolutely does not apply to community developed modules in any way whatsoever, and it is absolutely required for any field created outside of a module (such that it gets ignored rather than removed in certain operations, it is essentially treated as data). And yes it existed in v5, and it was a major feature. This was the times of OpenBravo taking primacy with their dynamic low code DDL java thing, and OpenERP had a precursor to Studio in it. They even had a website openerp.tv dedicated to tutorials on how to do it.On Wed, Jun 19, 2024 at 5:41 PM Frederik Kramer <notifications@odoo-community.org> wrote:Well, this is not the only instance of that magical x_ I came across this (at least if I remember well) already in times of OpenERP Version 5 or so. Here for instance it again seems to be more related to backend UI changes and some reasoning is also provided by Ray
https://www.odoo.com/forum/help-1/fixing-a-custom-field-and-database-implications-90794Am 18. Juni 2024 23:32:27 MESZ schrieb Graeme Gellatly <notifications@odoo-community.org>:I took a quick read and yes it is a misunderstanding of the documentation. If reading a specific section about creating custom models over RPC calls, do not try and apply it to module development in general. All the documentation is correct as is Daniel's statement. Just a misread.On Wed, Jun 19, 2024 at 9:19 AM Graeme Gellatly <graeme@moahub.nz> wrote:Before Odoo studio, there was another frontend editor, like way back in v5. But it is only for fields created through the UI, not modules. Never modules, it would be a nonsense. The only time you would use in a module is if it contained dynamic field creation, e.g. like studio, or you have some kind of variable dynamic model like say custom field service worksheets. I think this is simply a misunderstanding of the documentation.On Tue, Jun 18, 2024 at 12:16 AM Frederik Kramer <notifications@odoo-community.org> wrote:Thanks Pedro, thanks Christian and Francesco for your comments, i think the first appearance of that magical "x_" was long before Odoo Studio even existed but i do definitely agree that backend UI changes done with Odoo Studio (or earlier through Developer Tools and Plain BE functions) should be avoided in any production grade DB. However, technically forbid to use that "methods" is not all too simple (if the customer pretends to have certain rights on his landscape) or comes from an origin where nobody even told them ;-) To me it seems (i.e. would be my conclusion) that Odoo S.A. always wanted to have that "x_" prefix and the community mostly ignored it (if i remember well, i have occassionaly seen app store modules that followed this 'requirement'). Now what bothers me most is that Odoo S.A. isn't consistent either on the matter and obviously never forced to comply (would have been easily possible). So probably we we better follow the "wisdom of the crowd" altogether and continue to ignore that "magic convention". Best Frederik Am 17.06.24 um 13:43 schrieb Pedro M. Baeza: > IMO, that prefix must only apply to fields created through UI / Odoo > Studio, not on community modules. And if you have to maintain that DB, > I advise you to forbid both Odoo Studio and manual field creation. > > Regards. > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Dr.-Ing. Frederik Kramer
Geschäftsführer
initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.
Phone: +49 4181 13503-12
Fax: +49 4181 13503-10
Mobil: +49 179 3901819
Email: frederik.kramer@initos.com
Web: www.initos.com
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by "Graeme Gellatly" <graeme@moahub.nz> - 08:07 - 19 Jun 2024 -
Re: Please share your thoughts on the use of `x_` prefix for custom fields in Odoo
Well, this is not the only instance of that magical x_ I came across this (at least if I remember well) already in times of OpenERP Version 5 or so. Here for instance it again seems to be more related to backend UI changes and some reasoning is also provided by Ray
https://www.odoo.com/forum/help-1/fixing-a-custom-field-and-database-implications-90794Am 18. Juni 2024 23:32:27 MESZ schrieb Graeme Gellatly <notifications@odoo-community.org>:I took a quick read and yes it is a misunderstanding of the documentation. If reading a specific section about creating custom models over RPC calls, do not try and apply it to module development in general. All the documentation is correct as is Daniel's statement. Just a misread.On Wed, Jun 19, 2024 at 9:19 AM Graeme Gellatly <graeme@moahub.nz> wrote:Before Odoo studio, there was another frontend editor, like way back in v5. But it is only for fields created through the UI, not modules. Never modules, it would be a nonsense. The only time you would use in a module is if it contained dynamic field creation, e.g. like studio, or you have some kind of variable dynamic model like say custom field service worksheets. I think this is simply a misunderstanding of the documentation.On Tue, Jun 18, 2024 at 12:16 AM Frederik Kramer <notifications@odoo-community.org> wrote:Thanks Pedro, thanks Christian and Francesco for your comments, i think the first appearance of that magical "x_" was long before Odoo Studio even existed but i do definitely agree that backend UI changes done with Odoo Studio (or earlier through Developer Tools and Plain BE functions) should be avoided in any production grade DB. However, technically forbid to use that "methods" is not all too simple (if the customer pretends to have certain rights on his landscape) or comes from an origin where nobody even told them ;-) To me it seems (i.e. would be my conclusion) that Odoo S.A. always wanted to have that "x_" prefix and the community mostly ignored it (if i remember well, i have occassionaly seen app store modules that followed this 'requirement'). Now what bothers me most is that Odoo S.A. isn't consistent either on the matter and obviously never forced to comply (would have been easily possible). So probably we we better follow the "wisdom of the crowd" altogether and continue to ignore that "magic convention". Best Frederik Am 17.06.24 um 13:43 schrieb Pedro M. Baeza: > IMO, that prefix must only apply to fields created through UI / Odoo > Studio, not on community modules. And if you have to maintain that DB, > I advise you to forbid both Odoo Studio and manual field creation. > > Regards. > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Dr.-Ing. Frederik Kramer
Geschäftsführer
initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.
Phone: +49 4181 13503-12
Fax: +49 4181 13503-10
Mobil: +49 179 3901819
Email: frederik.kramer@initos.com
Web: www.initos.com
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155
by Frederik Kramer - 07:35 - 19 Jun 2024 -
Re: Please share your thoughts on the use of `x_` prefix for custom fields in Odoo
I took a quick read and yes it is a misunderstanding of the documentation. If reading a specific section about creating custom models over RPC calls, do not try and apply it to module development in general. All the documentation is correct as is Daniel's statement. Just a misread.On Wed, Jun 19, 2024 at 9:19 AM Graeme Gellatly <graeme@moahub.nz> wrote:Before Odoo studio, there was another frontend editor, like way back in v5. But it is only for fields created through the UI, not modules. Never modules, it would be a nonsense. The only time you would use in a module is if it contained dynamic field creation, e.g. like studio, or you have some kind of variable dynamic model like say custom field service worksheets. I think this is simply a misunderstanding of the documentation.On Tue, Jun 18, 2024 at 12:16 AM Frederik Kramer <notifications@odoo-community.org> wrote:Thanks Pedro, thanks Christian and Francesco for your comments, i think the first appearance of that magical "x_" was long before Odoo Studio even existed but i do definitely agree that backend UI changes done with Odoo Studio (or earlier through Developer Tools and Plain BE functions) should be avoided in any production grade DB. However, technically forbid to use that "methods" is not all too simple (if the customer pretends to have certain rights on his landscape) or comes from an origin where nobody even told them ;-) To me it seems (i.e. would be my conclusion) that Odoo S.A. always wanted to have that "x_" prefix and the community mostly ignored it (if i remember well, i have occassionaly seen app store modules that followed this 'requirement'). Now what bothers me most is that Odoo S.A. isn't consistent either on the matter and obviously never forced to comply (would have been easily possible). So probably we we better follow the "wisdom of the crowd" altogether and continue to ignore that "magic convention". Best Frederik Am 17.06.24 um 13:43 schrieb Pedro M. Baeza: > IMO, that prefix must only apply to fields created through UI / Odoo > Studio, not on community modules. And if you have to maintain that DB, > I advise you to forbid both Odoo Studio and manual field creation. > > Regards. > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by "Graeme Gellatly" <graeme@moahub.nz> - 11:31 - 18 Jun 2024
-
-
OCA Weblate, why the lack of speed?
Greetings! I've done plenty of translating for Odoo in Sweden. Modules and documentation for Odoo mainly in Transifex but also some for OCA, using Weblate. I like the tool Weblate. Sometimes it's more helpful than Transifex! But I've always wondered why it's so slow. I often get the "500 time out" -error and it's more frequently before lunch than after! Who's in charge? What's the plan, if any...? I assume others has experienced the same. I'm new to this e-mailing list and maybe this has been discussed recently? If so, my apology for highlighting the issue! regards, // jakob -- Med vänlig hälsning / Best regards/ 顺祝商祺, Jakob Krabbe VERTEL AB | Jakob Krabbe | jakob.krabbe@vertel.se +46 (0)13 99 19 480 | +46 (0) 709 24 54 75 | vertel.se
by Jakob Krabbe - 09:06 - 17 Jun 2024-
Re: OCA Weblate, why the lack of speed?
Thanks Stéphane for all your efforts and the clear feedback!Regards,Le mer. 26 juin 2024 à 11:22, Stéphane Bidoul <notifications@odoo-community.org> a écrit :Hi Pierre,Thanks a lot for proposing your help.I think it is (was) simply an issue with the 10 years old spinning disks being too slow for the kind of weblate workload we have.Now we have SSD and more RAM for caching so thing should be better much better.The next step now is indeed the Weblate 5 upgrade, for which Remy Cazenave has already proposed his support.You may want to get in touch with him to see if some collaboration makes sense.After that we'll see what can be done, as there are many possible avenues for improvements such as translation memories, approval workflow for communities who need it, rewriting the project and component creation scripts using the REST API (if they are still needed), etc.-sbiOn Wed, Jun 26, 2024 at 11:07 AM Pierre Verkest <notifications@odoo-community.org> wrote:> While the root cause is still unclear it still seems related to weblate.I don't really know weblate (only over a few translations I've done). However it's a python project and I would be very happy to help with performance issues topics, I guess the OCA weblate instance is probably quite an importante one.Are there already techies introspecting such issues or are you confident with new servers ? Do you need help to understand and fix the issue ?Le mar. 25 juin 2024 à 23:37, Stéphane Bidoul <notifications@odoo-community.org> a écrit :The performance issues on the OCA server have been acute again today.While the root cause is still unclear it still seems related to weblate.So I have had to take weblate down and started the move to the new machine.Thank you all for your patience.Best regards,On Sun, Jun 23, 2024 at 6:51 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:Hi everyone,Back from holidays, I indeed notice a lot of alerts and a very high load on our poor weblate instance that is already stretching our server past reasonable limits.As a short term measure, I have banned a couple of IP addresses that clearly abused the system.Now the good news is that I started configuring the new OCA server and we will progressively start moving the services to the new machine. This will also unblock the weblate upgrade to 5.x.I'll post here as this progresses, over the coming weeks and months.Best regards,On Thu, Jun 20, 2024 at 4:23 PM Frederik Kramer <notifications@odoo-community.org> wrote:Hi Jakob,
sorry you are right. I can share your pain today as i was also trying to interact with part of our infrastructure that was equally lacking reliability and peformance. However, i am pretty sure that we will soon (as in volountary soon) have solutions for these problems. In the meantime thank you for your willingsness to help
Best Frederik
Am 20.06.24 um 16:03 schrieb Jakob Krabbe:
Thank you for your reply! After a few days with Weblate and 504 Gateway Time-out, I'm now moving on with other tasks. I hope you or maybe Stephané could post a notice on this list when such upgrade has been made! regards, // jakob Den 2024-06-17 kl. 09:37, skrev Frederik Kramer: > Hi Jakob, > > afaik, OCA uses weblate because it doesn't just us as much as Transifex > charged us. If i am not mistaken we run Weblate ourselfes and if i > understood (Stephané Bidoul, who is the master of OCAs hardware > architecture) we are about to migrate on a more powerful hardware server > (also for that purpose). But Stephané can certainly be more precise on > that. So in the best case it should improve somewhen soon :-) > > Best and thanks for the question > > Frederik > > Am 17.06.24 um 09:07 schrieb Jakob Krabbe: >> Greetings! >> I've done plenty of translating for Odoo in Sweden. Modules and >> documentation for Odoo mainly in Transifex but also some for OCA, using >> Weblate. >> >> I like the tool Weblate. Sometimes it's more helpful than Transifex! >> >> But I've always wondered why it's so slow. I often get the "500 time >> out" -error and it's more frequently before lunch than after! >> >> Who's in charge? What's the plan, if any...? >> >> I assume others has experienced the same. I'm new to this e-mailing list >> and maybe this has been discussed recently? If so, my apology for >> highlighting the issue! >> >> regards, >> >> // jakob >> >> >> >> >> -- Med vänlig hälsning / Best regards/ 顺祝商祺, Jakob Krabbe VERTEL >> AB | Jakob Krabbe | jakob.krabbe@vertel.se >> <mailto:jakob.krabbe@vertel.se> +46 (0)13 99 19 480 | +46 (0) 709 24 >> 54 75 | vertel.se >> >> _______________________________________________ >> Mailing-List: https://odoo-community.org/groups/contributors-15 >> <https://odoo-community.org/groups/contributors-15> >> Post to: mailto:contributors@odoo-community.org >> <mailto:contributors@odoo-community.org> >> Unsubscribe: https://odoo-community.org/groups?unsubscribe >> <https://odoo-community.org/groups?unsubscribe> >> > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 > 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 > 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com <mailto:frederik.kramer@initos.com> > Internet:www.initos.com <http://www.initos.com> > > Geschäftsführung: > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke > > Sitz der Gesellschaft: Buchholz i.d.N. > Amtsgericht Tostedt, HRB 205226 > USt-IdNr.: DE815580155 > Steuer-Nr: 15/200/53247 > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > -- Med vänlig hälsning / Best regards/ 顺祝商祺, Jakob Krabbe VERTEL AB | Jakob Krabbe | jakob.krabbe@vertel.se +46 (0)13 99 19 480 | +46 (0) 709 24 54 75 | vertel.se
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
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
--Pierre_______________________________________________
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
--Pierre
by Pierre Verkest - 01:51 - 26 Jun 2024 -
Re: OCA Weblate, why the lack of speed?
Thanks Stéphane, it seems very fast!PS: remind the locked modules, as you know...Da "Stéphane Bidoul" notifications@odoo-community.orgA "Contributors" contributors@odoo-community.orgCcData Wed, 26 Jun 2024 07:57:41 -0000Oggetto Re: OCA Weblate, why the lack of speed?
And weblate is back online, on the new machine.Let me know of any issue.Happy translation!-sbiOn Tue, Jun 25, 2024 at 11:32 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:The performance issues on the OCA server have been acute again today.While the root cause is still unclear it still seems related to weblate.So I have had to take weblate down and started the move to the new machine.Thank you all for your patience.Best regards,Stefano Consolarowww.mymage.it
by Stefano Consolaro - 11:56 - 26 Jun 2024 -
Re: OCA Weblate, why the lack of speed?
Hi Pierre,Thanks a lot for proposing your help.I think it is (was) simply an issue with the 10 years old spinning disks being too slow for the kind of weblate workload we have.Now we have SSD and more RAM for caching so thing should be better much better.The next step now is indeed the Weblate 5 upgrade, for which Remy Cazenave has already proposed his support.You may want to get in touch with him to see if some collaboration makes sense.After that we'll see what can be done, as there are many possible avenues for improvements such as translation memories, approval workflow for communities who need it, rewriting the project and component creation scripts using the REST API (if they are still needed), etc.-sbiOn Wed, Jun 26, 2024 at 11:07 AM Pierre Verkest <notifications@odoo-community.org> wrote:> While the root cause is still unclear it still seems related to weblate.I don't really know weblate (only over a few translations I've done). However it's a python project and I would be very happy to help with performance issues topics, I guess the OCA weblate instance is probably quite an importante one.Are there already techies introspecting such issues or are you confident with new servers ? Do you need help to understand and fix the issue ?Le mar. 25 juin 2024 à 23:37, Stéphane Bidoul <notifications@odoo-community.org> a écrit :The performance issues on the OCA server have been acute again today.While the root cause is still unclear it still seems related to weblate.So I have had to take weblate down and started the move to the new machine.Thank you all for your patience.Best regards,On Sun, Jun 23, 2024 at 6:51 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:Hi everyone,Back from holidays, I indeed notice a lot of alerts and a very high load on our poor weblate instance that is already stretching our server past reasonable limits.As a short term measure, I have banned a couple of IP addresses that clearly abused the system.Now the good news is that I started configuring the new OCA server and we will progressively start moving the services to the new machine. This will also unblock the weblate upgrade to 5.x.I'll post here as this progresses, over the coming weeks and months.Best regards,On Thu, Jun 20, 2024 at 4:23 PM Frederik Kramer <notifications@odoo-community.org> wrote:Hi Jakob,
sorry you are right. I can share your pain today as i was also trying to interact with part of our infrastructure that was equally lacking reliability and peformance. However, i am pretty sure that we will soon (as in volountary soon) have solutions for these problems. In the meantime thank you for your willingsness to help
Best Frederik
Am 20.06.24 um 16:03 schrieb Jakob Krabbe:
Thank you for your reply! After a few days with Weblate and 504 Gateway Time-out, I'm now moving on with other tasks. I hope you or maybe Stephané could post a notice on this list when such upgrade has been made! regards, // jakob Den 2024-06-17 kl. 09:37, skrev Frederik Kramer: > Hi Jakob, > > afaik, OCA uses weblate because it doesn't just us as much as Transifex > charged us. If i am not mistaken we run Weblate ourselfes and if i > understood (Stephané Bidoul, who is the master of OCAs hardware > architecture) we are about to migrate on a more powerful hardware server > (also for that purpose). But Stephané can certainly be more precise on > that. So in the best case it should improve somewhen soon :-) > > Best and thanks for the question > > Frederik > > Am 17.06.24 um 09:07 schrieb Jakob Krabbe: >> Greetings! >> I've done plenty of translating for Odoo in Sweden. Modules and >> documentation for Odoo mainly in Transifex but also some for OCA, using >> Weblate. >> >> I like the tool Weblate. Sometimes it's more helpful than Transifex! >> >> But I've always wondered why it's so slow. I often get the "500 time >> out" -error and it's more frequently before lunch than after! >> >> Who's in charge? What's the plan, if any...? >> >> I assume others has experienced the same. I'm new to this e-mailing list >> and maybe this has been discussed recently? If so, my apology for >> highlighting the issue! >> >> regards, >> >> // jakob >> >> >> >> >> -- Med vänlig hälsning / Best regards/ 顺祝商祺, Jakob Krabbe VERTEL >> AB | Jakob Krabbe | jakob.krabbe@vertel.se >> <mailto:jakob.krabbe@vertel.se> +46 (0)13 99 19 480 | +46 (0) 709 24 >> 54 75 | vertel.se >> >> _______________________________________________ >> Mailing-List: https://odoo-community.org/groups/contributors-15 >> <https://odoo-community.org/groups/contributors-15> >> Post to: mailto:contributors@odoo-community.org >> <mailto:contributors@odoo-community.org> >> Unsubscribe: https://odoo-community.org/groups?unsubscribe >> <https://odoo-community.org/groups?unsubscribe> >> > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 > 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 > 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com <mailto:frederik.kramer@initos.com> > Internet:www.initos.com <http://www.initos.com> > > Geschäftsführung: > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke > > Sitz der Gesellschaft: Buchholz i.d.N. > Amtsgericht Tostedt, HRB 205226 > USt-IdNr.: DE815580155 > Steuer-Nr: 15/200/53247 > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > -- Med vänlig hälsning / Best regards/ 顺祝商祺, Jakob Krabbe VERTEL AB | Jakob Krabbe | jakob.krabbe@vertel.se +46 (0)13 99 19 480 | +46 (0) 709 24 54 75 | vertel.se
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
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
--Pierre_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Stéphane Bidoul - 11:21 - 26 Jun 2024 -
Re: OCA Weblate, why the lack of speed?
Indeed, very appreciated!Let's wait for v5.x to be implemented to suggest further possible improvements.Cheers!Il giorno mer 26 giu 2024 alle ore 11:02 Frederik Kramer <notifications@odoo-community.org> ha scritto:Great Stéphane,
thanks for this effort.
Best Frederik
Am 26.06.24 um 09:57 schrieb Stéphane Bidoul:
And weblate is back online, on the new machine.
Let me know of any issue.
Happy translation!
-sbi
On Tue, Jun 25, 2024 at 11:32 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
The performance issues on the OCA server have been acute again today.
While the root cause is still unclear it still seems related to weblate.
So I have had to take weblate down and started the move to the new machine.
Thank you all for your patience.
Best regards,
On Sun, Jun 23, 2024 at 6:51 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
Hi everyone,
Back from holidays, I indeed notice a lot of alerts and a very high load on our poor weblate instance that is already stretching our server past reasonable limits.
As a short term measure, I have banned a couple of IP addresses that clearly abused the system.
Now the good news is that I started configuring the new OCA server and we will progressively start moving the services to the new machine. This will also unblock the weblate upgrade to 5.x.
I'll post here as this progresses, over the coming weeks and months.
Best regards,
On Thu, Jun 20, 2024 at 4:23 PM Frederik Kramer <notifications@odoo-community.org> wrote:
Hi Jakob,
sorry you are right. I can share your pain today as i was also trying to interact with part of our infrastructure that was equally lacking reliability and peformance. However, i am pretty sure that we will soon (as in volountary soon) have solutions for these problems. In the meantime thank you for your willingsness to help
Best Frederik
Am 20.06.24 um 16:03 schrieb Jakob Krabbe:
Thank you for your reply! After a few days with Weblate and 504 Gateway Time-out, I'm now moving on with other tasks. I hope you or maybe Stephané could post a notice on this list when such upgrade has been made! regards, // jakob Den 2024-06-17 kl. 09:37, skrev Frederik Kramer: > Hi Jakob, > > afaik, OCA uses weblate because it doesn't just us as much as Transifex > charged us. If i am not mistaken we run Weblate ourselfes and if i > understood (Stephané Bidoul, who is the master of OCAs hardware > architecture) we are about to migrate on a more powerful hardware server > (also for that purpose). But Stephané can certainly be more precise on > that. So in the best case it should improve somewhen soon :-) > > Best and thanks for the question > > Frederik > > Am 17.06.24 um 09:07 schrieb Jakob Krabbe: >> Greetings! >> I've done plenty of translating for Odoo in Sweden. Modules and >> documentation for Odoo mainly in Transifex but also some for OCA, using >> Weblate. >> >> I like the tool Weblate. Sometimes it's more helpful than Transifex! >> >> But I've always wondered why it's so slow. I often get the "500 time >> out" -error and it's more frequently before lunch than after! >> >> Who's in charge? What's the plan, if any...? >> >> I assume others has experienced the same. I'm new to this e-mailing list >> and maybe this has been discussed recently? If so, my apology for >> highlighting the issue! >> >> regards, >> >> // jakob >> >> >> >> >> -- Med vänlig hälsning / Best regards/ 顺祝商祺, Jakob Krabbe VERTEL >> AB | Jakob Krabbe | jakob.krabbe@vertel.se >> <mailto:jakob.krabbe@vertel.se> +46 (0)13 99 19 480 | +46 (0) 709 24 >> 54 75 | vertel.se >> >> _______________________________________________ >> Mailing-List: https://odoo-community.org/groups/contributors-15 >> <https://odoo-community.org/groups/contributors-15> >> Post to: mailto:contributors@odoo-community.org >> <mailto:contributors@odoo-community.org> >> Unsubscribe: https://odoo-community.org/groups?unsubscribe >> <https://odoo-community.org/groups?unsubscribe> >> > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 > 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 > 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com <mailto:frederik.kramer@initos.com> > Internet:www.initos.com <http://www.initos.com> > > Geschäftsführung: > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke > > Sitz der Gesellschaft: Buchholz i.d.N. > Amtsgericht Tostedt, HRB 205226 > USt-IdNr.: DE815580155 > Steuer-Nr: 15/200/53247 > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > -- Med vänlig hälsning / Best regards/ 顺祝商祺, Jakob Krabbe VERTEL AB | Jakob Krabbe | jakob.krabbe@vertel.se +46 (0)13 99 19 480 | +46 (0) 709 24 54 75 | vertel.se
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
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 Foresti - 11:07 - 26 Jun 2024 -
Re: OCA Weblate, why the lack of speed?
> While the root cause is still unclear it still seems related to weblate.I don't really know weblate (only over a few translations I've done). However it's a python project and I would be very happy to help with performance issues topics, I guess the OCA weblate instance is probably quite an importante one.Are there already techies introspecting such issues or are you confident with new servers ? Do you need help to understand and fix the issue ?Le mar. 25 juin 2024 à 23:37, Stéphane Bidoul <notifications@odoo-community.org> a écrit :The performance issues on the OCA server have been acute again today.While the root cause is still unclear it still seems related to weblate.So I have had to take weblate down and started the move to the new machine.Thank you all for your patience.Best regards,On Sun, Jun 23, 2024 at 6:51 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:Hi everyone,Back from holidays, I indeed notice a lot of alerts and a very high load on our poor weblate instance that is already stretching our server past reasonable limits.As a short term measure, I have banned a couple of IP addresses that clearly abused the system.Now the good news is that I started configuring the new OCA server and we will progressively start moving the services to the new machine. This will also unblock the weblate upgrade to 5.x.I'll post here as this progresses, over the coming weeks and months.Best regards,On Thu, Jun 20, 2024 at 4:23 PM Frederik Kramer <notifications@odoo-community.org> wrote:Hi Jakob,
sorry you are right. I can share your pain today as i was also trying to interact with part of our infrastructure that was equally lacking reliability and peformance. However, i am pretty sure that we will soon (as in volountary soon) have solutions for these problems. In the meantime thank you for your willingsness to help
Best Frederik
Am 20.06.24 um 16:03 schrieb Jakob Krabbe:
Thank you for your reply! After a few days with Weblate and 504 Gateway Time-out, I'm now moving on with other tasks. I hope you or maybe Stephané could post a notice on this list when such upgrade has been made! regards, // jakob Den 2024-06-17 kl. 09:37, skrev Frederik Kramer: > Hi Jakob, > > afaik, OCA uses weblate because it doesn't just us as much as Transifex > charged us. If i am not mistaken we run Weblate ourselfes and if i > understood (Stephané Bidoul, who is the master of OCAs hardware > architecture) we are about to migrate on a more powerful hardware server > (also for that purpose). But Stephané can certainly be more precise on > that. So in the best case it should improve somewhen soon :-) > > Best and thanks for the question > > Frederik > > Am 17.06.24 um 09:07 schrieb Jakob Krabbe: >> Greetings! >> I've done plenty of translating for Odoo in Sweden. Modules and >> documentation for Odoo mainly in Transifex but also some for OCA, using >> Weblate. >> >> I like the tool Weblate. Sometimes it's more helpful than Transifex! >> >> But I've always wondered why it's so slow. I often get the "500 time >> out" -error and it's more frequently before lunch than after! >> >> Who's in charge? What's the plan, if any...? >> >> I assume others has experienced the same. I'm new to this e-mailing list >> and maybe this has been discussed recently? If so, my apology for >> highlighting the issue! >> >> regards, >> >> // jakob >> >> >> >> >> -- Med vänlig hälsning / Best regards/ 顺祝商祺, Jakob Krabbe VERTEL >> AB | Jakob Krabbe | jakob.krabbe@vertel.se >> <mailto:jakob.krabbe@vertel.se> +46 (0)13 99 19 480 | +46 (0) 709 24 >> 54 75 | vertel.se >> >> _______________________________________________ >> Mailing-List: https://odoo-community.org/groups/contributors-15 >> <https://odoo-community.org/groups/contributors-15> >> Post to: mailto:contributors@odoo-community.org >> <mailto:contributors@odoo-community.org> >> Unsubscribe: https://odoo-community.org/groups?unsubscribe >> <https://odoo-community.org/groups?unsubscribe> >> > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 > 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 > 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com <mailto:frederik.kramer@initos.com> > Internet:www.initos.com <http://www.initos.com> > > Geschäftsführung: > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke > > Sitz der Gesellschaft: Buchholz i.d.N. > Amtsgericht Tostedt, HRB 205226 > USt-IdNr.: DE815580155 > Steuer-Nr: 15/200/53247 > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > -- Med vänlig hälsning / Best regards/ 顺祝商祺, Jakob Krabbe VERTEL AB | Jakob Krabbe | jakob.krabbe@vertel.se +46 (0)13 99 19 480 | +46 (0) 709 24 54 75 | vertel.se
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
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
--Pierre
by Pierre Verkest - 11:06 - 26 Jun 2024
-
-
dms not published at apps.odoo.com
Greetings! In a project, we depend on an OCA module, dms https://github.com/OCA/dms/tree/14.0 When posting our project, we keep getting errors and we suspect that the unpublished OCA project dms is the reason! https://apps.odoo.com/apps/modules/browse?series=14.0&price=Free&search=dms What's the procedure!? Who's in charge!? Would it be possible to publish? // jakob -- Med vänlig hälsning / Best regards/ 顺祝商祺, Jakob Krabbe VERTEL AB | Jakob Krabbe | jakob.krabbe@vertel.se +46 (0)13 99 19 480 | +46 (0) 709 24 54 75 | vertel.se
by Jakob Krabbe - 02:41 - 14 Jun 2024-
Re: dms not published at apps.odoo.com
Hello Jacob,
I can try to help.
I think the problem is the App Sotre inability to deal with modules than moved between repos:
Transcript:
ssh://git@github.com/OCA/dms.git#17.0
Edit Scan Draft
No module found in repository ssh://git@github.com/OCA/dms.git#17.0.
Each module needs to be in a separate folder at the root of the repository, even if there is only one module.
If you have all the files of your module at the root of your repository, you need to create a new folder with the name of your module and move all the files in it.
ssh://git@github.com/OCA/dms.git#16.0
Edit Scan Active
Module dms already exists for another serie. Please select a free module name or use the right user account.
dms_storage: unmet dependency dms for series 16.0. Dependency might be invalid.
dms_user_role: unmet dependency dms for series 16.0. Dependency might be invalid.
dms_auto_classification: unmet dependency dms for series 16.0. Dependency might be invalid.
ssh://git@github.com/OCA/dms.git#15.0
Edit Scan Active
Module dms already exists for another serie. Please select a free module name or use the right user account.
dms_field: unmet dependency dms for series 15.0. Dependency might be invalid.
hr_dms_field: unmet dependency dms_field for series 15.0. Dependency might be invalid.
dms_user_role: unmet dependency dms for series 15.0. Dependency might be invalid.
dms_field_auto_classification is updated before its dependency dms_auto_classification. Throw back to the end of the queue.
dms_auto_classification: unmet dependency dms for series 15.0. Dependency might be invalid.
dms_attachment_link: unmet dependency dms for series 15.0. Dependency might be invalid.
On 14/06/2024 13:42, Jakob Krabbe wrote:
Greetings! In a project, we depend on an OCA module, dms https://github.com/OCA/dms/tree/14.0 When posting our project, we keep getting errors and we suspect that the unpublished OCA project dms is the reason! https://apps.odoo.com/apps/modules/browse?series=14.0&price=Free&search=dms What's the procedure!? Who's in charge!? Would it be possible to publish? // jakob -- Med vänlig hälsning / Best regards/ 顺祝商祺, Jakob Krabbe VERTEL AB | Jakob Krabbe | jakob.krabbe@vertel.se +46 (0)13 99 19 480 | +46 (0) 709 24 54 75 | vertel.se
_______________________________________________
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 PARTNERMeet with me.
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais
by Daniel Reis - 03:06 - 14 Jun 2024
-
-
apologies for mass PR creation
Hello everyone, I asked yesterday Vincent to fix the name of Camptocamp in the manifest of the OCA addons, without realizing the impact this would have on the CI. We are sorry for the disruption caused, and I should have checked before acting about the proper way to do this. Please accept our humble apologies. Now if you have a recommendation on how to deal with the update in the proper way, we will be happy to get your feedback. Kind regards, -- Alexandre Fayolle
by Alexandre Fayolle - 12:21 - 14 Jun 2024-
Re: apologies for mass PR creation
Thanks for the apologies. I think this kind of massive changes that has nothing to do with the community and that involves a lot of repositories, should be planned with the community (like now you are doing with this message).Following that, anything done massively should have a pilot test to check that everything is OK instead of blindly performing 100 PRs. The commit message was not following the conventions, and that meant to double the number of pipelines to execute. I know this is not something that costs us directly (apart from a delay in all the real contributions checks), but we should also see for the environment not wasting CPU resources.Well, I don't want to dig more into something that has no remedy. Just for future actions. Now, a less impacting way to do this is as some proposals:- To be changed only for newer branches or when an update is done, like ForgeFlow did to pass from Eficent.- Do it progressively.- Do it directly for not having 3 checks: the PR one + the ocabot one + the merge one.And I add another one: you can put `[ci skip]` at the end of the commit message for avoiding the check at all, but this only serves if you do directly the write or merge the PR without ocabot.Regards.
by Pedro M. Baeza - 01:51 - 14 Jun 2024 -
Re: apologies for mass PR creation
We can possibly find someone. Still, it would be nice to avoid triggering a full CI chain of all the affected branches. I'm not sure if there is a way to tell the gihub actions to skip all or parts of the checks? Alexandre On 14/06/2024 13:07, Alexey Pelykh wrote: > IMHO, there's no other way to do that unless someone with write access > to the repos will exceptionally commit/merge those changes from local repo > > Thus maybe just balancing a-repo-a-day?
by Alexandre Fayolle - 01:25 - 14 Jun 2024 -
Re: apologies for mass PR creation
We can possibly find someone. Still, it would be nice to avoid triggering a full CI chain of all the affected branches. I'm not sure if there is a way to tell the gihub actions to skip all or parts of the checks? Alexandre On 14/06/2024 13:07, Alexey Pelykh wrote: > IMHO, there's no other way to do that unless someone with write access > to the repos will exceptionally commit/merge those changes from local repo > > Thus maybe just balancing a-repo-a-day? > >> On 14 Jun 2024, at 12:47, Vincent Van Rossem >> <notifications@odoo-community.org> wrote: >> >> Hello dear Community and Contributors, >> >> My apologies for mass creating PRs and for wasting resources. >> >> Kind regards, >> >> Vincent >> >> On Fri, Jun 14, 2024 at 12:22 PM Alexandre Fayolle >> <notifications@odoo-community.org >> <mailto:notifications@odoo-community.org>> wrote: >> >> Hello everyone, >> >> I asked yesterday Vincent to fix the name of Camptocamp in the manifest >> of the OCA addons, without realizing the impact this would have on the CI. >> >> We are sorry for the disruption caused, and I should have checked before >> acting about the proper way to do this. Please accept our humble apologies. >> >> Now if you have a recommendation on how to deal with the update in the >> proper way, we will be happy to get your feedback. >> >> Kind regards, >> >> -- Alexandre Fayolle >> >> _______________________________________________ >> Mailing-List: https://odoo-community.org/groups/contributors-15 >> <https://odoo-community.org/groups/contributors-15> >> Post to: mailto:contributors@odoo-community.org >> <mailto:contributors@odoo-community.org> >> Unsubscribe: https://odoo-community.org/groups?unsubscribe >> <https://odoo-community.org/groups?unsubscribe> >> >> _______________________________________________ >> Mailing-List: https://odoo-community.org/groups/contributors-15 >> <https://odoo-community.org/groups/contributors-15> >> Post to: mailto:contributors@odoo-community.org >> Unsubscribe: https://odoo-community.org/groups?unsubscribe >> <https://odoo-community.org/groups?unsubscribe> >> > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
by Alexandre Fayolle - 01:25 - 14 Jun 2024 -
Re: apologies for mass PR creation
Hi,That reflects the amount of work you did 'til now :-)I would say, at that time, code was done by 'Camptocamp SA'. So, it should not be changed before a new module update. I think the approach used by Forgeflow. You can have a talk with Jordi or Lois.My two centsLe ven. 14 juin 2024, 13:07, Alexey Pelykh <notifications@odoo-community.org> a écrit :IMHO, there's no other way to do that unless someone with write access to the repos will exceptionally commit/merge those changes from local repo
Thus maybe just balancing a-repo-a-day?On 14 Jun 2024, at 12:47, Vincent Van Rossem <notifications@odoo-community.org> wrote:Hello dear Community and Contributors,My apologies for mass creating PRs and for wasting resources.Kind regards,VincentOn Fri, Jun 14, 2024 at 12:22 PM Alexandre Fayolle <notifications@odoo-community.org> wrote:Hello everyone, I asked yesterday Vincent to fix the name of Camptocamp in the manifest of the OCA addons, without realizing the impact this would have on the CI. We are sorry for the disruption caused, and I should have checked before acting about the proper way to do this. Please accept our humble apologies. Now if you have a recommendation on how to deal with the update in the proper way, we will be happy to get your feedback. Kind regards, -- Alexandre Fayolle_______________________________________________
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 Denis Roussel - 01:25 - 14 Jun 2024 -
Re: apologies for mass PR creation
IMHO, there's no other way to do that unless someone with write access to the repos will exceptionally commit/merge those changes from local repo
Thus maybe just balancing a-repo-a-day?On 14 Jun 2024, at 12:47, Vincent Van Rossem <notifications@odoo-community.org> wrote:Hello dear Community and Contributors,My apologies for mass creating PRs and for wasting resources.Kind regards,VincentOn Fri, Jun 14, 2024 at 12:22 PM Alexandre Fayolle <notifications@odoo-community.org> wrote:Hello everyone, I asked yesterday Vincent to fix the name of Camptocamp in the manifest of the OCA addons, without realizing the impact this would have on the CI. We are sorry for the disruption caused, and I should have checked before acting about the proper way to do this. Please accept our humble apologies. Now if you have a recommendation on how to deal with the update in the proper way, we will be happy to get your feedback. Kind regards, -- Alexandre Fayolle_______________________________________________
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 Alexey Pelykh - 01:06 - 14 Jun 2024
-
-
Contributors Odoo community
Good afternoon,I am writing to the Association to estimate my income as an OCA collaborator, to participate in everything that the community demands and needs and can help us collaborate in this important collaborative project.Best regards from Seville (Spain)Jose Luis Baños
CEO I Senior Lean Service Consultan
by Jose Luis Baños - 06:50 - 13 Jun 2024-
Re: Contributors Odoo community
0.00On Fri, Jun 14, 2024 at 4:51 AM José Luis Baños <notifications@odoo-community.org> wrote:Good afternoon,I am writing to the Association to estimate my income as an OCA collaborator, to participate in everything that the community demands and needs and can help us collaborate in this important collaborative project.Best regards from Seville (Spain)Jose Luis Baños
CEO I Senior Lean Service Consultan_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by "Graeme Gellatly" <graeme@moahub.nz> - 06:17 - 14 Jun 2024
-
-
Collaborate with OCA
Good afternoon, I am writing to the Association to estimate my income as an OCA collaborator, to participate in everything that the community demands and needs and can help us collaborate in this important collaborative project. Best regards from Seville (Spain) Jose Luis Baños CEO I Senior Lean Service Consultan
by "Jose Baños Bellido" <jlbb1955@icloud.com> - 06:26 - 13 Jun 2024-
Colaborar con OCA
Good afternoon, I am writing to the Association to estimate my income as an OCA collaborator, to participate in everything that the community demands and needs and can help us collaborate in this important collaborative project. Best regards from Seville (Spain) Jose Luis Baños CEO I Senior Lean Service Consultan
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Jose Luis Baños - 06:55 - 13 Jun 2024
-
-
Medical vertical
G'day all, hope this week is treating all of you well! I wanted to check what's up with medical vertical repo - clearly it's abandoned and I guess there was a just reason to do that (as in, use X instead of Odoo). So whoever worked with medical domain - please chime in. Cheers, Alexey
by Alexey Pelykh - 06:16 - 12 Jun 2024-
Re: Medical vertical
Sure we all will contribute.First is always a search of a paying customer 😄Thanks and appreciated.Regards,Technology Services @ www.serpentcs.comBusiness Solutions @ www.serpentcs.inEnterprise Mobile Apps @ www.odooonline.comQuality Assurance @ www.odooqa.comSAP Hana @ www.prozone-tech.comPortal & DMS @ www.alfray.inOn Thu, 13 Jun 2024 at 1:05 AM, Jorge Elena Poblet <notifications@odoo-community.org> wrote:Hi all,
By chance, I have a couple of opportunities that might be interested in a vertical solution such as this.Hopefully, if they like the project, we might be able to contribute ...
Thanks Enric for the info!El 12/06/2024 20:15 Alexey Pelykh <notifications@odoo-community.org> escribió:
Hi Enric,
Super-useful, thanks! Another email on its way :)
Thanks again!
Alexey
On 12 Jun 2024, at 20:07, Enric Tobella Alomar <notifications@odoo-community.org> wrote:
Hi Alexey,
It was abandonded due to some License issues
Actually, OCA received a DMCA from github https://odoo-community.org/blog/news-updates-1/vertical-medical-75. After that, most collaborators left the repository.
From my side, I have been working on a completely new Medical Repo for Odoo that is under an OpenSource License (we started from scratch in order to avoid the License infringement), but not under OCA Umbrella (not too many contributors were interested). We are open to go back to OCA if there is interest. However, it does not fill all the gaps right now, because my customers didn't need all the parts of a complete HIS inside Odoo. Th. solution is quite clean and we are improving it.
If you are interested, you can contact me directly.
Kind regards,
El mié, 12 jun 2024 a las 19:32, Alexey Pelykh (<notifications@odoo-community.org>) escribió:
Hi Joe,
Closer to "why those who did the repo stopped doing the repo". Likely because Odoo didn't fit well as there are other open-source solutions like OpenEMR, OpenEHR etc.
Kind regards,Alexey
On 12 Jun 2024, at 19:27, Joerg Lorenz <notifications@odoo-community.org> wrote:
Hi Alexey,
are you looking for the ones who did the repo?
Or do you - because of requirement at hand - look to get an odoo based solution here?
Best, Joe
Von: "Alexey Pelykh" <notifications@odoo-community.org>
An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
Gesendet: Mittwoch, 12. Juni 2024 18:17:23
Betreff: Medical vertical
G'day all, hope this week is treating all of you well! I wanted to check what's up with medical vertical repo - clearly it's abandoned and I guess there was a just reason to do that (as in, use X instead of Odoo). So whoever worked with medical domain - please chime in. Cheers, Alexey
_______________________________________________
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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Jorge Elena Poblet
Founder & CEO
Personal Contact:
+34 822 179 267 /
+34 622 40 08 08+1 305-686-8151 / +1 561-403-4406
Global Offices:
Spain: Tenerife, and Gran Canaria, Canary Islands
United States: Miami, Florida and Katy, Texas
Follow Us:
Legal Advice
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Jay Vora - 09:42 - 12 Jun 2024 -
Re: Medical vertical
Hi all,
By chance, I have a couple of opportunities that might be interested in a vertical solution such as this.Hopefully, if they like the project, we might be able to contribute ...
Thanks Enric for the info!El 12/06/2024 20:15 Alexey Pelykh <notifications@odoo-community.org> escribió:
Hi Enric,
Super-useful, thanks! Another email on its way :)
Thanks again!
Alexey
On 12 Jun 2024, at 20:07, Enric Tobella Alomar <notifications@odoo-community.org> wrote:
Hi Alexey,
It was abandonded due to some License issues
Actually, OCA received a DMCA from github https://odoo-community.org/blog/news-updates-1/vertical-medical-75. After that, most collaborators left the repository.
From my side, I have been working on a completely new Medical Repo for Odoo that is under an OpenSource License (we started from scratch in order to avoid the License infringement), but not under OCA Umbrella (not too many contributors were interested). We are open to go back to OCA if there is interest. However, it does not fill all the gaps right now, because my customers didn't need all the parts of a complete HIS inside Odoo. Th. solution is quite clean and we are improving it.
If you are interested, you can contact me directly.
Kind regards,
El mié, 12 jun 2024 a las 19:32, Alexey Pelykh (<notifications@odoo-community.org>) escribió:
Hi Joe,
Closer to "why those who did the repo stopped doing the repo". Likely because Odoo didn't fit well as there are other open-source solutions like OpenEMR, OpenEHR etc.
Kind regards,Alexey
On 12 Jun 2024, at 19:27, Joerg Lorenz <notifications@odoo-community.org> wrote:
Hi Alexey,
are you looking for the ones who did the repo?
Or do you - because of requirement at hand - look to get an odoo based solution here?
Best, Joe
Von: "Alexey Pelykh" <notifications@odoo-community.org>
An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
Gesendet: Mittwoch, 12. Juni 2024 18:17:23
Betreff: Medical vertical
G'day all, hope this week is treating all of you well! I wanted to check what's up with medical vertical repo - clearly it's abandoned and I guess there was a just reason to do that (as in, use X instead of Odoo). So whoever worked with medical domain - please chime in. Cheers, Alexey
_______________________________________________
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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Jorge Elena Poblet
Founder & CEO
Personal Contact:
+34 822 179 267 /
+34 622 40 08 08+1 305-686-8151 / +1 561-403-4406
Global Offices:
Spain: Tenerife, and Gran Canaria, Canary Islands
United States: Miami, Florida and Katy, Texas
Follow Us:
Legal Advice
by Jorge Elena Poblet - 09:35 - 12 Jun 2024 -
Re: Medical vertical
Hi Enric,
Super-useful, thanks! Another email on its way :)Thanks again!AlexeyOn 12 Jun 2024, at 20:07, Enric Tobella Alomar <notifications@odoo-community.org> wrote:Hi Alexey,It was abandonded due to some License issuesActually, OCA received a DMCA from github https://odoo-community.org/blog/news-updates-1/vertical-medical-75. After that, most collaborators left the repository.From my side, I have been working on a completely new Medical Repo for Odoo that is under an OpenSource License (we started from scratch in order to avoid the License infringement), but not under OCA Umbrella (not too many contributors were interested). We are open to go back to OCA if there is interest. However, it does not fill all the gaps right now, because my customers didn't need all the parts of a complete HIS inside Odoo. Th. solution is quite clean and we are improving it.If you are interested, you can contact me directly.Kind regards,El mié, 12 jun 2024 a las 19:32, Alexey Pelykh (<notifications@odoo-community.org>) escribió:Hi Joe,
Closer to "why those who did the repo stopped doing the repo". Likely because Odoo didn't fit well as there are other open-source solutions like OpenEMR, OpenEHR etc.Kind regards,AlexeyOn 12 Jun 2024, at 19:27, Joerg Lorenz <notifications@odoo-community.org> wrote:Hi Alexey,are you looking for the ones who did the repo?Or do you - because of requirement at hand - look to get an odoo based solution here?Best, JoeVon: "Alexey Pelykh" <notifications@odoo-community.org>
An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
Gesendet: Mittwoch, 12. Juni 2024 18:17:23
Betreff: Medical verticalG'day all, hope this week is treating all of you well! I wanted to check what's up with medical vertical repo - clearly it's abandoned and I guess there was a just reason to do that (as in, use X instead of Odoo). So whoever worked with medical domain - please chime in. Cheers, Alexey
_______________________________________________
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 Alexey Pelykh - 09:15 - 12 Jun 2024 -
Re: Medical vertical
Hi Alexey,It was abandonded due to some License issuesActually, OCA received a DMCA from github https://odoo-community.org/blog/news-updates-1/vertical-medical-75. After that, most collaborators left the repository.From my side, I have been working on a completely new Medical Repo for Odoo that is under an OpenSource License (we started from scratch in order to avoid the License infringement), but not under OCA Umbrella (not too many contributors were interested). We are open to go back to OCA if there is interest. However, it does not fill all the gaps right now, because my customers didn't need all the parts of a complete HIS inside Odoo. Th. solution is quite clean and we are improving it.If you are interested, you can contact me directly.Kind regards,El mié, 12 jun 2024 a las 19:32, Alexey Pelykh (<notifications@odoo-community.org>) escribió:Hi Joe,
Closer to "why those who did the repo stopped doing the repo". Likely because Odoo didn't fit well as there are other open-source solutions like OpenEMR, OpenEHR etc.Kind regards,AlexeyOn 12 Jun 2024, at 19:27, Joerg Lorenz <notifications@odoo-community.org> wrote:Hi Alexey,are you looking for the ones who did the repo?Or do you - because of requirement at hand - look to get an odoo based solution here?Best, JoeVon: "Alexey Pelykh" <notifications@odoo-community.org>
An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
Gesendet: Mittwoch, 12. Juni 2024 18:17:23
Betreff: Medical verticalG'day all, hope this week is treating all of you well! I wanted to check what's up with medical vertical repo - clearly it's abandoned and I guess there was a just reason to do that (as in, use X instead of Odoo). So whoever worked with medical domain - please chime in. Cheers, Alexey
_______________________________________________
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
by Enric Tobella Alomar - 08:06 - 12 Jun 2024 -
Re: Medical vertical
Hi Joe,
Closer to "why those who did the repo stopped doing the repo". Likely because Odoo didn't fit well as there are other open-source solutions like OpenEMR, OpenEHR etc.Kind regards,AlexeyOn 12 Jun 2024, at 19:27, Joerg Lorenz <notifications@odoo-community.org> wrote:Hi Alexey,are you looking for the ones who did the repo?Or do you - because of requirement at hand - look to get an odoo based solution here?Best, JoeVon: "Alexey Pelykh" <notifications@odoo-community.org>
An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
Gesendet: Mittwoch, 12. Juni 2024 18:17:23
Betreff: Medical verticalG'day all, hope this week is treating all of you well! I wanted to check what's up with medical vertical repo - clearly it's abandoned and I guess there was a just reason to do that (as in, use X instead of Odoo). So whoever worked with medical domain - please chime in. Cheers, Alexey
_______________________________________________
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 Alexey Pelykh - 07:31 - 12 Jun 2024
-
-
Module to notify via mail of new login
Hi,we are looking for an odoo module that will send an email to the user each time a new login is done (similar to what happens with social media, banking, etc.).Is there something ready-available in OCA?
by Francesco Foresti - 11:16 - 12 Jun 2024-
Re: Module to notify via mail of new login
Thank you, I think this is worth a module as it looks like a feature that should be available OOB - how else can a user review suspicious logins with their account?
(I'm on 14, maybe it's available in later versions)FrancescoIl giorno mer 12 giu 2024 alle ore 11:47 Tom Blauwendraat <notifications@odoo-community.org> ha scritto:Yes, any time a new record in res.users.login is created
On 6/12/24 11:29, Graeme Gellatly wrote:
Automated actions probably does it out of the box
On Wed, 12 Jun 2024, 9:17 pm Francesco Foresti, <notifications@odoo-community.org> wrote:
Hi,
we are looking for an odoo module that will send an email to the user each time a new login is done (similar to what happens with social media, banking, etc.).
Is there something ready-available in OCA?
_______________________________________________
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 Foresti - 12:17 - 12 Jun 2024 -
Re: Module to notify via mail of new login
Yes, any time a new record in res.users.login is created
On 6/12/24 11:29, Graeme Gellatly wrote:
Automated actions probably does it out of the box
On Wed, 12 Jun 2024, 9:17 pm Francesco Foresti, <notifications@odoo-community.org> wrote:
Hi,
we are looking for an odoo module that will send an email to the user each time a new login is done (similar to what happens with social media, banking, etc.).
Is there something ready-available in OCA?
_______________________________________________
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 - 11:46 - 12 Jun 2024 -
Re: Module to notify via mail of new login
Automated actions probably does it out of the boxOn Wed, 12 Jun 2024, 9:17 pm Francesco Foresti, <notifications@odoo-community.org> wrote:Hi,we are looking for an odoo module that will send an email to the user each time a new login is done (similar to what happens with social media, banking, etc.).Is there something ready-available in OCA?_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by "Graeme Gellatly" <graeme@moahub.nz> - 11:26 - 12 Jun 2024
-
-
OCA Days 2024 - Call for Speakers and Early Bird Member Registration
Hello OCA Contributors
I hope this message finds you well.As you know our OCA Days 2024 are coming up in few months time:--OCA Days 202430th September - 1st OctoberVal Benoit, LiègeI just wanted to remind our paid upOCA members, that the Early Bird registration for OCA Days 2024 finishes at the end of June, after that the price increases:- Members Early Bird Registration - €125 till 30th June
- Members Full Price Registration - €175 from 1st July
If you aren't an OCA member already, you can still become one here for €50, then you can take advantage of the early bird discount.If you don't wish to become a member but would still like to attend the OCA Days 2024 - you can purchase a:- Non-Member Full Price Registration - €190 at any point
Our call for speakers is also open, if you have a proposal to submit, we would love to hear from you. Just fill in the form on this page.Please, if you have any questions, do not hesitate to get in touch.RebeccaRebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly (OCA) - 02:31 - 11 Jun 2024 -
odoo14 website mega-menu unexpected mobile behaviour?
Hello,In odoo14 website if we add a mega-menu to the navbar then switch to mobile simulation, we get a non-expanded drop-down menu by default (see attachment megamenu1.png), I've made this screenshot made from OCA runboat.I'm having some sort of bug from mobile simulation in my current database: my custom mega-menu is loaded as already expanded when the website navbar is loaded.A few weeks ago, in a previous version of the database, that mega menu drop-down was properly loaded as non-expanded.I've noticed that this behaviour also applies if I create an entirely new mega-menu, so it's not strictly related to the specific item.I have tried to regenerate asset bundles and use the "-u all" command in order to resync database, however this pretty standard procedure didn't help for this situation.Do you have any hint to solve this problem?Thank you--Francesco Ballerini
by Francesco Ballerini - 04:05 - 10 Jun 2024-
Re: odoo14 website mega-menu unexpected mobile behaviour?
Thanks for your feedback Virginie,It happens quite often that I post a message and find a solution a few moments later, but I'm glad to know this could be helpful for other people : )Best regards,Francesco BalleriniIl giorno lun 10 giu 2024 alle ore 17:37 Virginie Dewulf <virginie@odoo-community.org> ha scritto:Hello,Thanks for sharing your questions and even the answers :)(I am really not making fun of you, just to make it clear!).I'm sure it might help others to solve this kind of errors in the future!Have a nice day,Le lun. 10 juin 2024 à 16:42, Francesco Ballerini <notifications@odoo-community.org> a écrit :Just found the reason: it was a mega-menu option "hamburger type" that I've changed from "default" to "off-canvas" few weeks ago. It was causing the different behaviour.--Francesco Ballerini_______________________________________________
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 - 06:06 - 10 Jun 2024 -
Re: odoo14 website mega-menu unexpected mobile behaviour?
Hello,Thanks for sharing your questions and even the answers :)(I am really not making fun of you, just to make it clear!).I'm sure it might help others to solve this kind of errors in the future!Have a nice day,Le lun. 10 juin 2024 à 16:42, Francesco Ballerini <notifications@odoo-community.org> a écrit :Just found the reason: it was a mega-menu option "hamburger type" that I've changed from "default" to "off-canvas" few weeks ago. It was causing the different behaviour.--Francesco Ballerini_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Virginie Dewulf - 05:36 - 10 Jun 2024 -
Re: odoo14 website mega-menu unexpected mobile behaviour?
Just found the reason: it was a mega-menu option "hamburger type" that I've changed from "default" to "off-canvas" few weeks ago. It was causing the different behaviour.--Francesco Ballerini
by Francesco Ballerini - 04:41 - 10 Jun 2024
-
-
contribution request
Hi, I am Mohamed!I am using web_notify module for version 17 as I had to upgrade it from version 16, and there was no any module for version 17.I would like to contribute to your repository in order to add the upgraded module for version 17, thanks 🙏
by Mohamed Alkobrosly - 10:46 - 10 Jun 2024-
Re: contribution request
Hello Mohamed,Please do so, your contribution is welcome.Make sure you review the migration guide here:ThanksDanielOn Mon, Jun 10, 2024 at 9:47 AM mohamed alkobrosly <notifications@odoo-community.org> wrote:Hi, I am Mohamed!I am using web_notify module for version 17 as I had to upgrade it from version 16, and there was no any module for version 17.I would like to contribute to your repository in order to add the upgraded module for version 17, thanks 🙏_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
by Daniel Reis - 11:01 - 10 Jun 2024 -
Re: contribution request
Hi Mohamed, Normally, you would have to sign the OCA CLA and then open up a PR on github.com/OCA/web, and follow these guidelines: https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-17.0 However, someone else already did all that: https://github.com/OCA/web/pull/2747 So, maybe you can leave your review for his work. It always needs 2 reviews in order to get merged, so your review will be welcomed. -Tom On 6/10/24 10:47, mohamed alkobrosly wrote: > Hi, I am Mohamed! > > I am using web_notify module for version 17 as I had to upgrade it > from version 16, and there was no any module for version 17. > > I would like to contribute to your repository in order to add the > upgraded module for version 17, thanks 🙏 > > _______________________________________________ > 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 - 11:01 - 10 Jun 2024
-
