We recently upgraded our Drupal to 6.19 and upgraded all our modules prior to going live with our site. We use it for an online store using Ubercart module. However, every year we reset the usernames and start over for new members and this year we used Delete All module to remove all the old usernames and import new users (roughly 5000) from a CSV import. When we deleted all the users using the Delete All module, it did give us an error: sequences doesn't exist, but we researched and found that sequences is no longer a table in Drupal 6. Therefore, we assumed it would be OK. The import also went fine with no errors. However, now when a user is logged in (any role) after random period of time, it would switch the user to someone else. We aren't sure if Delete All module didn't remove some foreign relation and it is causing this issue; however, we want to resolve it and would appreciate if anyone can give us any suggestions.

Thanks in advance!

Comments

kbahey’s picture

kbahey commented
Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

It looks like a sessions table problem. Seems session entries are still in the table and users' cookies map to it?

The delete_all module uses Drupal's API, and calls user_delete() to do the delete for the specific user, which in turn calls sess_destroy_uid. This should take care of the session entry for that user.

So delete_all may not be the reason for what you are seeing.

To verify, do a TRUNCATE on the sessions table, and see if the problem occurs again.

pdesai’s picture

pdesai commented

We tried to TRUNCATE the session table but still no resolution. I am logged in as admin and after a while I am logged in as a regular user.

kbahey’s picture

kbahey commented

It is very odd.

I don't see how else can delete_all be the source of this problem.

Check other modules that are in there (masquerade, devel, ...etc.)

pdesai’s picture

pdesai commented

This started to happen when we used the delete_all and cleared users and imported users. There is no other change.

pdesai’s picture

pdesai commented

Any other ideas?

kbahey’s picture

kbahey commented

Disable the module and uninstall it, to see if the issue persists.

I can't imagine how the module would do this ...

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (outdated)

I am closing this issue because is for a branch that is now not supported. Only branches compatible with Drupal 7, Drupal 9, or Drupal 10 are now supported.