Viewing 4 replies - 1 through 4 (of 4 total)
  • Sounds like a botched WordPress upgrade, actually — W3TC might be complicating things because of caching, but I’m not convinced it’s at the root of this issue.

    W3TC can be completely removed without needing Dashboard access, so I’d start with this again and also initiate a manual WordPress upgrade (not, of course, overwriting wp-config.php or /wp-content/).

    I’d also remove the W3TC directives from the .htaccess file. We can help with this if you’d like a hand, shoot us a note (we make W3TC): http://www.w3-edge.com/contact/

    @mrunal_patel, did you find all the help you needed?

    Thread Starter mrunal_patel

    (@mrunal_patel)

    @frederick Townes
    Actually I got all that problem because some clown had hacked my website and deleted the SQL database.
    But still the site kept showing many (cached) pages thanks to your W3 plug-in.
    So, now I’m grateful to you for keeping my site partially alive for the readers, during that time, otherwise it’d have been a total blackout. 🙂

    Later on, I restored my website using a backup SQL file.
    Now the site is up and running properly: http://www.mrunal.org

    Thanks and God bless you.

    I’m really sorry to hear that. I’m glad you got everything back. As you might imagine, it’s quite hard to make something that works with the infinite possible WordPress configurations out there, but we’ll keep trying.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘[Help] Another no0b victim of W3 Total Cache logged out of his site’ is closed to new replies.