Skip to Content
Menu
Musisz się zarejestrować, aby móc wchodzić w interakcje z tą społecznością.
To pytanie dostało ostrzeżenie
1 Odpowiedz
405 Widoki

Hello everyone,

I'm facing an issue with my Odoo Enterprise on-premise subscription regarding the Lines of Code (LoC) count for a custom module.

Our company has a custom subscription plan which, as we understand it, allows us to fully customize Odoo with our own modules without being charged for LoC. We are fully responsible for the development, maintenance, and upgrades of these custom modules.

However, after adding a new custom module, our system has started reporting a significant number of LoC that we are being billed for.

My question is:

  1. Has anyone else experienced a similar issue where Odoo's LoC count is incorrectly applied to custom modules that are self-managed?
  2. Are there specific configuration settings or technical steps I might be missing to properly inform the Odoo system that these modules should be excluded from the LoC count?

Any advice on how to technically address this issue or what to check in the system's configuration would be greatly appreciated.

Thank you in advance for your help.

Awatar
Odrzuć
Autor

Thank you for the solutions on how to exclude custom modules from the LoC count. I followed the suggestions, and I can confirm that the LoC for my custom modules are no longer being counted, which is a great step forward!.

However, the main issue persists. My Odoo Enterprise subscription has not been fully activated. The system still shows that I am on a trial or limited subscription, and I only have a month of validity.

I have already opened a support ticket with Odoo about this, but I have not received a response yet.

Given your expertise, do you have any suggestions on how to properly activate or link a custom Enterprise subscription to an on-premise installation? Are there specific steps I might be missing, or a configuration parameter that needs to be checked?

Any advice you could offer would be a huge help.

Thank you again for your time and assistance.

Autor

Thank you for the solutions on how to exclude custom modules from the LoC count. I followed the suggestions, and I can confirm that the LoC for my custom modules are no longer being counted, which is a great step forward!.

However, the main issue persists. My Odoo Enterprise subscription has not been fully activated. The system still shows that I am on a trial or limited subscription, and I only have a month of validity.

I have already opened a support ticket with Odoo about this, but I have not received a response yet.

Given your expertise, do you have any suggestions on how to properly activate or link a custom Enterprise subscription to an on-premise installation? Are there specific steps I might be missing, or a configuration parameter that needs to be checked?

Any advice you could offer would be a huge help.

Thank you again for your time and assistance.

Najlepsza odpowiedź

You need to indicate in the manifest of your modules that they are excluded from the CLOC count:

"cloc_exclude": [
    "lib/common.py", # exclude a single file
    "data/*.xml",    # exclude all XML files in a specific folder
    "example/**/*",  # exclude all files in a folder hierarchy recursively
    "**/*.scss",     # exclude all scss file from the module
]

See https://www.odoo.com/documentation/18.0/developer/reference/cli.html#cloc

Awatar
Odrzuć
Powiązane posty Odpowiedzi Widoki Czynność
1
cze 25
695
1
kwi 25
2098
2
lut 25
4661
2
lis 24
4225
1
paź 24
2042