faster is better than slow | Download Swift
+ Reply to Thread
Results 1 to 5 of 5

Thread: Upgraded to Swift Premium Which Broke WP Super Cache!?

  1. #1


    Exclamation Upgraded to Swift Premium Which Broke WP Super Cache!?

    I had been using the free version of Swift for about a year. I was so pleased I decided to upgrade to the premium version. I upgraded yesterday and spent the afternoon setting up my site etc.

    Everything is fine except the WP Super Cache plugin now does not work. I have used Super Cache without issue along with the free swift theme with no issues. As soon as I upgraded to the premium version of Swift I've had issues. Of course I've done the basics. I've tried deleting and reinstalling WP Super Cache which didn't work. I've tried deleting all other plugins except for WP super cache and it still doesn't work. I'm just confused on what the issue could be because I really haven't changed anything except upgrading to Swift Premium.

    As a workaround I tried temporarily installing W3 Total Cache which appeared to work. However, I prefer WP Super Cache because I'm on shared hostin. Being on Lunar Pages shared hosting, W3 Total Cache has a ton of bells and whistles that just do me no good.

    In the past I've compared the performance of my sites and server load using W3 and Super cache and WP Super Cache has always been a little better for my setup.

    I've enabled logging and I've attached a txt file of my error log as an attachment. Basically the log amounts to the same scenario again and again for any page that is accessed:

    14:14:00 / No wp-cache file exists. Must generate a new one.
    14:14:00 / In WP Cache Phase 2
    14:14:00 / Setting up WordPress actions
    14:14:00 / Created output buffer
    14:14:01 / Output buffer callback
    14:14:01 / No closing html tag. Not caching.
    14:14:01 / wp_cache_shutdown_callback: collecting meta data.
    14:14:10 / No wp-cache file exists. Must generate a new one.
    14:14:10 / In WP Cache Phase 2
    14:14:10 / Setting up WordPress actions
    14:14:10 / Created output buffer
    14:14:10 / Output buffer callback
    14:14:10 / No closing html tag. Not caching.
    14:14:10 / wp_cache_shutdown_callback: collecting meta data.

    I've went through the FAQ for WP Super-Cache and checked their trouble shooting tips and nothing seems to work. I'm in the process of double checking again but I'm hoping someone has had this same issue and can help speed things up for me.

    Can someone anyone PLEASE HELP me get this figured out? I don't know why upgrading to Swift Premium made this happen but this identical setup was fine using the free version of Swift.
    Since I already know WP Super Cache worked well (and I know how to configure it correctly) I wanted to stay with it over W3.
    Last edited by singledad; 03-14-2012 at 12:18 AM.

  2. #2


    Previously when I checked the page source info for my site to see there was a note about caching successfully, there was nothing. Now I see this at the end of my page source code

    <!-- Page not cached by WP Super Cache. No closing HTML tag. Check your theme. -->

  3. #3


    Ok...I think I fixed it. I went into the footer.php file of the theme and added the closing </html> tag that wasn't there, immediately after the </body> tag. I certainly don't remember deleting it from the footer after I upgraded. Is this just a coding error Satish? Not saying I couldn't have deleted it when I edited the footer...but I certainly don't remember editing that far down in the footer after upgrading to Swift Premium.

    Worth a check anyway and hopefully that will help anyone who has this same problem!
    Last edited by singledad; 03-14-2012 at 12:17 AM.

  4. #4


    It's missing.
    Will be fixed in the next version, thank you

  5. #5


    Quote Originally Posted by Satish View Post
    It's missing.
    Will be fixed in the next version, thank you
    I'm glad I didn't break it! I was pretty confident I didn't accidentally delete it but I wanted to ask and confirm I wasn't losing my mind!

    It's always those little details that get you, lol! I'm glad that's all it was.

    Although I did spend about 40 minutes making the solution ten times more complicated than it needed to be. When I finally got around to running debug and then I saw that message appear in the footer it didn't take too long to dawn on me how easy of a fix it was.

+ Reply to Thread

Similar Threads

  1. Wp-super cache or Total Cache
    By vipin_lalla in forum Support
    Replies: 1
    Last Post: 05-04-2012, 04:28 PM
  2. Replies: 2
    Last Post: 04-10-2012, 12:07 PM
  3. WP super cache
    By elitepronostic in forum Support
    Replies: 1
    Last Post: 02-11-2012, 02:46 PM
  4. Replies: 1
    Last Post: 09-24-2011, 04:58 PM
  5. Change the permissions of swift/cache folder to 777 and custom-style.css to 666
    By theconservativeblog in forum Bug report and suggestions.
    Replies: 1
    Last Post: 11-17-2009, 03:16 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts