Message Threads | The Odoo Community Association

Javascript Debug

Hello you,

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

Has anyone here an idea ?

Thank you all.

has got anyone an idea why the javascript/scss/... sources are not located under the running domain

Vielen Dank und viele Grüße

Stefan Wild
Geschäftsführer

sewisoft GmbH
Örtleinsweg 39
96148 Baunach

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

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

by Stefan Wild - 02:26 - 17 Dec 2022

4 attachments 4 attachments

Weblate project is locked

Hi,

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

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

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

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

https://github.com/OCA/commission/tree/fa60e0c6f13b58e2081d6376d0366564b32d6c0f/account_commission/i18n

Questions:

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

2. How can we unlock such projects?

Thank you.

--

Yoshi Tashiro

by Yoshi Tashiro. - 03:01 - 16 Dec 2022

Re: Module name, name collision

BTW:

https://www.odoo-code-search.com/

The feature already exists to tell you if the mod name exists.

This friends have it for free, it should be nice if OCA contacts them and let them serve something (may be paid).

Regards.

El mar, 22 nov 2022 a la(s) 09:17, David Beal (notifications@odoo-community.org) escribió:

Hi all,

It seems there are miscellaneous practices to deal with name collision in OCA, mainly regarding Odoo SA module names

here mgmt is used
https://github.com/OCA/helpdesk/tree/14.0

here and in some other repos oca is used
https://github.com/OCA/edi

Is there any other practice ?

Should we converge on the same standard ? with a rename in future version with apriori openupgrade file ?

Personally I prefer oca, but it probably needs to be voted !?

What do you think?

Regards

Thanks

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

--

Nhomar G Hernández

Vauxoo | CEO

¡Construyamos algo genial!
Cel: +52 (477) 393.3942 | Telegram: nhomar | Twitter: @nhomar

México · Venezuela · Costa Rica · Perú

phone nhomar@vauxoo.com vauxoo.com/contactus

by Nhomar Hernández - 10:51 - 15 Dec 2022

Re: Module name, name collision

IMHO.

Avoid prefixes or suffixes.

an script in the ci with a centralize DB with module names would be the practical solution.

1. A quick service with elastic.

2. An script that makes a push to such index.

3. Serve a quick rest search.

4. An script for the CI that makes:

curl url/search/modules_here -r
read_response.json -> found

5. Red if exists (with proper output).

Why not the prefix/suffix.

1. Nothing will avoid with such technique the duplication of functions and modules.

2. In dev time the developer will know where the problem is (now I do simply a search in google, but as I said it can be automated).

Regards.

El mar, 22 nov 2022 a la(s) 09:17, David Beal (notifications@odoo-community.org) escribió:

Hi all,

It seems there are miscellaneous practices to deal with name collision in OCA, mainly regarding Odoo SA module names

here mgmt is used
https://github.com/OCA/helpdesk/tree/14.0

here and in some other repos oca is used
https://github.com/OCA/edi

Is there any other practice ?

Should we converge on the same standard ? with a rename in future version with apriori openupgrade file ?

Personally I prefer oca, but it probably needs to be voted !?

What do you think?

Regards

Thanks

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

--

Nhomar G Hernández

Vauxoo | CEO

¡Construyamos algo genial!
Cel: +52 (477) 393.3942 | Telegram: nhomar | Twitter: @nhomar

México · Venezuela · Costa Rica · Perú

phone nhomar@vauxoo.com vauxoo.com/contactus

by Nhomar Hernández - 10:46 - 15 Dec 2022

Re: Module name, name collision

Hello,

It could be contextual, if we find that a better name would reflect what the module does.

However, I would go with an `_oca` suffix by default to avoid the name collision.

Cheers,

Yannick

On Tue, 22 Nov 2022 at 16:17, David Beal <notifications@odoo-community.org> wrote:

Hi all,

It seems there are miscellaneous practices to deal with name collision in OCA, mainly regarding Odoo SA module names

here mgmt is used
https://github.com/OCA/helpdesk/tree/14.0

here and in some other repos oca is used
https://github.com/OCA/edi

Is there any other practice ?

Should we converge on the same standard ? with a rename in future version with apriori openupgrade file ?

Personally I prefer oca, but it probably needs to be voted !?

