Update from 2.9 to 3.04 Killed My Database

  • Hi,

    I have setup Elementor for auto-update. As it went from 2.9 to 3.04 my database went from 56mb to 1.1gb on a website and another website to 500mb. On investigation of the second website, it seems that the options table had hundreds of entries with options name elementor_1_elementor_updater_batch_%, 28mb. Total elementor% entries where 230mb.

    Why does this happen?
    How do I clean these entries?

    Many thanks
    PS Happy to give dumps of the two options tables pre/post update.

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

  • Standard Elementor plugin options names are as follows.

    _elementor_installed_time
_transient_elementor_remote_info_api_data_3.0.5
_transient_timeout_elementor_remote_info_api_data_3.0.5
elementor_active_kit	
elementor_allow_tracking	
elementor_beta	
elementor_clear_cache	
elementor_enable_inspector	
elementor_install_history	
elementor_log	
elementor_maintenance_mode_exclude_mode	
elementor_maintenance_mode_exclude_roles	
elementor_maintenance_mode_mode	
elementor_maintenance_mode_template_id	
elementor_remote_info_feed_data	
elementor_remote_info_library	
elementor_replace_url	
elementor_reset_api_data	
elementor_rollback	
elementor_safe_mode	
elementor_scheme_color	
elementor_scheme_color-picker	
elementor_scheme_typography	
elementor_tracker_notice	
elementor_version
    Plugin Author ArielK

    (@arielk-1)

    There seems to be something preventing the database from being updated.

    Can you please share with us more details about the server/WP environment?

    Thread Starter walad7bab

    (@walad7bab)

    Sorry, I had replied via email but it never updated here.

    The option_name with highest frequency is “elementor_1_elementor_updater_batch_%” for example

    Option_name:
    elementor_1_elementor_updater_batch_346e001a0f3fed105873c028d307

    Option_value:
    a:4:{i:0;a:1:{s:8:”callback”;a:2:{i:0;s:31:”Elementor\Core\Upgrade\Upgrades”;i:1;s:37:”_v_3_0_0_move_general_settings_to_kit”;}}i:1;a:1:{s:8:”callback”;a:2:{i:0;s:31:”Elementor\Core\Upgrade\Upgrades”;i:1;s:35:”_v_3_0_0_move_default_colors_to_kit”;}}i:2;a:1:{s:8:”callback”;a:2:{i:0;s:31:”Elementor\Core\Upgrade\Upgrades”;i:1;s:33:”_v_3_0_0_move_saved_colors_to_kit”;}}i:3;a:1:{s:8:”callback”;a:2:{i:0;s:31:”Elementor\Core\Upgrade\Upgrades”;i:1;s:39:”_v_3_0_0_move_default_typography_to_kit”;}}}

    I can provide you with a database dump if you have a private drive.

    • This reply was modified 4 years, 6 months ago by walad7bab.
    Thread Starter walad7bab

    (@walad7bab)

    A little more insight, on my smaller website, here is SQL result

    SELECT * FROM *****options WHERE option_name LIKE ‘%elementor%’
    (467075 total, Query took 0.2126 seconds.)

    I am hosted on ionos.co.uk

    Hi,

    I’m having the same problem, my wp_options table is full of elementor_1_elementor_updater_batch_****(actual size 1.79GB)

    Any solutions?

    Thanks

    I had the exact same problem. It also filled up error logs until the drive was full and totally took down the site. Can’t get rid of the notice to run the elementor database update in the admin either. Did you have any luck resolving this? Can I just delete those 100k rows?

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Update from 2.9 to 3.04 Killed My Database’ is closed to new replies.