skip the inactivate employee in leaves summary
[FIX]Display answers in order by posted date in descending (latest to old)
Update holidays_summary_report.py

Add context to search method
Update holidays_summary_report.py
[FIX] portal: avoid errors during autovacuum

When the cron for autovacuum runs, the osv_memory objects are deleted. The portal.wizard.user object has a required field (wizard_id) linked to another osv_memory object (portal.user) which causes a traceback when the cron tries to delete portal.user object before the portal.wizard.user. opw 609918
[FIX] configuration file dbfilter's option has no effect

lp bug: https://launchpad.net/bugs/940439 fixed

bzr revid: fme@openerp.com-20140508075025-yszqmzie1z4n7l4j
Merge pull request #946 from joshuajan/7.0_hr_holidays_report_fix

skip the inactivate employee in leaves summary
[FIX]product: disable menu name come from report declaration.because it's called from wizard
[FIX] ir.model.fields: better unlink

When droping a column, remove also the relation table in case of custom m2m field.
The relation table needs to be dropped otherwise an unremovable constraint to the targetted table is kept (and anyway is not needed anymore).
Merge pull request #993 from odoo-dev/saas-5-issue-902

[MERGE][FIX] product: incomplete declaration of report pricelist
[FIX] Crm partner assign: Sort the partners by grade / published implemented. else the display are not explicit on website, because old order takes all the implemented partner but on website we display the number of reference published
[FIX] orm: better removal of custom m2m fields

orm: do not try to create ir.model.relation for custom m2m as self._module is either empty (for custom models), either the one of the last inheriting module (which is wrong). The field should be removed manually and should not be impacted by the uninstallation of modules. The removal of the relation table can be done when removing manually the custom field (see rev 6af3193).

ir.model: when removing a model, drop the table with the CASCADE instruction. This will remove left constraints from remaining m2m tables.
This means that dropping a table (either manually removing a custom model or uninstalling a module) will not drop the relation table for a custom m2m field. This is not ideal but better than the previous behaviour (which was to fail the DROP TABLE instruction and keep the table with a few columns and unconsistent data).
Changed the type of fields.date_order on purhcase.order object from date to datetime
[FIX] account_analytic_account: handle partners without fiscal position gracefully
[FIX] website: if the first menu refered to a website page and the route for this path is overwrited, the route is not used, the template has not the values of the route. (e.g. contact-us menu in first position if website_crm is installed)
[FIX] website_crm: the path '/crm/contactus' have an error if you does'nt use the website contact form or if you reload the page, insead of redirect to contact form.
[FIX] product: allow user to set price at template creation

The lst_price field on product.template is a related to list_price. As we do not allow to set a value for related fields at creation (see orm.py , L4180), we display the list_price instead (float field).
On the product.product form, we display the lst_price (function field, readonly) as we don't want to allow changing the template price from the product. opw 609497
Merge pull request #1021 from odoo-dev/saas-5-fix-routing-for-index-chm

[FIX] website: if the first menu referred to a website page and the route for this path is overwritten, the route is not used, the template has not the values of the route. (e.g. contact-us menu in first position if website_crm is installed)
[FIX] website_crm: the path '/crm/contactus' have an error if you doesn't use the website contact form or if you reload the page, instead of redirect to contact form.
[FIX] website: error for rendering of the sitemap template. qweb can't render the xmlns attribute.
[FIX] mass_mailing: load images in emails

The emails containing emails generated with the image widget have absolute path (src='/website/static/...'), adding <base> tag allows the mail client to load it correctly.