Most people who start with OpenERP doesn't make the right set-up of the software. Because of the wrong set-up the systems often reacts with errors and long trace backs.
Those starters are by definition not experienced. So they don't understand what the trace back is trying to tell them.
A lot of more experienced users have also their problems in interpreting the trace backs.
Next step for both categories is to post the trace-backs on the forum with their cry for help. If this happens it pollutes our nice forum.
Is it an idea to make some kind of a guide: "How to read your trace back yourself". If one can read is self one can communicate more effective on this forum. I am not experienced enought to make such a guide. But I hope your answers will be a start.
We can look at the generic examples in the Python tutorial: http://docs.python.org/2/tutorial/errors.html
But I find this to generic.
I give an example of how it is done for an opensource CMS called plone.
In this case they give examples of trace backs and what is the cause. Is this available for OpenERP?
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
|Asked: 3/7/13, 4:16 PM|
|Seen: 12068 times|
|Last updated: 3/16/15, 8:10 AM|