All the content on my site was gone. When I went to investigate, I found my error log was filled with the following error:
WordPress database error Table './database_name/prefix_posts' is marked as crashed and should be repaired for query SELECT YEAR(post_date) AS `year`, MONTH(post_date) AS `month`, count(ID) as posts FROM prefix_posts WHERE post_type = 'post' AND post_status = 'publish' GROUP BY YEAR(post_date), MONTH(post_date) ORDER BY post_date DESC made by require, require_once, include, do_action, call_user_func_array, flexx_after_content, get_sidebar, locate_template, load_template, require_once, dynamic_sidebar, call_user_func_array, WP_Widget->display_callback, WP_Widget_Archives->widget, wp_get_archives
A very scary looking error, but it was easy to fix.
My Preferred Repair Method
[user@server ~/public_html]$ mysql -u user -p Enter password: Welcome to the MySQL monitor. Commands end with ; or g. Your MySQL connection id is 1120449 Server version: 5.1.48 MySQL Community Server (GPL) Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved. This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL v2 license Type 'help;' or 'h' for help. Type 'c' to clear the current input statement. mysql> connect database Connection id: 1120477 Current database: database mysql> select * from prefix_posts limit 1; ERROR 2006 (HY000): MySQL server has gone away No connection. Trying to reconnect... Connection id: 1120568 Current database: database ERROR 145 (HY000): Table './database/prefix_posts' is marked as crashed and should be repaired mysql> repair table prefix_posts; +-----------------------+--------+----------+----------+ | Table | Op | Msg_type | Msg_text | +-----------------------+--------+----------+----------+ | database.prefix_posts | repair | status | OK | +-----------------------+--------+----------+----------+ 1 row in set (3.56 sec) mysql> select * from prefix_posts limit 1; +----+-------------+---------------------+---------------------+--------------+------------+---------------+--------------+-------------+----------------+-------------+---------------+-----------+---------+--------+---------------------+---------------------+-----------------------+-------------+------------------------------------------------------------+------------+------------+----------------+---------------+ | ID | post_author | post_date | post_date_gmt | post_content | post_title | post_category | post_excerpt | post_status | comment_status | ping_status | post_password | post_name | to_ping | pinged | post_modified | post_modified_gmt | post_content_filtered | post_parent | guid | menu_order | post_type | post_mime_type | comment_count | +----+-------------+---------------------+---------------------+--------------+------------+---------------+--------------+-------------+----------------+-------------+---------------+-----------+---------+--------+---------------------+---------------------+-----------------------+-------------+------------------------------------------------------------+------------+------------+----------------+---------------+ | 12 | 8 | 2008-05-20 10:09:49 | 2008-05-20 15:09:49 | | 308image1 | 0 | | inherit | open | open | | 308image1 | | | 2008-05-20 10:09:49 | 2008-05-20 15:09:49 | | 0 | http://gaarai.com/wp-content/uploads/2008/05/308image1.gif | 0 | attachment | image/gif | 0 | +----+-------------+---------------------+---------------------+--------------+------------+---------------+--------------+-------------+----------------+-------------+---------------+-----------+---------+--------+---------------------+---------------------+-----------------------+-------------+------------------------------------------------------------+------------+------------+----------------+---------------+ 1 row in set (0.00 sec) mysql> exit Bye [user@server ~/public_html]$
For me, this was the easiest and quickest way to repair the table.
Repairing Tables with phpMyAdmin
For you, you might prefer to use phpMyAdmin. Fortunately, repairing a table with phpMyAdmin is easy.
- Log in to your phpMyAdmin or connect to it via your cPanel back-end.
- Select the database with the crashed table.
- Put a checkmark next to each crashed table.
- Select “Repair table” from the “With selected:” drop down at the bottom of the list.
- Let phpMyAdmin do its thing.
Did I help you?
- Send me a tip via Paypal.
- Help with this site’s hosting with my Linode referral code.
Here are 4 different methods to fix the scary-looking error: “WordPress database error Table ‘./db/wp_options’ is marked as crashed and should be repaired”.
NOTE: It is critically important that you backup your database before performing any of the following suggestions. You’re fully responsible for undertaking this yourself, I can’t be held responsible if you break anything.
Option 1. Repair the crashed table
Step 1. Log in to your phpMyAdmin or connect to it via your cPanel back-end
Step 2. Select the database with the crashed table
Step 3. Put a checkmark next to each crashed table or select them all
Step 4. Select “Repair table” from the “With selected:” drop-down at the bottom of the list.
Let phpMyAdmin do its thing.
If the database table engine is MyISAM the check was successful:
but if the engine is InnoDB then the repair will fail with the error message: The storage engine for the table doesn’t support repair
If Repair does not work and the table is still crashed, try the following:
Option 2. Change crashed table engine
Step 1. Log in to your phpMyAdmin or connect to it via your cPanel back-end
Step 2. Select the database with the crashed table
Step 3. Click on the crashed table name
Step 4. Click on the tab
Step 5. Under Table options change the Storage Engine from MyISAM to InnoDB or vice versa.
Step 6. Click on the button under Table options section
Option 3. Re-import the crashed table
The table contains rows that have crashed, so exporting the table’s content will export all rows besides those that have crashed. And if the table’s crashing rows aren’t essential to the functioning of WordPress itself, such as transients, plugin settings, etc. – this will then put an end to the problem.
Export table content
Step 1. Log in to your phpMyAdmin or connect to it via your cPanel back-end
Step 2. Select the database with the crashed table
Step 3. Click on the crashed table name
Step 4. Click on the
Step 5. Click on the button
Truncate the table
After the table content was successfully exported and saved as a file on your device, you need to truncate the table (delete all content) and re-import the downloaded file.
Step 6. click on the tab
Step 7. Scroll down to the bottom and click on the Empty the table (TRUNCATE) link
Step 8. Click OK on the confirmation popup
and you will see the confirmation message:
Import the table
Now you need to import back the downloaded file to the table.
Step 9. Click on the
Step 10. Click on Choose FIle then select the exported file and click on Open.
Step 5. Click on the button at the bottom and wait for the import to finish.
Option 4. Restore the crashed table
Backups are important, and if you have regular daily backups you can easily restore the crashed table from the backup.
The restore process is different depending on the backup solution of plugin that you use.
- PHPMyAdmin: Restoring your database from backup using phpMyAdmin
- Softaculous: How to Restore a Backup
- Updraft: How do I restore my site with UpdraftPlus?
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit «Cookie Settings» to provide a controlled consent.
[user@server ~/public_html]$ mysql —u user —p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or g.
Your MySQL connection id is 1120449
Server version: 5.1.48 MySQL Community Server (GPL)
Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL v2 license
Type ‘help;’ or ‘h’ for help. Type ‘c’ to clear the current input statement.
mysql> connect database
Connection id: 1120477
Current database: database
mysql> select * from prefix_posts limit 1;
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect…
Connection id: 1120568
Current database: database
ERROR 145 (HY000): Table ‘./database/prefix_posts’ is marked as crashed and should be repaired
mysql> repair table prefix_posts;
+————————+———+———-+———-+
| Table | Op | Msg_type | Msg_text |
+————————+———+———-+———-+
| database.prefix_posts | repair | status | OK |
+————————+———+———-+———-+
1 row in set (3.56 sec)
mysql> select * from prefix_posts limit 1;
+—-+————-+———————+———————+—————+————+—————+—————+————-+—————-+————-+—————+————+———+———+———————+———————+————————+————-+————————————————————+————+————+—————-+—————+
| ID | post_author | post_date | post_date_gmt | post_content | post_title | post_category | post_excerpt | post_status | comment_status | ping_status | post_password | post_name | to_ping | pinged | post_modified | post_modified_gmt | post_content_filtered | post_parent | guid | menu_order | post_type | post_mime_type | comment_count |
+—-+————-+———————+———————+—————+————+—————+—————+————-+—————-+————-+—————+————+———+———+———————+———————+————————+————-+————————————————————+————+————+—————-+—————+
| 12 | 8 | 2008—05—20 10:09:49 | 2008—05—20 15:09:49 | | 308image1 | 0 | | inherit | open | open | | 308image1 | | | 2008—05—20 10:09:49 | 2008—05—20 15:09:49 | | 0 | http://gaarai.com/wp-content/uploads/2008/05/308image1.gif | 0 | attachment | image/gif | 0 |
+—-+————-+———————+———————+—————+————+—————+—————+————-+—————-+————-+—————+————+———+———+———————+———————+————————+————-+————————————————————+————+————+—————-+—————+
1 row in set (0.00 sec)
mysql> exit
Bye
[user@server ~/public_html]$
Содержание
- Database error, table doesn’t exist
- Fix “WordPress database error Table … is marked as crashed and should be repaired”
- My Preferred Repair Method
- Repairing Tables with phpMyAdmin
- Comments
- Leave a Reply
- WordPress database error: [Table ‘wp_Dest.wp_users’ doesn’t exist]
- WordPress database error Table during upgrade to 4.0
Database error, table doesn’t exist
Hi,
I was trying to install the plugin in a live environment (AWS), and I’ve got a huge (
90MB) error log. One line (repeated):
As it turned out, MLP didn’t create the table, so I added it by hand, then used the ‘Reset Database’ function in the Reset plugin.
I had to also modify the code to make it work.
maxgalleria-media-library.php:2321 : $folder_id -> ‘$folder_id’
maxgalleria-media-library.php:511 : delete ENGINE=MyISAM
Thank you. Yes, we have a few cases where the database engine would not create the table due to engine type. Removing ENGINE=MyISAM will prevent this in the future. I will look into the change suggested for line 2321.
I also getting an error like:
WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ” at line 4 for query select post_title, ID, wp_mgmlp_folders.folder_id nfrom wp_posts nLEFT JOIN wp_mgmlp_folders ON(wp_posts.ID = wp_mgmlp_folders.post_id)nwhere by do_action(‘toplevel_page_media-library-folders’), WP_Hook->do_action, WP_Hook->apply_filters, MaxGalleriaMediaLib->media_library, MaxGalleriaMediaLib->get_parents
I have tried changing table as innodb and done maxgalleria-media-library.php:2321: $folder_id -> ‘$folder_id’
maxgalleria-media-library.php:511: delete ENGINE=MyISAM
but still not fixed, there is a duplicate key error first,…then after playing with the plugin wp-admin/admin.php?page=media-library-folders page goes blank and error occured as infinite loop, reinstalling the plugin also not saved from the problem
I tested 2321: $folder_id -> ‘$folder_id’ and did not get the expected result so I don’t think that will be changing. Don’t worry about the duplicate key error as it is only trying to add the same record twice and that issue is resolved in the next release which will come out next week.
Did you try resetting the folders data (database reset) as described in the troubleshooting tips of the plugin’s Support page on your site?
Thank you for quick reply. I have cleared folders data and reinstalled. the plugin works without any error in wordpress 5.3.2. we are using bedrock version of wordpress and error shows in that installation. currently using free version of the plugin for testing purpose. we will wait till next release, hence we need to purchase pro version if it works smoothly with bedrock too.
Latest release works properly.
This https://www.youtube.com/watch?v=OYoy-BYFIeE is a Media Library Folders Pro ACF Integration video uploaded 2 years back, can you please post a video about how to integrate it with acf pro and acf gutenberg blocks (https://wordpress.org/plugins/acf-blocks/), it may be helpful hence we need to purcahse and use it along with latest gutenberg block editor.
I’ll look into the possibility of making a video and will get back to you.
Источник
Fix “WordPress database error Table … is marked as crashed and should be repaired”
All the content on my site was gone. When I went to investigate, I found my error log was filled with the following error:
A very scary looking error, but it was easy to fix.
My Preferred Repair Method
For me, this was the easiest and quickest way to repair the table.
Repairing Tables with phpMyAdmin
For you, you might prefer to use phpMyAdmin. Fortunately, repairing a table with phpMyAdmin is easy.
- Log in to your phpMyAdmin or connect to it via your cPanel back-end.
- Select the database with the crashed table.
- Put a checkmark next to each crashed table.
- Select “Repair table” from the “With selected:” drop down at the bottom of the list.
- Let phpMyAdmin do its thing.
I tried this and I get the same error, it doesn’t repair the table. I don’t have shell access to the server the hosts the database. Anything else I can try? 🙁
The key is to be able to run that query. If you can, you might try scripting up something that runs that repair query.
Good tip, I used the phpMyAdmin method and it fixed my database issue perfectly – Thanks
Glad to hear that it worked for you.
Nice tip , I have used it & repaired table successfully .
Thanks – you’re a life saver! I freaked when I saw the message that my options table had crashed. Was able to fix it easily following your advice. Really appreciated.
[…] tomto článku jsem se dozvěděl jak tento problém […]
Great tip, this saved me a lot of time. As someone who had never touched MySQL before this was really helpful.
Thanks for the tip!
What can cause this issue and does it fix it for the long term?
You can find details about how table corruption can occur in these documents: Corrupted MyISAM Tables and Problems from Tables Not Being Closed Properly. If MySQL itself is crashing, this document has details on potential solutions: What to Do If MySQL Keeps Crashing.
As for whether or not repair table can prevent the issue from occurring again in the long-term, it can not. The repair table instruction tells MySQL to try to automatically repair the corrupted data, but it cannot do anything about the actual source of the corruption. The true source must be identified and fixed if the problems happen consistently.
Thanks A LOT! It worked perfectly. Now I can login again to my wp admin.
Great! Thank you so much.
The phpmyadmin thing just worked!
[…] Fix “WordPress database error Table … is marked as crashed and should be repaired” :: Chris Je… […]
Thanks dear,. You solved my problem
Thank you! I used the cpanel method and it worked like magic.
Leave a Reply
I believe that the free flow of information and ideas is key to the past and future development of mankind. Unless the content declares otherwise, the post content on this site is declared public domain (CC0 1.0 Universal) and can be used in any manner with or without attribution or permission. Of course, if you wish to give attribution back to me, that would be very nice. 🙂
You can view this site’s privacy policy here.
Источник
WordPress database error: [Table ‘wp_Dest.wp_users’ doesn’t exist]
I’m getting a strange error while trying to register on my website that looks like this:
I admit I used a really shitty plugin to change my table prefix and then had to change it back because my website was showing the installation again but everything works except this.
The weird thing is that when I changed it from wpD to wp_ It gave an error that wpD didn’t exist, and now that I changed it back to wpD it gives the error that wp_users doesnt exist… what the heck is going on?
- This topic was modified 2 years, 7 months ago by Steven Stern (sterndata) .
Forum Moderator & Support Team Rep
Look at your database using PHPMYADMIN. Does the table exist?
Why did you feel the need to change your table prefix? When you look at your DB with PHPMYADMIN, are the prefixes consistent and do they match the prefix set in wp-config.php?
Well as I mentioned I changed the prefix with a plugin from wpD to wp_, which returned the error that wpD doesn’t exist which was correct even though config.php CLEARLY had the prefix wp_ set. Then I changed it back and the error it gave was that wp_ didn’t exist which is also true although the config.php CLEARLY had wpD as a prefix.
I thought it was a server caching issue so I waited a while after which I was able to register a user. Then I thought my problems were over but 5 minutes later I got this error:
WordPress database error: [Unknown column ‘wpdusers.ID’ in ‘field list’]
Now this table does exist 100%, I’m looking at it now.
(I wanted to change the prefix because I’m building an application on top of wordpress and I need my own tables so I wanted to clean up the messy prefix.)
Forum Moderator & Support Team Rep
Make sure that the prefix is consisent across all tables and matches wp-config.php.
Jep, checked the entire database, they all match the prefix set in config. I’m quite astounded by the register form wanting to send something to the wrong table that doesn’t exist.
Forum Moderator & Support Team Rep
It may be that the table wp_users is corrupt. Use phpmyadmin to repair it.
Hmm I got this error:
“The storage engine for the table doesn’t support r…”
I don’t know if it matters but I have only 2 registered admins.
Forum Moderator & Support Team Rep
That’s fine. That’s just advisory.
EVERY SINGLE TABLE in the database starts with “wp_”, as in “wp_posts”, “wp_postmeta”, etc.?
The table prefix set in wp-config.php is “wp_”.
No no, every one of them right now starts with ‘wpD’, and the prefix set in config.php is ‘wpD’.
Wait no that’s not correct, I have a plugin called WPdatatables that makes its own tables without a the wpD prefix and simple uses wp.
Forum Moderator & Support Team Rep
That’s wrong. ALL tables for a given site MUST have the same prefix.
Источник
WordPress database error Table during upgrade to 4.0
During 4.0 upgrade, go the log filled with many entries of those below. The table described is available after update. Is it there anything I should do or be concerned about? Thanks.
Hi @alx359 , thanks for reporting this back to us!
If the tables wc_admin_notes and wc_admin_note_actions do exist, there should be no reason for concern. Seems like you hit some edge case where WC Admin was already running, but not all tables were in place yet.
Please be sure to run the database update if you haven’t done it yet (e.g. from WooCommerce > Status > Tools > Update database)
I’ve created an issue in GitHub to make sure we’ll look into the problem: https://github.com/woocommerce/woocommerce/issues/25876
- This reply was modified 2 years, 7 months ago by Peter Fabian .
I’m not sure this is an edge case. I’ve gotten this set of errors on every WC site I’ve updated, and I’m up to five now, all of which have the same set of errors. Out of the five, three did not have the WC Admin running elsewhere, if that helps.
Thanks for sharing your experience, @linux4me2 . We’re already working on a fix for this and will publish it with the next update.
I have similar problem after updating to 4.0.
Complains in the error log about missing tables:
wc_admin_notes
wc_admin_note_actions
wp_actionscheduler_actions
Should I have those?
But in my case I think that I used WP-Optimize plugin to delete those tables after the upgrade to 4.0. If I recall correctly the plugin said that these tables were no longer in use.
WooCommerce Admin related database tables in the WooCommerce 4.0 update;
- This reply was modified 2 years, 7 months ago by Luke Cavanagh . Reason: clarify wording
Thanks for helping.
I just uninstalled Woocommerce, cron jobs weren’t working with it activated. I’ll reinstall Woocommerce again when a new version arrives, if lucky it might recreate those missing tables.
Same errors in log:
.wp_wc_order_stats’ doesn’t exist
.wp_wc_customer_lookup’ doesn’t exist
.wp_wc_order_stats’ doesn’t exist
.wp_wc_order_product_lookup’ doesn’t exist
.wp_wc_order_coupon_lookup’ doesn’t exist
tables do not exist in my database. Tryied to uninstall woocommerce, delate tables and reinstall but still missing tables.
I don’t have any of these tables:
wp_wc_admin_notes
wp_wc_admin_note_actions
wp_wc_category_lookup
wp_wc_customer_lookup
wp_wc_order_coupon_lookup
wp_wc_order_product_lookup
wp_wc_order_stats
wp_wc_order_tax_lookup
Any update on this? How did you resolve it? I encountered the same problem after using WP Optimize plugin, probably deleting some of those tables. Reinstalling WooCommerce didn’t help. Particularly, this is the table I am missing: “wp_actionscheduler_actions”.
“WooCommerce > Status > Tools > Update database” does not work, and cron jobs are affected also.
I would like to have an SQL code that can recreate this table!
HI @roxymathew,
I had a local version with the right tables in database. I have copied manually the tables and the problem disappeared.
This is the SQL…hope can help you:
CREATE TABLE IF NOT EXISTS wp_wc_admin_notes (
note_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
name varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
type varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL,
locale varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL,
title longtext COLLATE utf8mb4_unicode_ci NOT NULL,
content longtext COLLATE utf8mb4_unicode_ci NOT NULL,
icon varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
content_data longtext COLLATE utf8mb4_unicode_ci,
status varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
source varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
date_created datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
date_reminder datetime DEFAULT NULL,
is_snoozable tinyint(1) NOT NULL DEFAULT ‘0’,
PRIMARY KEY ( note_id )
) ENGINE=InnoDB AUTO_INCREMENT=7 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_wc_admin_note_actions (
action_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
note_id bigint(20) unsigned NOT NULL,
name varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
label varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
query longtext COLLATE utf8mb4_unicode_ci NOT NULL,
status varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
is_primary tinyint(1) NOT NULL DEFAULT ‘0’,
PRIMARY KEY ( action_id ),
KEY note_id ( note_id )
) ENGINE=InnoDB AUTO_INCREMENT=14 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_wc_category_lookup (
category_tree_id bigint(20) unsigned NOT NULL,
category_id bigint(20) unsigned NOT NULL,
PRIMARY KEY ( category_tree_id , category_id )
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_wc_customer_lookup (
customer_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
user_id bigint(20) unsigned DEFAULT NULL,
username varchar(60) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
first_name varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
last_name varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
email varchar(100) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
date_last_active timestamp NULL DEFAULT NULL,
date_registered timestamp NULL DEFAULT NULL,
country char(2) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
postcode varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
city varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
state varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
PRIMARY KEY ( customer_id ),
UNIQUE KEY user_id ( user_id ),
KEY email ( email )
) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_wc_download_log (
download_log_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
timestamp datetime NOT NULL,
permission_id bigint(20) unsigned NOT NULL,
user_id bigint(20) unsigned DEFAULT NULL,
user_ip_address varchar(100) COLLATE utf8mb4_unicode_ci DEFAULT ”,
PRIMARY KEY ( download_log_id ),
KEY permission_id ( permission_id ),
KEY timestamp ( timestamp ),
CONSTRAINT fk_wp_wc_download_log_permission_id FOREIGN KEY ( permission_id ) REFERENCES wp_woocommerce_downloadable_product_permissions ( permission_id ) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_wc_order_coupon_lookup (
order_id bigint(20) unsigned NOT NULL,
coupon_id bigint(20) unsigned NOT NULL,
date_created datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
discount_amount double NOT NULL DEFAULT ‘0’,
PRIMARY KEY ( order_id , coupon_id ),
KEY coupon_id ( coupon_id ),
KEY date_created ( date_created )
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_wc_order_product_lookup (
order_item_id bigint(20) unsigned NOT NULL,
order_id bigint(20) unsigned NOT NULL,
product_id bigint(20) unsigned NOT NULL,
variation_id bigint(20) unsigned NOT NULL,
customer_id bigint(20) unsigned DEFAULT NULL,
date_created datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
product_qty int(11) NOT NULL,
product_net_revenue double NOT NULL DEFAULT ‘0’,
product_gross_revenue double NOT NULL DEFAULT ‘0’,
coupon_amount double NOT NULL DEFAULT ‘0’,
tax_amount double NOT NULL DEFAULT ‘0’,
shipping_amount double NOT NULL DEFAULT ‘0’,
shipping_tax_amount double NOT NULL DEFAULT ‘0’,
PRIMARY KEY ( order_item_id ),
KEY order_id ( order_id ),
KEY product_id ( product_id ),
KEY customer_id ( customer_id ),
KEY date_created ( date_created )
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_wc_order_stats (
order_id bigint(20) unsigned NOT NULL,
parent_id bigint(20) unsigned NOT NULL DEFAULT ‘0’,
date_created datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
date_created_gmt datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
num_items_sold int(11) NOT NULL DEFAULT ‘0’,
total_sales double NOT NULL DEFAULT ‘0’,
tax_total double NOT NULL DEFAULT ‘0’,
shipping_total double NOT NULL DEFAULT ‘0’,
net_total double NOT NULL DEFAULT ‘0’,
returning_customer tinyint(1) DEFAULT NULL,
status varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
customer_id bigint(20) unsigned NOT NULL,
PRIMARY KEY ( order_id ),
KEY date_created ( date_created ),
KEY customer_id ( customer_id ),
KEY status ( status (191))
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_wc_order_tax_lookup (
order_id bigint(20) unsigned NOT NULL,
tax_rate_id bigint(20) unsigned NOT NULL,
date_created datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
shipping_tax double NOT NULL DEFAULT ‘0’,
order_tax double NOT NULL DEFAULT ‘0’,
total_tax double NOT NULL DEFAULT ‘0’,
PRIMARY KEY ( order_id , tax_rate_id ),
KEY tax_rate_id ( tax_rate_id ),
KEY date_created ( date_created )
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_wc_product_meta_lookup (
product_id bigint(20) NOT NULL,
sku varchar(100) COLLATE utf8mb4_unicode_ci DEFAULT ”,
virtual tinyint(1) DEFAULT ‘0’,
downloadable tinyint(1) DEFAULT ‘0’,
min_price decimal(19,4) DEFAULT NULL,
max_price decimal(19,4) DEFAULT NULL,
onsale tinyint(1) DEFAULT ‘0’,
stock_quantity double DEFAULT NULL,
stock_status varchar(100) COLLATE utf8mb4_unicode_ci DEFAULT ‘instock’,
rating_count bigint(20) DEFAULT ‘0’,
average_rating decimal(3,2) DEFAULT ‘0.00’,
total_sales bigint(20) DEFAULT ‘0’,
tax_status varchar(100) COLLATE utf8mb4_unicode_ci DEFAULT ‘taxable’,
tax_class varchar(100) COLLATE utf8mb4_unicode_ci DEFAULT ”,
PRIMARY KEY ( product_id ),
KEY virtual ( virtual ),
KEY downloadable ( downloadable ),
KEY stock_status ( stock_status ),
KEY stock_quantity ( stock_quantity ),
KEY onsale ( onsale ),
KEY min_max_price ( min_price , max_price )
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_wc_tax_rate_classes (
tax_rate_class_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
name varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
slug varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
PRIMARY KEY ( tax_rate_class_id ),
UNIQUE KEY slug ( slug (191))
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_wc_webhooks (
webhook_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
status varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
name text COLLATE utf8mb4_unicode_ci NOT NULL,
user_id bigint(20) unsigned NOT NULL,
delivery_url text COLLATE utf8mb4_unicode_ci NOT NULL,
secret text COLLATE utf8mb4_unicode_ci NOT NULL,
topic varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
date_created datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
date_created_gmt datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
date_modified datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
date_modified_gmt datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
api_version smallint(4) NOT NULL,
failure_count smallint(10) NOT NULL DEFAULT ‘0’,
pending_delivery tinyint(1) NOT NULL DEFAULT ‘0’,
PRIMARY KEY ( webhook_id ),
KEY user_id ( user_id )
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_woocommerce_api_keys (
key_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
user_id bigint(20) unsigned NOT NULL,
description varchar(200) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
permissions varchar(10) COLLATE utf8mb4_unicode_ci NOT NULL,
consumer_key char(64) COLLATE utf8mb4_unicode_ci NOT NULL,
consumer_secret char(43) COLLATE utf8mb4_unicode_ci NOT NULL,
nonces longtext COLLATE utf8mb4_unicode_ci,
truncated_key char(7) COLLATE utf8mb4_unicode_ci NOT NULL,
last_access datetime DEFAULT NULL,
PRIMARY KEY ( key_id ),
KEY consumer_key ( consumer_key ),
KEY consumer_secret ( consumer_secret )
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_woocommerce_attribute_taxonomies (
attribute_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
attribute_name varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
attribute_label varchar(200) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
attribute_type varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL,
attribute_orderby varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL,
attribute_public int(1) NOT NULL DEFAULT ‘1’,
PRIMARY KEY ( attribute_id ),
KEY attribute_name ( attribute_name (20))
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_woocommerce_downloadable_product_permissions (
permission_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
download_id varchar(36) COLLATE utf8mb4_unicode_ci NOT NULL,
product_id bigint(20) unsigned NOT NULL,
order_id bigint(20) unsigned NOT NULL DEFAULT ‘0’,
order_key varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
user_email varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
user_id bigint(20) unsigned DEFAULT NULL,
downloads_remaining varchar(9) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
access_granted datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’,
access_expires datetime DEFAULT NULL,
download_count bigint(20) unsigned NOT NULL DEFAULT ‘0’,
PRIMARY KEY ( permission_id ),
KEY download_order_key_product ( product_id , order_id , order_key (16), download_id ),
KEY download_order_product ( download_id , order_id , product_id ),
KEY order_id ( order_id ),
KEY user_order_remaining_expires ( user_id , order_id , downloads_remaining , access_expires )
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_woocommerce_log (
log_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
timestamp datetime NOT NULL,
level smallint(4) NOT NULL,
source varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
message longtext COLLATE utf8mb4_unicode_ci NOT NULL,
context longtext COLLATE utf8mb4_unicode_ci,
PRIMARY KEY ( log_id ),
KEY level ( level )
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_woocommerce_order_itemmeta (
meta_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
order_item_id bigint(20) unsigned NOT NULL,
meta_key varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
meta_value longtext COLLATE utf8mb4_unicode_ci,
PRIMARY KEY ( meta_id ),
KEY order_item_id ( order_item_id ),
KEY meta_key ( meta_key (32))
) ENGINE=InnoDB AUTO_INCREMENT=68 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_woocommerce_order_items (
order_item_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
order_item_name text COLLATE utf8mb4_unicode_ci NOT NULL,
order_item_type varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
order_id bigint(20) unsigned NOT NULL,
PRIMARY KEY ( order_item_id ),
KEY order_id ( order_id )
) ENGINE=InnoDB AUTO_INCREMENT=9 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_woocommerce_payment_tokenmeta (
meta_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
payment_token_id bigint(20) unsigned NOT NULL,
meta_key varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
meta_value longtext COLLATE utf8mb4_unicode_ci,
PRIMARY KEY ( meta_id ),
KEY payment_token_id ( payment_token_id ),
KEY meta_key ( meta_key (32))
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_woocommerce_payment_tokens (
token_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
gateway_id varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
token text COLLATE utf8mb4_unicode_ci NOT NULL,
user_id bigint(20) unsigned NOT NULL DEFAULT ‘0’,
type varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
is_default tinyint(1) NOT NULL DEFAULT ‘0’,
PRIMARY KEY ( token_id ),
KEY user_id ( user_id )
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_woocommerce_sessions (
session_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
session_key char(32) COLLATE utf8mb4_unicode_ci NOT NULL,
session_value longtext COLLATE utf8mb4_unicode_ci NOT NULL,
session_expiry bigint(20) unsigned NOT NULL,
PRIMARY KEY ( session_id ),
UNIQUE KEY session_key ( session_key )
) ENGINE=InnoDB AUTO_INCREMENT=30 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_woocommerce_shipping_zones (
zone_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
zone_name varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
zone_order bigint(20) unsigned NOT NULL,
PRIMARY KEY ( zone_id )
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_woocommerce_shipping_zone_locations (
location_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
zone_id bigint(20) unsigned NOT NULL,
location_code varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
location_type varchar(40) COLLATE utf8mb4_unicode_ci NOT NULL,
PRIMARY KEY ( location_id ),
KEY location_id ( location_id ),
KEY location_type_code ( location_type (10), location_code (20))
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_woocommerce_shipping_zone_methods (
zone_id bigint(20) unsigned NOT NULL,
instance_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
method_id varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
method_order bigint(20) unsigned NOT NULL,
is_enabled tinyint(1) NOT NULL DEFAULT ‘1’,
PRIMARY KEY ( instance_id )
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_woocommerce_tax_rates (
tax_rate_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
tax_rate_country varchar(2) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
tax_rate_state varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
tax_rate varchar(8) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
tax_rate_name varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
tax_rate_priority bigint(20) unsigned NOT NULL,
tax_rate_compound int(1) NOT NULL DEFAULT ‘0’,
tax_rate_shipping int(1) NOT NULL DEFAULT ‘1’,
tax_rate_order bigint(20) unsigned NOT NULL,
tax_rate_class varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT ”,
PRIMARY KEY ( tax_rate_id ),
KEY tax_rate_country ( tax_rate_country ),
KEY tax_rate_state ( tax_rate_state (2)),
KEY tax_rate_class ( tax_rate_class (10)),
KEY tax_rate_priority ( tax_rate_priority )
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
CREATE TABLE IF NOT EXISTS wp_woocommerce_tax_rate_locations (
location_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
location_code varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL,
tax_rate_id bigint(20) unsigned NOT NULL,
location_type varchar(40) COLLATE utf8mb4_unicode_ci NOT NULL,
PRIMARY KEY ( location_id ),
KEY tax_rate_id ( tax_rate_id ),
KEY location_type_code ( location_type (10), location_code (20))
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
Источник
During 4.0 upgrade, go the log filled with many entries of those below. The table described is available after update. Is it there anything I should do or be concerned about? Thanks.
WordPress database error Table 'my-domain-wp-Tm6qKxT9.wp_eb51a9edfd_wc_admin_notes' doesn't exist for query SELECT note_id FROM wp_eb51a9edfd_wc_admin_notes WHERE name = 'wc-update-db-reminder' ORDER BY note_id ASC made by require_once('wp-admin/admin.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Install::check_version, WC_Install::install, WC_Install::maybe_update_db_version, WC_Notes_Run_Db_Update::show_reminder, WC_Notes_Run_Db_Update::get_current_notice, WC_Data_Store->__call, AutomatticWooCommerceAdminNotesDataStore->get_notes_with_name
WordPress database error Table 'my-domain-wp-Tm6qKxT9.wp_eb51a9edfd_wc_admin_notes' doesn't exist for query SHOW FULL COLUMNS FROM <code>wp_eb51a9edfd_wc_admin_notes</code> made by require_once('wp-admin/admin.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Install::check_version, WC_Install::install, WC_Install::maybe_update_db_version, WC_Notes_Run_Db_Update::show_reminder, WC_Notes_Run_Db_Update::update_needed_notice, WC_Data->save, WC_Data_Store->create, AutomatticWooCommerceAdminNotesDataStore->create
WordPress database error Table 'my-domain-wp-Tm6qKxT9.wp_eb51a9edfd_wc_admin_note_actions' doesn't exist for query DELETE FROM wp_eb51a9edfd_wc_admin_note_actions WHERE note_id = 0 made by require_once('wp-admin/admin.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Install::check_version, WC_Install::install, WC_Install::maybe_update_db_version, WC_Notes_Run_Db_Update::show_reminder, WC_Notes_Run_Db_Update::update_needed_notice, WC_Data->save, WC_Data_Store->create, AutomatticWooCommerceAdminNotesDataStore->create, AutomatticWooCommerceAdminNotesDataStore->save_actions
WordPress database error Table 'my-domain-wp-Tm6qKxT9.wp_eb51a9edfd_wc_admin_note_actions' doesn't exist for query SHOW FULL COLUMNS FROM <code>wp_eb51a9edfd_wc_admin_note_actions</code> made by require_once('wp-admin/admin.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Install::check_version, WC_Install::install, WC_Install::maybe_update_db_version, WC_Notes_Run_Db_Update::show_reminder, WC_Notes_Run_Db_Update::update_needed_notice, WC_Data->save, WC_Data_Store->create, AutomatticWooCommerceAdminNotesDataStore->create, AutomatticWooCommerceAdminNotesDataStore->save_actions
WordPress database error Table 'my-domain-wp-Tm6qKxT9.wp_eb51a9edfd_wc_admin_note_actions' doesn't exist for query SHOW FULL COLUMNS FROM <code>wp_eb51a9edfd_wc_admin_note_actions</code> made by require_once('wp-admin/admin.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Install::check_version, WC_Install::install, WC_Install::maybe_update_db_version, WC_Notes_Run_Db_Update::show_reminder, WC_Notes_Run_Db_Update::update_needed_notice, WC_Data->save, WC_Data_Store->create, AutomatticWooCommerceAdminNotesDataStore->create, AutomatticWooCommerceAdminNotesDataStore->save_actions
WordPress database error Table 'my-domain-wp-Tm6qKxT9.wp_eb51a9edfd_wc_admin_note_actions' doesn't exist for query SELECT action_id, name, label, query, status, is_primary
FROM wp_eb51a9edfd_wc_admin_note_actions
Two days ago, out of nowhere, a particular table in the WordPress in hongkiat.com went corrupted. The ‘wp_comments‘ table of the WordPress database just crashed without signs, warnings nor error messages. So how did I came to know? Here are the symptoms:
- If you try to back up your database, you’ll be thrown with this error message – wp_comments is marked as crashed and should be repaired when using LOCK TABLES
- Recent comments widget appears blank.
- Top commenter widget appears blank.
- Comment posted will not be written into DB, therefore will not be shown.
- Comments section in WP Admin appears to have zero records.
After searching the Internet high and low in hoping to find similar cases to help me identify and fix the problem, I end up with nothing. So I tried it my way and luckily enough, I managed to solved it. I thought writing the entry out will not only help those who suffered the same, also keep myself reminded just in case I hit on this error again in the future.
The fix / Solution
To fix this, you must have access to the wordpress database, either via PhpMyAdmin or Secure Shell (SSH). Most shared hosting account comes with phpMyAdmin, but either option you should be extremely careful because you dealing with the database. Any wrong move will cause more data lost.
PhpMyAdmin
In PhpMyadmin, select the WordPress database and look for the error table. In my case, the ‘wp_comments‘ table. Check it, and scroll all the way down and look for ‘With selected‘ drop-down box. Select Repair table and things should be alright.
Secure Shell
- Login to your shell
- Enter ‘mysql -u username -p database_name‘ to access databases
- Enter ‘show databases;’ to view all databases
- Enter ‘use database_name;‘ to engage the database
- Enter ‘show tables;‘ to show all tables within the database
- Enter ‘check table wordpress_table_name‘ to verify this is the corrupted table
- Fix it with ‘repair table wordpress_table_name‘
- Enter ‘check table wordpress_table_name‘ again to make sure it’s fixed
Step 3 and 5 are not necessary if you are familiar with your databases and tables. Hope this helps.
Hey Team, Just tried updating from Woocommerce 3.9.2 to 4.5.1 but it crashed my staging site. I have tried disabling plugins, installing Action Scheduler, and so many other things but problem remains. Even tried a fresh install of Woocommerce on a staged copy of the site. Anyone have any solutions of any kind?
Here is the error stack I currently have in my errorlog file. Hope this helps contribute to a resolve.
`
WordPress Environment
WC Version: 3.9.2
WP Version: 5.5.1
WP Memory Limit: 512 MB
WP Cron: ✔
Language: en
Server Environment
Server Info: LiteSpeed
PHP Version: 7.2.32
PHP Post Max Size: 256 MB
PHP Time Limit: 240
PHP Max Input Vars: 5000
cURL Version: 7.62.0
OpenSSL/1.0.2k
SUHOSIN Installed: –
MySQL Version: 5.5.5-10.4.13-MariaDB
Max Upload Size: 256 MB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ✔
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔
Database
WC Database Version: 3.9.2
WC Database Prefix:
Total Database Size: 14.07MB
Database Data Size: 14.04MB
Database Index Size: 0.03MB
woocommerce_sessions: Data: 0.09MB + Index: 0.00MB + Engine InnoDB
woocommerce_api_keys: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
woocommerce_order_items: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
woocommerce_order_itemmeta: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
woocommerce_tax_rates: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
woocommerce_payment_tokens: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
woocommerce_log: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
cerber_acl: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
cerber_blocks: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
cerber_countries: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
cerber_lab: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
cerber_lab_ip: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
cerber_lab_net: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
cerber_log: Data: 0.06MB + Index: 0.03MB + Engine MyISAM
cerber_qmem: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
cerber_traffic: Data: 0.31MB + Index: 0.00MB + Engine MyISAM
aiowps_events: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
aiowps_failed_logins: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
aiowps_global_meta: Data: 2.62MB + Index: 0.00MB + Engine MyISAM
aiowps_login_activity: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
aiowps_login_lockdown: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
aiowps_permanent_block: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
cerber_files: Data: 4.42MB + Index: 0.00MB + Engine MyISAM
cerber_sets: Data: 0.09MB + Index: 0.00MB + Engine MyISAM
cerber_uss: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
commentmeta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
comments: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
links: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
ms_snippets: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
nf3_actions: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
nf3_action_meta: Data: 0.09MB + Index: 0.00MB + Engine InnoDB
nf3_chunks: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
nf3_fields: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
nf3_field_meta: Data: 1.52MB + Index: 0.00MB + Engine InnoDB
nf3_forms: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
nf3_form_meta: Data: 0.13MB + Index: 0.00MB + Engine InnoDB
nf3_objects: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
nf3_object_meta: Data: 0.03MB + Index: 0.00MB + Engine InnoDB
nf3_relationships: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
nf3_upgrades: Data: 0.32MB + Index: 0.00MB + Engine MyISAM
options: Data: 2.28MB + Index: 0.00MB + Engine MyISAM
postmeta: Data: 0.99MB + Index: 0.00MB + Engine MyISAM
posts: Data: 0.14MB + Index: 0.00MB + Engine MyISAM
rank_math_404_logs: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
rank_math_internal_links: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
rank_math_internal_meta: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
rank_math_redirections: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
rank_math_redirections_cache: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
rank_math_sc_analytics: Data: 0.13MB + Index: 0.00MB + Engine InnoDB
snippets: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
termmeta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
terms: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
term_relationships: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
term_taxonomy: Data: 0.01MB + Index: 0.00MB + Engine MyISAM
tm_taskmeta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
tm_tasks: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
usermeta: Data: 0.01MB + Index: 0.00MB + Engine MyISAM
users: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wc_admin_notes: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wc_admin_note_actions: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wc_customer_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wc_download_log: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wc_order_coupon_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wc_order_product_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wc_order_stats: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wc_order_tax_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wc_product_meta_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wc_tax_rate_classes: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wc_webhooks: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
Post Type Counts
attachment: 177
custom_css: 2
custom-css-js: 1
customize_changeset: 1
elementor_library: 4
erm_menu: 1
erm_menu_item: 7
ml-slide: 6
ml-slider: 1
nav_menu_item: 28
nf_sub: 5
oembed_cache: 3
page: 39
post: 14
product: 21
revision: 22
rpt_pricing_table: 1
shop_order: 1
ufaq: 9
Security
Secure connection (HTTPS): ✔
Hide errors from visitors: ✔
Active Plugins (27)
404page — your smart custom 404 error page: by Peter Raschendorfer – 11.2.6
Advanced Product Fields for WooCommerce: by StudioWombat – 1.3.2
All In One WP Security: by Tips and Tricks HQ
Peter Petreski
Ruhul
Ivy – 4.4.4
Better Font Awesome: by Mickey Kay – 1.7.2
Code Snippets: by Code Snippets Pro – 2.14.0
Elementor Pro: by Elementor.com – 3.0.4
Elementor: by Elementor.com – 3.0.7
ELEX WooCommerce Catalog Mode: by ELEXtensions – 1.1.1
Insert Headers and Footers: by WPBeginner – 1.4.6
Ninja Forms: by Saturday Drive – 3.4.27
Premium Addons for Elementor: by Leap13 – 3.21.2
Premium Addons PRO: by Leap13 – 2.1.1
Product Enquiry for WooCommerce: by WisdmLabs – 3.0.1
Really Simple SSL: by Really Simple Plugins – 3.3.5
Rank Math SEO: by Rank Math – 1.0.47.1
SG Optimizer: by SiteGround – 5.6.5
ShiftNav — Responsive Mobile Menu: by Chris Mavricos
SevenSpark – 1.7.0.1
Simple Custom CSS: by John Regan
Danny Van Kooten – 4.0.4
TinyMCE Advanced: by Andrew Ozz – 5.5.0
UpdraftPlus — Backup/Restore: by UpdraftPlus.Com
DavidAnderson – 1.16.29
Widget Options: by Widget Options Team – 3.7.4
Extra Product Options (Product Addons) for WooCommerce: by ThemeHigh – 3.0.0
WooCommerce: by Automattic – 3.9.2 – 4.5.1 is available
WP Cerber Security, Anti-spam & Malware Scan: by Cerber Tech Inc. – 8.6.7
WP-Optimize — Clean, Compress, Cache: by David Anderson
Ruhani Rabin
Team Updraft – 3.1.2
WP Rollback: by Impress.org – 1.7.1
Custom Product Tabs for WooCommerce: by YIKES
Inc. – 1.7.4
Inactive Plugins (0)
Dropin Plugins (1)
advanced-cache.php: advanced-cache.php
Must Use Plugins (1)
installatron_hide_status_test.php: by –
Settings
API Enabled: ✔
Force SSL: ✔
Currency: CAD ($)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: 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
Shop base: ❌ Page not set
Cart: #2884 — /cart/
Checkout: #2886 — /checkout/
My account: #2888 — /my-account/
Terms and conditions: #2899 — /terms-conditions/
Theme
Name: OceanWP
Version: 1.8.7 – 1.8.8 is available
Author URL: https://oceanwp.org/about-me/
Child Theme: ❌ – If you are modifying WooCommerce on a parent theme that you did not build personally we recommend using a child theme. See: How to create a child theme
WooCommerce Support: ✔
Templates
Overrides: oceanwp/woocommerce/cart/mini-cart.php
oceanwp/woocommerce/content-single-product.php
oceanwp/woocommerce/loop/loop-start.php
oceanwp/woocommerce/single-product/title.php
Action Scheduler
Complete: 0
Oldest: –
Newest: –
Pending: 0
Oldest: –
Newest: –
Canceled: 0
Oldest: –
Newest: –
In-progress: 0
Oldest: –
Newest: –
Failed: 0
Oldest: –
Newest: –
`———————————