By Rosamunda on

I´ve recently installed logintoboggan module in version 6.4, and the page didn´t reloaded... when it finally did, it showed LOTS OF ERRORS. (I´ve been using logintobbogan since 4.7, so, don´t know what could have go wrong).
So, I´ve decided to delete it.

But since then, all modules that are related to User access/authentication breaks my site.
I´ve repair the tables, reinstalled (using devel), the system module... but nothing happens...
What could it be wrong? I´m really desperate here.

Thanks for your help and advice!!!

Rosamunda

⋅ Categories: Drupal 6.x

Comments

Rosamunda’s picture

Rosamunda commented

I´ve checked the USERS table (even after I repair it) and found this message:

consulta SQL: CHECK TABLE `users`;
Filas: 2

Table Op Msg_type Msg_text
planetac_planeta.users check warning Found row where the auto_increment column has the value 0

planetac_planeta.users check status OK

I´ve try to reinstall user module, but the problem remains.

lhtown’s picture

lhtown commented

I am not familiar with logintoboggan.

However, I see that the error message alluded to the auto_increment value 0.

There are a number of posts about auto_increment problems on the forums. Basically, it is the value that tells Drupal what number to use next. For instance, if the last node number was 543, it is what tells the next number to be 544.

If that is the problem, you can easily fix it by setting it at a value that is higher than any of your current data. You will have to edit your database using phpmyadmin or another way to do this.

I believe there is an auto_increment value for nodes as well as users and possibly some other things.

Rosamunda’s picture

Rosamunda commented

Thanks for your reply!
I´ll searched in the forums, and the answers that I´ve found didn´t solved the issue. But I think that was because I didn´t quite understand the problem.
I´ll see if I can change that value manually...

gpk’s picture

gpk commented

1. Note that the {users} table is supposed to contain a row in which uid = 0; this is for anonymous users but may be the cause of MySQL's complaints.
2. I can't see anything in logintoboggan that would cause permanent "damage" to a site. How did you uninstall the module? What error messages are you seeing?

gpk
----
www.alexoria.co.uk

gpk
----
www.alexoria.co.uk