Hello,
I’m needing to setup a form that will allow users to request a sale catalog from a livestock company.
I would like the info to be able to be exported as a single mailing list (ie. an excel spreadsheet with a column for name, address, etc.) rather than receiving individual email requests.
Can anyone suggest how I should go about this? Can you do this with Contact Form 7? How do I get the data stored somewhere/retrieve it?

Example of form needed: https://www.44farms.com/public-sales/the-fall-bull-sale/

Thanks in advance!

I see there is a way to EXPORT the forms. Is there a way to IMPORT them? I need to import them into another website. Thanks.

Hi everyone, i have a big problem on my website. I’m trying to install and activate woocommerce (last version) but when I go to activate it, it make a fatal error blocking access to the site. The debug shows me that:

Errore sul database di WordPress: [Table ‘dbs356719.asdbactionscheduler_actions’ doesn’t exist]
SELECT a.action_id FROM asdbactionscheduler_actions a WHERE a.hook=’action_scheduler/migration_hook’ AND a.status=’in-progress’ ORDER BY scheduled_date_gmt DESC LIMIT 1

Errore sul database di WordPress: [Table ‘dbs356719.asdbactionscheduler_actions’ doesn’t exist]
SELECT a.action_id FROM asdbactionscheduler_actions a WHERE a.hook=’action_scheduler/migration_hook’ AND a.status=’pending’ ORDER BY scheduled_date_gmt ASC LIMIT 1

Errore sul database di WordPress: [Table ‘dbs356719.asdbactionscheduler_actions’ doesn’t exist]
SELECT a.action_id FROM asdbactionscheduler_actions a WHERE a.hook=’action_scheduler/migration_hook’ AND a.status=’in-progress’ ORDER BY scheduled_date_gmt DESC LIMIT 1

Errore sul database di WordPress: [Table ‘dbs356719.asdbactionscheduler_actions’ doesn’t exist]
SELECT a.action_id FROM asdbactionscheduler_actions a WHERE a.hook=’action_scheduler/migration_hook’ AND a.status=’pending’ ORDER BY scheduled_date_gmt ASC LIMIT 1

Errore sul database di WordPress: [Table ‘dbs356719.asdbactionscheduler_groups’ doesn’t exist]
SELECT group_id FROM asdbactionscheduler_groups WHERE slug=’action-scheduler-migration’

Errore sul database di WordPress: [Table ‘dbs356719.asdbactionscheduler_groups’ doesn’t exist]
SHOW FULL COLUMNS FROM asdbactionscheduler_groups

Errore sul database di WordPress: [Table ‘dbs356719.asdbactionscheduler_actions’ doesn’t exist]
SHOW FULL COLUMNS FROM asdbactionscheduler_actions

Si è verificato un errore critico sul tuo sito web. Controlla la casella di posta dell’amministratore del sito per istruzioni.

Scopri di più riguardo al debug in WordPress.

Only version 3.1.6 works good.

I’ve contacted woocommerce support, here is their answer:

Hi Alberto,

Thank you for reaching out to WooCommerce.com support.

I understand that when you’re activating WooCommerce on your site, you’re seeing the following error:

Errore sul database di WordPress: [Table ‘dbs356719.asdbactionscheduler_actions’ doesn’t exist]
SELECT a.action_id FROM asdbactionscheduler_actions a WHERE a.hook=’action_scheduler/migration_hook’ AND a.status=’in-progress’ ORDER BY scheduled_date_gmt DESC LIMIT 1
The error occurs when one of the active plugins or themes is conflicting with WooCommerce.

