• Donncha,

    It appears that when WP Super Cache generates the config file wp-cache-config.php it leaves a closing php tag and an empty line at the end of the file.

    ?>

    This seemed to break <!–dynamic-cache-content–> and mfunc/mclude in my testing.

    Just a quick note that you may want to double check the file generation for that extra output. In the site I’m working on, I’m using lots of output buffering, and it’s a combination of magento and wp, sharing assets across both, so my issue may be completely due to my site.

    But that output should probably be removed.

    Thanks,
    Steve

    http://wordpress.org/extend/plugins/wp-super-cache/

Viewing 4 replies - 1 through 4 (of 4 total)
  • This is probably something on your site as the default config file doesn’t have an extra carriage return at the end of the file. Did you edit the file in notepad?

    Thread Starter jevets

    (@jevets)

    I use sublime text2 and vim.

    I just tested on a fresh install of WP 3.2.1, and sure enough, there’s a closing php tag and a carriage return.

    Can you download the plugin again or even just open wp-cache-config-sample.php in Vim. Does that have the carriage return?

    The wp_cache_replace_line() function replaces existing lines without modifying them. Only new lines have a “\n” added to them so I don’t understand how the CR was added. Perhaps you can test? Replace the config file with the default one and see what happens? Obviously keep the settings backed up too!

    Thread Starter jevets

    (@jevets)

    It was a fresh install of WP and a fresh install of the plugin via auto WP plugin installer.

    The plugin’s default wp-cache-config-sample.php does not have the carriage return in vim, but it does show up in TextMate and Sublime Text2. Strange…

    I’ve just removed the closing php tag completely. Wonder if anyone else sees this same odd behavior.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘[Plugin: WP Super Cache] wp-cache-config.php output’ is closed to new replies.