• Resolved Curtis

    (@salsafire)


    Hello. Thank you for your plugin development. This is a wonderful plugin combining many useful tools and features.

    However, the following error messages were generated when I accessed the Advanced settings page, and with subsequent saves on the page. The settings on the page were saved, but the below error message persisted.

    I tried changing the fopen setting in the PHP ini file, and still had the error. I changed permissions on the wp-config file (444 -> 644) and still had the error.

    My config file is located one level above my public_html file, if that matters.

    I also noted the double forward slash (//) between public_html and wp-config.php in the fopen error message, and thought that may be the issue. Am I am somehow generating that as it does not seem correct?

    I’ve removed the personal data, and shared the rest of the error log.

    =============
    PHP Warning: fopen(/public_html//wp-config.php): failed to open stream: No such file or directory in /home/…/public_html/…/plugins/clearfy/admin/pages/additionally.php on line 34

    PHP Warning: filesize(): stat failed for /home/public_html//wp-config.php in /home/…/public_html/…/plugins/clearfy/admin/pages/additionally.php on line 35

    PHP Warning: fread() expects parameter 1 to be resource, boolean given in /home/…/public_html/…/plugins/clearfy/admin/pages/additionally.php on line 35

    PHP Warning: fclose() expects parameter 1 to be resource, boolean given in /home/…/public_html/…/plugins/clearfy/admin/pages/additionally.php on line 36

    ===

    Thank you for any help you can offer.

    Curt

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

    (@webcraftic)

    Hi,
    I think this error is due to the fact that your wp-config file is located elsewhere.
    I plan to release an update today, I will close these errors.

    Have you moved the wp-config file for security reasons?
    —–
    Regards,
    Alex K.

    Plugin Author webcraftic

    (@webcraftic)

    Hi, @salsafire
    Please check the plugin job. I tried to hide these errors so that they did not bother you. You need to upgrade to version 1.1.8
    —-
    Best regards,
    Alex K.

    Thread Starter Curtis

    (@salsafire)

    Alex,

    Thanks for the feedback.

    Yes, following recommendations from several sources I move it to provide a bit more of security through obscurity, and potential mis-configuration.

    Again thanks for getting back to me.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Failed to Open Stream Error’ is closed to new replies.