Sometimes there's an error and CS says:
Something went wrong. An error message is logged with current time: 2016-12-15 12:09:10
Very good! But where is the error message logged?
It is logged to files which are located in the CS install directory.
For example my local installation has the log files here:
.. or if it's not online you can read it in your browser by using the dumpWarningLog action.
fcgi:rms.fcgi?action=dumpWarningLog&date=<date>dateformat = YYYY-MM-DD
exe:rms.exe?action=dumpWarningLog&date=<date>dateformat = YYYY-MM-DD
When using the dumpWarningLog I can see the errors. But when looking in the file earlier I did not. Are errors written all the time or only at certain times?
The data is written to the logfile immediately. Infact &action=dumpWarningLog reads the values from that file. You can see this if you rename the logfile on disk, and try to refresh the &action=dumpWarnignLog. Then you'll get an error saying it can't open the logfile.
But the big question is; how can we get the same information in the Online environment? Since &action=dumpWarningLog has been disabled we're totally in the dark when these errors happen.
Currently, only the operation team has access to this log through OC. I guess customers will never get access to it (due to security reasons), but it could be discussed if partners should be able to view the log.
It is very much needed. I'm currently writing a long script in Online, and have to test it every time I make the slightest of changes. If I make too many changes at once, and it starts failing there is really no way to find the error easily.
Or perhaps it would be easier if we just send the error by mail to the address we define in the system settings.
No more security settings necessary :)
I've submitted this as a wish. We REALLY need to get access to the logfiles in Online.
A suggestion would be to make some sort of portal that partners can log into where we can download logfiles for our customers.
Is there any news regarding this issue?
I'm still having problems debugging screens Online :)
Isn't enabling the 'print exceptions to screen' debug option a solution for this?
Well, I can't find it if its available for screens
If you go to .../ticket.fcgi?action=debug, and enable "Print exceptions to screen", then most exceptions will print to the screen. Some exceptions, specifically query exceptions, will still not be printed due to security concerns.
LukkDette nettstedet bruker informasjonskapsler. SuperOffice bruker informasjonskapsler hovedsaklig for å overvåke trafikken på nettstedet, og for å forbedre innholdet. Fortsett å bruke nettstedet hvis du samtykker til at vi bruker informasjonskapsler. Les mer: Personvernerklæring