Géry Debongnie
fddf2a722e
Here is the issue that initiated this work: the bank reconciliation tour sometimes failed in community. The reason was that the discuss client action seemed to be loaded after the tour started, and interfered with the second step of the tour. What happened exactly was the following: - web client is loaded - initial action is starting (but not complete) (this is discuss) - tour manager is loaded and starts the reconciliation tour - the reconciliation tour changes the url to trigger an hash change - the web client calls loadState on the action manager - the action manager perform a doAction with the tour url - the discuss client action is now ready, and replace the reconciliation action - the tour is broken. The underlying cause is really a generic problem: the action manager does not add the client action starting process in its 'dropprevious' concurrency primitive. This is probably not really an issue for the act_window actions, since they have custom loading code that make sure the loading process is put in the drop previous, but it is definitely a problem for all client actions. The solution is quite simple, and should also protect the act window renderers: put the action controller in the drop previous
Odoo
Odoo is a suite of web based open source business apps.
The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Warehouse Management, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, Purchase Management, ...
Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
Getting started with Odoo
For a standard installation please follow the Setup instructions from the documentation.
Then follow the developer tutorials