I’ve been working on a project using Odoo 8.0 which at the time of writing isn’t fully released yet (the Odoo). These are some notes on working at the bleeding edge as the release stabilises.
Working with a git version that is changing frequently means you need to upgrade your database on a fairly regular basis. To do that the
-u all command to openerp is very handy.
./openerp-server -d mydatabase -u all --stop-after-init --config=/etc/openerp/openerp-server.conf
The one feature we found caught us out initially was with the new reports. The QWeb and bootstrap 3 were fine, it was the caching that surprised us. As developers we tend to be trying lots of incremental changes on reports and at first it looked like our changes weren’t working. Luckily we realised it was actually a new feature, caching. This can be turned off against the reports assuming you have the access to the technical features. It’s not on against every report, but invoices are one area it is used. Partly because the reports are intended to be legal documents that shouldn’t change once they have been printed.
At the moment these are the open bugs on github I’m tracking. If you need to apply one of the patches to get on with things just stick ‘
.patch’ onto the github url and you will have a patch file you can apply in the usual fashion, i.e.
patch -p1 < nnnn.patch
Some of these are caused by constant upgrading on the bleeding edge, others are things I hope get fixed before the final cut. Note that these pull requests may not be the best way to fix the issues, but they do generally fix the symptoms so I have found them useful for getting on with my own development.
Error context: View `product.template.form` [view_id: 259, xml_id: product.product_template_form_view_variant_button, model: product.template, parent_id: 252]
Issue 1267 – Fixed
This one is just a tweak to the writeability of a few fields.
Issue 1284 – Fixed XML RPC and None values