Hello,
Thank you for contacting us. As stated in the pinned post we do not check often this forum and provide free support via our free support form: http://livecomposerplugin.com/support/support-request/ (no purchase or registration needed). I’m sorry again for this inconvenience.
As for your question, please check this knowledge base article: https://livecomposer.help/article/240-how-to-hide-the-server-warnings
For any further support please visit: http://livecomposerplugin.com/support/support-request/
Thank you!
I can say that hiding is not the solution. These warnings still appear in server log, which causes slower server performance and as well this code causes triggering unnecessary exception loops in the core of php which causes again performance decrease. I can say that wordpress itself by default has lots of warnings, but they are working on it. I myself if I was working at wordpress would fix lots of bugs, but have not enough time and have lots of freelance jobs and full time job. So I can only notice things and share my notices while chilling at home and drinking beer. 🙂
As well I can share this when plugin developers are too slow in development I create my own repository and put my changes there as well. I think its even possible somehow to override update urls of plugin. Just don’t remmeber how. So whenever you release your own personal version of plugin you can update it directly from github. 🙂
