Didn’t correctly export WP Datatables Column names

  • I just used this plugin to take a live site down to my local machine to develop using Local (which you have explicit support for according to your docs), the plugin didn’t seem to correctly backup/restore some data.

    It makes me believe that in production there’s risk for this same thing happening.

    WP Datatables is a plugin that lets you visualize DB tables on the frontend and has much more functionality, it’s possible to rename the column name set in the DB to your own desired column display name that should be shown on the on the frontend.

    The changes are stored inside a table called “<prefix>_wpdatatables_columns”

    In this screenshot you can see the original name for columns of a table and the display name desired: https://prnt.sc/D_Y-_u4B_omT This is from the live database.

    After restoring the migrated zip…you can see that for this same table id, the column display names show the same value as the original column name: https://prnt.sc/epgmKAdPHSxQ

    I took a look at the exported database.sql file and looked for the query where the wpdatatables columns table was being created. It looked like the correct replacement display names were in there for tableid 6, but for some reason that wasnt the final outcome.

    Obviously you might say this is not your plugin’s fault but just mentioning it here so that maybe you can try reproducing it on your end to see if the same thing happens.

    TLDR:

    The display name set for table columns in a WP Datatables table, doesn’t carry over when restored to a localhost website using Local: https://localwp.com/ (which you mention that your plugin has extensive support for)

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Delicious Brains Support

    (@dbisupport)

    Hi @uriahs-victor!

    WP Migrate Support Team here. Thanks for reaching out with your query! We would be happy to assist.

    This is the first time we’re hearing about this issue. We’ve also had very few queries related to WP Datatables.

    If it’s okay, can you kindly share the exported database with us, so we can check? You may omit any sensitive data.

    If you can also share any error logs that could be related to the issue, please send them in.

    Thread Starter Uriahs Victor

    (@uriahs-victor)

    @dbisupport Unfortunately the DB SQL file is 121 MB big and does have quite a bit of sensitive customer data as well as long CREATE statements which would most likely cause breakage if I tried to manually edit the sql file.

    Maybe you can try reproducing this on your end by simply launching a test with WP Datatables Lite? By creating a table in the DB and then renaming the display columns inside the WP Datatables Lite table and then export with WP Migrate and try restoring on a Local by Flywheel

    Plugin Support Delicious Brains Support

    (@dbisupport)

    Hi Uriah,

    Thanks for your patience. I wasn’t able to replicate this issue. When I imported my export file to Local, the values in the display_header were retained.

    See screenshot below:

    https://share.getcloudapp.com/E0umjZKD

    The other rows are from another table where I didn’t change the display header.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Didn’t correctly export WP Datatables Column names’ is closed to new replies.