Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REF] l10n_mx: using code instaed color in onchange t#8500 #234

Conversation

goliveirab
Copy link

Isuue: https://github.com/Vauxoo/mexico/issues/772
Avoiding use of 'color' field to change the tags.

Result

@goliveirab
Copy link
Author

goliveirab commented Aug 10, 2017

@luistorresm @moylop260 could you please check this..

qdp-odoo and others added 16 commits August 24, 2017 15:29
split fields_view_get() and used an abstact mixin class in place of of FormatAddress

[IMP] base: added a m2o field (ir.ui.view) on res.country to decide the layout of the form view to input addresses.
…ds inside the 'street' fields defined in base
… a list the city instead of a varchar field, when inputting addresses
…calized TIN number algorithm without forcing to prefix that number with the country code (which is weird for people).
When installing costa rican localization the partners titles has
a wrong reference to base module that cause a warning messge in
server log. In total the localization had 8 partners titles that
not exists in base which was removed the reference and another 2
that exists in base but not had any difference.

Courtesy of Vauxoo.

Closes odoo#15495
…oo#205)

Code extracted from saas-14:
https://github.com/Vauxoo/odoo/blob/de38d0262b17f8e55926ac051f685afca2a82804/addons/l10n_mx/data/fiscal_position_data.xml#L114-L124

[IMP] l10n_mx: Added lost data to fiscal positions (Vauxoo#215)

Fixed error "External ID not found in the system:
l10n_mx.account_fiscal_position_foreign" while parsing
/home/odoo/odoo-10.0/addons/l10n_mx/data/fiscal_position_data.xml:4
…ner form view

*street fields should be editable only if we modify the main partner address
*creating a res.city through the m2o should has default country and a domain
In base/res_partner.py, _fields_view_get calls _fields_view_get_address that could calls again
_fields_view_get in case of address_view_id is specified. That leads to issue in base_address_city
because the _fields_view_get_address method will replace two times the city field and then, we get
a view with two city_id fields.

see odoo#16870 for screenshots
…t.account issue#746 (Vauxoo#232)

* [REF] l10n_mx: Onchange delete tag_ids when you change code in account.account issue#746

* [REF] l10n_mx: using pipe
… lang (Vauxoo#236)

It was decided by Moylop to do this patch

FIX odoo#18363

- [  ] TODO- Remove this ugly fix after issue
  odoo#18363 be solved

  Odoo Ticket 766.489
Like the address_format could be changed by each country, this method
is required to append the field city_id in the views, to all country
address formats.

But if We need inherit the view to add a parameter in city or city_id,
WE need overwrite this method. Now, with this change, We only inherit
the view, and not all the method.
Copy link
Collaborator

@luistorresm luistorresm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@moylop260

This is the change that you hope?

Regards

@goliveirab
Copy link
Author

@moylop260
Any news/changes about this?

@moylop260
Copy link

Could you remember the rational of this change, please?

@goliveirab
Copy link
Author

The main purpouse here is to avoid using the field 'color' to filter de tags.

@moylop260
Copy link

Yes, the main description has that sentence.
But the why?

@goliveirab
Copy link
Author

The filter of the tags is made based in the color field, if the color changes then the method could not work as expected, so avoiding the use of that field may avoid that.

@moylop260
Copy link

Could you fix the conflicts, please?

@moylop260
Copy link

@nhomar
Do you define the previous version of this feature, We need your approval here, please

@luistorresm
Copy link
Collaborator

@goliveirab

Could you make a update of this branch, please?

@goliveirab goliveirab force-pushed the 10.0-onchange-delete-tag_ids-issue772-goliveirab branch from 787fcef to 84df3bf Compare September 1, 2017 00:31
@goliveirab
Copy link
Author

goliveirab commented Sep 1, 2017

@moylop260 could you please check it.
@luistorresm

@goliveirab
Copy link
Author

Is there any changes or request about this?
@moylop260
@luistorresm

# TODO: Remove this ugly fix, needed because es_419 lang is not
# supported by odoo yet.
# Remove this section after issue
# https://github.com/odoo/odoo/issues/18363 be solved.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Issue odoo#18363 is closed

@moylop260
Copy link

@goliveirab
I'm waiting @nhomar approval
from #234 (comment)

@luistorresm
Copy link
Collaborator

@moylop260

This PR has around of 8 months, and We do not have this problem.

You think that We could close it?

Regards

@moylop260 moylop260 closed this May 26, 2018
@luisg123v luisg123v deleted the 10.0-onchange-delete-tag_ids-issue772-goliveirab branch July 14, 2022 01:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants