Siirry sisältöön
Menu
Sinun on rekisteröidyttävä, jotta voit olla vuorovaikutuksessa yhteisön kanssa.
Tämä kysymys on merkitty
2 Vastaukset
55527 Näkymät

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.

Avatar
Hylkää
Paras vastaus

Hi ,

In order for you to understand the trace back , the best way is to learn python programming.

Avatar
Hylkää
Tekijä

The trace backs are presented to all of us. Most of us are not programmers. And not Python programmers. There must be some smart things to look for which can be done by an intelligent person without programming knowledge. I am not looking for the "best" way but for the intelligent way.

Tekijä Paras vastaus

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.

http://developer.plone.org/troubleshooting/exceptions.html

In this case they give examples of trace backs and what is the cause. Is this available for OpenERP?

Avatar
Hylkää
Aiheeseen liittyviä artikkeleita Vastaukset Näkymät Toimenpide
4
tammik. 25
59947
1
kesäk. 23
5485
0
elok. 21
2688
1
toukok. 19
4069
0
maalisk. 15
4309