Hi Marcel,
This is generally caused by an older widget. You can unzip the widget, and update the mx.logger function to console.{logLevel}.
Unfortunately, I do not know how to identify which widget is causing the issue. Best would be to see which page causes the log message and then check which widget is used on the page