profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/florian-dacosta/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.

florian-dacosta/connector-prestashop 2

Connect Odoo with Prestashop

bguillot/prestapyt 0

Prestapyt is a library for Python to interact with the PrestaShop's Web Service API.

florian-dacosta/account-financial-reporting 0

Financial reports for Odoo

florian-dacosta/ak-odoo-incubator 0

Misc Odoo modules maturing before going to a specific repo

florian-dacosta/chronopost 0

Lib to create chronopost label from their webservice

florian-dacosta/docker-openupgrade 0

Basic Docker Images with OpenUpgrade

push eventakretion/delivery-carrier

Florian da Costa

commit sha 584734df37604cd1855169a3ee85de42fae8b576

Fix generate_edi_file decorator

view details

push time in 12 days

push eventakretion/delivery-carrier

Florian da Costa

commit sha a49d8ec2dab498b284b1e0ac5b1c54829b7ddfb6

Fix notification for geodis M means mail AND sms while P means email

view details

push time in 15 days

push eventakretion/delivery-carrier

Florian da Costa

commit sha 57c0bc75bfcab5d11277f1ec3e02571e31e42583

Fix Geodis notif M mean phone and mail and P means email

view details

push time in 15 days

push eventakretion/roulier

Florian da Costa

commit sha 37d448f95dfc1d68a5503b0f3ec6f5f996eb6e83

Update Geolabel ImpressionEtiquette url to https for geodis

view details

Florian

commit sha 032e0c9f979a1882c0a8204437b2230a1c40f286

Merge pull request #152 from akretion/py2-update-geodis-urls Update Geolabel ImpressionEtiquette url to https for geodis

view details

Florian da Costa

commit sha f17ed9bc4115dacd64c2f52b95998137e9c1e0eb

Add UPS support for label generation

view details

Florian da Costa

commit sha 0a6eb8319a315111c82d4aeb601e926f77ccc264

Raise error if unkown response from ups webservice

view details

push time in 15 days

push eventakretion/roulier

Florian da Costa

commit sha 37d448f95dfc1d68a5503b0f3ec6f5f996eb6e83

Update Geolabel ImpressionEtiquette url to https for geodis

view details

Florian

commit sha 032e0c9f979a1882c0a8204437b2230a1c40f286

Merge pull request #152 from akretion/py2-update-geodis-urls Update Geolabel ImpressionEtiquette url to https for geodis

view details

push time in 15 days

pull request commentOCA/rma

[14.0] [MIG] rma_sale module

@chienandalu PR has been updated with last changes on v13 I guess it is ready to review @ernestotejeda

chafique-delli

comment created time in 15 days

push eventakretion/rma

Chafique

commit sha 0d98089699b39911f0246ce6a7a86d3a290a7a1d

[14.0][MIG] rma_sale module

view details

push time in 15 days

pull request commentakretion/sale-import

[sale_import_delivery_carrier] Match delivery carrier by code instead of name

I fixed the inconsistency in the API, replaced "name" by "code". We can merge this whenever you are ready

florian-dacosta

comment created time in 16 days

push eventakretion/sale-import

Sébastien BEAU

commit sha 49dd5a59cca921caf6b58765bbb3a279d6b3c58b

[FIX] Validation should be done during chunk processing

view details

Sébastien BEAU

commit sha 188e6ffc7a5798b4529cc802e205f592a9228025

[IMP] start adding sale_channel_product extracted from shopinvader. TODO check all contributor and add them in the readme. Laurent Mignon, Pierrick Brun, François Honoré ...

view details

Sébastien BEAU

commit sha 4353427270d79e23c0ef6e7d56c0de07120850b1

[FIX] add setup

view details

Kevin Khao

commit sha 136fcc0fe6681f655230e9ca1acdefc96056e3a3

[ADD] sale_channel_hook_stock_variation: add

view details

Kevin Khao

commit sha 9c0c3d8e50e9a6b95c47466f05054042fbe36b66

[FIX] Fix logic for stock variation notification

view details

Kevin Khao

commit sha 2df39a1b8650b913f640b730968717ac424b98d8

[FIX] Correcting job logic

view details

KevinKhao

