Title: Warning message Last modified: August 20, 2016 --- # Warning message * [Jonathan](https://wordpress.org/support/users/iwd82/) * (@iwd82) * [13 years, 5 months ago](https://wordpress.org/support/topic/warning-message-32/) * A vast number of error message appears after the last update (Version 3.1.1). * Example: `Warning: file_put_contents(/www/htdocs/user/wordpress/wp-content/logs/ newsletter/main-d8948252.txt) [function.file-put-contents]: failed to open stream: No such file or directory in /www/htdocs/user/wordpress/wp-content/plugins/newsletter/ includes/logger.php on line 49` * Several dozen of these error messages are also displayed in the backend. * This is very unfortunate. Please solve the problem quickly! * [http://wordpress.org/extend/plugins/newsletter/](http://wordpress.org/extend/plugins/newsletter/) Viewing 11 replies - 1 through 11 (of 11 total) * Plugin Author [Stefano Lissa](https://wordpress.org/support/users/satollo/) * (@satollo) * [13 years, 5 months ago](https://wordpress.org/support/topic/warning-message-32/#post-3500786) * Those messages are caused by the absence of the “logs” folder in your wp-content folder. Newsletter tries to create it upon installation, probably your wp-content folder has permissions that block new folders creation. * I’ll add some code to disable log writing if the folder is not there. * Stefano. * Thread Starter [Jonathan](https://wordpress.org/support/users/iwd82/) * (@iwd82) * [13 years, 5 months ago](https://wordpress.org/support/topic/warning-message-32/#post-3500790) * I have now created the folder “logs” manually. But the error messages are still displayed. The write permission of wp-config are set to “755”. What can I do to use the plugin without error messages? * Plugin Author [Stefano Lissa](https://wordpress.org/support/users/satollo/) * (@satollo) * [13 years, 5 months ago](https://wordpress.org/support/topic/warning-message-32/#post-3500791) * Does there are files inside the folder you created? For example “main-xxxxxx. txt”? * If not, probably the plugin cannot write the log file. If you set 755 it depends on the user you are when setting the permissions and the user used to run PHP. * Try 777. * Stefano. * Thread Starter [Jonathan](https://wordpress.org/support/users/iwd82/) * (@iwd82) * [13 years, 5 months ago](https://wordpress.org/support/topic/warning-message-32/#post-3500798) * Hi Stefano, * It still does not work. I like no updates, I have to edit it manually. These issues are annoying. * How can I edit the “main xxxxxx.txt”manually? What should I include in this file? * Is there the an alternative of possibility, to use the predecessor version of your plugins? * Plugin Author [Stefano Lissa](https://wordpress.org/support/users/satollo/) * (@satollo) * [13 years, 5 months ago](https://wordpress.org/support/topic/warning-message-32/#post-3500802) * Hi, * but the log level on diagnostic panel is set to none? * Stefano. * Thread Starter [Jonathan](https://wordpress.org/support/users/iwd82/) * (@iwd82) * [13 years, 5 months ago](https://wordpress.org/support/topic/warning-message-32/#post-3500805) * It does not work. * Where can I download the previous version? * – Jonathan * Plugin Author [Stefano Lissa](https://wordpress.org/support/users/satollo/) * (@satollo) * [13 years, 5 months ago](https://wordpress.org/support/topic/warning-message-32/#post-3500807) * On version 3.1.2 the log is disabled if the folder is not present or the files cannot be written. * Should solve your problem. * Stefano. * ps: even oldest version wrote on that files, maybe you enabled the log on diagnostic panel? What means it does not work? Does the log level cannot be set? * Thread Starter [Jonathan](https://wordpress.org/support/users/iwd82/) * (@iwd82) * [13 years, 5 months ago](https://wordpress.org/support/topic/warning-message-32/#post-3500809) * It does not work because: * after I have set the permission to 777 and additional added `wp-content/logs/ newsletter/statistics-d1234567.txt` manually, the error message remains at `/ wp-admin`-page and also in the backend. * I hope the plugin still works without errors. When you say that the error message will disappear in the next update, I’ll wait. When do you plan the next update? * Plugin Author [Stefano Lissa](https://wordpress.org/support/users/satollo/) * (@satollo) * [13 years, 5 months ago](https://wordpress.org/support/topic/warning-message-32/#post-3500821) * The files generated inside the folder are created by Newsletter when the logging is enabled. If there are no permission problem to create and write to files on that folder and the logging is active there should be no problems. * The logging is active? If not there is a bug, since Newsletter should not write on those files. * Stefano. * Thread Starter [Jonathan](https://wordpress.org/support/users/iwd82/) * (@iwd82) * [13 years, 5 months ago](https://wordpress.org/support/topic/warning-message-32/#post-3500842) * Stefano, how can I enable this logging function after I set permission on `wp- config` to 777? * Plugin Author [Stefano Lissa](https://wordpress.org/support/users/satollo/) * (@satollo) * [13 years, 5 months ago](https://wordpress.org/support/topic/warning-message-32/#post-3500843) * On diagnostic panel. * Stefano. Viewing 11 replies - 1 through 11 (of 11 total) The topic ‘Warning message’ is closed to new replies. * ![](https://ps.w.org/newsletter/assets/icon-256x256.png?rev=1052028) * [Newsletter - Send awesome emails from WordPress](https://wordpress.org/plugins/newsletter/) * [Frequently Asked Questions](https://wordpress.org/plugins/newsletter/#faq) * [Support Threads](https://wordpress.org/support/plugin/newsletter/) * [Active Topics](https://wordpress.org/support/plugin/newsletter/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/newsletter/unresolved/) * [Reviews](https://wordpress.org/support/plugin/newsletter/reviews/) * 11 replies * 2 participants * Last reply from: [Stefano Lissa](https://wordpress.org/support/users/satollo/) * Last activity: [13 years, 5 months ago](https://wordpress.org/support/topic/warning-message-32/#post-3500843) * Status: not resolved