My problem with W3 Total Cache

  • (It would be super if you guys would stop closing threads so that when someone with the same problem but different symptoms comes along, a new thread is not needed to be started. I know that running forums is tough but this is a simple thing that you guys should cease doing immediately.)

    I have the same issue as found in this thread:
    https://www.ads-software.com/support/topic/uninstall-of-w3-total-cache-crashes-whole-wp-site-1?replies=7#post-6025870

    Willie Jackson’s post suggests the following solution:
    1. Remove the WordPress drop-ins.
    PROBLEM: You may see advanced-cache.php, object-cache.php, and/or db.php in your wp-content directory – I SEE NONE OF THESE

    2. Delete w3-total-cache plugin folder
    PROBLEM: I DON’T HAVE THIS FOLDER

    3. Edit your wp-config.php file
    PROBLEM: THAT CODE IS NOT IN THIS FILE

    4. Edit your .htaccess file
    PROBLEM: THAT CODE IS NOT IN THIS FILE

    I have tried everything I can think of. I have tried reinstalling this very unhelpful hack and it has rendered my site unusable.

    Any other help would be greatly appreciated. I would once again request that this thread remain open as your software is eternally buggy and you will never solve everyone’s problems by closing threads.

    Thank you.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter CygnusFTK

    (@cygnusftk)

    W3 Total Cache Error: some files appear to be missing or out of place. Please re-install plugin or remove /home3/notfeel1/public_html/livingroom/wp-content/object-cache.php.
    Warning: require_once(WP_PLUGIN_DIR/w3-total-cache/inc/functions/compat.php): failed to open stream: No such file or directory in /home3/notfeel1/public_html/livingroom/wp-content/plugins/w3-total-cache/inc/define.php on line 1478

    is the error I am getting.

    Problem:
    THERE IS NO w3-total-cache directory in my plugins directory… thus, no inc directory… and thus… no define.php file to call this error.

    WTF is going on?

    Thread Starter CygnusFTK

    (@cygnusftk)

    Unbelievably toolish moderation tactics. You should be embarrassed. I am for you.

    Thread Starter CygnusFTK

    (@cygnusftk)

    Can the moderator who has been editing this thread – including the title which exposes WordPress and this Plug-in as extremely buggy – please explain why this thread: https://www.ads-software.com/support/topic/uninstall-of-w3-total-cache-crashes-whole-wp-site-1?replies=7#post-6025870 was closed?

    There were open questions that were not answered. I found the thread through a search and could have revived that thread which contains useful information. It is unlikely people are going to bounce around from thread to thread in an effort to volunteer to help out.

    Moderator James Huff

    (@macmanx)

    Can the moderator who has been editing this thread – including the title which exposes WordPress and this Plug-in as extremely buggy

    The title of this thread was originally “w3 total cache nonsense again,” it would appear that a moderator edited the title to be more relevant, as this is your first ever post here about W3TC, not exactly “nonsense again.” This avoids confusion, as those helping you would waste time trying to find out where you had nonsense before this.

    “WordPress” was never mentioned in this thread’s titled, and would have been redundant anyway, as these are the WordPress forums, and this is a WordPress plugin.

    please explain why this thread: https://www.ads-software.com/support/topic/uninstall-of-w3-total-cache-crashes-whole-wp-site-1?replies=7#post-6025870 was closed?

    Threads after a certain age are automatically closed. Absolutely no one (those who needed help and those providing help) provided anything of value to that thread after 4 months, and the original thread started a whole year ago.

    This does not mean in any way that you can’t re-open the issue with your own thread, as you have done.

    There were open questions that were not answered.

    Four months has passed before the system automatically closed it. Leaving it open would have most likely not resulted in a solution suddenly appearing, rather it would have resulted in more spam constantly appearing.

    I found the thread through a search and could have revived that thread which contains useful information.

    Instead, you referenced it in your own issue opened here, which is the right way to do it. ??

    The folks behind W3TC are good people, it’s very unlikely that the bug reported a whole year ago still stands. Your issue might be related, but it’s more than likely not the same.

    It is unlikely people are going to bounce around from thread to thread in an effort to volunteer to help out.

    I agree, it’s far more likely that people will revive old unrelated threads, which is why we had to start automatically closing old threads in the first place.

    Unbelievably toolish moderation tactics. You should be embarrassed.

    Your preceding reply was caught as spam by the automated system and rescued in 52 seconds by me. I am not embarrassed by that tactic nor that efficiency considering the hundreds of spam we need to deal with here on a daily basis as volunteers.

    Thread Starter CygnusFTK

    (@cygnusftk)

    Fair enough. I figured age of posts had something to do with it… and I hadn’t considered the spamming issue (no other way to fix that?).

    I have tried to contact W3TC people through their website and await their reply. I will post the solution here when and if I ever figure it out.

    Thank you for your response, James. At least some light has been shed on part of my frustration today.

    Moderator James Huff

    (@macmanx)

    You’re welcome!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘My problem with W3 Total Cache’ is closed to new replies.