Closed (fixed)
Project:
User Expire
Version:
2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Feb 2017 at 18:30 UTC
Updated:
1 Aug 2025 at 16:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
gregglesComment #3
gregglesComment #4
cafuego commentedBumping the version so I can make a fork.
Comment #6
cafuego commentedComment #8
cafuego commentedAlso pushed a fix for the Drupal 7 version.
Comment #9
gregglesThis change seems reasonable to me. Thanks for providing it for both d7 and d9.
It seems ideal to add a test for this if you'd be willing to do that, cafuego? I don't think we should block merging on that, though.
Comment #10
cafuego commentedMaybe? A bit of a false start but in theory now sorted.
Comment #12
lazysoundsystem commentedUpdated the patch as it no longer applied with yesterday's release of 8.x-1.x
Comment #13
berliner commentedAdding a static patch file version against 8.x-1.1
Comment #15
trackleft2Comment #16
sahil.sharma@io-media.com commentedHi,
By when we can expect this change mereged to 2.x and a new release or if this is an expected behaviour and not a bug so good to use patch instead.
Thanks!!
Comment #17
sahil.sharma@io-media.com commented*
Comment #18
sahil.sharma@io-media.com commentedComment #19
trackleft2Hi sahil.sharma@io-media.com I'll add this to the plan for the next release. Thanks! The patch looks ok to me, so feel free to use it until then.
Comment #21
trackleft2The PHPUnit test introduced in this MR does not appear to adequately test this functionality.
I say this because the https://git.drupalcode.org/project/user_expire/-/jobs/5542470 test passed with or without the fix. Running the "Test Only Changes" test should fail but it does not.
Comment #22
dhruv.mittal commentedComment #23
dhruv.mittal commentedI've added test for the changes please review
Comment #25
trackleft2I've tested this, and it appears to work as expected.
Comment #27
trackleft2Comment #28
rafal.sereda commentedI don't think the proposed solution is the best one. I can imagine that updating the LastAccess value for a user can be problematic in some scenarios. This way, we completely lose information that a particular user has never logged in to our system.
Comment #29
trackleft2Thank you for your comment @rafal.sereda, should we also check if the user has ever logged in before setting the value?
Possibly like this?
If you agree, we can open a new issue, and add it to the release plan for the next bugfix release #3536705: [Meta] Release Plan for User Expire Patch Release 2.1.2 (bugfix)