This issue existed in previous version also. I'm assuming the adapter could have an options property logging:false to avoid logging messages like this on ...
確定! 回上一頁