Last Update User field causing problems

  • Resolved harski111

    (@harski111)


    4 years, 4 months ago

    Hi!

    I noticed about week ago that when I try to update my records from the backend, records doesn’t update to the database at all. No error messages appear, but when I edit a field and click save, field data does not update.

    When using frontend pages fields data can be updated normally. Also using “with selected” addon to edit fields works normally.

    I turned on the error log and noticed this:

    PDb_submission\main_query\base_query::execute_query record store error: Unknown column 'last_update_user' in 'field list' for query: UPDATE wp_participants_database SET 'date_updated'= "2022-03-08 20:53:16",......

    So there is error with this field. Is there anything I can do to solve this?

    • This topic was modified 4 years, 4 months ago by harski111.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Roland Barker

    (@xnau)

    4 years, 4 months ago

    Try deactivating/reactivating the plugin. It looks like the column wasn’t added, it’s a recently added column to the main db.

    Thread Starter harski111

    (@harski111)

    4 years, 4 months ago

    Hi!

    Thanks for the reply but it didn’t help.

    I looked at my database with phpmyadmin and noticed that wp_participants_database table (that stores the records) has no column called “last_update_user”.

    Table wp_participants_database_fields has a row called “last_update_user”.

    Thread Starter harski111

    (@harski111)

    4 years, 4 months ago

    Hi!

    Got this working!
    It was my mySQL database settings that were messed up. Tried to add that missing column by myself and received error:

    Error Code: 1118
 Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.

    My row format was compact, changed it to dynamic and after that I was able to add that missing “last_update_user” column, and now everything works normally.

    It would have helped if there was an error message at the record page, that tells if record saving fails with reason like this.

    Now there was no error messages at all, I had to get it from the error log. Even a small error message that only tells if record saving fails with any reason.

    Plugin Author Roland Barker

    (@xnau)

    4 years, 4 months ago

    I’m glad you got that fixed, and thanks for the suggestion, it’s a good idea to let people know what’s going on, also makes it easier for me to support it too.

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

The topic ‘Last Update User field causing problems’ is closed to new replies.