nudeworldorder

Oh yeah. Actually the problem went away as suddenly as it appeared. Sorry I forgot to come back and note that here. Almost certainly nothing to do with your plug-in. If anything I suspect the glitch was on Gravatar’s side, though I can’t confirm one way or another.

I’m confused. Are you asking for help or sharing advice? If the latter, I’d love to know what one line you changed to fix it.

It’s been quite some time since I wrestled with this, but since I was mentioned, as best I can remember, due to the way the WordPress feature is implemented, it’s actually the original file that should be excluded, with the -scaled image treated as the main one.

But take it with a grain of salt, since I’m not able to easily retest this. Someone who’s got a local WordPress install for testing could probably clear up exactly what the correct behavior is fairly easily.

Seeing as I already got it working (with a little manual intervention, as above) I’m not sure I’m really in a position to test out the fix anymore. But thank you for addressing this, I’m sure it will come in handy for others.

Huh… I’m confused about why it was working previously then, but thanks for your help.

It’s licensed under GPL, so you can use it for any purpose. Of course if it serves you well, I’m sure a donation would be appreciated.

Thank you. I sounds like they’re actively working that, so maybe I’ll just wait until the cookie functionality is improved.

In the mean time I’m using a “hack” solution, based on something else I found online. I just edited WP Night Mode so that its cookie is named wordpress_logged_in_DarkMode and is deleted when it’s turned off (instead of just set to false). So WP Super Cache is fooled into thinking anyone in Night Mode is logged in. It’s not elegant, but it seems to work.

Thanks. So it looks like wpsc_add_cookie is what I need. I didn’t know about this feature. That will indeed be a better solution than excluding people based on the cookie. I’m not quite sure I understand where to put code to use that fuction, but I guess I’ll just start trying things.

By default, the cache is disabled for logged-in users. This most likely explains why it’s slower for them. You can turn on caching for known users in the advanced settings.