mfunc is going away in the next version

  • The next version of WP Super Cache will be released next week. If you use the dynamic cache functionality you’ll want to prepare.

    Support for the mfunc/mclude/dynamic-cached-content tags will be removed.

    In their place is a filter called wpsc_cachedata. You can use a WP Super Cache plugin to hook on to that and add or change template tags. It’s a lot safer than running exec() on potentially unknown code.

    Download the development version of the plugin on a test server and upgrade your theme if you need to show dynamic content on your site.

    There’s more information here, including test code: https://ocaoimh.ie/y/5b

    https://www.ads-software.com/extend/plugins/wp-super-cache/

Viewing 12 replies - 16 through 27 (of 27 total)

  • @donncha O Caoimh

    The blank page syndrome is also occurring to users of W3TC which started shortly after the last WP update.

    “””@Young Master – I don’t know. This might be an issue with your hosting or a bug in the plugin or a conflict with another plugin. That report is too vague, you’ll have to try to debug it I’m afraid.”””

    I was about to uninstall that one and reinstall WP Supercache until I saw that others are having the blank white page issue too.

    Our hosting provider (Liquid Web) said that they’ve had thousands of clients contacting them about the problem and it’s a caching issue.

    @donncha O Caoimh, I dont think if this issue is caused by conflict with another plugin or an issue with my web host because I have got several websites each running on different web host and all of them are experiencing the same problem.

    If you look around the Internet you will see that this issue has been occurring for a while – years. What is frustrating is that WPSC is totally awesome except for this one issue.

    I tried to find a solution of this problem with Bullet Proof Security Plugin Author who is also experiencing the same problem but we couldnt find a solution for this problem.

    @donncha O Caoimh

    Can you help me explain what may cause this error ?? ??

    https://content.screencast.com/users/Kim1243/folders/Jing/media/3f3bc797-754e-4e1f-9785-5446d2993e18/2013-08-02_0147.png

    Thanks

    @young\ Master and @gooma2 – your problem may be related to a duff distribution of php-apc. I know WPSupercache will try to use it, if installed, and W3TC has options to hook it in.

    Try removing it (assuming you have it). I saw tell-tale errors in my logs about failed cache access. It absolutely killed a box of mine.

    Thank you @davemee for your advice but unfortunately I dont use APC in any of my web hosting accounts.

    @nathanfranklinau – try the development version of WP Super Cache. I added really experimental code that uses the shutdown hook to display the buffer if dynamic caching is enabled. You should be able to use an output buffer in the wpsc_cachedata cacheaction hook now.

    It does come with a warning. The request that generates the cached page won’t serve a compressed page. I could not, for all my trying, get that to work properly. Unless that gets fixed I’ll probably revert the change as it adds to the complexity of the plugin for a feature that is unfortunately only used by a minority of sites. Any patches or help is welcome!

    https://ocaoimh.ie/y/2o

    If you have a new version coming out can you please fix th emajor fail of WP Super cache using absolute addresses rather than relative that makes it fail a server migration

    JW555 – unfortunately not. I’ve tried that in the past but some hosts have really weird setups where the filesystem path seen by Apache is not the same seen by PHP.

    I do need to make the recovery from that error better. There’s no reason the plugin couldn’t fix the path itself. It all takes time however of which I am short of these days.

    I reverted the buggy code that would let you use an output buffer callback. It was overly complicated and depends on PHP’s shutdown process which I don’t 100% trust. After reviewing the code this evening something is sending output to the browser and then the gzip headers were ignored. The code was there to be tested for a month but nobody commented on it or helped fix the bugs.

    Unfortunately this means site owners won’t be able to use an output buffer when generating the dynamic bits in dynamic pages but at least the plugin will finally be rid of any mention of eval().

    I realised this morning that there’s an easy work around. If you must use a dynamic cache call your dynamic code in the theme or as an action hook wherever it’s supposed to be. This will make sure that the first cached page has the dynamic bit.

    But also hook it onto the cacheaction for the cached pages. To stop it executing twice when the cached page is generated set a flag and check for that. I’ll update the example plugin over the next few days.

    I checked in code yesterday to support using an output buffer. Here’s my post about it. Barring any last minute bugs there’ll be a release tomorrow.

    https://ocaoimh.ie/y/6j

    And version 1.4 is out. More details here: https://ocaoimh.ie/y/6l

    If you’re using mfunc et al do not upgrade. Read that post first as you’ll need to update your sites.

Viewing 12 replies - 16 through 27 (of 27 total)
  • The topic ‘mfunc is going away in the next version’ is closed to new replies.

Tags