- Use less instead of sass
- Use class name of both old and new designs
- Small CSS tweaks to support both designs
- JS compatibility fixes + a little cleanup
- The ctrl-enter shortcut only reconciles balanced entries
* fix a crash when grouping on non-many2one fields (due to the
group.values object being not initialized)
* display correct label when grouping on selection fields
We should have a better way to deal with fields differences. There is
this weird concept called "abstraction", which could be applied and
would allow everyone to focus on their business and not on dealing with
this, but that would probably not fit with our codebase.
Many2One fields were broken in views opened by default in edit mode, since rev.
a0ddaf8. The autocomplete widget was appended to the DOM at
'.oe_application > *:visible:last', but since the mentionned rev., the views
are rendered in fragments detached from the DOM, and once they are ready, the
old content is detached and the new one is attached instead. It means that by
appending the autocomplete widget within '.oe_application > *:visible:last',
it is detached from the DOM with the previous content, and Many2One fields can
thus not work.
This rev. simply removes the appendTo option of autocomplete, so that the
widget is directly appended to the body.
Also updates a tour's selector matching an autocomplete ul as it isn't inside
the .modal anymore.
* Correct inheritance of async method
* Correct calls to do_hide/show
* Fetch the template in `willStart`
* Correct bootstrap structure for the layout, remove useless branding
and dom depth
* Each planner page is now in its own bootstrap grid
* Compatibility between both webclients
This introduces a new way to define web_planners. They now take the
following form:
<template id="project_planner">
<t t-call="web_planner.pages">
<t t-call="web_planner.category">
<t t-set="menu_categorytitle" t-value="'Prepare'"/>
<t t-set="menu_categoryclasses" t-value="'fa-flag-checkered'"/>
<t t-call="web_planner.page">
<t t-set="page_title" t-value="'Welcome'"/>
<t t-set="hide_mark_as_done" t-value="True"/>
<t t-set="hide_from_menu" t-value="True"/>
<!-- content here -->
</t>
</t>
</template>
The menu is not manually created anymore, it is automatically generated.
Pages do not have to be part of a category and can just be defined as
children of web_planner.pages. A page can have hide_mark_as_done and
hide_from_menu, these are optional and will both default to False when
omitted.
Allows you to set deferred revenue categories on your contracts and contract templates; contracts will set their revenue category on the lines of their invoices
- add contract_type field on account.analytic.account and real_quantity on account.analytic.invoice.line
- refactor contract form and list views for better clarity (hide unnecessary fields depending on the type of contract)
- divide account_analityc_account class according to contract type for future work
- divide contract template menu in 3 menus depending on contract_type
- add on_change_uom behaviour on account recurring lines
- rewrite tests in python
- add new report (pivot & graph)
- end date of contract is now computed from the template recurring rules
- small fixes & usability improvements
for compatibility with the enterprise edition.
Also add type=button as the type attribute should always be specified for the
<button> element (different browsers may use different default types).
Someone really smart decided to change web_kanban by moving something
from web to web_kanban. This makes sense, but it is a problem because
the code in web is not shared between enterprise and community, but
web_kanban is shared.
Also, it was put in kanban_view. If we have a module system in
javascript, is might be a good idea to use it.
So, this commit moves the code in a new file, and update the code to
the last version from enterprise. Yay for two codebase in parallel.
When the max seats available is set to 0, there should not be a limit to
the seats available.
Previously this was not taken into account in the frontend event ticket
sale, so an event would appear to be sold out.
fixes#6999
opw-645542
The removed code stood for optional dependencies to im_chat module (integrate 'odoo support' in chat contact list). Since the new javascript system (require and define) doesn't allow optional dependency, this code will always crash if im_chat was not installed, causing warning in the js console.
The 'im_livechat.im_livechat' js dependency is a wrong conversion of the code to the new js system. im_livechat is not a dependency, but is loaded from OpenERP service server. Since this one runs under odoo-saas6 version, im_odoo_support will load js code fomr this version, and so require to use 'openerp' js object instead of the 'require' dependency.
boot.js log:
* ``Missing dependencies``:
These modules do not appear in the page. It is possible that the JavaScript
file is not in the page or that the module name is wrong
* ``Failed modules``:
A javascript error is detected
* ``Rejected modules``:
The module returns a rejected deferred. It (and its dependent modules) is not
loaded.
* ``Rejected linked modules``:
Modules who depend on a rejected module
* ``Non loaded modules``:
Modules who depend on a missing or a failed module
Each module can return a deferred. In that case, the module is marked as loaded
only when the deferred is resolved, and its value is equal to the resolved value.
The module can be rejected (unloaded). This will be logged in the console as info.
Remove if_dom_contains from the website, the modules return a rejected deferred if
the DOM doesn't contains the seleted values.
Arthur Maniet