commit sha e4e784bc676a2c731eece96cee1e3d5e2174c8f1

[FIX] Fix notification logic

view details

KevinKhao

commit sha 78848cb4c4f06e77d254f022411eaa97e2b14052

[IMP] Add selectable product stock field

view details

KevinKhao

commit sha e0f18ddc926829dbd97368dbefdc9fe8c15777f1

[IMP] Improve pluggability of ImporterSaleChannel component

view details

Kevin Khao

commit sha ea031ddfc72026c29796c3331fa7b2949bea90ad

[FIX] Add unused file

view details

Kevin Khao

commit sha 0b86de530b1d65a60e2f71280adf14de462a890c

Update sale_channel_hook_stock_variation/models/channel_product_product.py Co-authored-by: beau sebastien <sebastien.beau@akretion.com>

view details

Kevin Khao

commit sha af060c9ef401874e8972e37166f632f6aee8b3c5

Update sale_channel_hook_stock_variation/models/stock_move.py Co-authored-by: beau sebastien <sebastien.beau@akretion.com>

view details

Kevin Khao

commit sha 0958f5e5604fa8994e3d275a8499ea792028b4a3

Update sale_channel_hook_stock_variation/models/stock_move.py Co-authored-by: beau sebastien <sebastien.beau@akretion.com>

view details

Kevin Khao

commit sha f18198c497fb3aea2bb8f11e469d8f73339e9e1c

Update sale_channel_hook_stock_variation/models/stock_move.py Co-authored-by: beau sebastien <sebastien.beau@akretion.com>

view details

Kevin Khao

commit sha 650de604936bced175e16d834e136842231e417d

Update sale_channel_hook_stock_variation/models/stock_move.py Co-authored-by: beau sebastien <sebastien.beau@akretion.com>

view details

Kevin Khao

commit sha c576ce32686c876be57687f81f69747f6a2a927f

[IMP] Add tests

view details

Kevin Khao

commit sha 9b39d11264f5915c6940b453e8759c8de30525ad

Update sale_channel_hook_stock_variation/models/stock_move.py Co-authored-by: beau sebastien <sebastien.beau@akretion.com>

view details

Kevin Khao

commit sha 0be8fcd696c646879fbd0cdf8fb6e45920277971

Update sale_channel_hook_stock_variation/models/channel_product_product.py Co-authored-by: beau sebastien <sebastien.beau@akretion.com>

view details

Kevin Khao

commit sha a2a81299b2dcb23657dac8c80fbe91072ff76187

Update sale_channel_hook_stock_variation/models/sale_channel.py Co-authored-by: beau sebastien <sebastien.beau@akretion.com>

view details

Kevin Khao

commit sha 25257ec613825a2538342b8e1c21a4b79b50d47b

Update sale_channel_hook_stock_variation/models/channel_product_product.py Co-authored-by: beau sebastien <sebastien.beau@akretion.com>

view details

push time in 16 days

push eventakretion/delivery-carrier

Florian da Costa

commit sha 8ac035718c6b1841b9db91f8f119c277e94ff2d7

Add delivery_roulier_ups for v14

view details

push time in 16 days

push eventakretion/roulier

Florian da Costa

commit sha d699f735ec23248877cc9382c86282d5d73ff0aa

Add UPS support for generating labels

view details

push time in 16 days

push eventakretion/roulier

Florian da Costa

commit sha e3ac56041538e38cdf0a8412818c2e6764c61f08

Raise error if unkown response from ups webservice

view details

push time in 16 days

create barnchakretion/roulier

branch : py-ups-zpl-encoding

created branch time in 16 days

create barnchakretion/delivery-carrier

branch : 14-roulier-ups

created branch time in 17 days

push eventakretion/roulier

Florian da Costa

commit sha e9bfa5ba93d5a7eb4f8e7157a185798181231312

Add ups REST support for label generation

view details

push time in 17 days

push eventakretion/roulier

Florian da Costa

commit sha 9220a4fd0f1d853353125daefd4ba5289711844c

Add UPS support for label generation

view details

push time in 17 days

pull request commentakretion/sale-import

[sale_import_delivery_carrier] Match delivery carrier by code instead of name

@hparfr @sebastienbeau Any objection?

