WordPress.org

31. Kemper Boyd
    Member
    Posted 2 years ago #

    Hello, I have the same problem mentioned here, I think I have followed every trick I could find on this topic, but nothing still gets cached.

    I'm using WordPress 2.7 with wp-super-cache 0.9.7

    I have all write permissions granted to the webserver user, required files were correctly created in wp-content by the plugin itself, cache/supercache are both 777, .htaccess files match what's in the plugin admin page (both the one in the webroot and the one in the cache dir), WP_CACHE is defined, PHP safe mode is disabled... I don't really know where else to investigate - no change I made moved me from 0 cached pages.

    The site is struggling and I really could use help from caching.

    Thanks in advance for your help!

32. Kemper Boyd
    Member
    Posted 2 years ago #

    I installed the dev version and all I get for every page is "Not caching POST request."

33. Kemper Boyd
    Member
    Posted 2 years ago #

    UPDATE: after looking for conflicting plugins (which I did not find) the only way I could get wp-super-cache to work is by commenting out the lines that check if request is POST or if compression is enabled in wp-cache-phase2.php. After doing that the cache is building up. Am i going to go into troubles for doing this?

34. smoke489
    Member
    Posted 2 years ago #

    I checked my wp-config file, and the define WP_CACHE does, in fact appear before the require_once(ABSPATH . 'wp-settings.php');...should the define WP_CACHE be located DIRECTLY above the require_once, or is it fine as long as the define comes first?

    If my wp-config file is fine the way it is, then the order of these two statements doesn't seem to be my issue...

    Thanks!

