Support » Plugin: Error Log Monitor » php-errors.log does not exist or is inaccessible.

  • Resolved gabu69

    (@gabu69)


    I have a wordpress website with an install over

    Nginx and HHVM (instead of php)

    When I install the plug in I set all correctly but i get this error:

    The log file /wp-content/logs/php-errors.log does not exist or is inaccessible.

    Why? File exist and had 775 permissions

    what else should i need to do?

    https://wordpress.org/plugins/error-log-monitor/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Janis Elsts

    (@whiteshadow)

    Is /wp-content/logs/php-errors.log the actual, unedited log file name that the plugin displays? The file name is incorrect, which is probably the source of the problem. It’s a relative path, but it contains a leading forward slash that makes it look like an absolute path.

    Please set error_log to the full path of the log file. For example, if WordPress is installed in /home/xyz/public_html, the log file name would be something like /home/xyz/public_html/wp-content/logs/php-errors.log.

    ahhhh yea was the path that wasnt complete

    thanks for the great support janis

    I must be some special kind of dunce! I really can’t figure out to specify the absolute path. I must have tried all the permutations by now and still get the ‘does not exist or is inaccessib;e’ error message.

    The fullest path I have used is: “/home/html/globalfarmplatform.org/wp-content/logs/php-errors.log”. (When I look at the directory structure using Filezilla, I see all of this other than “/home”. Is it necessary?)

    File permissions for directory wp-content/logs and file php-errors.log are both ‘0755’.

    Am growing desperate .. any hints or suggestions?

    Patrick

    Ignore, ignore, ignore!

    I’ve just used the tip in “Three ways to monitor PHP errors” and found the absolute path. Needless to say it was non-obvious. Wel, at least to me, evidently!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘php-errors.log does not exist or is inaccessible.’ is closed to new replies.