florian-dacosta

comment created time in 18 days

push eventakretion/stock-logistics-warehouse

Florian da Costa

commit sha 44bf049836d865eba87c6b884b23e703bd20f6b4

[MIG] stock_orderpoint_automatic_creation: Migration to 14.0

view details

push time in 18 days

push eventakretion/stock-logistics-warehouse

Florian da Costa

commit sha 03bb401ac1d4bfb1f89c9b7b6706adcecc723d66

[MIG] stock_orderpoint_automatic_creation: Migration to 14.0

view details

push time in 18 days

pull request commentOCA/delivery-carrier

[13.0][MIG] delivery_ups_oca: Migration 13.0 + Refactor

Well, that is kind of what I said, base_delivery_carrier_label could be split into multiple modules to really be simpler and have more optional modules depending on the need.

But there are some common ground usefull for every carrier and I think it is a shame to let it go. Doing some generic carrier stuff in each carrier module is fine when one use only 1 or 2 carriers. But as soon as one use more, it can become a mess.

An example is the carrier_account model. Adding login, password fields on delivery.carrier directly as in this module has several problems :

  • Duplicate fields for every carrier
  • if for a same carrier, you use multiple delivery methods, you have to duplicate the configuration
  • Totally inflexible => if you share delivery method between company but not the carrier accounts, you are blocked ?
  • If you want to use your carrier account with preprod/test environement (which is usually handy) with module server_environment, you would just do one generic module (that already exists) instead of doing one more additional module per carrier...
  • ...

Kind of problems that were resolved by a separated/generic model which is droped here out of the blue.

I understand that for a simple case, it is a bit more of maintenance, but it also make it kind of impossible to use for more complex cases. I have such a case on my side and this kind of refactore make the module UPS impossible to use for me.

I don't see such a big maintenance burden of base_delivery_carrier_label, which is already refactored and migrated to 14. And it could be even smaller splitting its functionality. If there were a consensus, I could take the time to do such another recactore for v14 (maybe it is a bit late for v13?)

