coopiteasy / addons Goto Github PK

Disabled in 57cff4f

This line has the side effect of issuing a warning for all models that inherit this mixin and set defaults to resource_calendar_id

2024-01-26 15:09:10,166 69244 WARNING sixteen-odoo odoo.fields: Redundant default on resource.resource.calendar_id 
2024-01-26 15:09:10,170 69244 WARNING sixteen-odoo odoo.fields: Redundant default on hr.employee.resource_calendar_id 
2024-01-26 15:09:10,175 69244 WARNING sixteen-odoo odoo.fields: Redundant default on resource.mixin.resource_calendar_id 
2024-01-26 15:09:10,362 69244 INFO sixteen-odoo odoo.modules.loading: loading spreadsheet_dashboard_hr_timesheet/data/dashboards.xml 
2024-01-26 15:09:10,555 69244 INFO sixteen-odoo odoo.modules.loading: Module spreadsheet_dashboard_hr_timesheet loaded in 0.52s, 26 queries (+26 other) 
2024-01-26 15:09:10,555 69244 INFO sixteen-odoo odoo.modules.loading: Loading module sale_management (54/62) 
2024-01-26 15:09:10,726 69244 WARNING sixteen-odoo odoo.fields: Redundant default on resource.resource.calendar_id 
2024-01-26 15:09:10,730 69244 WARNING sixteen-odoo odoo.fields: Redundant default on hr.employee.resource_calendar_id 
2024-01-26 15:09:10,736 69244 WARNING sixteen-odoo odoo.fields: Redundant default on resource.mixin.resource_calendar_id 
2024-01-26 15:09:11,037 69244 WARNING sixteen-odoo odoo.fields: Redundant default on resource.resource.calendar_id 
2024-01-26 15:09:11,038 69244 WARNING sixteen-odoo odoo.fields: Redundant default on hr.employee.resource_calendar_id 
2024-01-26 15:09:11,102 69244 WARNING sixteen-odoo odoo.fields: Redundant default on resource.mixin.resource_calendar_id 
... and more

More information on the warning :

  # A readonly related field without an inverse method should not have a
  # default value, as it does not make sense.
  if self.default and self.readonly and not self.inverse:
      _logger.warning("Redundant default on %s", self)

Steps to reproduce:

1. Create a new product.
2. Toggle 'Is a Meal' on.
3. There is no 'mL' string next to the value of the container volumes.
4. Save.
5. Edit. There is now an 'mL' string next to the container volume values.

How to reproduce:

1. Add a meal to cart.
2. Press 'purchase' without finalising purchase. This automagically adds containers to the cart.
3. Go back to shopping cart.
4. There are still containers in the cart, which the user can alter in quantity. This is confusing behaviour.

email_template_config adds the feature to remove the "force mail send" default parameter for mail templates.

Without this, payment reconciliations in Cooperators fail whenever there is an issue when sending the user portal invitation email. This is unpleasant for new implementation, when one wants to test the cooperator data before the go live, so before these emails are sent, and be able to reconcile share increases whose automatic email cannot be turned off.

The problem arose post migration to v14, since email_template_config hasn't been ported yet.

Rational

• create an empty module that depends on l10n_fr + pos_customer_wallet and install it with demo data;
• on account_customer_wallet installation : it will create accounting demo data : (account_account_customer_wallet_demo, account_journal_customer_wallet_demo)
• on l10n_fr installation : it will unlink account and journal created before. See _load_for_current_company code.
• on pos_custom_wallet : it will fail when loading the file pos_customer_wallet/demo/account_journal_demo.xml

odoo.tools.convert.ParseError: "Cannot update missing record 'account_customer_wallet.account_journal_customer_wallet_demo'" while parsing /home/sylvain/grap_dev/grap-odoo-env-12.0/src/coopiteasy/coopiteasy-addons/pos_customer_wallet/demo/account_journal_demo.xml:7, near
<record id="account_customer_wallet.account_journal_customer_wallet_demo" model="account.journal">
        <field name="journal_user" eval="True"/>
    </record>

Possible solution :

• Move demo data definition into test_module.py file. (We loose the possibility to test the module out of the box, as functional people should recreate manually data account, journal, etc...)
• create dedicated "test" module that depends on l10n_generic_coa
• add a new demo company "Wallet Company" and add accounting stuff in that new company. So when installing l10n_xx module, existing account settings will not be deleted.

Done in d492e85

It won't install for some reason.