Problems in trying to view the debug log

  • Resolved ericr23

    (@ericr23)


    1 year, 8 months ago

    1. The link to the view script adds an extra subdirectory: 
    https://www.domain.org/news/news/wp-content/cache/view_09…5e.php?wp-admin=1&wp-json=1&filter=

    I am able to access it by removing one of the /news from the path.

    But then,

    2. The provided Username/Password login doesn’t work for me, nor does any other that I tried. I had to remove the login lines from the start of the view file.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter ericr23

    (@ericr23)

    And then after a while, Super Cache (sensibly!) deletes the altered view file. So how can I log in to it?

    Plugin Support Dan (a11n)

    (@drawmyface)

    Hi there

    By default the file should be found in https://www.domain.org/wp-content/cache/. The plugin does not add any extra directories to that file path.

    What is your cache location set to in Settings > WP Super Cache > Advanced?

    Do you have any other plugins or custom code that might be responsible for the additional?/news?subdirectory? You can perform a plugin conflict test by disabling other plugins one by one and checking if the issue persists.

    Do you have any custom settings in your?wp-config.php?file related to file paths?

    Thread Starter ericr23

    (@ericr23)

    The cache location is set as /home/xxx/public_html/news/wp-content/cache/. That is the default (which I confirmed by deleting it and having it reset). And that’s where the debug log and the view file are; it’s just the link in the debug tab to the view file that has the extra /news in the path. There is no custom directory directive in the wp-config or htaccess file. There is no /news/news subdirectory. The WordPress address and site address are both set as https://www.xxx.org/news.

    • This reply was modified 1 year, 8 months ago by ericr23.
    Thread Starter ericr23

    (@ericr23)

    Also, in wp-config: define('WPCACHEHOME', '/home/xxx/public_html/news/wp-content/plugins/wp-super-cache/');

    Thread Starter ericr23

    (@ericr23)

    Poking around, I see a wp-cache-config.php file in /wp-content, and a line in it: wp_cache_home_path = '/news/';. If I comment out that line, Super Cache adds it back. I change it to '/', Super Cache changes it back. This may not be relevant, of course. Again, it is only the link to the view script for the debug log that has the extra /news in the path; the view script and the debug log are exactly where they’re supposed to be: /home/xxx/public_html/news/wp-content/cache/.

    Thread Starter ericr23

    (@ericr23)

    Line 12 of debug.php, creating the link, appears to remove $_SERVER[‘DOCUMENT_ROOT’] from $cache_path – leaving the extra /news?

    Hey @ericr23!

    Apologies for taking this long to respond. I would like to thank you very much, for taking the time to debug the issue yourself and sending us your findings. Thanks the information you provided, we were able to identify the bug and squash it!

    I’ve opened a PR with a fix that should hopefully go out in the next version.

    Cheers!

    Thread Starter ericr23

    (@ericr23)

    Wow – I’m so pleased! My programming knowledge is strictly as-needed, so that’s great. Thanks.

    Plugin Support lastsplash (a11n)

    (@lastsplash)

    You are welcome.

    If you need additional assistance with WP Super Cache in the future, feel free to open a new thread.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Problems in trying to view the debug log’ is closed to new replies.