Coming from a bug in web_settings_dashboard. Invited user didn't have any rights
when created from the dashboard, which was leading to an error.
This bug leaded to a new discussion. Better to have basic employee having user
rights for all main applications. For bigger entreprises there is an admin that
will carefully remove extra rights, if necessary. The target is small businesses,
it makes sense that every way to create a user gives the same result.
In conclusion, each new user has a full access to the applications by default
How is it implemented ?
We added an inactive default user which original access right to the groups
'base.group_user' and 'base.group_partner_manager' in base. Each
application will extend the default user's access right by adding the maximal
access right for this application.
On user creation, we will use by default the 'group_id' field from the default
user. We will in the same time remove the ugly 'default_groups_ref' key which
was passed sometimes in the context for some fields in some views, and sometimes
nothing.
So, the user can modify the access rights for the default user, but he should be
aware that removing project user access rights for a default user will prevent
a *created on the fly in a task* user will not be able to access the task.
- New filter "not cancelled" for attendees management
- No more readonly nor invisibility on "minimum number of seats"
- Event questions and mail scheduling have been put under an optional
tab
This commit adds a way to configure scheduled emails on events. It replaces
existing automatic emails at confirmation and subscription. It proposes to
configure some schedulers, based on subscription or event, using a template
and a configurable timedelta.
A cron is added that regularly checks for event mailing schedulers to execute
and launch them. The granularity of send emails is therefore limited to the
granularity of the cron, aka 1 hour.
[TEST] Added tests for this feature.
Also cleaned a bit event, country_id is now a pure related instead
of a computed field trying to be a related. Also removed default templates
on event category. Configuration in the event itself should be easy
enough for most use cases.
ir.rule records are in noupdate data blocks to let the admin
alter them without fear of them being reset at next update.
Other records such as groups are in normal mode, so they
can be updated whenever necessary
bzr revid: odo@openerp.com-20121218232001-t425t4hi7qbmsip2
event should not inherit anymore from crm.case.section: it's a new object
put a parent_id field to keep the hierarchy
sale team m2o is kept, but it's a widget=selection: The reply-to on the event is also filled when choosing a sale team
put domain on locaiton room: same country as selected location country
cost: rename in registration cost
demo data: not fixed date
maximum and minimum registration: return warning when we try to open an event that haven't not the requirements
Improved form view
bzr revid: hmo@tinyerp.com-20100715134144-lmfwa02wnsntdd9q
Event :
* Change button icon for all searchview.
* Develop 'group by partner' functionality in make invoice wizard of registration form.
* change yaml as per changes in make invoice wizard.
* remove 'List of register event' wizard and put link on in event form.
* ADD 'Send a new mail' button for mail
* Improve history functionality.
* add group : event/manager and event/subscriber.
Membership .
* merge two sql query in one repor_membership file.
* develop search view of that report.
* change icon for search view.
bzr revid: hmo@tinyerp.com-20100626101340-bt77wjb8ug3a3flj
dut-odoo