debug.log

  • Resolved Pexle Chris

    (@pexlechris)


    5 years, 5 months ago

    Wordfence, in the last scan found a log file that your plugin created that is public accessible. Is it good idea to be public accessible?

    Also, this file says that imgs that aren’t exists (maybe because of the previous Prestashop installation) is slowly loaded

    WPSSO Core warning: Slow PHP function detected – getimagesize() took 2.631 secs for https://www.mydomain.com/pictures/mypicture.gif (longer than recommended max of 1.500 secs).

    What does it mean this message?

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

    (@jsmoriss)

    There is no log file in the plugin folder, so that would be a “false positive”. If you copy-paste the original error/warning message, perhaps that would help.

    I’m not sure what you mean by “imgs that aren’t exists” – which images?

    You have entered “https://www.mydomain.com/pictures/mypicture.gif” somewhere in the settings and WPSSO is getting the information about that image, and the server in question is slow to respond.

    js.

    Thread Starter Pexle Chris

    (@pexlechris)

    1) The file in the wp-content.

    2) I have not set something like this in the settings.

    Before your plugin, I was using Yoast SEO.
    Does it matters?

    Plugin Author JS Morisset

    (@jsmoriss)

    Ah, you must mean the debug.log file from WordPress – this is not a log file from WPSSO, nor is the log file located in the WPSSO folder. See here for more information on the WordPress debug.log file:

    Debugging in WordPress

    If you use the “View Source” feature of your browser and search for “https://www.mydomain.com/pictures/mypicture.gif” in the webpage content, it should give you an idea of where that image is being used. WPSSO is getting that image from its settings or your post/page settings or the post/page content.

    I’m getting a 404 when trying to view “https://www.mydomain.com/pictures/mypicture.gif”, so you should definitely fix that image path.

    js.

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