Don’t Store at umeta_id=0 !!!!!!!!!!!!!!!!!!!!!!

  • Resolved designdrumm

    (@designdrumm)


    5 years, 3 months ago

    For the love of God and all you hold dear, please don’t store umeta_id=0!
    Please fix. I can’t login because you store something at umeta_id=0.

    Well, actually it logs in, but redirects to the login page. This may be on your end. Shows successful in DB. The issue is not central to you. Wordfence is doing it too (umeta_id=0) and I am going to post the same there.

    Common Sense Rule: You never store at ID=0, that is where poorly developed scripts store at!!

    🙂

    Anxiously await an update. I certainly enjoy your plugin and the caching it provides. Thank you for that and a free version!

    Best,
    designdrumm

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter designdrumm

    (@designdrumm)

    5 years, 3 months ago

    Hello,
    This is the error message I get:

    [05-Jun-2019 19:42:03 UTC] WordPress database error Duplicate entry ‘0’ for key ‘PRIMARY’ for query INSERT INTO wpab_usermeta (user_id, meta_key, meta_value) VALUES (1, ‘session_tokens’, ‘a:1:{s:64:\”REMOVED INFO\”;a:4:{s:10:\”expiration\”;i:1559936523;s:2:\”ip\”;s:11:\”97.99.93.13\”;s:2:\”ua\”;s:119:\”Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.1.2 Safari/605.1.15\”;s:5:\”login\”;i:1559763723;}}’) made by wp_signon, wp_set_auth_cookie, WP_Session_Tokens->create, WP_Session_Tokens->update, WP_User_Meta_Session_Tokens->update_session, WP_User_Meta_Session_Tokens->update_sessions, update_user_meta, update_metadata, add_metadata, W3TC\DbCache_Wpdb->insert, W3TC\DbCache_WpdbInjection_QueryCaching->insert, W3TC\_CallUnderlying->insert, W3TC\DbCache_Wpdb->insert, W3TC\DbCache_WpdbInjection->insert, W3TC\DbCache_Wpdb->default_insert, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection->query, W3TC\DbCache_Wpdb->default_query

    Best,
    designdrumm

    • This reply was modified 5 years, 3 months ago by designdrumm. Reason: wrong plugin
    Thread Starter designdrumm

    (@designdrumm)

    5 years, 3 months ago

    Hello again,
    It looks like the 'session_tokens' meta is being stored at umeta_id=0.

    When Wordfence is installed, they are storing 'wfls-last-login' here as well so when you logout then try to login again, there is a DB error and makes the login redirect fail. Because of the .htaccess redirects, it sends me back to the login page. The login still happens though and shows in the database as logged in. So you have to logout via the url before logging in again. Well, from what I experienced anyway.

    HTH,

    Best,
    designdrumm

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    5 years, 3 months ago

    Hello,
    I spoke with the team and we’ve thoroughly inspected this. This issue is not related to W3 Total Cache.

    Thread Starter designdrumm

    (@designdrumm)

    5 years, 3 months ago

    Hi Marko,
    How did you come to this conclusion? What basis do you have for that statement? I would like to know so I can weed out who is related. The error I am getting implicates your plugin. Please inform me as to how you find it is not.

    Not saying your wrong, just need clarification on why it’s not.

    TIA,

    Best,
    designdrumm

    Thread Starter designdrumm

    (@designdrumm)

    5 years, 3 months ago

    Hello Marko,
    I retract my request. It seem it was an issue with a corrupt and incomplete usermeta table. By deleting and reloading the SQL in phpMyAdmin it seems to have fixed the issue.
    I also had a user with no usermeta at all. Not sure if this was aid to the issue, but since adding meta, the issue has gone.

    Thanks for the quick reply!

    Best,
    designdrumm

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    5 years, 3 months ago

    Hello,
    Glad to know the issue is resolved.

    Thread Starter designdrumm

    (@designdrumm)

    5 years, 2 months ago

    Hello again,
    Looks like the problem is back.

    I looked into it further and it looks like when a user login happens, when database caching updates the session token, the first parameter for the insert, the umeta_id is defaulting to 0. This collides with WordFence and triggers their ip block because of the silent error that is happening. Wordfence is blocking my ip every time.

    Not sure why this is happening. May be a bug in WordPress itself. Maybe the session function is bugging and not inserting correctly. Not positive.

    But just so you know, that is what I found out and the problem still exists.

    Best,
    designdrumm

    Thread Starter designdrumm

    (@designdrumm)

    5 years, 2 months ago

    Hello again,
    Ok, I figured out what was the problem. My usermeta and user tables both did not have Auto_Increment set, so WordPress was storing at umeta_id = 0; When I exported the MySQL, the auto index option did not save to the file and I updated without. Well, that is my theory anyway. Sorry for the noise.

    All is fixed now. 🙂

    Best,
    designdrumm

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Don’t Store at umeta_id=0 !!!!!!!!!!!!!!!!!!!!!!’ is closed to new replies.