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.

Sign up for GitHub

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

Jump to bottom

[16.0] date_range lost compatibility with web_advanced_search #722

Closed
kikopeiro opened this issue Sep 13, 2023 · 2 comments · Fixed by #723
Closed

[16.0] date_range lost compatibility with web_advanced_search #722

kikopeiro opened this issue Sep 13, 2023 · 2 comments · Fixed by #723
Labels
bug

Comments

@kikopeiro
Copy link
Contributor

Module

date_range

Describe the bug

After #717 web_advanced_search is not working properly, throws this error

OwlError: An error occured in the owl lifecycle (see this Error's "cause" property)
    at handleError (https://XXXXXXXXXXXXXXXXXX/web/assets/1122-191e1e2/web.assets_common.min.js:1472:101)
    at owl.App.handleError (https://XXXXXXXXXXXXXXXXXX/web/assets/1122-191e1e2/web.assets_common.min.js:2098:29)
    at RootFiber._render (https://XXXXXXXXXXXXXXXXXX/web/assets/1122-191e1e2/web.assets_common.min.js:1497:19)
    at RootFiber.render (https://XXXXXXXXXXXXXXXXXX/web/assets/1122-191e1e2/web.assets_common.min.js:1495:6)
    at ComponentNode.render (https://XXXXXXXXXXXXXXXXXX/web/assets/1122-191e1e2/web.assets_common.min.js:1571:56)

Caused by: TypeError: Cannot read properties of undefined (reading '0')
    at CustomFilterItem.setDefaultValue (https://XXXXXXXXXXXXXXXXXX/web/assets/1167-8cb4da3/web.assets_backend.min.js:1837:154)
    at CustomFilterItem.setDefaultValue (https://XXXXXXXXXXXXXXXXXX/web/assets/1167-8cb4da3/web.assets_backend.min.js:15435:459)
    at setDefaultValue (patch date_range.CustomFilterItem) (https://XXXXXXXXXXXXXXXXXX/web/assets/1167-8cb4da3/web.assets_backend.min.js:1657:22)
    at CustomFilterItem.setDefaultValue (https://XXXXXXXXXXXXXXXXXX/web/assets/1167-8cb4da3/web.assets_backend.min.js:15235:579)
    at setDefaultValue (patch web_advanced_search.CustomFilterItem) (https://XXXXXXXXXXXXXXXXXX/web/assets/1167-8cb4da3/web.assets_backend.min.js:1657:22)
    at CustomFilterItem.addNewCondition (https://XXXXXXXXXXXXXXXXXX/web/assets/1167-8cb4da3/web.assets_backend.min.js:1835:155)
    at CustomFilterItem.setup (https://XXXXXXXXXXXXXXXXXX/web/assets/1167-8cb4da3/web.assets_backend.min.js:1834:392)
    at CustomFilterItem.setup (https://XXXXXXXXXXXXXXXXXX/web/assets/1167-8cb4da3/web.assets_backend.min.js:15434:484)
    at setup (patch date_range.CustomFilterItem) (https://XXXXXXXXXXXXXXXXXX/web/assets/1167-8cb4da3/web.assets_backend.min.js:1657:22)
    at CustomFilterItem.setup (https://XXXXXXXXXXXXXXXXXX/web/assets/1167-8cb4da3/web.assets_backend.min.js:15235:421)

To Reproduce

Affected versions:

Steps to reproduce the behavior:

  1. with date_range and web_advanced_search installed
  2. On valuation report (stock_account) Inventory> Reporting>Valuation (similar response could have with other model )
  3. Click inside "Filters" and move your mouse between "Group By" and "Filters"
Peek.2023-09-13.14-47.mp4

CC @CarlosRoca13
@kikopeiro kikopeiro added the bug label Sep 13, 2023
@kikopeiro kikopeiro changed the title [16.0] date_range lose compatibility with web_advanced_search [16.0] date_range lost compatibility with web_advanced_search Sep 13, 2023
@pedrobaeza pedrobaeza mentioned this issue Sep 13, 2023
Closed
@pedrobaeza
Copy link
Member

He is on holidays, so please research the possible fix.

hugosantosred added a commit to factorlibre/server-ux that referenced this issue Sep 13, 2023
@hugosantosred
[FIX] Avoid redefinition of this.OPERATORS as a new object
3c4e47b 
This causes problems with the inheritance of this.OPERATORS
from other addons, if new operators are added

Fixes OCA#722
@hugosantosred hugosantosred mentioned this issue Sep 13, 2023
Merged
hugosantosred added a commit to factorlibre/server-ux that referenced this issue Sep 14, 2023
@hugosantosred
[FIX] Avoid redefinition of this.OPERATORS as a new object
55f146a 
This causes problems with the inheritance of this.OPERATORS
from other addons, if new operators are added

Fixes OCA#722
@pedrobaeza pedrobaeza linked a pull request Sep 14, 2023 that will close this issue
[16.0][FIX] date_range: Avoid redefinition of this.OPERATORS as a new object #723
Merged
@kikopeiro
Copy link
Contributor Author

Perfect! This issue seems that have been fixed!

Thanks @hugosantosred

ramiadavid pushed a commit to ramiadavid/server-ux that referenced this issue Nov 26, 2023
@hugosantosred @ramiadavid
[FIX] Avoid redefinition of this.OPERATORS as a new object
ce5f387 
This causes problems with the inheritance of this.OPERATORS
from other addons, if new operators are added

Fixes OCA#722
agyamuta pushed a commit to ursais/server-ux that referenced this issue Dec 14, 2023
@hugosantosred @agyamuta
[FIX] Avoid redefinition of this.OPERATORS as a new object
19c0fc6 
This causes problems with the inheritance of this.OPERATORS
from other addons, if new operators are added

Fixes OCA#722
eLBati pushed a commit to eLBati/server-ux that referenced this issue Sep 12, 2024
@hugosantosred @eLBati
[FIX] Avoid redefinition of this.OPERATORS as a new object
84ee887 
This causes problems with the inheritance of this.OPERATORS
from other addons, if new operators are added

Fixes OCA#722
Kimkhoi3010 pushed a commit to Kimkhoi3010/server-ux that referenced this issue Sep 25, 2024
@hugosantosred @Kimkhoi3010
[FIX] Avoid redefinition of this.OPERATORS as a new object
2e35436 
This causes problems with the inheritance of this.OPERATORS
from other addons, if new operators are added

Fixes OCA#722
Kimkhoi3010 pushed a commit to Kimkhoi3010/server-ux that referenced this issue Sep 27, 2024
@hugosantosred @Kimkhoi3010
[FIX] Avoid redefinition of this.OPERATORS as a new object
64c256e 
This causes problems with the inheritance of this.OPERATORS
from other addons, if new operators are added

Fixes OCA#722
BertVGroenendael pushed a commit to DynAppsNV/server-ux that referenced this issue Oct 16, 2024
@hugosantosred @BertVGroenendael
[FIX] Avoid redefinition of this.OPERATORS as a new object
7b8a489 
This causes problems with the inheritance of this.OPERATORS
from other addons, if new operators are added

Fixes OCA#722
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[16.0][FIX] date_range: Avoid redefinition of this.OPERATORS as a new object factorlibre/server-ux
2 participants
@kikopeiro @pedrobaeza