WordPress.org

Ready to get started?Download WordPress

Forums

WP Super Cache
Ob_start, @font-face and Legacy mode (9 posts)

  1. saharusa
    Member
    Posted 3 years ago #

    Don't know what is going on anymore, but WP-Super-Cache isn't functioning like before, I think it all started when I choose to use Half-On (Now, Legacy mode)

    Everything seems to work ok, (mfunc functions are dynamically loading) the only 'small' problem is a new cache file is generated with each visit or not generated at all.

    I checked the debug mode, the only thing i see is ob_start and strange checking for closing html tags on @font-face ttf files.

    I comment out every ob_start call in other plugins (wp-widget-cache, page-navi, all-in-one-seo-pack)

    Nothing help, same errors, any idea/ direction where or what to check ?

    Here's the debug output:

    07:43:36 / Supercache Late Init: add wp_cache_serve_cache_file to init
    07:43:36 / Supercache Late Loader running on init
    07:43:36 / Cookie detected: wordpress_logged_in_2652771ebdc9f02d5b7dbbc450372bb3
    07:43:36 / supercache dir: /var/www/home/mysite/mytheme/wp-content/cache/supercache/mydomain.com/
    07:43:36 / Cookie detected: wordpress_logged_in_2652771ebdc9f02d5b7dbbc450372bb3
    07:43:36 / No wp-cache file exists. Must generate a new one.
    07:43:36 / In WP Cache Phase 2
    07:43:36 / Setting up WordPress actions
    07:43:36 / Created output buffer
    07:43:36 / scheduled wp_cache_gc for 10 seconds time.
    07:43:36 / Output buffer callback
    07:43:36 / Buffer is blank. Output buffer may have been corrupted by another plugin or this is a redirected URL. Look for text 'ob_start' in the files of your plugins directory.
    07:43:36 / No closing html tag. Not caching.
    07:43:45 /wp-content/themes/mytheme/include/fnt/OtherCustomFont.ttf Supercache Late Init: add wp_cache_serve_cache_file to init
    07:43:45 /wp-content/themes/mytheme/include/fnt/OtherCustomFont.ttf Supercache Late Loader running on init
    07:43:45 /wp-content/themes/mytheme/include/fnt/OtherCustomFont.ttf Cookie detected: wordpress_logged_in_2652771ebdc9f02d5b7dbbc450372bb3
    07:43:45 /wp-content/themes/mytheme/include/fnt/OtherCustomFont.ttf supercache dir: /var/www/home/mysite/wp-content/cache/supercache/mydomain.com/wp-content/themes/mytheme/include/fnt/OtherCustomFont.ttf/
    07:43:45 /wp-content/themes/mytheme/include/fnt/OtherCustomFont.ttf No wp-cache file exists. Must generate a new one.
    07:43:45 /wp-content/themes/mytheme/include/fnt/OtherCustomFont.ttf In WP Cache Phase 2
    07:43:45 /wp-content/themes/mytheme/include/fnt/OtherCustomFont.ttf Setting up WordPress actions
    07:43:45 /wp-content/themes/mytheme/include/fnt/OtherCustomFont.ttf Created output buffer
    07:43:45 /wp-content/themes/mytheme/include/fnt/OtherCustomFont.ttf Output buffer callback
    07:43:45 /wp-content/themes/mytheme/include/fnt/OtherCustomFont.ttf Buffer is blank. Output buffer may have been corrupted by another plugin or this is a redirected URL. Look for text 'ob_start' in the files of your plugins directory.
    07:43:45 /wp-content/themes/mytheme/include/fnt/OtherCustomFont.ttf No closing html tag. Not caching.
    07:43:47 /wp-content/themes/mytheme/include/fnt/SiteCustomFont.ttf Supercache Late Init: add wp_cache_serve_cache_file to init
    07:43:47 /wp-content/themes/mytheme/include/fnt/SiteCustomFont.ttf Supercache Late Loader running on init
    07:43:47 /wp-content/themes/mytheme/include/fnt/SiteCustomFont.ttf Cookie detected: wordpress_logged_in_2652771ebdc9f02d5b7dbbc450372bb3
    07:43:47 /wp-content/themes/mytheme/include/fnt/SiteCustomFont.ttf supercache dir: /var/www/home/mysite/wp-content/cache/supercache/mydomain.com/wp-content/themes/mytheme/include/fnt/SiteCustomFont.ttf/
    07:43:47 /wp-content/themes/mytheme/include/fnt/SiteCustomFont.ttf No wp-cache file exists. Must generate a new one.
    07:43:47 /wp-content/themes/mytheme/include/fnt/SiteCustomFont.ttf In WP Cache Phase 2
    07:43:47 /wp-content/themes/mytheme/include/fnt/SiteCustomFont.ttf Setting up WordPress actions
    07:43:47 /wp-content/themes/mytheme/include/fnt/SiteCustomFont.ttf Created output buffer
    07:43:47 /wp-content/themes/mytheme/include/fnt/SiteCustomFont.ttf Output buffer callback
    07:43:47 /wp-content/themes/mytheme/include/fnt/SiteCustomFont.ttf Buffer is blank. Output buffer may have been corrupted by another plugin or this is a redirected URL. Look for text 'ob_start' in the files of your plugins directory.
    07:43:47 /wp-content/themes/mytheme/include/fnt/SiteCustomFont.ttf No closing html tag. Not caching.

    Thanks

  2. saharusa
    Member
    Posted 3 years ago #

    Btw, I also can't find the usual Wp Super Cache footprint after the closing html tag like before.

  3. Donncha O Caoimh
    Member
    Plugin Author

    Posted 3 years ago #

    Are you 100% certain those .ttf files actually exist? If they did they do they shouldn't need PHP to be served.

    That's really strange that the output buffer is blank. :(

  4. saharusa
    Member
    Posted 3 years ago #

    Very strange,

    This is what I'm doing, I have function using mfunc to check for client browser (php check) than decide which css files to load (ff or ie for example) these css files contains links to the ttf files.

    The files exist.

    any idea what is going on, or what else should I check ?

  5. Donncha O Caoimh
    Member
    Plugin Author

    Posted 3 years ago #

    What happens if you remove the mfunc code? It looks like Javascript can be used to do the same thing.

  6. saharusa
    Member
    Posted 3 years ago #

    I checked that, this isn't the problem, (also, i didn't notice any problem with this function over a year now)

    To make sure I disabled the browser detection, the debug came up with same results as above (ttf files) so i remove the custom fonts, so the real problem is the buffer being blank:

    08:20:40 / Supercache Late Init: add wp_cache_serve_cache_file to init
    08:20:40 / Supercache Late Loader running on init
    08:20:40 / Cookie detected: wordpress_logged_in_2652871ebdc9c02d5a7dbbc450372bb4
    08:20:40 / supercache dir: /var/www/home/mysite/mytheme/wp-content/cache/supercache/mydomain.com/
    08:20:40 / Cookie detected: wordpress_logged_in_2652871ebdc9c02d5a7dbbc450372bb4
    08:20:40 / No wp-cache file exists. Must generate a new one.
    08:20:40 / In WP Cache Phase 2
    08:20:40 / Setting up WordPress actions
    08:20:40 / Created output buffer
    08:20:40 / Output buffer callback
    08:20:40 / Buffer is blank. Output buffer may have been corrupted by another plugin or this is a redirected URL. Look for text 'ob_start' in the files of your plugins directory.
    08:20:40 / No closing html tag. Not caching.
  7. saharusa
    Member
    Posted 3 years ago #

    I even remove the plugin and installed it again.

    When I check the source code at frontend, no sign of WpSuperCache..

  8. Donncha O Caoimh
    Member
    Plugin Author

    Posted 3 years ago #

    And debug log shows the same output buffer problem? That's bizarre! I'm afraid I can't suggest anything else. :(

  9. saharusa
    Member
    Posted 3 years ago #

    Same log... really strange, on the same server i got another installation of wp with this great plugin and everything is working fine.

    I even removed all plugins and changed back to default theme and got the same results.

    Can it be something with the options ?
    After I uninstall the plugin and inatalled it again, same settings appear like before.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic