Odoo is the world's easiest all-in-one management software. It includes hundreds of business apps:
CRM | e-Commerce | Accounting | Inventory | PoS | Project management | MRP | etc.
Let's just say I hand craft some lovely XML for a view, update the module and am brought to a screeching halt by this error message:
except_orm: ('ValidateError', u'Error occurred while validating the field(s) arch: Invalid XML for View Architecture!')
How would you approach resolving this issue?
Is there a way to see more detail about what the complaint is?
Would you cut out everything inside
<field name="arch" type="xml"> </field>
then add it back a piece at a time until the error shows up again?
You can see more details about the error (offending view, what is the problem) in the server log file.
It is sometimes more convenient not to work with OpenERP as a service when developing. If you run
openerp-server without the
--log-file option, it should output to
/path/to/openerp-server --config=/path/to/openerp-server.conf --debug )
In a general manner, when you develop, you better have to activate the debug logging's level, so you'll have more details about the errors in the logs.
To activate the debug level, you can start your server with the option
More details about the logging options:
[EDIT] more information about the log file
Please try to give a substantial answer. If you wanted to comment on the question or answer, just use the commenting tool. Please remember that you can always revise your answers - no need to answer the same question twice. Also, please don't forget to vote - it really helps to select the best questions and answers!
About This Community
This platform is for beginners and experts willing to share their Odoo knowledge. It's not a forum to discuss ideas, but a knowledge base of questions and their answers.Register
Odoo Training Center
Access to our E-learning platform and experience all Odoo Apps through learning videos, exercises and Quizz.Test it now
|Asked: 2/12/13, 8:55 AM|
|Seen: 3041 times|
|Last updated: 3/16/15, 8:10 AM|