profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/pedrobaeza/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

odoo/odoo 22505

Odoo. Open Source Apps To Grow Your Business.

OCA/OpenUpgrade 423

Open source upgrade path for Odoo/OpenERP

OCA/ansible-odoo 98

Ansible role for Odoo

OCA/dms 43

Odoo modules for a Document Management System

OCA/product-pack 13

Odoo modules related to product packs

issue closedOCA/OCB

[12.0] Text fields in product.template can't get blank when more than one language active

Impacted versions:

  • 12.0

Steps to reproduce:

  • Activate another language in "Settings > Translations".
  • Go to Products (product.template model) and select any one.
  • Fill any text field, like "Internal Notes" for example.
  • Save and edit again, remove any text in that field.
  • Save, the first text written is now shown again.

Current behavior:

  • Text fields cannot be blank once edited.

Expected behavior:

  • Text field can be blank once edited.

Video/Screenshot link (optional):

Support ticket number submitted via odoo.com/help (optional):

closed time in 9 minutes

antonio-trey

issue commentOCA/OCB

[12.0] Text fields in product.template can't get blank when more than one language active

This issue tracker is just for specific issues of OCB, not odoo/odoo ones.

Anyways, that's the intended behavior, and a workaround is to put an space.

antonio-trey

comment created time in 9 minutes

delete branch Tecnativa/OpenUpgrade

delete branch : 13.0-account-name_empty_string

delete time in 38 minutes

push eventOCA/OpenUpgrade

Pedro M. Baeza

commit sha 6a719b4bc22034752fcc96dd9076d098b345325d

[OU-FIX] account: Avoid empty string on name There can be the possibility of having an empty string in any of the sources of the field `name`. If that's the case, it will be populated with such data, leading to not being able to save the generated invoice through UI until putting '/' in the DB. With this trick, we avoid this circumstance. TT32007

view details

Pedro M. Baeza

commit sha daec18e4a432f2f2b990baee2331d28e3c7294d5

Merge pull request #2916 from Tecnativa/13.0-account-name_empty_string [13.0][OU-FIX] account: Avoid empty string on name

view details

push time in 38 minutes

PR merged OCA/OpenUpgrade

[13.0][OU-FIX] account: Avoid empty string on name approved

There can be the possibility of having an empty string in any of the sources of the field name. If that's the case, it will be populated with such data, leading to not being able to save the generated invoice through UI until putting '/' in the DB.

With this trick, we avoid this circumstance.

@Tecnativa TT32007

+2 -1

0 comment

1 changed file

pedrobaeza

pr closed time in 38 minutes

PR opened OCA/OpenUpgrade

[13.0][OU-FIX] account: Avoid empty string on name

There can be the possibility of having an empty string in any of the sources of the field name. If that's the case, it will be populated with such data, leading to not being able to save the generated invoice through UI until putting '/' in the DB.

With this trick, we avoid this circumstance.

@Tecnativa TT32007

+2 -1

0 comment

1 changed file

pr created time in an hour

create barnchTecnativa/OpenUpgrade

branch : 13.0-account-name_empty_string

created branch time in an hour

pull request commentOCA/l10n-spain

[IMP] l10n_es_facturae: Migration script, set column as nullable

Entonces lo que habría que hacer es lo que se hace cuando un modelo deja de existir, que es borrar sus FK constraints (incluidos ondelete). Hay un método openupgradelib para hacerlo de una tacada diciendo el modelo.

etobella

comment created time in 2 hours

PullRequestReviewEvent

pull request commentOCA/delivery-carrier

[13.0][MIG] base_delivery_carrier_files: Migration to 13.0

/ocabot merge nobump

victoralmau

comment created time in 3 hours

pull request commentOCA/l10n-spain

[IMP] l10n_es_facturae: Migration script, set column as nullable

Ésta no es la solución adecuda me temo. Al no indicar cuál es el stacktrace, no te puedo dar pautas más exactas, pero la eliminación será porque un XML-ID que existía antes, ahora desaparece, y Odoo lo intenta eliminar, pero tiene cosas asociadas. En este caso, en el script de migración debe intentar eliminarlo manualmente con el método de openupgradelib delete_safely_by_xml_id (o nombre similar), y si no es posible, marcar el XML-ID como noupdate=1. Tal vez se podría ampliar el método existente para hacer eso del XML-ID.

etobella

comment created time in 3 hours

issue commentOCA/l10n-spain

Asiento contable regularización 303 con cuotas a compensar

De todas formas, siempre se pueden cambiar a mano las casillas.

SoniaViciana

comment created time in 3 hours

issue commentOCA/l10n-spain

