Fatal error when logging in

  • Resolved vincentjolanda

    (@vincentjolanda)


    2 years, 8 months ago

    Hello,

    recently I get a fatal error at my-account page when user is trying to logging in. (Don‘t get no error at wp-admin).

    I have Groups v2.18.0 and Groups for woocommerce v1.25.0.

    wordpress version: 6.3.1

    Error:
    WordPress database error Table ‘DBxxxx.v4x_groups_group’ doesn’t exist for query SELECT COUNT(*) FROM vx_groups_group made by require(‘wp-blog-header.php’)
    and
    PHP Fatal error: Uncaught TypeError: mysqli_num_fields(): Argument #1 ($result) must be of type mysqli_result, bool given in /…/wp-includes/class-wpdb.php:3854

    After disabling the plugin the error disappears and users can login.
    But I think groups-for-woocommerce requires this plugin, right?

    Can you help me?

    regards


Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Kento

    (@proaktion)

    2 years, 8 months ago

    Hi,

    The error you get indicates that one of the database tables that Groups creates – and requires – is missing. This table stores information about groups that the plugin handles and is essential.

    This table should not be missing and must have been deleted by accident. Or if you have moved the site to another server, maybe the table was not imported.

    I would recommend to recover from a backup to make sure your database is consistent.

    Regarding the extension, yes, it requires Groups to be active. The table that is missing is essential for Groups, thus it is also essential for the extension to work properly.

    Thread Starter vincentjolanda

    (@vincentjolanda)

    2 years, 8 months ago

    Hi, thanks for the quick response,

    I haven‘t moved the site or changed anything besides updating WP.
    Will it be enough to recover the backup of just the plugin as there are a couple of customers and purchases and I don‘t know exactly when this issue occured.

    Plugin Author Kento

    (@proaktion)

    2 years, 8 months ago

    You’re very welcome, I hope this will help, I would recommend to following steps:

    First make a backup of the site and database as it currently is.

    From your previous backup, look at the database backup and find the CREATE TABLE v4x_groups_group ... statement for the table that is missing. Use that statement to create the table. Locate the INSERT INTO v4x_groups_group ... statement that will insert the group data into the table.

    If that table is the only one missing, then this could solve the issue for you.

    If your database has been corrupted further than just this missing table, you will need to consider the decision to revert to a previous backup and insert the new data after that.

    Thread Starter vincentjolanda

    (@vincentjolanda)

    2 years, 8 months ago

    Hi, thanks for the detailed instruction.
    As I had to find a quick solution, I run the backup completely yesterday.
    It worked again, means, no fatal error and a customer when purchasing a certain product got registered immediately.
    Today morning I tried it again and after several attempts to get in as testuser (not getting logged in – without any message!), suddenly the fatal error came back!

    Turning off the plugin the login works again (without the register function though!)

    So something must be causing the database malfunction.

    My login form is created by elementor.

    I‘m not very comfortable with editing the database.

    Any further advice please?

    regards

    Thread Starter vincentjolanda

    (@vincentjolanda)

    2 years, 8 months ago

    Hi, I think I got it fixed.

    The strong database caching caused the issue!

    I compared some old and new (malfunctioned) databases, but didn‘t find something missing.
    So there must have been some other trigger. … it was the W3 total cache plugin with the strong database caching activated.
    After turning this off, everything works fine.

    thanks, best regards

    Nice plugin, btw, works perfect for our usecase

    Plugin Author Kento

    (@proaktion)

    2 years, 8 months ago

    Thank you very much for posting your findings, would you mind letting us know which exact settings in W3TC you were using when this happened? It would be interesting to research it on our side.

    Thread Starter vincentjolanda

    (@vincentjolanda)

    2 years, 8 months ago

    Hi, sure, where can I upload the json file of the settings (with database cache enabled)

    Plugin Author Kento

    (@proaktion)

    2 years, 8 months ago

    I think it’s better not to share your exported settings in case it contains any sensitive data. If you recall which settings were used in the database caching section, that would already be helpful. I was asking because you mentioned “strong database caching activated” and I’m not sure what settings that would involve in W3TC.

    Thread Starter vincentjolanda

    (@vincentjolanda)

    2 years, 8 months ago

    Ok, so I simply activated/deactivated “database cache” in the general settings in W3TC. No advanced settings. With “strong” I meant it had a strong effect 😉

    regards

    Plugin Author Kento

    (@proaktion)

    2 years, 8 months ago

    Thank you very much, that is very helpful! The effect was strong indeed 😛

    Cheers!

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

The topic ‘Fatal error when logging in’ is closed to new replies.