Hi,
We have noticed that the console.log function have stopped in more and more SuperOffice enviroments, we currently have 3 prod enviroments that have stopped working, and today we got a sod enviroment as well.
It just seems to stop working from one day to another.
alert works just fine, console.warn and other variants of console logging works, but, console.log is the most crusial since we use it to check objects etc, and its quite anoying to have to stringify em to use in console.warn :)
Anyone else have noticed this, and have a solution?
Regards
Pär Pettersson
All Replies (4)
And, in the enviroments, its not dependent on the screen.
We can just create a new screen with the following:
--scriptstart--
console.log("This will not show");
console.warn("This will show");
--scriptend---And only the console.warn is printed.
Hi Pär,
Seems to me that we are hijacking it in SCIL.js. Just type "console.log" + enter in the console, and you can see it. I am not aware of why, I am sure there is a good reason. Seems like you can do "SCIL.Log._enableConsole = true;" to make it work again. NOTE: This is just my own discovery, and not official advice from SuperOffice ;-)
Sverre
Can this be changed/removed?, really annoying when trying to debug something..