- Issue created by @MaxPah
- π©πͺGermany jan kellermann
Only user 0 was persistent_login-user and we had to change in persistent_login.install:
->condition('uid', $sandbox['current'], '>')
to
->condition('uid', $sandbox['current'], '>=')
- First commit to issue fork.
-
gapple β
committed cd70fa10 on 8.x-1.x
Fix #3478340 by jan kellermann, maxpah, fenstrat, gapple: Error on...
-
gapple β
committed cd70fa10 on 8.x-1.x
-
gapple β
committed 2720c568 on 2.x
Fix #3478340 by jan kellermann, maxpah, fenstrat, gapple: Error on...
-
gapple β
committed 2720c568 on 2.x
- π¨π¦Canada gapple
Thanks for the quick patch & review :)
New patch releases should be available shortly.
- π·π΄Romania cslevy
This still doesn't fix the issue. I attached an extra patch, which also should be included.
- π©πͺGermany andrerb
Thanks for the patch. I also still had the problem. After the 3rd iteration of the update hook and the query for $token_users, $sandbox[βcurrentβ] was set to the last item in the pl table. Therefore the $token_users array was empty and the following query for $valid_users failed.
- π«π·France MaxPah
Hello !
Thanks for the quick patch and release but this still crash on my side.
Additionnal patch #9 π Error on hook_update_8108 uid IN ()' cannot be empty Active is working.
- π¨π¦Canada gapple
That's odd... On the last iteration
$sandbox['#finished'] = $sandbox['processed'] / $sandbox['total'];
should equal1
to complete the batch.
Are there tokens stored for the anonymous user (uid:0)? That would increase$sandbox['total']
to one more than will be returned in the$token_users
queries - but that shouldn't happen so some checks might need to be added elsewhere π¬. -
gapple β
committed 53a1d813 on 2.x
Fix #3478340 by cslevy, andrerb, maxpah, gapple: Error on...
-
gapple β
committed 53a1d813 on 2.x
-
gapple β
committed b869a7b9 on 8.x-1.x
Fix #3478340 by cslevy, andrerb, maxpah, gapple: Error on...
-
gapple β
committed b869a7b9 on 8.x-1.x
- π¨π¦Canada gapple
π€ that's a final fix for this issue.
Just wanted to also note that the tokens in the database aren't accepted even if provided by a browser, and this cleanup is only really needed for sites with tokens configured to a permanent lifetime, so there isn't a problem if the update is not completed on a site (provided it doesn't block any other necessary updates).
Automatically closed - issue fixed for 2 weeks with no activity.