- Jun 16, 2014
-
-
Christophe Matthieu authored
-
Fabien Meghazi authored
[FIX] new style for default form views
-
Fabien Meghazi authored
-
Mansi Kariya authored
Added standard and Schedule-vi chart with taxes removed private and public chart with taxes files
-
Thibault Delavallée authored
[FIX] issues when uninstalling modules: unlink ir.action.todo which are related to actions which will be deleted (fix issues when uninstalling modules) + check for menu existence before displaying need action
-
Olivier Dony authored
[FIX] graph/pivot tables: remove non stored fields from available measures
-
- Jun 13, 2014
-
-
Martin Trigaux authored
-
Martin Trigaux authored
-
Géry Debongnie authored
Non stored functional fields cannot be grouped by read_group, so it is useless, and even harmful, to display them in the measure list (in graph view).
-
- Jun 12, 2014
-
-
Olivier Dony authored
-
Olivier Dony authored
-
Richard Mathot authored
[FIX] survey: ordering of questions/labels was buggy
-
Richard Mathot authored
-
Thibault Delavallée authored
-
Géry Debongnie authored
[MERGP] Inline Searchview This task split the searchview in two parts: SearchView and SearchViewDrawer. The drawer is displayed inside the main view and the searchview stays in place. It also changes the scrolling behavior of the web client: the main view area can scroll without affecting the UI (so the various menus stays in place) Because of this, other large changes have been made: the drawer has been redesigned, the Custom Filter widget has been split in two (Custom Report and SaveCurrentFilter), the main view is now scrollable, so the UI stays in place and only the view can change The text 'Group By...' has been changed into 'Group By' (most addons had to be modified) bootstrap classes are used when it makes sense (for example, badge) the left menu is also scrollable (separately from the main view) It is likely that some stupid bugs have been introduced. Please don't hurt me.
-
Fabien Meghazi authored
[IMP] Form views default version is now 7.0
-
Thibault Delavallée authored
[FIX] [IMP] website_forum: usability fix: moved answers / votes column below the text on mobile displays, because it takes too much place and restrict the place left for the text. By the way some custom css has been removed, replaced by bootstrap css.
-
Géry Debongnie authored
hopefully, it should allow IE9 to correctly display the web client content
-
Fabien Meghazi authored
-
Olivier Dony authored
-
Olivier Dony authored
-
Jeremy Kersten authored
[FIX] Account, l10nbe - Respect name_search operator for account.account, so = really work as expected. Also fix data file in l10nbe which was relying on the old implementation.
-
Jeremy Kersten authored
[FIX] l10n-be data - Be more accurate in the belgium data. All accounts have by default a right padding of 0 to be on 6 char, so the csv need to have the accounts on 6 char since with have removed the default replacement of "=" by "=like" to allow the manual import
-
Jeremy Kersten authored
-
Denis Ledoux authored
sale_order module override state field of sale.oder (sale.sale.py) and forgot to reset the track_visibility, therefore sale orders state changes are no longer tracked once this module installed.
-
Christophe Simonis authored
-
Dimitri del Marmol authored
tested local install with saas5 version
-
Géry Debongnie authored
-
Géry Debongnie authored
and possibly also in IE
-
Richard Mathot authored
-
Fabien Meghazi authored
-
Nicolas Seinlet authored
- added a missing dependency (qrcode) - url for local test with port 8069 - check if pip2 needs to be used
-
Fabien Meghazi authored
-
Fabien Meghazi authored
[ADD] Pseudo `clone` mode for <templates> using primary="True"
-
Richard Mathot authored
-
- Jun 11, 2014
-
-
Olivier Dony authored
This will make sure already processed rules are persisted in case a timeout occurs while processing the next ones, ensuring that *some* progress can be made in most cases.
-
Olivier Dony authored
A safety guard already in place prevents the recursive trigger of rules while another rule is being executed, as a simple measure to prevent endless loops. This guard was missing when processing time-based rules.
-
Olivier Dony authored
A programming error introduced at rco@openerp.com-20121220142445-emzzvhlw400q37c9 fails to properly check when a rule has already been executed in the past. Time-based rules should only be executed if the trigger date is in the past and: - either they never executed before - or the last execution date is older than the trigger date
-
Olivier Dony authored
Executing a rule always updates the `last_run` value, which would always force a useless registry reload to occur. Only signal the change if the rule applies to a model that was not previoulsy monitored for base action rules.
-
Christophe Simonis authored
This merge is missing some files. This reverts commit dfa54b59, reversing changes made to df78e58d.
-