The best way to determine if the issue is being caused by a theme and/or plugin is to temporarily switch your theme to Storefront (https://woocommerce.com/products/storefront/?aff=10486&cid=1131038) and disable all plugins. Finally, test to see if the issue is resolved by activating WooCommerce.

To figure out which plugin is causing the problem, continue to the next step – reactivate your other plugins one by one, testing after each, until you find the one causing conflict.

Here’s a more extensive explanation in our docs: https://docs.woocommerce.com/document/how-to-test-for-conflicts/

Tools to help you troubleshoot:

Meks Quick Plugin Disabler is a plugin you can install which will remember what plugins you currently have active so it’s easy to switch them back on. Link: https://wordpress.org/plugins/meks-quick-plugin-disabler/

You can clone your site to a staging environment and perform tests without modifying your live site or impacting customers. Many hosts provide staging facilities, so it’s worth checking in with them. It’s also possible to do it using the free WP Staging plugin. Link: https://wordpress.org/plugins/wp-staging/

As a heads up, this support channel is for customers of our premium products sold on WooCommerce.com Extension Store, so the support we can provide you here is a bit limited. If you need additional assistance, please make a post on the WooCommerce Support Forums. Many of our team members help out there as well.

If you have purchased a product on WooCommerce.com, please reply here with the order number for your purchase so we can look this up and help further.

I’ve followed the instructions but:

Thanks for reply, Unfortunately your following istructions doesn’t work for me. I’ve deactivated all plugins i have and after i’ve installed woocommerce storefront, wordpress report to me the same error. There is a problem with database, my hosting can’t resolve my problem, they suggests me to contact you. I have no idea how to resolve the problem, i need the last version of woocommerce for my shopping online or my activity will stop. It seems that the problem is in “asdbactionscheduler_actions”, i dont know if it is a table of database in conflict, i have no tables in database called “asdbactionscheduler_actions”, i only know that “asdb” is a prefix assigned by me for the tables. Please help me.

Now wordpress give me these errors:

Errore sul database di WordPress: [Table ‘dbs356719.asdbactionscheduler_actions’ doesn’t exist]
SELECT a.action_id FROM asdbactionscheduler_actions a WHERE a.hook=’action_scheduler/migration_hook’ AND a.status=’in-progress’ ORDER BY scheduled_date_gmt DESC LIMIT 1

Errore sul database di WordPress: [Table ‘dbs356719.asdbactionscheduler_actions’ doesn’t exist]
SELECT a.action_id FROM asdbactionscheduler_actions a WHERE a.hook=’action_scheduler/migration_hook’ AND a.status=’pending’ ORDER BY scheduled_date_gmt ASC LIMIT 1

Errore sul database di WordPress: [Table ‘dbs356719.asdbactionscheduler_actions’ doesn’t exist]
SELECT a.action_id FROM asdbactionscheduler_actions a WHERE a.hook=’action_scheduler/migration_hook’ AND a.status=’in-progress’ ORDER BY scheduled_date_gmt DESC LIMIT 1

Errore sul database di WordPress: [Table ‘dbs356719.asdbactionscheduler_actions’ doesn’t exist]
SELECT a.action_id FROM asdbactionscheduler_actions a WHERE a.hook=’action_scheduler/migration_hook’ AND a.status=’pending’ ORDER BY scheduled_date_gmt ASC LIMIT 1

Errore sul database di WordPress: [Table ‘dbs356719.asdbactionscheduler_groups’ doesn’t exist]
SELECT group_id FROM asdbactionscheduler_groups WHERE slug=’action-scheduler-migration’

Errore sul database di WordPress: [Table ‘dbs356719.asdbactionscheduler_groups’ doesn’t exist]
SHOW FULL COLUMNS FROM asdbactionscheduler_groups

Errore sul database di WordPress: [Table ‘dbs356719.asdbactionscheduler_actions’ doesn’t exist]
SHOW FULL COLUMNS FROM asdbactionscheduler_actions

This plugin is very helpful to determine whether forms are even getting through the websites. Works well!

Hi, Folks

After update from 3.9.3 to 4.3.1 version, I’ve run database update.
Everything went without error, but on the new dashboard and on WooCommerce -> Customers, the data is not complete.
I see 988 customers instead of 1170. The last order is from April 23, 2020.
The thing is on ‘Reports -> Customers -> Customer List’ I see all Customers. Everything is ok also on WooCommrece -> Orders.

I’ve done update twice on PHP 7.3, and another one on staging server (different hosting) on PHP 7.1.

Orders made after database update are appearing on the system.

New stats looks great but for me it’s a little bit useless right now.

Any clues? Please help.

hi

when a course is purchased, the do_enroll function generates a post in wp_posts (post_type = tutor_enrolled). in this post, post_author is the user_id.

what can be the reason that this post_author is sometimes 0, leaving the student without being enrolled in the course?

thanks

I found database table entries from plugins I removed years ago! I forgot I even installed them to begin with. Cleaned up a lot of junk. Just what I needed.

I need to replace an outdated product name in every location on my website. But first, I want to see where this outdated product name exists or occurs. I have downloaded Search & Replace and also Better Search Replace, and both plugins do not show a detailed report or location of where the product name is. I also need it to show where it occurs in every location beyond my posts (wp_posts), and I don’t necessarily need to replace the name in my databases. Any suggestions? Does a plugin for this exist?

Hello, I have noticed that officially this plugin takes up the most database space on my sites, all of them. It’s not too surprising but I was wondering if anything can be done so that the database doesn’t get big? I have about 10 websites running this plugin and the average size for the table is minimum 40mb.

Hi
I have uninstalled Woocommerce from my site as it was never used, yet I notice database tables like: wp_woocommerce_shipping_zones / methods etc along with other tables which appear to be from plugins long ago uninstalled.

Is there a reliable plugin that will go through and see which tables are no longer in use and allow them to be removed?

It seems I have a lot of tables that are there in name only?

I have multiple Teams and somewhat when there is an update etc, all member data and team settings gets lost.

The easiest way to replicate the issue is to migrate a site with existing teams to a different domain.

I’m using the Modern Events Calendar plugin for WordPress and I am pushing the events from one site to another site (not a multisite!) via the Distributor plugin. When pushing events the mec_events and mec_dates tables’ database entries are not created till I manually hit the “update” button in the pushed event. As far as I get it said entries are pushed as post meta, and then converted to db entries on hitting the update button.

Or in other words: The update button of a event type post triggers stuff in the event plugin that I need to happen, and I’m unable to find out what exactly needs to happen, because the plugin is very complex. So my idea would be to find a way to actually push the update button to trigger everything I need BUT automatically. Dirty, I know, but seems to be the “easy way out” to me. The events are imported perfectly fine, and after manually using the update button in the event everything is correct. It’s just that I don’t want to have to do that every time manually for every event.

How can I trigger the same stuff that happens when manually using the update button, but via code / php?

(Obviously I already tried wp_update_post etc., pushing the event as draft and then publishing it via code, but none of those trigger the actions I need the event plugin to do, hence the creation of db entries from post meta. Only the dreaded big blue button does.)

Very simple example of what I tried would be this (after pushing the draft):

    // Publish post 37
      $post = array(
          'ID'           => 37,
          'post_status'   => 'publish',
      );
    
    
    // Update the post into the database
      wp_update_post( $post );

I assumed this (or wp_insert_post or save_post) would trigger all hooks of the update button, but to no avail.

After playing around with changing meta data using the following code I am now sure that wp_update_post doesn’t trigger the needed actions.

    function change_postmeta(){
    
           $args = array(
               'post_type'      => 'mec-events',
               'post_status'    => 'publish',
               'posts_per_page' => -1
           );
           $posts = get_posts( $args );
    
        foreach($posts as $p) :
    
            $meta = get_post_meta($ID, 'mec_start_date',true);
    
            echo "<script>console.log('POST IDs: " . json_encode($ID) . "</script>";
    
    
            if($meta) :
                $my_post = array();
                $my_post['ID'] = $p->ID;
                $my_post['post_content'] = $meta . "works!"  . $p->post_content ;
    
                // Update the post into the database
                wp_update_post( $my_post );
                unset($my_post);
    
                //remove the meta key
                delete_post_meta($p->ID, 'mec_start_date');
    
            endif;
    
        endforeach;
    
    
    }

Using this prints the event start date successfully to the content and saves it, but it doesn’t trigger the same stuff that happens when doing a manual update of a post. And I still haven’t found a way to find out what is actually tied to the blue button.

Hi!

Could you please add a PRIMARY KEY to the TEMPORARY TABLEs created by this plugin?

https://plugins.trac.wordpress.org/browser/pw-bulk-edit/trunk/includes/sql-builder.php#L113

https://plugins.trac.wordpress.org/browser/pw-bulk-edit/trunk/includes/sql-builder.php#L153

This will ensure that the plugin continues to work on WordPress.com (and elsewhere that requires primary keys to exist). Based on what the code is doing I think it should be as simple as adding PRIMARY KEY to the post_id field in both cases.

Additionally, but unrelated. I would suggest changing the filed definitions to match the tables that are selected from. For example, the wp_posts table uses bigint(20) unsigned for the ID column but this temporary table uses INT for post_id which means if someone has IDs larger than 2147483647 in their wp_posts table this code will not work as expected.

Please let me know if you have any questions!

Hi,

I’ve just installed this plugin and looks promising but I’ve notice an error on activation:

Error Unable to create or change a table without a primary key, when the system variable ‘sql_require_primary_key’ is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.

CREATE TABLE IF NOT EXISTS wp_rank_math_internal_meta (
  object_id bigint(20) UNSIGNED NOT NULL,
  internal_link_count int(10) UNSIGNED NULL DEFAULT 0,
  external_link_count int(10) UNSIGNED NULL DEFAULT 0,
  incoming_link_count int(10) UNSIGNED NULL DEFAULT 0,
  UNIQUE KEY object_id (object_id)
) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci

I know I can disable ‘sql_require_primary_key’ variable but obviously it can be a performance problem on larga databases and I think it’s a good practice always add a primary key.

Hello, we noticed that the two latest versions of GiveWP plugin fails to create the necessary database tables. We tested on 3 different hosts (localhost/laragon, cPanel shared hosting and AWS VPS running Ubuntu/RunCloud management software) and even after running the database update as prompted, the following tables are missing.

wp_give_sessions
wp_give_sequential_ordering

Fix for this is to install version 2.4.2 (which creates the tables correctly) and then upgrade to later versions or you can manually create the above mentioned tables to your DB.

Due to the missing tables Donation Confirmation page won’t load correctly, instead server returns error 500 (There has been critical error on your WordPress site…), however you won’t see the error if you use the popup modal form, it will just keep on loading with the circle animation.

Just FYI for anyone who is struggling to get the plugin to work. Also FYI for devs to take a look into this

Hi, we are setting up a new WordPress website that uses WooCommerce for the eCommerce side of the site. However, we get an error message from WooCommerce, which is “WooCommerce eBB6F6_wc_reserved_stock table creation failed. Does the wp_ifz5l user have CREATE privileges on the wp_1cq3p database?”, which is preventing us from developing the site further. As we are running the site on our own VPS, we are able to change the settings for the Database, so I had a look to see if the CREATE privilege had been disabled. I found however that this was not the case and the database user had this privilege enabled. After having a look at the WooCommerce Status page I also found that the following items were reported as “Table does not exist”:

eBB6F6_woocommerce_sessions
eBB6F6_woocommerce_api_keys
eBB6F6_woocommerce_attribute_taxonomies
eBB6F6_woocommerce_downloadable_product_permissions
eBB6F6_woocommerce_order_items
eBB6F6_woocommerce_order_itemmeta
eBB6F6_woocommerce_tax_rates
eBB6F6_woocommerce_tax_rate_locations
eBB6F6_woocommerce_shipping_zones
eBB6F6_woocommerce_shipping_zone_locations
eBB6F6_woocommerce_shipping_zone_methods
eBB6F6_woocommerce_payment_tokens
eBB6F6_woocommerce_payment_tokenmeta
eBB6F6_woocommerce_log

I have tried starting fresh several times (i.e. deleting the whole website and clearing the files then creating them anew along with a fresh WordPress install) but this has not fixed the problem. The theme we are running is Bridge and I have received the WooCommerce error both with and without the theme installed. Would you be able to help us with this issue?

Hi,

I recently migrated my domain. Since then, I have an issue with actionscheduler.

My table actionscheduler_logs is quickly huge. When the table actionscheduler_actions starts to have data, the “logs one” is getting bigger and bigger…

I deactivated WC admin function, reinstall Woocommerce version 4.3, but it continues to run.

The only I can manage the problem is by emptying the actionscheduler_actions and actionscheduler_logs tables…

Thanks for your help and for your reply.

`
### WordPress Environment ###

WordPress address (URL): https://toutpourmasante.fr
Site address (URL): https://toutpourmasante.fr
WC Version: 4.3.1
REST API Version: 1.0.10
WC Blocks Version: 2.7.2
Action Scheduler Version: 3.1.6
WC Admin Version: 1.3.1 inactif
Log Directory Writable:
WP Version: 5.4.2
WP Multisite: –
WP Memory Limit: 512 MB
WP Debug Mode: –
WP Cron:
Language: fr_FR
External object cache: –

### Server Environment ###

Server Info: Apache
PHP Version: 7.4.8
PHP Post Max Size: 512 MB
PHP Time Limit: 360
PHP Max Input Vars: 250000
cURL Version: 7.62.0
OpenSSL/1.0.2k

SUHOSIN Installed: –
MySQL Version: 5.5.5-10.3.23-MariaDB
Max Upload Size: 512 MB
Default Timezone is UTC:
fsockopen/cURL:
SoapClient:
DOMDocument:
GZip:
Multibyte String:
Remote Post:
Remote Get:

### Database ###

WC Database Version: 4.3.1
WC Database Prefix: mod407_
Taille totale de la base de données: 201.62MB
Taille de la base de données: 124.72MB
Taille de l’index: 76.90MB
mod407_woocommerce_sessions: Données : 0.19MB + Index : 0.02MB + Moteur InnoDB
mod407_woocommerce_api_keys: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB
mod407_woocommerce_attribute_taxonomies: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB
mod407_woocommerce_downloadable_product_permissions: Données : 2.52MB + Index : 5.81MB + Moteur InnoDB
mod407_woocommerce_order_items: Données : 1.52MB + Index : 0.22MB + Moteur InnoDB
mod407_woocommerce_order_itemmeta: Données : 4.52MB + Index : 5.03MB + Moteur InnoDB
mod407_woocommerce_tax_rates: Données : 0.02MB + Index : 0.06MB + Moteur InnoDB
mod407_woocommerce_tax_rate_locations: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB
mod407_woocommerce_shipping_zones: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_woocommerce_shipping_zone_locations: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB
mod407_woocommerce_shipping_zone_methods: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_woocommerce_payment_tokens: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB
mod407_woocommerce_payment_tokenmeta: Données : 0.08MB + Index : 0.09MB + Moteur InnoDB
mod407_woocommerce_log: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB
mod407_actionscheduler_actions: Données : 0.02MB + Index : 0.11MB + Moteur InnoDB
mod407_actionscheduler_claims: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_actionscheduler_groups: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_actionscheduler_logs: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB
mod407_aiowps_events: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_aiowps_failed_logins: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_aiowps_global_meta: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_aiowps_login_activity: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_aiowps_login_lockdown: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_aiowps_permanent_block: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_blc_filters: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_blc_instances: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_blc_links: Données : 0.09MB + Index : 0.00MB + Moteur InnoDB
mod407_blc_synch: Données : 0.50MB + Index : 0.00MB + Moteur InnoDB
mod407_booking: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_bookingdates: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_commentmeta: Données : 0.09MB + Index : 0.00MB + Moteur InnoDB
mod407_comments: Données : 4.52MB + Index : 0.72MB + Moteur InnoDB
mod407_cpappbk_clickatell: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_cpappbk_forms: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_cpappbk_form_cancellationlinks: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_cpappbk_form_followuplinks: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_cpappbk_form_reminderlinks: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_cpappbk_form_SchedudeCalContents: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_cpappbk_form_statusupemails: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_cpappbk_googlecalapi: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_cpappbk_googlecalapi_ev: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_cpappbk_mailchimp: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_cpappbk_messages: Données : 0.11MB + Index : 0.00MB + Moteur InnoDB
mod407_css_js_manager: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_edd_customermeta: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_edd_customers: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_ewwwio_images: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_ewwwio_queue: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_failed_jobs: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_gglcptch_whitelist: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_gp_glossaries: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_gp_glossary_entries: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_gp_meta: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_gp_originals: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_gp_permissions: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_gp_projects: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_gp_translations: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_gp_translation_sets: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_learndash_user_activity: Données : 0.38MB + Index : 0.78MB + Moteur InnoDB
mod407_learndash_user_activity_meta: Données : 1.52MB + Index : 0.70MB + Moteur InnoDB
mod407_links: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_litespeed_img_optm: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_litespeed_optimizer: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_login_redirects: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_mailchimp_carts: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_mailerlite_checkouts: Données : 0.44MB + Index : 0.00MB + Moteur InnoDB
mod407_options: Données : 13.06MB + Index : 9.61MB + Moteur InnoDB
mod407_postmeta: Données : 54.58MB + Index : 32.11MB + Moteur InnoDB
mod407_posts: Données : 14.50MB + Index : 3.50MB + Moteur InnoDB
mod407_pts_tables: Données : 0.38MB + Index : 0.00MB + Moteur InnoDB
mod407_queue: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_redirection_404: Données : 0.02MB + Index : 0.06MB + Moteur InnoDB
mod407_redirection_groups: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB
mod407_redirection_items: Données : 0.05MB + Index : 0.09MB + Moteur InnoDB
mod407_redirection_logs: Données : 0.09MB + Index : 0.08MB + Moteur InnoDB
mod407_rp4wp_cache: Données : 0.09MB + Index : 0.00MB + Moteur InnoDB
mod407_smush_dir_images: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB
mod407_sm_sessions: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB
mod407_termmeta: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB
mod407_terms: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB
mod407_term_relationships: Données : 0.05MB + Index : 0.05MB + Moteur InnoDB
mod407_term_taxonomy: Données : 0.11MB + Index : 0.03MB + Moteur InnoDB
mod407_tm_taskmeta: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB
mod407_tm_tasks: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB
mod407_usermeta: Données : 9.52MB + Index : 11.03MB + Moteur InnoDB
mod407_users: Données : 1.52MB + Index : 0.73MB + Moteur InnoDB
mod407_wcpdf_invoice_number: Données : 0.20MB + Index : 0.00MB + Moteur InnoDB
mod407_wc_admin_notes: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wc_admin_note_actions: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB
mod407_wc_category_lookup: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wc_customer_lookup: Données : 1.52MB + Index : 0.44MB + Moteur InnoDB
mod407_wc_download_log: Données : 1.52MB + Index : 1.94MB + Moteur InnoDB
mod407_wc_order_coupon_lookup: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB
mod407_wc_order_product_lookup: Données : 1.52MB + Index : 0.75MB + Moteur InnoDB
mod407_wc_order_stats: Données : 1.52MB + Index : 0.48MB + Moteur InnoDB
mod407_wc_order_tax_lookup: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB
mod407_wc_product_meta_lookup: Données : 0.02MB + Index : 0.09MB + Moteur InnoDB
mod407_wc_reserved_stock: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wc_tax_rate_classes: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB
mod407_wc_webhooks: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB
mod407_wfblockediplog: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wfblocks7: Données : 0.02MB + Index : 0.05MB + Moteur InnoDB
mod407_wfconfig: Données : 0.09MB + Index : 0.00MB + Moteur InnoDB
mod407_wfcrawlers: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wffilechanges: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wffilemods: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wfhits: Données : 0.02MB + Index : 0.05MB + Moteur InnoDB
mod407_wfhoover: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB
mod407_wfissues: Données : 0.02MB + Index : 0.06MB + Moteur InnoDB
mod407_wfknownfilelist: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wflivetraffichuman: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB
mod407_wflocs: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wflogins: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB
mod407_wfls_2fa_secrets: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB
mod407_wfls_settings: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wfnotifications: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wfpendingissues: Données : 0.02MB + Index : 0.06MB + Moteur InnoDB
mod407_wfreversecache: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wfsnipcache: Données : 0.02MB + Index : 0.05MB + Moteur InnoDB
mod407_wfstatus: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB
mod407_wftrafficrates: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wpfm_backup: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wppcp_group_users: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wppcp_private_page: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wp_pro_quiz_category: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wp_pro_quiz_form: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB
mod407_wp_pro_quiz_lock: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wp_pro_quiz_master: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wp_pro_quiz_prerequisite: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wp_pro_quiz_question: Données : 0.09MB + Index : 0.03MB + Moteur InnoDB
mod407_wp_pro_quiz_statistic: Données : 0.16MB + Index : 0.00MB + Moteur InnoDB
mod407_wp_pro_quiz_statistic_ref: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB
mod407_wp_pro_quiz_template: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_wp_pro_quiz_toplist: Données : 0.02MB + Index : 0.00MB + Moteur InnoDB
mod407_yoast_indexable: Données : 2.52MB + Index : 1.03MB + Moteur InnoDB
mod407_yoast_indexable_hierarchy: Données : 0.05MB + Index : 0.05MB + Moteur InnoDB
mod407_yoast_migrations: Données : 0.02MB + Index : 0.02MB + Moteur InnoDB
mod407_yoast_primary_term: Données : 0.02MB + Index : 0.03MB + Moteur InnoDB
mod407_yoast_seo_links: Données : 1.50MB + Index : 0.28MB + Moteur InnoDB
mod407_yoast_seo_meta: Données : 1.52MB + Index : 0.00MB + Moteur InnoDB

### Post Type Counts ###

attachment: 1131
booking_slot_freez: 1
custom_css: 6
customize_changeset: 57
download: 2
edd_log: 2
edd_payment: 2
elementor_library: 1
forum: 4
ig_campaign: 3
ig_message: 3
is_search_form: 1
mailpoet_page: 1
nav_menu_item: 53
oembed_cache: 48
page: 18
pf_contact: 231
post: 256
post_grid: 1
post_grid_layout: 6
product: 50
revision: 101
ris_gallery: 1
rp4wp_link: 679
rpt_pricing_table: 2
sa_slider: 2
sfwd-courses: 9
sfwd-lessons: 69
sfwd-question: 61
sfwd-quiz: 4
sfwd-topic: 66
sfwd-transactions: 1
shop_coupon: 8
shop_order: 6443
shop_order_refund: 8
simple-pay: 1
slick_slider: 3
sp_imageslider: 1
sumo_payment_plans: 1
sumo_pp_cron_jobs: 1
sumo_pp_masterlog: 7
sumo_pp_payments: 1
testimonial: 6
testimonial_rotator: 2
topic: 5
wc_membership_plan: 5
wc_product_table: 4
wc_user_membership: 1517
wcpa_pt_forms: 1
wcps: 1
wpcf7_contact_form: 1
wpforms: 1
wysijap: 1
xlwcty_thankyou: 5

### Security ###

Secure connection (HTTPS):
Hide errors from visitors:

### Active Plugins (50) ###

404 Page by SeedProd: par SeedProd – 1.0.0
a3 Lazy Load: par a3rev Software – 2.3.3
Ajax Search Lite: par Ernest Marcinko – 4.8.3
Autoptimize: par Frank Goossens (futtta) – 2.7.6
bbPress: par Les contributeurs à bbPress – 2.6.5
Beaver Builder Plugin (Lite Version): par The Beaver Builder Team – 2.3.2.5
Broken Link Checker: par WPMU DEV – 1.11.13
Contact Form 7: par Takayuki Miyoshi – 5.2.1
Cookie Notice: par dFactory – 1.3.2
Custom Permalinks: par Sami Ahmed Siddiqui – 1.5.1
Customer Reviews for WooCommerce: par Customer Reviews – 3.118
Design Upgrade for LearnDash: par Escape Creative – 2.7
Disable WooCommerce Admin: par – 1.0 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.3.1
Duplicate Page: par mndpsingh287 – 4.2
Easy FAQ with Expanding Text: par bgentry – 3.2.8.3.1
Enhanced E-commerce for Woocommerce store: par Tatvic – 2.3.4 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.3.1
reCaptcha by BestWebSoft: par BestWebSoft – 1.57
Google Site Verification plugin using Meta Tag: par Himanshu Parashar – 1.2
Kadence WooCommerce Email Designer: par Kadence WP – 1.4.3
LearnDash LMS – bbPress Integration: par LearnDash – 2.1.1
LearnDash LMS – Course Grid: par LearnDash – 1.6.0
LearnDash LMS – Stripe Integration: par LearnDash – 1.4.0
LearnDash LMS – WooCommerce Integration: par LearnDash – 1.7.0 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.3.1
LiteSpeed Cache: par LiteSpeed Technologies – 3.2.4
Loco Translate: par Tim Whitlock – 2.4.1
Neve Pro Addon: par ThemeIsle – 1.2.5
Redirection: par John Godley – 4.8
Related Posts pour WordPress: par Never5 – 2.0.3
Sassy Social Share: par Team Heateor – 3.3.10
LearnDash LMS: par LearnDash – 3.2.2
Shortcode Widget: par Gagan Deep Singh – 1.5.2
WooCommerce Side Cart: par XootiX – 2.1 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.3.1
Theme My Login: par Theme My Login – 7.1.1
Orbit Fox Companion: par Themeisle – 2.9.12
TinyMCE Advanced: par Andrew Ozz – 5.4.0
Ultimate Addons for Beaver Builder – Lite: par Brainstorm Force – 1.5.0
UpdraftPlus – Sauvegarde/Restauration: par UpdraftPlus.Com
DavidAnderson – 1.16.26

WooCommerce Product Table Lite: par WC Product Table – 1.9.3 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.3.1
NextMove Lite – Thank You Page for WooCommerce: par XLPlugins – 2.12.0 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.3.1
WooCommerce Customizer: par SkyVerge – 2.7.4 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.3.1
Direct Checkout for WooCommerce: par QuadLayers – 2.3.9 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.3.1
WooCommerce Stripe Gateway: par WooCommerce – 4.5.0 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.3.1
WooCommerce Menu Extension: par August Infotech – 1.6.2 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.3.1
WooCommerce PDF Invoices & Packing Slips: par Ewout Fernhout – 2.5.3
WooCommerce: par Automattic – 4.3.1
Yoast SEO: par Team Yoast – 14.7
Asset CleanUp : Page Speed Booster: par Gabriel Livan – 1.3.6.7
Smush: par WPMU DEV – 3.6.3
WPS Hide Login: par WPServeur
NicolasKulka
tabrisrp – 1.5.6

Beaver Builder Addons by WPZOOM: par WPZOOM – 1.3.1

### Inactive Plugins (2) ###

WooCommerce – MailerLite: par MailerLite – 1.4.8 – La version installée n’a pas été testée avec la version en cours de WooCommerce 4.3.1
WP Fastest Cache: par Emre Vona – 0.9.0.9

### Dropin Plugins (1) ###

advanced-cache.php: advanced-cache.php

### Must Use Plugins (1) ###

LearnDash LMS Multisite: par LearnDash – 1.0.0

### Settings ###

API Enabled:
Force SSL: –
Currency: EUR (€)
Currency Position: right
Thousand Separator:
Decimal Separator: ,
Number of Decimals: 2
Taxonomies: Product Types: course (course)
external (external)
grouped (grouped)
simple (simple)
variable (variable)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)

Connected to WooCommerce.com:

### WC Pages ###

Base de la boutique: #13 – /boutique/
Panier: #14 – /panier/
Commander: #15 – /commande/
Mon compte: #16 – /mon-compte/
Conditions générales de vente et d’utilisation: #20 – /conditions-generales-de-vente/

### Theme ###

Name: Neve Child
Version: 1.0.0
Author URL: https://themeisle.com
Child Theme:
Parent Theme Name: Neve
Parent Theme Version: 2.7.6
Parent Theme Author URL: https://themeisle.com
WooCommerce Support:

### Templates ###

Overrides: –

### Action Scheduler ###

Hi,

I tried everything and nothing works. My site has been hacked and now something keeps creating, or duplicating basic WordPress tables with different prefix (name). Here is an example:

wp_cvynetaio_commentmeta	    0	16.0 KB		32.0 KB	InnoDB	-	
wp_cvynetaio_comments	    	    0	16.0 KB		80.0 KB	InnoDB	-	
wp_cvynetaio_links	            	    0	16.0 KB		16.0 KB	InnoDB	-	
wp_cvynetaio_options		    131	528.0 KB	32.0 KB	InnoDB	-	
wp_cvynetaio_postmeta	            2	16.0 KB		32.0 KB	InnoDB	-	
wp_cvynetaio_posts	                    3	16.0 KB		64.0 KB	InnoDB	-	
wp_cvynetaio_term_relationships    0	16.0 KB		16.0 KB	InnoDB	-	
wp_cvynetaio_term_taxonomy	    0	16.0 KB		32.0 KB	InnoDB	-	
wp_cvynetaio_termmeta		       0	16.0 KB		32.0 KB	InnoDB	-	
wp_cvynetaio_terms		                 0	16.0 KB		32.0 KB	InnoDB	-	
wp_cvynetaio_usermeta		       15	16.0 KB		32.0 KB	InnoDB	-	
wp_cvynetaio_users		                0	16.0 KB		48.0 KB	InnoDB	-

Name cvynetaio is generated.

Another example with name fdobcsf:

wp_fdobcsf_commentmeta	            0	16.0 KB	32.0 KB	InnoDB	-	
wp_fdobcsf_comments	            0	16.0 KB	80.0 KB	InnoDB	-	
wp_fdobcsf_links	                    0	16.0 KB	16.0 KB	InnoDB	-	
wp_fdobcsf_options	                    114	64.0 KB	16.0 KB	InnoDB	-	
wp_fdobcsf_postmeta	                    4	16.0 KB	32.0 KB	InnoDB	-	
wp_fdobcsf_posts	                    3	16.0 KB	64.0 KB	InnoDB	-	
wp_fdobcsf_term_relationships	     0	16.0 KB	16.0 KB	InnoDB	-	
wp_fdobcsf_term_taxonomy	    0	16.0 KB	32.0 KB	InnoDB	-	
wp_fdobcsf_termmeta	            0	16.0 KB	32.0 KB	InnoDB	-	
wp_fdobcsf_terms	                    0	16.0 KB	32.0 KB	InnoDB	-	
wp_fdobcsf_usermeta	                    15	16.0 KB	32.0 KB	InnoDB	-	
wp_fdobcsf_users	                    0	16.0 KB	48.0 KB	InnoDB	-

It used to create around 600-800 tables a day. I removed some plugins and I managed to slow the process down by doing this but it didn’t fix it completely. If I leave it like this for a week or so, my database is full of useless tables.

Any suggestions on how to fix this? I tried Sucuri, Anti-Malware Security and Brute-Force Firewall, Wordfence, deleting and reinstalling plugins but nothing works.

Hello,

I was viewing wp_commentmeta table in phpMyAdmin when suddenly SSH connection to server got lost. Now my WordPress has the following errors.

wp_commentmeta: Table is marked as crashed and last repair failed
wp_wc_product_meta_lookup: 1 client is using or hasn’t closed the table properly
wp_actionscheduler_actions: 2 clients are using or haven’t closed the table properly
wp_actionscheduler_claims: 2 clients are using or haven’t closed the table properly
wp_actionscheduler_logs: 2 clients are using or haven’t closed the table properly

What I am suppose to do?

I am a novice. Please help.

Thank you,

Hello, I have a question. I have two plugins on my website:

1 – WP-Optimize – Clean, Compress, Cache
2 – Database

Both have the function of optimizing database tables; I would like someone to tell me if they really do the same thing, or if the functions, despite being tables optimization, operate differently.

Thankful,

Irina