At the time of the context_wo_lang patch (7.0 revision 6577), the orm did not keep the language in copy_data, this patch intended to be more consistent.
Since server revision 5146 7.0, the new behaviour is to use the translated version in copy_data. Removign this change will be more consistent with the orm.
The expected behaviour is now the following:
In user lang: translated product name + translated '(copy)'
In other lang: same as original product
bzr revid: mat@openerp.com-20140508153236-00gxvxenh8fy03km
At the time of the context_wo_lang patch (7.0 revision 6577), the orm did not keep the language in copy_data, this patch intended to be more consistent.
Since server revision 5146 7.0, the new behaviour is to use the translated version in copy_data. Removign this change will be more consistent with the orm.
The expected behaviour is now the following:
In user lang: translated product name + translated '(copy)'
In other lang: same as original product
lp bug: https://launchpad.net/bugs/1159913 fixed
bzr revid: mat@openerp.com-20140508134937-7cbja3vsv311z5j4
The number of leave requests left is based on the employee_id key in the context, when displaying the status of an hr.holidays we don't have the information in the name_get of the hr.holidays.status.
The fallback on the number of employees is done with the uid but we can not rely on it as well as the name_get on m2o field is done with superuser_id.
bzr revid: mat@openerp.com-20140508124946-ttyr84iajg9q6l0y
The additional parameters were made to avoid overwriting values when changing of template.
As we can not add parameters in only one module, we overwrite values only for not saved records.
This mitigates the overwrite while not changing the API.
bzr revid: mat@openerp.com-20140508083948-gkk7d1250a8znhlt
Instead of raising an exception (which only interupt the call of the onchange methods), return a dictionnary to set the forbidden partner or product to an empty value.
The call is not blocking in a way to forbid creating a record that uses this partner/product but it is not possible to select it through the web interface.
bzr revid: mat@openerp.com-20140507113940-d8iynfl1lcskht63
Instead of raising an exception (which only interupt the call of the onchange methods), return a dictionnary to set the forbidden partner or product to an empty value.
The call is not blocking in a way it forbid to create a record that uses this partner/product but it make it not possible to select it through the web interface.
bzr revid: mat@openerp.com-20140507102550-sms5nbf0u7pdkci9
The body is the field used to actually display the 'log in with ...'
As not shown in the view, when adding a new provider, this field was empty and therefore wasnt visible on the login form...
bzr revid: dle@openerp.com-20140507102414-vz7ur7zvh4ptuk2e
- fixed reopen link that was broken (python code appearing)
- fixed close link that was leading to a 500 error due to post -> question
- fixed link to question author, was redirecting to the current user
- fixed displayed number of questions in the forum, now displaying actual question
number, not number of displayed questions in the page
- improved guidelines: added link back to the forum
- fixed tags display: now by posts_count desc, unused tags are not shown
- users are now displayed by desc karma
- converting a comment as an answer does not allow to create a new answer if another
one by uid is already present, it just moves the comment
- display tag name in 'filter' bar when filtering on a tag
- display active tag in a blue color
- order answers: correct first, then most upvoted
bzr revid: tde@openerp.com-20140506150145-c1uvlaqtyvkjcwea
- gamification.goal do not depends of mail.thread anymore (message posting and fields tracking was slow)
- check reward works in batch mode
- fix update method that did not reset variable in loop
- when the cron is running commit after each goal definition update
bzr revid: mat@openerp.com-20140506145623-476s3q3vxoybya77
- display tag name in 'filter' bar when filtering on a tag
- display active tag in a blue color
- order answers: correct first, then most upvoted
bzr revid: tde@openerp.com-20140506123001-fz5gt6i9zw6ondcu
Removing the inheritance to mail.thread will avoid posting message at creation and other tracking mechanism at each write. Updating a challenge with a large number of users will be significantly faster.
bzr revid: mat@openerp.com-20140506093716-xvpe1n2ase2zix0v
- fixed reopen link that was broken (python code appearing)
- fixed close link that was leading to a 500 error due to post -> question
- fixed link to question author, was redirecting to the current user
- fixed displayed number of questions in the forum, now displaying actual question
number, not number of displayed questions in the page
- improved guidelines: added link back to the forum
- fixed tags display: now by posts_count desc, unused tags are not shown
- users are now displayed by desc karma
- converting a comment as an answer does not allow to create a new answer if another
one by uid is already present, it just moves the comment
bzr revid: tde@openerp.com-20140505154523-6dld9sfm0nc0oulu
Martin Trigaux