When computing the duration to close or to open a lead, do not use some kind of complex computation with working days. It does not make sense to use the number of intervals with the number of days. The computation was incorrect and very slow.
Replaced by simple calendar delta.
* fix crawler to discard URL fragments before deduplicating and crawling
* fix website_forum links which should not be links (either because their urls
are JSON-RPC methods or because their urls are side-effecting
* remove stray print statements
* side-improvements (simplifications) to some methods
also do some trivial cleanup/simplification of website_crm while at it:
* Initialize a dict directly via literal
* Use straightforward dict copy instead of whatever that convoluted crap was
* Use gencomp for set creation
* Lift a pair of keysets to the original dict creation
* move URLs of purely-JS-hook <a> to data-href so the crawler does not try to
access them (they're JSON-RPC endpoints...)
* replace side-effecting links (...) by styled buttons
* fix crawler to not take fragments in account when deduplicating and
navigating URLs
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
Richard Mathot (OpenERP)