Excluded object in wp-config… non-persistent?

  • Resolved fightsmarttrav

    (@fightsmarttrav)


    10 months, 1 week ago

    Hey Til,

    I added the following block to my wp-config and flused the redis cache:

    define( ‘WP_REDIS_IGNORED_GROUPS’, [ ‘users’ ] );

    I see that this has added ‘users’ to the non-persistent groups when I check Query Monitor on my site, but how long is that still cached for… even being ‘non persistent’?

    I’m having issues with users getting password reset errors and I’m wondering if it’s because the ‘users’ table is being cached, and the unique key isn’t being matched correctly with the URL parameter upon password reset due to stale data.

    If that’s the case, would this exclusion do the trick?

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    10 months, 1 week ago

    Ignored groups are still cached for the duration of the request, just like the default WP object cache does it, otherwise you’d have duplicate SQL queries.

    Are you using any specific plugins that are messing with your password resets?

    Thread Starter fightsmarttrav

    (@fightsmarttrav)

    10 months, 1 week ago

    Hey Til,

    Thanks as always for the reply.

    I was previously using a custom password reset manager, but deactivated it last week after a different issue. I reverted back to the normal user.php functions two days go, and yesterday received the support request when a user was persistently getting the error, “Your password reset link appears to be invalid. Please request a new link below.”

    I was not getting the same error for the first 8 times I tested the users link, but then I did get it once. ChatGPT suggested that it might be due to a stale version of the key in users.php being transmitted to the user upon attempted password reset, which led me down this rabbit hole… but it seems as though I’m now just operating within normal wordpress functionality.

    Wp-Rocket excludes wp-login.php from the cache, so it wouldn’t be that. I have excluded wp-login.php from cloudflare cache as well.

    Not sure where to go from here, but I’ll ask the user to retry today and perhaps the non-persistent object has worked.

    Thank you as always for your work in these forums. I can never recommend your plugin enough.

    Plugin Author Till Krüss

    (@tillkruess)

    10 months, 1 week ago

    After deactivating the custom password reset plugin, did you try a new reset with a fresh token?

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

The topic ‘Excluded object in wp-config… non-persistent?’ is closed to new replies.