What do you think?

Regards

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 Yannick Payot - 05:26 - 15 Dec 2022

M14 Accounting for French 'Collectivités locales'

Dear french OCA contributors,

I am actually working on a RFQ for accounting software of a French Polynesia City Hall. It works the same as in France due to the regulations.

We need M14 implementation (Budgets and Accounting) and PES (Protocole d'échanges standards)

https://www.collectivites-locales.gouv.fr/finances-locales/linstruction-m14-comptabilite-des-communes

https://www.collectivites-locales.gouv.fr/finances-locales/le-protocole-dechange-standard-pes

RFQ deadline is before january 4th 2023

Launching production is planned april 2023

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

Best regards

by Cyril VINH-TUNG - 07:01 - 15 Dec 2022

Re: Translation for Odoo core<=12.0

Hi Martin,

so I'll go with direct PR on OCB wheen needed.

Thanks all

Sergio Corato

Il giorno mer 14 dic 2022 alle ore 16:17 Martin Trigaux (mat) <notifications@odoo-community.org> ha scritto:

Hi there,

Martin, managing the Transifex project at Odoo S.A. here.
Just to add that the 13.0 Transifex project is going away very soon too (probably end of year), it's no longer supported since the release of 16.0. We have a limited number of terms in our Transifex plan so we can't keep forever for all versions unfortunately.

As said Moises, we will not accept PR on deprecated branches (we can accept translation PR on a supported version if it's in a language/module that are not on Transifex). So OCA/OCB is your best bet but adding past projects on Weblate is not negligible in term of size.
To give you a rough idea to those managing the OCA Weblate project if you consider it : Odoo 13.0 is 236k source words and it's increasing of ~30k at each release.

Best,

Martin

On 14/12/2022 12:06, Sergio Corato wrote:

Hi all,

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

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

Thanks,

Sergio Corato

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

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

by Sergio Corato - 05:35 - 14 Dec 2022

Re: OCA - Github - Switch brach by default

PSC *representatives* have admin rights to change default branches.

-sbi

On Wed, Dec 14, 2022 at 3:27 PM Rafael Blasco <notifications@odoo-community.org> wrote:

Hello!

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

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

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

More branches by default are v14, etc.

Thanks
Regards
Rafael

_______________________________________________
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 - 04:26 - 14 Dec 2022

Re: Translation for Odoo core<=12.0

Hi there,

Martin, managing the Transifex project at Odoo S.A. here.
Just to add that the 13.0 Transifex project is going away very soon too (probably end of year), it's no longer supported since the release of 16.0. We have a limited number of terms in our Transifex plan so we can't keep forever for all versions unfortunately.

As said Moises, we will not accept PR on deprecated branches (we can accept translation PR on a supported version if it's in a language/module that are not on Transifex). So OCA/OCB is your best bet but adding past projects on Weblate is not negligible in term of size.
To give you a rough idea to those managing the OCA Weblate project if you consider it : Odoo 13.0 is 236k source words and it's increasing of ~30k at each release.

Best,

Martin

On 14/12/2022 12:06, Sergio Corato wrote:

Hi all,

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

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

Thanks,

Sergio Corato

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

by Martin Trigaux - 04:16 - 14 Dec 2022

Re: Translation for Odoo core<=12.0

Hi Moisés,

no, I mean https://github.com/OCA/OCB

Sergio Corato

Il giorno mer 14 dic 2022 alle ore 15:27 Moises Lopez <notifications@odoo-community.org> ha scritto:

Hi Sergio

Did you mean, create a new PR to
https://github.com/odoo/odoo?

If yes, It could breaks Odoo SA contributing guidelines

1) Odoo doesn't accept PR related to translations:
- https://github.com/odoo/odoo/wiki/Contributing#how-can-i-translate-odoo-in-my-language

2) Odoo doesn't accept PR for deprecated branches/versions:
- https://github.com/odoo/odoo/wiki/Contributing#against-which-version-should-i-submit-a-patch

A workaround, create in your custom module a translation file:
- "your_module/i18n_extra/{LANG}.po"

with the terms that you need to change for all installed modules and improve the translation from transifex for stable ones

On Wed 14 Dec 2022 at 5:06 a.m. Sergio Corato <notifications@odoo-community.org> wrote:
Hi all,

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

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

Thanks,
Sergio Corato

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

--
Moisés López Calderón
Mobile: (+521) 477-752-22-30
Twitter: @moylop260
hangout: moylop260@vauxoo.com
http://www.vauxoo.com - Odoo Gold Partner
Twitter: @vauxoo

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

by Sergio Corato - 03:36 - 14 Dec 2022

Re: Translation for Odoo core<=12.0

Hi Sergio

Did you mean, create a new PR to

https://github.com/odoo/odoo?

If yes, It could breaks Odoo SA contributing guidelines

1) Odoo doesn't accept PR related to translations:

