Gravity Forms tables causing error with backup

  • Resolved metricmedia

    (@metricmedia)


    6 years, 9 months ago

    Gravity Forms recently updated, which deprecated some old tables that are no longer needed. Now whenever Ithemes Security backup runs, it triggers something in Gravity Forms that generates errors like the below.

    This happens even if all the indicated tables have been excluded from backup.

    Gravity Forms says “exclude the tables from backup” but apparently Ithemes is somehow accessing those tables even though they are excluded. Is there a way to get Ithemes Security to actually ignore these completely? Or do we have to delete the tables? Can you guys maybe talk to Gravity Forms and work this out?

    2018-06-19 06:59:19 Error (1024): An outdated add-on or custom code is attempting to access the wp_rg_lead table which is not valid in this version of Gravity Forms. Update your add-ons and custom code to prevent loss of form data. Further details: https://docs.gravityforms.com/database-storage-structure-reference/#changes-from-gravity-forms-2-2 file: /path/to/wp-content/plugins/gravityforms/gravityforms.php (line 5153)
    Request URI: /some-url/
    User IP: some-ip
    Trace: (gravityforms.php:5153),(class-wp-hook.php:286),(plugin.php:203),(wp-db.php:1789),(wp-db.php:2380),(class-itsec-backup.php:147),(class-itsec-backup.php:84),(class-itsec-backup.php:62),(class-wp-hook.php:286),(class-wp-hook.php:310),(plugin.php:453),(class-itsec-scheduler.php:269),(class-itsec-scheduler-page-load.php:252),(class-itsec-scheduler-page-load.php:224),(class-wp-hook.php:286),(class-wp-hook.php:310),(plugin.php:453),(wp-settings.php:450),(wp-config.php:130),(wp-load.php:37),(publicIncludes.inc.php:92),(calling-page.php:2)

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter metricmedia

    (@metricmedia)

    Anybody?

    Gravity Forms recently updated, which deprecated some old tables that are no longer needed.

    Or do we have to delete the tables?

    Do I understand correctly that Gravity Forms does not delete the old (wp_rg_*) tables ?

    Check with Gravity Forms whether these tables are supposed to still exist after migration and whether these old tables can be safely deleted.

    The only solution I see (based on the current info available) is to delete (or perhaps just rename) the old tables.

    • This reply was modified 6 years, 9 months ago by nlpro.
    Thread Starter metricmedia

    (@metricmedia)

    Correct, they do not delete the tables. However they have decided to tie error messages to any attempt to access them.

    I am inquiring if we can safely delete.

    Thanks for the feedback.

    I didn’t mention this in my previous post but the iTSec plugin Database Backup module will still try to access tables (to get the DDL (Data Definition Language) create statement of the table) even when they are excluded from the database backup.
    So it’s only the tables data that is excluded from the database backup. Its definition (table create DDL statement) is still included.

    The following piece of text underneath the Exclude Tables setting also points in this direction:

    …Select log tables above to exclude their data from the backup. Note: The table itself will be backed up, but not the data in the table.

    Thread Starter metricmedia

    (@metricmedia)

    Ah I see. OK well guess we still need to delete them then.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Gravity Forms tables causing error with backup’ is closed to new replies.