CDN Support is not working – if user logged in

  • Resolved vollcom

    (@vollcom)


    3 months, 3 weeks ago

    Hey Donncha,

    We all love your plugin… but today I found a small issue 🙂 When a user logged in, the CDN support isn’t functioning. When the user is logged out, the CDN support works fine 🙂

    Could you please fix this as soon as possible? 😉

    I’ve encountered this problem before, about four years ago, and you were able to resolve it then –

    https://wordpress.org/support/topic/enable-cdn-support-not-work-if-you-logged-in/

    Just a reminder: CDN is CDN and caching is caching, they are two different things. The CDN must always work.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Donncha O Caoimh (a11n)

    (@donncha)

    3 months, 3 weeks ago

    Ah, thanks for reporting that. I think I know why that isn’t working.

    Do you have caching disabled for logged in users? I added a DONOTCACHEPAGE check to short circuit the caching process, saving the web server CPU cycles, but, of course that means the buffer isn’t created, and the CDN doesn’t operate.

    Thread Starter vollcom

    (@vollcom)

    3 months, 3 weeks ago

    yes … we use always:

    Disable caching for logged in visitors. (Recommended) …

    Can you fix them in your next update pls? 🙂

    Plugin Author Donncha O Caoimh (a11n)

    (@donncha)

    3 months, 2 weeks ago

    A fix will be in the next release. I have created a patch for it here. However, if you don’t want to wait for the next release you can edit wp-cache-phase2.php, look for the wp_cache_postload function and remove this chunk of code around line 391:

    
if ( defined( 'DONOTCACHEPAGE' ) && DONOTCACHEPAGE ) {
	wp_cache_debug( 'wp_cache_postload: DONOTCACHEPAGE defined. Not running.' );
	return false;
}

    There’s a DONOTCACHEPAGE check in the output buffer callback that’s done after the CDN has been run.

    Thread Starter vollcom

    (@vollcom)

    3 months, 1 week ago

    THX Donncha 🙂

    Perfect 🙂

    Plugin Author Donncha O Caoimh (a11n)

    (@donncha)

    3 months ago

    Version 1.12.1 was just released which fixes this problem. Thanks for reporting it.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.