- https://github.com/odoo/odoo/wiki/Contributing#how-can-i-translate-odoo-in-my-language

2) Odoo doesn't accept PR for deprecated branches/versions:

- https://github.com/odoo/odoo/wiki/Contributing#against-which-version-should-i-submit-a-patch

A workaround, create in your custom module a translation file:

- "your_module/i18n_extra/{LANG}.po"

with the terms that you need to change for all installed modules and improve the translation from transifex for stable ones

On Wed 14 Dec 2022 at 5:06 a.m. Sergio Corato <notifications@odoo-community.org> wrote:

Hi all,

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

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

Thanks,
Sergio Corato

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

--

Moisés López Calderón

Mobile: (+521) 477-752-22-30

Twitter: @moylop260

hangout: moylop260@vauxoo.com
http://www.vauxoo.com - Odoo Gold Partner

Twitter: @vauxoo

by Moisés López Calderón - 03:26 - 14 Dec 2022

OCA - Github - Switch brach by default

Hello!

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

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

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

More branches by default are v14, etc.

Thanks

Regards

Rafael

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

Translation for Odoo core<=12.0

Hi all,

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

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

Thanks,

Sergio Corato

by Sergio Corato - 12:05 - 14 Dec 2022

Re: pre-commit changes

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

Regards.

by Pedro M. Baeza - 04:25 - 9 Dec 2022

Re: Proposing myself as banking-maintainers PSC

+1

Sent from my iPhone

On 9 Dec 2022, at 16:12, Tom Blauwendraat <notifications@odoo-community.org> wrote:

+1!

On 12/9/22 14:41, Rafael Blasco wrote:

Hello!

Any other positive vote here? 😅

Thank you!

Regards,

Rafael

El vie, 7 oct 2022 a las 8:46, Jairo Llopis (<notifications@odoo-community.org>) escribió:

+1

El mié, 5 oct 2022 a las 16:52, Fernando La Chica (<notifications@odoo-community.org>) escribió:

+1

El mié, 5 oct 2022 15:42, Sergio Corato <notifications@odoo-community.org> escribió:

+1

Sergio Corato

Il giorno mer 5 ott 2022 alle ore 15:01 Rafael Blasco <notifications@odoo-community.org> ha scritto:

Dear contributors,

I would like to apply as PSC for banking-maintainers

I have been working with Odoo in Accounting and Payment, Banking as long as my mind remember, and my stack of well-known modules is big.

I have reviewed and implemented quite lot of modules under this umbrella like *import_paypal, import_txt_xls, import_online* , etc.. , design, review and contribute in *mandate, *sepa*, account_payment_mode and all the set of modules around… (*_order, *:_order_return, etc.). Playing a lot to with reconcile and payment.

I’m already PSC of other repositories including accounting and I think I can help in accounting staff, as you know, reviewing functionally, testing, and organizing.

https://github.com/rafaelbn

Thanks to consider my request

Regards,

Rafael Blasco

PD: Let’s go for OCA Odoo 16! 😃I sadly won’t be presencially in OCA Days but I’ll be strongly online!!!

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

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

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

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

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

by Alexey Pelykh - 04:16 - 9 Dec 2022

Re: Proposing myself as banking-maintainers PSC

+1!

On 12/9/22 14:41, Rafael Blasco wrote:

Hello!

Any other positive vote here? 😅

Thank you!

Regards,

Rafael

El vie, 7 oct 2022 a las 8:46, Jairo Llopis (<notifications@odoo-community.org>) escribió:

+1

