• Resolved OPunWide

    (@opunwide)


    I develop on one server and rsync the changes to another. I can make it work in both locations, but syncing is a problem.

    First a question: during syncing, I assume I should exclude all “cache/hyper-cache/*” files, right?

    Now the issue.

    The file advanced-cache.php has a semi-hard-coded location for an index file. For my local server, it shows as:

    $hc_file = '/var/www/websites/active/sswd/public/wp-a/wp-content/cache/hyper-cache/' . strtolower($_SERVER['HTTP_HOST']) . $hc_uri . '/index' . $hyper_cache_group . '.html';

    When I sync that file, as part of my content, Hyper Cache won’t work because the location is different. Couldn’t this be resolved by using ABSPATH, WP_CONTENT_DIR or something?

    I can make it start to work again by my manually logging in to the remote site and then setting and saving any configuration in Hyper Cache. But that extra step will keep me from using this on my sites because it’s an extra step that I’ll forget to do. Syncing WP is enough of a pain already.

    Also, I tried to register on satollo.com to use the forum there, but couldn’t. On https://www.satollo.net/wp-login.php?action=register is shows:
    Register For This Site
    ERROR: Banned IP address.
    ERROR: Registration stopped by Sabre.

    https://www.ads-software.com/plugins/hyper-cache/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Stefano Lissa

    (@satollo)

    Force a path on hyper cache configuration which is common to your server (you can for example use symlinks).

    Thread Starter OPunWide

    (@opunwide)

    Hardly “resolved”. I can’t make the paths common. One is on a local Ubuntu server, the other is on a shared hosting system that I have limited control on. The absolute paths are very different. If you were using relative paths, no problem.

    You also skipped by question about syncing. Do I exclude all “cache/hyper-cache/*” files?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘syncing sites, question and issue’ is closed to new replies.