diff --git a/web_advanced_search/README.rst b/web_advanced_search/README.rst index f9660708..edf0646d 100644 --- a/web_advanced_search/README.rst +++ b/web_advanced_search/README.rst @@ -75,6 +75,50 @@ Improvements to the search view in this addon: * Beautiful, human-readable, domain representation when adding an advanced filter +Changelog +========= + +11.0.1.0.2 (2018-10-31) +~~~~~~~~~~~~~~~~~~~~~~~ + +* Fix initialization of 1st domain node + + Sometime the dialog is not ready yet, like on EE version. + Hence when you inject the 1st domain node + the dialog must be already opened. + + [simahawk] + + +11.0.1.0.1 (2018-09-18) +~~~~~~~~~~~~~~~~~~~~~~~ + +* Fix `undefined` in x2m fields + + Before this patch, when searching with the "equals to" operator in any + x2many field, the searched parameter was always `undefined`. + + The problem was that the underlying field manager implementation was + treating those fields as x2many, while the widget used was the `one2many` + one. + + This patch simply mocks the underlying fake record to make think that + any relational field is always a `one2many`. This sets all pieces in + place and makes the field manager work as expected, and thus you can + search as expected too. + +* Make linter happy + + [Yajo] + + +11.0.1.0.0 (2018-07-20) +~~~~~~~~~~~~~~~~~~~~~~~ + +* Rename, refactor, migrate to v11 + + [Yajo] + Bug Tracker =========== @@ -93,6 +137,7 @@ Authors * Therp BV * Tecnativa +* Camptocamp Contributors ~~~~~~~~~~~~ @@ -102,6 +147,7 @@ Contributors * Jairo Llopis * Rami Alwafaie * Jose Mª Bernet +* Simone Orsi Maintainers ~~~~~~~~~~~ diff --git a/web_advanced_search/readme/HISTORY.rst b/web_advanced_search/readme/HISTORY.rst new file mode 100644 index 00000000..7b791ed9 --- /dev/null +++ b/web_advanced_search/readme/HISTORY.rst @@ -0,0 +1,40 @@ +11.0.1.0.2 (2018-10-31) +~~~~~~~~~~~~~~~~~~~~~~~ + +* Fix initialization of 1st domain node + + Sometime the dialog is not ready yet, like on EE version. + Hence when you inject the 1st domain node + the dialog must be already opened. + + [simahawk] + + +11.0.1.0.1 (2018-09-18) +~~~~~~~~~~~~~~~~~~~~~~~ + +* Fix `undefined` in x2m fields + + Before this patch, when searching with the "equals to" operator in any + x2many field, the searched parameter was always `undefined`. + + The problem was that the underlying field manager implementation was + treating those fields as x2many, while the widget used was the `one2many` + one. + + This patch simply mocks the underlying fake record to make think that + any relational field is always a `one2many`. This sets all pieces in + place and makes the field manager work as expected, and thus you can + search as expected too. + +* Make linter happy + + [Yajo] + + +11.0.1.0.0 (2018-07-20) +~~~~~~~~~~~~~~~~~~~~~~~ + +* Rename, refactor, migrate to v11 + + [Yajo] diff --git a/web_advanced_search/static/description/index.html b/web_advanced_search/static/description/index.html index 53cba64b..d53d19a3 100644 --- a/web_advanced_search/static/description/index.html +++ b/web_advanced_search/static/description/index.html @@ -372,19 +372,25 @@ ul.auto-toc {

Table of contents

-

Usage

+

Usage

To use this module, you need to:

  • Open Filters in a search view
    • @@ -408,7 +414,7 @@ this indefinetely, so it is possible to search for moves belonging to a journal which has a user who is member of a certain group etc.

-

Known issues / Roadmap

+

Known issues / Roadmap

Improvements to the domain widget, not exclusively related to this addon:

  • Use relational widgets when filtering a relational field
    • @@ -425,8 +431,49 @@ advanced domain editor advanced filter
+
+

Changelog

+
+

11.0.1.0.2 (2018-10-31)

+
    +

  • Fix initialization of 1st domain node

    +

    Sometime the dialog is not ready yet, like on EE version. +Hence when you inject the 1st domain node +the dialog must be already opened.

    +

    [simahawk]

    +
    • +
+
+
+

11.0.1.0.1 (2018-09-18)

+
    +

  • Fix undefined in x2m fields

    +

    Before this patch, when searching with the “equals to” operator in any +x2many field, the searched parameter was always undefined.

    +

    The problem was that the underlying field manager implementation was +treating those fields as x2many, while the widget used was the one2many +one.

    +

    This patch simply mocks the underlying fake record to make think that +any relational field is always a one2many. This sets all pieces in +place and makes the field manager work as expected, and thus you can +search as expected too.

    +
    • +

  • Make linter happy

    +

    [Yajo]

    +
    • +
+
+
+

11.0.1.0.0 (2018-07-20)

+
    +

  • Rename, refactor, migrate to v11

    +

    [Yajo]

    +
    • +
+
+
-

Bug Tracker

+

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed @@ -434,26 +481,28 @@ If you spotted it first, help us smashing it by providing a detailed and welcome

Do not contact contributors directly about support or help with technical issues.

-

Credits

+

Credits

-

Authors

+

Authors

  • Therp BV
  • Tecnativa
    • +
  • Camptocamp
-

Maintainers

+

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose