Shouldn't allow to select view in the location field. Otherwise you'll end having pickings composed of stock moves using view stock locations.

Keep the reference to category and search view in pager.
Update the search template to include form and keep correct reference to the category (as a slug and not a parameter).
Fixes #688

When a new ir.model.field is created, add the new field in the fields_by_model (cache of custom fields). This is required as the __init__ method would not retrieve the new field if fields_by_model is already set.
Otherwise, the _columns would not contain the new fields and we could not access it without restarting the server (e.g. the installation of a module adds ir.model.fields and use it in the a view.

Comparing an id and a browse record will always fail so the exception would have always been raised when changing a model (e.g. updating a module with custom fields).

Fixes #1743, opw 611307

product_id column of pos_order_line is a product_product
the left join of l.product_id was done on product_template, instead of product_product

It worked as long as the ids product_product were the same as product_template. Meaning that, if you used variants, this report view was screwed.

Sometimes a node can't be translated using the website Translate
mode. The translation is added to the Application term list but
the id of the view is not correct.

This happen when a translatable node is a children of a inherited
node whose branding could not be kept. data-oe-source-id was left
over because it was not registered in MOVABLE_BRANDING

If a portal user has engouh karma, this is possible for him, at least graphically, to delete forum posts, even if is not the author of it.
So, he should be allowed to delete forum posts in the ACL

When this situation happens. the 'cost' is None and the web interface cannot handle this value, provoking a JS error. Thus, prefer to fallback on the standard way to get the cost: based on the current standard price of the product.
Fixes #1032

Was removed (for unknown reason) during refactoring of product and template (opw 611699)

The buttons for new providers needs at least the zocial css class to be seen as button. As the field css_class is not in the default form view, add it by default.

Due to forward-port, the variable standard_price was reintroduced instead of valuation_price_unit
Move the change of currency after the fifo/lifo computation.
Fixes #1801

The cleditor width does not include the margins. Setting 100% will make the editable area too large (104%) on Firefox (opw 611700).
Replaced by auto, the default value adviced by CLEditor.

The type 'general' no longer exists on a account.voucher. As in general context, removed the default value on this menu.
Fixes #1261, it produces a traceback in 8.0 where the selection fields are less fault-tolerant.

When uninstalling/installing sale module, this can be problematic

The field tax_amount is fieled with onchanges and the compute_tax method. Setting a different value than the one computed by the system may lead to unbalanced move (which is obviously wrong).
In the future, handeling these operations by setting the correct value to the tax accounts would be better.

The field partner_id is not required on an account.voucher but the validation was failing if none was set (opw 611663).
This patch makes a fallback on the account of the voucher if neither a partner nor a writeoff account is specified.

Datetime like Tue Jul 13 23:18:36 +0000 2010 is not accepted by IE and return "Invalid date".
Therefore, We parse the date to a format known by IE (and other browsers)
Trick took from http://stackoverflow.com/questions/3243546/problem-with-javascript-date-function-in-ie-7-returns-nan

When uninstalling/updating a module, we may execute unlink method on product.template before product.product. In such cases, the product is already removed after removeing the template (_inherits) and the chained unlink of the product would fail (traceback when browsing).

The date_order field of the pos.order is a datetime, not a date
As, in report.pos.order, the date field is related to date_order of the pos.order

We usually do not commit fixes altering the model fields structure in 7.0, but this one is retro-compatible, as the database structure won't change

Sometimes, focus_field could be a button, and in such cases, we should not focus on it

opw-612045

Inventory lines without production lot number should
be compared with the stock level of products without
a production lot. Otherwise the final result of a
validated inventory is wrong as soon as there are
lines with and without production lot for the same
product.

Adds corresponding regression test.

Fixes https://bugs.launchpad.net/openobject-addons/+bug/1008099
Manual rebase of #1658, courtesy of Numerigraphe

Avoid revalidating the complete account moves
that contain the lines being reconciled.
The reconciliation does not change the validity
of those moves anyway.
This represents a very important speed up of
reconciliation when moves with several hundred
lines are involved.

[FIX] Fixed the issue of calendar view reload events inconsistency, when the slow create popup creates event through any form button which is kind of object, action or workflow at that time events are reloaded but still button action is not called like workflow is not triggered and hence state of the event is still not changed and due to domain newly created event is filtered, note that events are refetched when create_completed is triggered and create_completed is triggered right after creation of record, but there are case where some form button changes state of the record and it requires to refetched for example we have scenario in mrp order planning where Confirm Production creates event but before workflow is triggered and state of the event is changed, events are reloaded and newly created event will not returned because of domain.