* remove ZeroClipboard, pain to test locally and deployment didn't work
right due to needing absolute path to the swf always
* remove the clipboard alteration on the fly, behaves oddly and can be
confusing
* add an explicit button to expand and collapse the setup content
* fixup some styling
The first line having the globalisation code is the globalized amount,
then the next line having this same globalisation code
is the last line of the globalisation (the last children).
The first line must no be included in the bank statement,
but the last line must (as this is a real children line)
This is a regression of commit: cbc52f80eb
Official doc concerning globalization code:
The value which is mentioned (1 to 9), specifies the hierarchy level of the
globalisation of which this record is the first.
The same code will be repeated at the end of the globalisation
courtesy of mva. This adds the weekday function to date objects in
pyeval. This will be useful for adding better filters (such as this
week) in the searchview.
All the translation files from the email_template module are merged into the mail module.
Comments are untouched because there are extracted from the .pot file
crm_lead:
overwritte create and write from crm_lead to force assign_date to be computed according to the field user_id is updated.
Else when the assignation was done manually, this field was not updated and so the lead not added in the instant pipe from the saleman (section_user)
sales_team:
Add context when assignation is done by cron to avoid to spam the sales. Notification of assignation will be only done via a log on the lead/opportunity.
Don't force to write assign date since write of crm_lead is overwritted to do it
Misc improve - check that leads exists before to make useless call to browse/write on nothing
Move section_user before the use of this one in a many2many, else demo data are not installable because field id is never created in db. (same 'issue' that https://github.com/odoo/odoo/issues/2386)
Add a cron to compute score each hours
Add merge pageview and merge (clean) score when we merge opportunities via merge_opportunities/merge_dependencies
Score the lead after the assignation to salesteam. Because when we assign to salesteam, sometimes we call the method merge_opportunities which one delete old scores on this lead, all score rules needs to be recomputed since the fields have been updated. So we compute now the score not at starting, but between assignation to salesteam and salesman.
- delete a forgotten print
- allow pg_dump custom dumps to be larger than the available disk size, the
previous commit allowed dumps to be larger than memory, this one remove this
limitation. zip dumps are still limited to by the disk size.
- let the user choose between the pg_dump custom format or the zip format including the filestore
- use file objects to allow dumps larger than memory
- postgres subprocess invocation is now clean and thread-safe, we dont touch the local process environ anymore
- add a manifest to the zip dump format with version information about odoo, postgres (pg_dump doesnt output it) and modules
Avoid messing up actual output with logs. Useful when using odoo shell in a
pipeline. Example:
echo "for i in env['res.partner'].search([]): print i.email" | ./odoo.py shell -d master | xargs -n1 echo cmd
Christophe Simonis