Okay
  Public Ticket #3165663
Bug version 5.1
Closed

Comments

  • Michael Stuart started the conversation

    There's a bug in version 5.1 where you cannot save edits. Error is "unknown column XXXX in field list" when trying to save new or old wpdatatables. 

    Error goes away if you go back to version 5.

  •  1,688
    Miloš replied

    Hi, Michael

    Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

    -

    We are not able to reproduce this issue on our local Test sites with version 5.1  or 5.0.

    Could we please take a look at your Wp-Admin end?

    And i presume this happens for all of your tables, not just some specific ones?

    Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

    We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

    You can write credentials here just check PRIVATE Reply so nobody can see them except us.

    Kind Regards, 

    Miloš Jovanović
    [email protected]

    Rate my support

    wpDataTables: FAQ | Facebook | Twitter | InstagramFront-end and back-end demo | Docs

    Amelia: FAQ | Facebook | Twitter | InstagramAmelia demo sites | Docs | Discord Community

    You can try wpDataTables add-ons before purchasing on these sandbox sites:

    Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables

  •   Michael Stuart replied privately
  •   Miloš replied privately
  • Michael Stuart replied

    Yes it's granted

  •   Miloš replied privately
  • Michael Stuart replied

    Plesk has a feature to harden wordpress sites that changes the the wp_ prefix among other things,  which might have prevented table update? 

    Anyway, you fixed it!

    Thanks! 

  •   Miloš replied privately