- removed unused categories, aka report designer, CRM and knowledge management
- renamed Warehouse to Inventory
- defined all user groups in base_security, instead of having most of them in
base_security and 3 others defined in other files. Portal, public and
partner_manager groups are now present in base_security. This uniformize
the declaration of groups and module categories.
- define a new Extra / Other category, holding those 3 groups, to ease the
classification and display
- rename Usability ot Extra Rights[IMP] base: config: module category cleaning
- removed unused categories, aka report designer, CRM and knowledge management
- renamed Warehouse to Inventory
- defined all user groups in base_security, instead of having most of them in
base_security and 3 others defined in other files. Portal, public and
partner_manager groups are now present in base_security. This uniformize
the declaration of groups and module categories.
- define a new Extra / Other category, holding those 3 groups, to ease the
classification and display
- rename Usability ot Extra Rights
When running the test_menu tour with phantomjs, there was an error when
calling customize_chart because classList is not supported on phantomjs.
The workaround is to use addClass() of jQuery instead.
Also add missing call to _super() in start(), and remove ignored arguments
passed to customize_chart().
Before this rev., lighter columns seemed larger than the other ones as
their background-color is the same as the webclient background-color.
This rev. removes the gaps between columns (margin is replaced by padding).
portal users into a mail.template.
A new field is used in the wizard_user model, that is the portal
user itself. It was not stored previously probably because of the
old wizard limitations (links to existing records). Storing it
directly eases the process of retrieving the portal user.
The biography of established users (with high karma) can be seen
with an expanded tooltip. This gives to users that participate
some kind of reward and gratitude of their work.
Among others small improvements :
- [event] remove automatic logging of new registrations on event; for big events
it produces only noise
- [event_sale] fix product creation from event management; better display of
address and date of the event
- [website_event_track] add a cancel state on the track model. The stat button
on the event shows only not-canceled state. Also added some tips.
proposal.
Instead of posting a chatter message with the post data + storing a blob on the track
store directly the various data on the track object itself.
Post a message on the event to warn a new track has been created.
Updated the track website view. Instead of storing a blob, rebuild a correct
and editable track view on the website.
Among various small fixes, some changes :
- correct computation of default sales team, located in sales_team with a
small code cleaning. Rely on this method everywhere it is necessary.
- add a configuration option to enable the use of leads in sales team;
otherwise it is hidden
- better display of alias in empty list help;
- add a menu for next activities, that are the opportunities with an action
whose deadline is near assigned to the current user;
- automatic update of aliases configuration on sales team, based on whether
they use leads and/or opportunities;
- add a wizard to log the lost reasong when deactivating a lead or an
opportunity
Client actions are wrapped into a container since rev. 4e24b816. However,
when opening a new action from a client action (i.e. when stacking over a
client action), the client action should be detached together with its
container. It wasn't the case as only the action was detached.
Since account_check_printing doesn't add a functionality without a 'concrete'
check printing module like l10n_us_check_printing, move tests to this module
The account_check_writing module offers the structure for other modules
to add check printing facilities (like l10n_us_check_printing), in and of
itself it brings no functionality.
In the old design, the widget container needs to take care of the
scrolling since it is not instanciated inside a oe-view-manager.
In the new design, the o_content takes care of scrolling so those CSS
rules are not required (and are even harmful, cropping popovers).
- scroll to the right when adding a new column
- apply style on column quick create card
- darken background color of odd columns in grouped mode
- remove some unused rules
- Ensure compatibility with both editions of web
- Use the Pager widget instead of re-implementing it
- Fix the use of Dialogs which was broken (wrong type of Dialog was used)
- Convert css into less
- Some js linting
The fold rule of kanban view hides all o_kanban_record,
so we need to put the tip inside one of them instead of
alongside them in order to have a proper folding behavior.
Previously, the tip stayed on top of everything when
the kanban column was folded.
- website_portal define a basic /my/home controller
- website_portal_sale extend it to display orders
- website_mail add a generic template to display chatter and post messages on pages
A new generic chatter template is available in website_mail
This template allows access rights escalation when some kind of token or uuid
is available on the model or if you use the object_shasign function in the
main controller of website_maill to generate a cryptographic signature to allow
commenting on any object.
To use this chatter, you need to make a t-call to website_maill.thread in your
template after having set the following variables:
- chatter_object: the browserecord of the mail_thread object (mandatory)
- token: if you use a token system (optional)
- token_field: name of the field that stores the token on your object (optional)
- sha_in: if you use a shasign to allow public comment (optional)
- nosubscribe: set False if you want the partner to be set as follower of the object (optional)
- message_type, subtype: see message_post in mail_thread.py
Split of website_portal into a generic (and mostly empty) website_portal and a sales-related website_portal_sale (sales order, quotes, invoices)
This allows other modules to extend website_portal without depending on sales
- remove tags translatability
- add unique constraints
- res.partner.category is kept until we remove the parent_store test.
- hr remove tag parenthood
- hr remove unsed views and menu
When storing files send in POST in session_store, store them with a
name based on the name of the session file itself (ease matching sessions
and files for debugging purpose)
Thibault Delavallée