Permissions on ir.attachments must not only respect the access rights
of the object they are attached to, but must also be careful about
directory permissions as introduced by the document module.
Minor fix in copy() method to avoid reading all fields of the
attachment including the binary data itself, when only the name
is needed. Also made the "(copy)" suffix translatable.
bzr revid: odo@openerp.com-20110218141012-a7wjqn2f48iioca9
Due to the way ir.attachment permissions depend on the permissions of the
document they are attached too, normal filtering rules do not work for all
cases and a correct search() method is needed. This patch fixes some cases
that were not covered by search() yet.
An additional patch will be needed in the document module to also check
for access rights of the parent directory (a concept that does not exist
without the document module).
bzr revid: odo@openerp.com-20110218131454-0y4czja86w3ynaxb
This includes, fixes in account type report_type.
Coding standard respect (regex, xml, comment etc.)
Suppression of line2bank overriding
Suppression of field bvr_number that is exactly the same data of post_number
Better demo data in order to have main company linked to a bank account that will allows BVR printing testing
Escaping of entity in bvr report
bzr revid: nicolas.bessi@camptocamp.com-20110217083353-1n5m5fv3fq389r01
This situation can occur due to custom fields (x_...) that are creating shortcuts between
objects without respecting the module dependencies. For example a custom m2o fields
connecting a partner and a product would fail to be loaded at server startup when only
base is loaded, because product.product is not yet available.
This can usually be simply ignored, as the prefetching is just an optimization.
The custom fields should never be accessed during startup (e.g not function field
should use them), so that should never cause any issue.
bzr revid: odo@openerp.com-20110216142128-a9f4um5ky8cetl38
This includes, fixes in account type report_type.
Coding standard respect (regex, xml, comment etc.)
Suppression of line2bank overriding
Suppression of field bvr_number that is exactly the same data of post_number
Better demo data in order to have main company linked to a bank account that will allows BVR printing testing
Escaping of entity in bvr report
Fixing v11 bugs
bzr revid: nicolas.bessi@camptocamp.com-20110209085905-hkzt1asp70dav0p2
This revision introduces two new config parameters and the corresponding
server startup parameters:
- osv_memory_count_limit: limit on number or records in each osv_mem table
- osv_memory_age_limit: limit on maximum age of records in each osv_mem table
The default values have been changed to count=False (disabled), age=1 (hour),
so that in the default config the server will only expire osv_memory records
that are 1 hour old or more, avoiding problems related with some
osv_memory classes that instantiate a large number of short-lived objects.
A corresponding set of YAML tests has been added to test the proper behaviour
of the new parameters, and check the various use cases.
lp bug: https://launchpad.net/bugs/555271 fixed
lp bug: https://launchpad.net/bugs/709559 fixed
bzr revid: odo@openerp.com-20110208140924-0bgxqgt1oyrxwz3z
Switch to using the action_id itself instead of reverse-matching action_id from view_id
* Not all ir_act_window have a view_id, for some we're supposed to go through ir_act_window_view
* Multiple ir_act_window (or ir_act_window_view) may have the same view_id, and we don't really have enough information to select the right one
Keep the old resolution via view_id for now, in case users update their web client and their addons out of sync
bzr revid: xmo@openerp.com-20110208123241-lj8v12ygz2a0jsgx
This issue caused the parent_left and parent_right values to be correct
only for the first record being update as part of a batch update on several
children from the same parent. An example of the consequences is the linked
bug 708503.
lp bug: https://launchpad.net/bugs/708603 fixed
bzr revid: odo@openerp.com-20110203225102-a7v8bv90l2ph5ujh