We could have something like this : base_delivery_carrier_label

  • carrier_account and helper to get the right account from a delivery method (overridable for flexibility)
  • shipping label : class inheriting ir_attachment for the carrier labels => very usefull to be able to find the labels attachment from the other picking attachments. add a link with the package Could be usefull to : reprint label later without re-generating a new one from the carrier webservice delete it if you cancel the tracking/label...
  • helpers to avoid re-coding the same in all carrier modules and have some flexibility (overidable methods)
    • to create labels, attach it on the pickingand fill the racking number (instead of re-coding it in every carrier modules)
    • to get the address of the sender (overiddable) (in this ups module it is the warehouse address, but one could want the company instead, better to have this choice in a base module, once again, to be able to override it for all carriers and not carrier per carrier

delivery_carrier_option Possibility to choose specific options on a picking for a specific delivery carrier.

delivery_carrier_label_before_shipping (we'd have to find another name...)

  • make it possible to generate the labels before the actual transfer of the picking (when the picking is actually at ready state) (If necessary, on my side, I don't think I use this feature but base_delivery_carrier_label add some stuff to be able to do it)

@StefanRijnhart @chienandalu @pedrobaeza

victoralmau

comment created time in 22 days

push eventakretion/synchronizer

Florian da Costa

commit sha cd472c48cc1448819812f3c1afc3f556f31b0796

Change the way we remove _ids from external apps Before we would check what changed in base_domain since last sync and remove it if not what has to be done since last sync. Problem is, if something did not belong to base_domain anymore, then it would never be to remove. Now, we get the current list from external apps, and we check, what in this list is not valid anymore. It should work for all cases

view details

push time in 23 days

pull request commentOCA/account-reconcile

[14][MIG] account_move_base_import

@rvalyi I looked into it. And I really did not understand the issue... Let me try to explain with an example In account_reconcile_reconciliation_date tests use journals, it finds the journal with a search and LIMIT 1. The test user has 2 allowed companies. So, the journal search domain correspond to 2 journals in Odoo database, but only one is returned because of the limit. So test user is allowed on company 2 and 3. we search a journal with type "sale", with limit 1. Odoo return the journal from company 2. => The test work

Now, if we install account_move_base_import, the same tests fails because instead of returning the journal from company 2, it returns the journal from company 3... I dug into it and I found that this line causes the issue : https://github.com/akretion/account-reconcile/blob/14.0-mig--account-move-base-import/account_move_base_import/models/account_journal.py#L69 It makes no sense to me, but adding a boolean field on the journal with default = True, changes the result of the journal search with LIMIT 1. Even stranger, this change of order is only effective the first time the tests are launched at installation. If you install the modules and then lauch tests again, the behavior is not changed but the default True boolea field and the tests are ok.

Anyway, even if I feel I am missing something around here, IMO, the root problem is that the account_reconcile_reconciliation_date module make a search on journals without specifying the company, although there are multiple journals. So the result could be kind of random, since the order is not enough to always get the same result. (both journals from tests have the same sequence, type and code, which is the default order on journals). What I did to fix this was just to add the company in the journal search domain...

I think it solves our issue.

florian-dacosta

comment created time in 23 days

PR opened OCA/delivery-carrier

[14][delivery_roulier] Avoid failure if getting price from carrier webservice is not implemented

Somme carriers implemented as submodule of delivery roulier does not manage getting the price from the carrier webservice. Because it is not made possible by the carrier, of just because this was not implemented yet, the main/original goal of these modules beeing to be able to generate the carrier labels.

This PR aims to avoid a failure if the price for such a carrier is asked by Odoo but not implemented. (in this case we just return a null price).

This should solve the issue here https://github.com/OCA/delivery-carrier/issues/407 Although it won't give a price, but this could be implemented as an improvement if needed (in roulier lib)

@delkano

+13 -0

0 comment

1 changed file

pr created time in 24 days

push eventakretion/account-reconcile

Florian da Costa

commit sha 6aa7ee4a22963e3b09da74bbfd03308b9e6fba5d

[FIX] account_reconcile_reconciliation_date tests compatibility with account_move_base_import Make sure always the current company journal is chosen, else we may chose journals from different company (among allowed companies) and then have a payment with inconistent companies)

view details

push time in 24 days

push eventStores-Discount/OCB

Xavier-Do

commit sha c9d3120689b6fbe9ac901076f219862217b5211d

[REM] codeowner: remove github codeowner Github codeowner is replaced with a runbot version of codeowners for multiple reason: - github codeowners is difficult to maintain, the precedence rule will sometimes remove teams from some file because of a more specific rule added by another team. - github codeowner does not support version specific rules, especially the "all except master" rule. For this use case teams needs to adapt the new codeowner when freezing a new version. - github will trigger codeowner on failed rebase, and add almost all teams as reviewer. Runbot has specific commit and file limit to avoid this problem. - runbot codeowner is centralised and does not need to be managed cross repo/version - runbot codeowner works for enterprise Any mofification on codeowner should be requested to runbot team. closes odoo/odoo#74127 X-original-commit: 305a42f5fc97bd6a438dd818756c64553de67bff Signed-off-by: Xavier Dollé (xdo) <xdo@odoo.com>

view details

Adrien Widart

commit sha 8d362af654c1905535d78fbf8d73677633b65d63

[FIX] fleet: use services dates in report start date computation When adding some services to a vehicle that does not have any immatriculation date, the costs report does not consider these services. To reproduce the error: (DB without any demo data) 1. Create a vehicle V - Remove the Immatriculation Date 2. Add a service for V - The category of the service type does not matter - Cost > 0 - Date: today 3. Fleet > Reporting > Costs Error: Costs Analysis is empty, the service is not considered In the SQL view, the date used as start point is the oldest immatriculation date. Therefore, if the vehicle doesn't have this date, the report lines won't be generated. OPW-2477004

view details

Adrien Widart

commit sha 7ea6300f951bd426c94d721bb56e6ad85a58bd30

[FIX] fleet: always include current month in costs report When consulting the costs reports, if the beginning of the dates range has a day greater than the day of today (e.g., start date: 2021/02/25, today: 2021/07/10 => 25 > 10), the costs of the current month won't be include in the report. To reproduce the issue: (DB without any demo data. Let X be the day of the month for today) 1. Create a vehicle V 2. Add a service S1 for V - The category of the service type does not matter - Cost: 500 - Date: today 3. Add a second service S2 for V - Same service type - Cost: 250 - Date: Last month with a day > X (so if today is 2021/07/26, date could be 2021/06/27) 4. Fleet > Reporting > Costs Error: The report does not include S1 When generating the dates range, the current date is used as the end of the interval. Since the interval step is '1 month', it will lead to an issue in the above case: Suppose today is 2021/07/26, the interval starts on 2021/06/27. Then, if we add one month to this date, we have 2021/07/27, which is after the end of the interval (2021/07/26), so the date is ignored. As a result, current month won't be included in the report. Note: A similar issue can happen with the contracts OPW-2477004 closes odoo/odoo#74219 Signed-off-by: Kevin Baptiste <kba@odoo.com>

view details

Hardik Prajapati

commit sha a145e1242118d3e539790327221486e1bd94e59a

[FIX] web: resize list in form view overflows Currently, When the One2many list contains a large amount of fields and the user clicks or resizes the header, list takes table width as its initial width and because of this list to overflows outside of the form view. Issue raised after commit: d58edef12aab50fcd4494ba3b276e7d9d58d4d56 after this commit, clicking or resizing the list header does not impact the width of the list. TaskID-2388582 closes odoo/odoo#69024 Signed-off-by: Simon Genin (ges@odoo) <ges@odoo.com>

view details

Xavier-Do

commit sha 4f68396857b2c2467813204da0f5ac970de7c3bc

[FIX] *: add explicit license to all manifest The license is missing in most enterprise manifest so the decision was taken to make it explicit in all cases. When not defined, a warning will be triggered starting from 14.0 when falling back on the default LGPL-3. closes odoo/odoo#74231 Related: odoo/enterprise#19850 Related: odoo/design-themes#43 Signed-off-by: Xavier Dollé (xdo) <xdo@odoo.com>

view details

Andrea Grazioso (agr-odoo)

commit sha d783ab83c5420e988ccd62691fc8a800978dcac8

[FIX] web: fix property assignment in pivot view Sales > Reporting > Sales Select the measure "Customer (count)" TypeError: Cannot add property group_operator, object is not extensible As the object is immutable we need to workaround the assignment. The previous fix 35967fabd54f596fa75fb2db7fbb1cfc5d7c8da9 will be moved in the `documents_spreadsheet` code opw-2606424 closes odoo/odoo#74211 Related: odoo/enterprise#19859 Signed-off-by: Nicolas Lempereur (nle) <nle@odoo.com>

view details

Swapnesh Shah

commit sha e8c5302e5cb11f185d1d5b1ef43ab641b2be6f76

[FIX] website: do not allow to create/edit views Before this commit, User was allowed to create new records from form view through Graph view' action. Since we do not have a way to prevent opening form view from Graph and also we should not Introduce new form view on stable version. With this commit, we are disabling create/edit/copy from action. closes odoo/odoo#70820 Signed-off-by: Romain Derie <rdeodoo@users.noreply.github.com>

view details

Anh Thao Pham (pta)

commit sha fb13be1bcdc0731d56eb1d1d22a05584ca7e3d68

[FIX] hr_timesheet: fix incorrect company on timesheet report - Create 2 companies (i.e. Company A & Company B) - Create user with access to both companies and default company set to Company B - Log with created user - Switch to Company A - Go to Project and create a new Project (i.e. Project X) - Go to Timesheets and add a line for Project X - Display all timesheets in list view - Select created timesheet and print "Timesheet Entries" Logo and address printed on timesheet report are from Company B. Company used for timesheet report is default company of current user. This fix will use company linked to the project if it is unique. Otherwise, it will use current company. opw-2502182 opw-2509463 closes odoo/odoo#74265 X-original-commit: 0812641544d49746d111ca4bb88a2091bf0dd6c8 Signed-off-by: LTU-Odoo <IT-Ideas@users.noreply.github.com>

view details

Ivan Yelizariev

commit sha ce487c920c777735e5e7e46ee131cb18dfc5c9fc

[FIX] product: speed up _get_possible_combinations Excluding non-active records decreases number of combinations generated in _cartesian_product. The excluded combinations have to be rejected anyway [1], so don't waste time on it. STEPS: * activate "Product Configurator" * create a product with many attributes * make some `product.template.attribute.value` inactive (ptav_active = False): ** create a sale order with that value (e.g. color "Black" in "Customizable Desk (CONFIG)") ** delete that value in `product.template` form (tab "Variants") * add the product to a sale order * RESULT: `_cartesian_product` doesn't generates combination with archived attribute [1] https://github.com/odoo/odoo/blob/f9d26509a714ecd290c42e1d58e416bb01268447/addons/product/models/product_template.py#L839-L841 --- opw-2540675 closes odoo/odoo#74119 Signed-off-by: Ivan Yelizariev // IEL <yelizariev@users.noreply.github.com>

view details

Laurent Smet

commit sha 49d1dbbb74ea97e4337fe1af3b8074dc9146143c

[FIX] account: Fix tag_ids when refunding an invoice with tax affecting base A tax line affecting the base of subsequent taxes is a line having some values in 'tax_ids' & 'tag_ids'. When creating a refund, tags was wrongly computed in this case. closes odoo/odoo#74223 Issue: 2596368 X-original-commit: 97ac9d1c8f6af3cfc43ca117b2b0359dd8233ad4 Signed-off-by: William André (wan) <wan@odoo.com> Signed-off-by: Laurent Smet <smetl@users.noreply.github.com>

view details

Achraf (abz)

commit sha 7fd4dea0af1917b82bc92d77c641672a8fc799f4

[FIX] account: Add layout to action send and print When sending the same invoice from Invoices > list view > select an invoice > action > Send and print, the email received by the client does not contain the header and the link to the invoice This PR adds the custom_layout attribute to the context of "Send & Print" action opw-2544654 closes odoo/odoo#74250 Signed-off-by: Josse Colpaert <jco@openerp.com>

view details

wan

commit sha 56f7afb253da6560cddae121f5b6cdab3e3b1c6e

[IMP] account: warn when the sequence format changed Explain the situation when a manual change has been done to the sequence of `account.move`. This was needed because some user didn't realize that they changed the sequence, and when they realized it, it had polluted multiple numbers after that. closes odoo/odoo#70941 Signed-off-by: Laurent Smet <smetl@users.noreply.github.com>

view details

Gorash

commit sha c29060c80e987edcfbeeaa7824540583de88f8ed

[FIX] web: avoid a scrollbar when a carousel is added in pages On Chrome, the browser displayed an horizontal scrollbar because the sr-only item inside the 'next' arrow was positioned absolutely, outside of the arrow, and thus outside of the window. This happened for the website carousel snippet when added in pages for instance. opw-2585526 closes odoo/odoo#74306 X-original-commit: 5bb454521f272fd2b4dd670eb2e9bf7173aa6b28 Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>

view details

Andrea Grazioso (agr-odoo)

commit sha ac9975d0eb50f39c6e42bc7a94761c4e34e92085

[FIX] mrp: fix recursive procurement handling in orderpoint Have 3 products: - Product A, manufactured from Product B, RR min 20 max 200 - Product B, manufactured from Product C, RR min 20 max 200 - Product C, stored, not manufactured, RR min 20 max 200 1. When triggering the scheduler, reordering rule are evaluated in batch, so procurements will be generated both for A and B. 2. The manufacture orders are created from procurement values: 2.A When manufacturing A, B is needed: the RR is triggered again and will evaluate again ALL the quantity needed for B (400, including the quantity already processed at step 1, but not yet written in a MO) 2.B Manufacture order for B is created from procurement values at step1, creating a MO for another 200 units We end up manufacturing 600 instead of 400 of Product B Fix by partially backporting bf5e1debf9c684c1bbf3ca440a87001fd7faf9fa along with a test opw-2509399 closes odoo/odoo#74314 Signed-off-by: Arnold Moyaux <amoyaux@users.noreply.github.com>

view details

Pierre Masereel

commit sha 7504dd34557968b0ecfea0d5d2b0025516d1dda5

[FIX] pos_restaurant: don't mark order as printed When the final receipt of an order is printed, the order is marked as printed, as it can be then removed, and nothing can be added to it anymore. When the Bill is printed, we should not mark it as printed, as there can be some modifications made after the bill is printed. So as the bill receipt is an inherited object from the final receipt, we have to change the behavior for the bill receipt to not mark the order as printed. OPW-2555272 closes odoo/odoo#74317 Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>

view details

JordiMForgeFlow

commit sha a31c267c3a79cd1b33f8245211417df358061563

[FIX] sale_mrp: filter cancelled moves when getting the related BoM The current behaviour does not filter the cancelled moves when getting the related BoM. This implies that, if a new BoM is created for the same product but with some changes, and the original delivery is cancelled, the sale order line will still consider the previous BoM. This causes that the relevant_bom ends up having more than one BoM, which should not be the expected result. After the fix, the cancelled moves will not be considered, as this is what should be expected from cancelled operations. closes odoo/odoo#74243 X-original-commit: 1e2feaa2851fa07018b912e6536585998487b5ab Signed-off-by: William Henrotin <Whenrow@users.noreply.github.com>

view details

Florent de Labarre

commit sha 59ac8d891de6e20604494d6cfc6fc357a88d226c

[FIX] stock: bypass optionnal delay description Fine tuning of https://github.com/odoo/odoo/commit/c7b32e0795bc1573d81563f31a75fa44c64b39c2 closes odoo/odoo#74004 Signed-off-by: William Henrotin <Whenrow@users.noreply.github.com>

view details

prro-odoo

commit sha db5617a05de41f01dee373276e3de519c268d182

[FIX] delivery: demo Delivery Products pulled into invoice How to reproduce the problem: - Install the delivery module - Create an SO and add a product. Click on Add Shipping. - Choose one of the demo Shipping methods - Deliver the main product. - Create an invoice: the Delivery Product is not present in the invoice, unless previously manually set as delivered in the SO. Cause of the problem : the demo values were having their Invoicing Policy set to Delivered Quantity instead of Ordered Quantity (due to the Sale app changing the default Invoicing Policy in 14.0) Solution : The demo products now have their Invoicing Policy set to Ordered Quantity manually. No further modification are needed in the creation of Delivery Products, as they have the correct values (when created from the Shipping Method form) opw-2496202 closes odoo/odoo#74349 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>

view details

Laurent Smet

commit sha 03f83eb87da00938b9d2df78651c1e06cf8a6d58

[FIX] account: Allow editing bank statement balances in 'processing' state When using the online synchronization, you could have a wrong balance in 'processing' state. In that case, don't force the user to reset the whole statement to 'open' and allow him to edit balances directly. closes odoo/odoo#74093 Task: 2606857 Signed-off-by: William André (wan) <wan@odoo.com>

view details

Gorash

commit sha 997c8f1b9e7b627ae4b27356c77c6e78ac75cb77

[FIX] website: avoid traceback when going to options of some themes Issue: traceback when website editor is entered and theme options are clicked on themes using an unknown-to-the-editor font family (see for the theme repo fix for such an example). opw-2559735 closes odoo/odoo#74294 Related: odoo/design-themes#268 Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>

view details

push time in 24 days

create barnchakretion/delivery-carrier

branch : 14-delivery-roulier-no-rate-shipment

created branch time in 24 days

issue commentOCA/delivery-carrier

[14.0] [RunBot] Can't make Colissimo (delivery_roulier_laposte_fr) work

Hello @delkano I checked and it seem we have an incompatibility for now with the website_sale_delivery module. Indeed, the module for la poste is made to generate carrier labels, but it does not get the price of the delivery. Laposte does not provide this or at least, it has not been implemented.

I'll make a PR to avoid the failure in that case and I'll check if the README has to be improved to specify clearly that the module does not provide a feature to get the price from the carrier. I think such a module https://github.com/OCA/delivery-carrier/tree/13.0/delivery_price_method could be usefull to still get the price from a grid in that case.

delkano

comment created time in 24 days

pull request commentOCA/account-reconcile

[14][MIG] account_move_base_import

@rvalyi Thanks for the merge try. It seems it failed though, I just rebased it in case it solve the issue Could you try again?

florian-dacosta

comment created time in a month