Asiento contable regularización 303 con cuotas a compensar

Sí, esto no tiene que ver con la versión de Odoo, si no con el cambio que hizo la AEAT en la forma de compensar las declaraciones.

SoniaViciana

comment created time in 3 hours

pull request commentOCA/e-commerce

[13.0][MIG] website_sale_order_type: Migration to 13.0

/ocabot merge nobump

oihane

comment created time in 8 hours

pull request commentOCA/l10n-spain

[14.0][FIX]l10n_es_aeat_sii_oca: Fix field name on default type function.

/ocabot merge patch

jesusVMayor

comment created time in 8 hours

PullRequestReviewEvent

delete branch ForgeFlow/OpenUpgrade

delete branch : 13.0-fix-delivery

delete time in 8 hours

delete branch Tecnativa/OpenUpgrade

delete branch : 13.0-delivery-invoice_policy

delete time in 8 hours

push eventOCA/OpenUpgrade

david

commit sha 04568932442198bfb553dfd9feeb2396f4b38466

[FIX] delivery: invoice_policy Odoo changed the behavior of delivery charges from v12 to v13 delegating the mode check into the new `invoice_policy` field in `delivery.carrier`. Initially, it was decided to keep the behavior in v12 that recomputes the price when the picking is validated, but there's no accurate flow translation between versions and some issues raise with this default: - Core UI forbids users changing this value in the standard shipping methods. Only extra carriers can choose it and the default `estimated` value remains. - The eCommerce behaves weirdly with "Real cost" methods, leading the customers to think that they get free delivery orders. For that reasons, a sane default must be Estimated cost for the majority of cases. TT31975

view details

Pedro M. Baeza

commit sha 96d2868980d792138129fed57ba5c7d3029fd980

Merge pull request #2913 from Tecnativa/13.0-delivery-invoice_policy [13.0][FIX] delivery: invoice_policy

view details

push time in 8 hours

PR merged OCA/OpenUpgrade

[13.0][FIX] delivery: invoice_policy approved

Odoo changed the behavior of delivery charges from v12 to v13 delegating the mode check into the new invoice_policy field in delivery.carrier.

Initially, it was decided to keep the behavior in v12 that recomputes the price when the picking is validated, but there's no accurate flow translation between versions and some issues raise with this default:

  • Core UI forbids users changing this value in the standard shipping methods. Only extra carriers can choose it and the default estimated value remains.
  • The eCommerce behaves weirdly with "Real cost" methods, leading the customers to think that they get free delivery orders.

For that reasons, a sane default must be Estimated cost for the majority of cases.

cc @Tecnativa TT31975

please review @pedrobaeza @victoralmau

+1 -11

6 comments

2 changed files

chienandalu

pr closed time in 8 hours

pull request commentOCA/OpenUpgrade

[13.0][FIX] delivery: invoice_policy

For clarification, the e-commerce weird behavior is a bug of Odoo, but for not having to "fight" with Odoo about it, let's go this way with the saner default. It consists of the initial payment cart render puts the proper price, but when selecting the desired delivery method, the sales line is added with 0, and then the ribbon goes to "Free" in the website.

chienandalu

comment created time in 8 hours

push eventTecnativa/web

Pedro M. Baeza

commit sha fbcb410ef4935ffa5effb855d2eb339b14ea1cc6

fixup! [IMP] web_pwa_cache: Introduce queued onchange cache mechanism

view details

push time in 9 hours

Pull request review commentOCA/stock-logistics-warehouse

[13.0] stock_cycle_count error on location_id

 def action_accuracy_stats(self):         self.ensure_one()         action = self.env.ref("stock_cycle_count.act_accuracy_stats")         result = action.read()[0]-        result["context"] = {"search_default_location_id": self.id}+        result["context"] = {"search_default_location_ids": self.complete_name}

You should remove this.

celm1990

comment created time in 10 hours

PullRequestReviewEvent

pull request commentOCA/margin-analysis

[12.0][IMP] sale_margin_delivered: No compute margin delivered fields for no delivered lines

It seems you haven't pushed such rebase to the branch.

sergio-teruel

comment created time in 11 hours

pull request commentOCA/OpenUpgrade

[13.0][OU-FIX] delivery: invoice_policy should be 'estimated' instead

We are also in a not comfortable with the real option now that we have seen more cases, and we are proposing to go to estimated. Please check #2913

The problem is that none of the current ones are exactly the same as the options in v12, and you will find several drawbacks in one or the other.

MiquelRForgeFlow

comment created time in a day

pull request commentOCA/OpenUpgrade

[13.0][FIX] delivery: invoice_policy

Also being discussed in #2715

chienandalu

comment created time in a day