Debugging Non-complex Issues

[z0lo13]

I have found that a lot of issues turned to be from people who didn't try to debug the problem and just posting that something simply does not work (Like a workflow function or button is not pressing, the calculations done twice etc.). Below some guidelines on how you can help debug issues within yetiforce.

THE 0 Step is to check your PHP configuration, only after you are sure it is matched the recommended ones continue to creating an issue.

THE 0.1 Step is to check that you are performing the right thing, do not expect the update or trigger of function if you don't know what it should change.

Step 1 is to enable displaying the exception errors and backtrace.
It could be done in the Debug.php file under the config folder.

Now you have +- two outcomes.

1. The error is displayed, it could be consoled, logged to error.log or PHP log on the server. If you know how to use search in your IDE just go function by function from the backtrace and you might find a problem line yourself. Post this results in issues and it will be fixed very quickly.

2. If nothing is displayed the error in the core and again could be related to server misconfiguration or 3rd party package.

I wrote nothing new here, but maybe for some people, it will help.