• Resolved simonmwilson

    (@simonmwilson)


    Some issues with the log settings page – nothing major, but fixable 🙂

    1. When I first load the page it comes up with /storage/www/logs/ as a path for Custom, and Apache as the log. If I change NOTHING on the page, and hit save, it tries to validate the dummy path, and fails with an error message CUSTOM Error Log Path not exist or is not writable, even though I’ve not asked it to use custom.

    2. If I select Custom with a path that Apache can write to but not navigate to (/var/log/httpd/ax where ax is apache owned and writable) it fails.

    3. If the Custom log file is empty, the log file viewer fails with an error – even though the settings are correct.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Federico Rota

    (@mrrotella)

    New release of the plugin solves the points 1. and 3.

    The problem of point 2. depends of your server configuration. The path must be writeable and readable by user apache and his group.
    Maybe the problem could be caused by lack of the slash at the end of path. In the new version of the plugin path field is saved with a trailing slash if it is missing.

    The update killed my blog:

    [Thu Sep 22 18:40:35 2016] [error] [client 59.167.157.243] PHP Fatal error: Can’t use function return value in write context in /var/www/wordpress/wp-content/plugins/authentication-and-xmlrpc-log-writer/admin/admin-class.php on line 130, referer: https://blog.simonandkate.net/wp-admin/update-core.php?action=do-plugin-upgrade

    Plugin Author Federico Rota

    (@mrrotella)

    I’m very sorry. I tested the plugin on my server before the update, and it not failed.
    I released a new version. Let me know if the update solve the problem.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Log settings’ is closed to new replies.