35. Donncha O Caoimh
    Member
    Posted 2 years ago #

    Kemper - that's odd. Something on your server is populating the $_POST array when it's not supposed to be. Do you have some sort of unusual proxy setup? (oh, and really, upgrade to 2.8.5, you WILL be hacked, it's only a matter of time)

    smoke - try enabling the debug system?

36. Kemper Boyd
    Member
    Posted 2 years ago #

    donncha thanks for your reply. The situation on that server is quite complicated, I took over after the guy who set up the whole site left, so I have to deal with a high load server made by someone else. In this, your plugin was a godsend, the server came back to life after a deadly weekend with lots of downs. At the moment I'm not able to find what could be populating POST (there is no proxy that I know of), but if commenting that part isn't gonna get me into trouble, I'll postpone the investigation after more urgent issues will be fixed.

    By the way, how smooth can the transition to 2.8.5 be (I'm a bit concerned since I'm basically walking in the dark)?

    Thanks again

37. Donncha O Caoimh
    Member
    Posted 2 years ago #

    It should upgrade easily. Try it on a test server in your office first, just to be careful.

38. Sakshin
    Member
    Posted 2 years ago #

    I got some problems with wp super cache too but slightly different.
    This is what google sees when it crawls my pages ... Blanco, so it cannot read and index it. The funny thing is that not all my pages give this result to google.

    <!-- Page not cached by WP Super Cache. Blank Page. Check output buffer usage by plugins. -->

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

    What to do?

39. smoke489
    Member
    Posted 2 years ago #

    Ok, I enabled the debug system, and I received the following errors pertaining to Super Cache not cacheing:

    No closing html tag. Not caching. -- Viewing the page source has a comment next to the closing html tag stating that I am logged in. Upon logging out, the comment states the following:

    </html>
    <!-- Dynamic page generated in 0.867 seconds. -->
    <!-- Cached page generated by WP-Super-Cache on 2009-11-09 19:02:13 -->

    URI rejected. Not Caching -- not sure what could be causing this.

    Please advise. Thank you!

40. Donncha O Caoimh
    Member
    Posted 2 years ago #

    smoke - it's probably another plugin using the output buffer incorrectly. There are lots of tips in the readme.txt

41. smoke489
    Member
    Posted 2 years ago #

    Sorry to be a pain...is there a list of plugins incompatible with Super Cache? I couldn't seem to find it in the readme.

    If there isn't, and I have to disable each plugin one by one to determine the culprit, how long do I need to keep each plugin disabled to see if super cache starts caching?

    Thank you!

42. Donncha O Caoimh
    Member
    Posted 2 years ago #

    There isn't a list. To test, just disable the plugin, visit your blog twice and check if the second visit was cached ... simple :)

43. Jorge A. Gonzalez
    Member
    Posted 2 years ago #

    removing the following lines in wp-cache-phase2.php fixed my problems, around line 38

    if ( $_SERVER["REQUEST_METHOD"] == 'POST' || !empty( $_POST ) || get_option( 'gzipcompression' ) ) {
    if ( isset( $GLOBALS[ 'wp_super_cache_debug' ] ) && $GLOBALS[ 'wp_super_cache_debug' ] ) wp_cache_debug( 'Not caching POST request.', 5 );
    return false;
    }

    I printed out my post and go this

    Array ( [ajax] => 0 )

    So assume that another plugin or my theme is messing things up. I will post more if find anything.

44. Jorge A. Gonzalez
    Member
    Posted 2 years ago #

    I found the problem, the plugin 'Complete Vbridge Plugin' was the problem.

    It was writing Array ( [ajax] => 0 ) to the post.

45. douglaswarnold
    Member
    Posted 2 years ago #

    donncha, Hello! This is Doug from Mansfield, MA; recently laid off and going back to night school for web site development after an 18 year career in graphic design for print. Learning about pixels now!

    My blog, gives me this error message: URI rejected. Not Caching

    Can you tell me what I'm doing wrong, please? Thank you!!

    Doug

46. douglaswarnold
    Member
    Posted 2 years ago #

    donncha, here's the link:

    http://01f2617.netsolhost.com/blog1/

    Thank you!
    Doug from Mansfield, MA

47. Donncha O Caoimh
    Member
    Posted 2 years ago #

    Checked the list of rejected URIs? Remove 1 at a time until it works again.

48. douglaswarnold
    Member
    Posted 2 years ago #

    donncha, thanks; that problem is fixed; but, now I get this message from the Super Cache settings page: Use your ftp client, or the following command to fix things:chmod 755

    But it doesn't say where (or how) using the ftp client to implement that instruction. Can you elaborate, please?

    Thanks!
    Doug

49. safin
    Member
    Posted 2 years ago #

    Hello,
    I have exact same issue of 0 pages getting cached and POST request bypass.
    Using vbulletin bridge.
    nasium did you find out the solution for the [ajax= => 0 vbulletin adds?

50. Donncha O Caoimh
    Member
    Posted 2 years ago #

    douglaswarnold - check the documentation for your ftp client, it's (sort of) basic ftp/file permissions stuff you should learn about to admin your site. Plenty to find on Google too.

51. yitwail
    Member
    Posted 2 years ago #

    I have tried I don't know how many hours to get this to work. After much googling, experimenting, and looking at logs and headers, I know that getting redirected to the login page--you don't need to actually login--will disable supercache. That's because a cookie named wordpress_test_cookie with the value WP Cookie check is created, and because the url for the login page has a query string, that is, it looks like domain/blog/wp-login.php?redirect_to=http%3A%2F%2Fdomain etc. (the ?redirect makes supercache think that the site isn't using pretty permalinks) This redirect happens each time you go to blog/wp-admin, for example, when you're not already logged in.

    if I make sure I never attempt to login, pages do get cached but unfortunately, when I check the header for a cached page, it always includes this header: WP-Cache Served supercache file from PHP

    As I understand it, this indicates something is still not right. Documentation says something about rewrite rules, but those are correct. This is about as frustrating an exercise as I've had in a long time. I suppose I should just accept that it probably works no worse that WP-Cache, but I sure would like an explanation or solution.

52. Donncha O Caoimh
    Member
    Posted 2 years ago #

    yitwail - it will still cache using wp-cache which for most people is just as fast as supercached pages.

Topic Closed

This topic has been closed to new replies.