El mié, 5 oct 2022 a las 16:52, Fernando La Chica (<notifications@odoo-community.org>) escribió:

+1

El mié, 5 oct 2022 15:42, Sergio Corato <notifications@odoo-community.org> escribió:

+1

Sergio Corato

Il giorno mer 5 ott 2022 alle ore 15:01 Rafael Blasco <notifications@odoo-community.org> ha scritto:

Dear contributors,

I would like to apply as PSC for banking-maintainers

I have been working with Odoo in Accounting and Payment, Banking as long as my mind remember, and my stack of well-known modules is big.

I have reviewed and implemented quite lot of modules under this umbrella like *import_paypal, import_txt_xls, import_online* , etc.. , design, review and contribute in *mandate, *sepa*, account_payment_mode and all the set of modules around… (*_order, *:_order_return, etc.). Playing a lot to with reconcile and payment.

I’m already PSC of other repositories including accounting and I think I can help in accounting staff, as you know, reviewing functionally, testing, and organizing.

https://github.com/rafaelbn

Thanks to consider my request

Regards,

Rafael Blasco

PD: Let’s go for OCA Odoo 16! 😃I sadly won’t be presencially in OCA Days but I’ll be strongly online!!!

_______________________________________________
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 Tom Blauwendraat - 04:10 - 9 Dec 2022

Re: Proposing myself as banking-maintainers PSC

Hello!

Any other positive vote here? 😅

Thank you!

Regards,

Rafael

El vie, 7 oct 2022 a las 8:46, Jairo Llopis (<notifications@odoo-community.org>) escribió:

+1

El mié, 5 oct 2022 a las 16:52, Fernando La Chica (<notifications@odoo-community.org>) escribió:

+1

El mié, 5 oct 2022 15:42, Sergio Corato <notifications@odoo-community.org> escribió:
+1
Sergio Corato

Il giorno mer 5 ott 2022 alle ore 15:01 Rafael Blasco <notifications@odoo-community.org> ha scritto:
Dear contributors,
I would like to apply as PSC for banking-maintainers
I have been working with Odoo in Accounting and Payment, Banking as long as my mind remember, and my stack of well-known modules is big.
I have reviewed and implemented quite lot of modules under this umbrella like *import_paypal, import_txt_xls, import_online* , etc.. , design, review and contribute in *mandate, *sepa*, account_payment_mode and all the set of modules around… (*_order, *:_order_return, etc.). Playing a lot to with reconcile and payment.
I’m already PSC of other repositories including accounting and I think I can help in accounting staff, as you know, reviewing functionally, testing, and organizing.
https://github.com/rafaelbn
Thanks to consider my request
Regards,
Rafael Blasco
PD: Let’s go for OCA Odoo 16! 😃I sadly won’t be presencially in OCA Days but I’ll be strongly online!!!

_______________________________________________
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 "Rafael Blasco" <rblasco@rbnpro.com> - 02:40 - 9 Dec 2022

Re: pre-commit changes

Actually, pre-commit config updates should be on their own commit, so that they don't contaminate the module history.

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

Thanks
Daniel

On 06/12/22 13:11, Marco Colombo wrote:

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

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

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

Have a nice day.

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

--

DANIEL REIS
MANAGING DIRECTOR

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

by Daniel Reis - 10:35 - 9 Dec 2022

Re: pre-commit changes

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

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

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

Have a nice day.

by Marco Colombo - 02:10 - 6 Dec 2022

Migration 12.0 -> 13.0 and field collision

Hi,

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

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

ERROR: duplicate key value violates unique constraint "ir_model_fields_name_unique"
DETAIL: Key (model, name)=(mail.message, notified_partner_ids) already exists.

ERROR mig_9008 OpenUpgrade: mail: error in migration script mail/migrations/13.0.1.0/pre-migration.py: duplicate key value violates unique constraint "ir_model_fields_name_unique"

I tracked down the issue and I found out that the `notified_partner_ids` field was an existing field added in 7.0 but deleted in 9.0.

Maybe this field should have been dropped or renamed to `openupgrade_legacy_xxx`, I don't know if it should be the case or if I made a mistake in my original upgrade path, but this field still exists in our database even if not referenced in any files.

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

https://github.com/OCA/server-tools/pull/2491

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

--