99% of wp_comments are entries from your plugin, here grouped by comment_type:
“sensei_course_status” –> 7192 entries
“sensei_lesson_status” –> 124277 entries
My question:
Do you know a way of how to clean up sensei-generated wp_comments-entries without loosing important data? Do you have any advice?
As my site got very slow while working on it, I did debug an checked the DB.
I noticed, that my wp_comments was blowing up extreeeeeeemely.
Almost a million entries (within a few hours) and a few hundred MB.
A loooooot of requests per second.
I was working with WpAllImport, did a mistake and reimported my DB backup.
I am not , but I think, after that, I did notice the lag of performance and the trouble started.
As a workaround I installed the ActionScheduler Plugin, which deactivates the crons.
https://github.com/Prospress/action-scheduler-disable-default-runner/
Additionally I did activate Crontrol, set the cron for ActionSchedule at a 5 Minutes Intervall, instead of a 1 Minute Intervall. But, no changes in terms of slowing down the entries.
Status Report:
### WordPress Environment ###
WordPress address (URL): https://monoda.de
Site address (URL): https://monoda.de
WC Version: 3.6.4
Log Directory Writable: ✔
WP Version: 5.2.1
WP Multisite: –
WP Memory Limit: 256 MB
WP Debug Mode: ✔
WP Cron: ✔
Language: de_DE
External object cache: –
### Server Environment ###
Server Info: Apache
PHP Version: 7.3.3-nmm1
PHP Post Max Size: 200 MB
PHP Time Limit: 0
PHP Max Input Vars: 3000
cURL Version: 7.47.0
OpenSSL/1.0.2g
SUHOSIN Installed: –
MySQL Version: 5.7.25-nmm1-log
Max Upload Size: 200 MB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ✔
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔
### Database ###
WC Database Version: 3.6.4
WC Database Prefix: wp_
MaxMind GeoIP Database: ✔
Datenbank-Gesamtgr??e: 11.18MB
Datenbank-Datengr??e: 11.06MB
Datenbank-Indexgr??e: 0.12MB
wp_woocommerce_sessions: Daten: 0.00MB + Index: 0.00MB
wp_woocommerce_api_keys: Daten: 0.00MB + Index: 0.00MB
wp_woocommerce_attribute_taxonomies: Daten: 0.00MB + Index: 0.00MB
wp_woocommerce_downloadable_product_permissions: Daten: 0.00MB + Index: 0.00MB
wp_woocommerce_order_items: Daten: 0.00MB + Index: 0.00MB
wp_woocommerce_order_itemmeta: Daten: 0.00MB + Index: 0.00MB
wp_woocommerce_tax_rates: Daten: 0.00MB + Index: 0.00MB
wp_woocommerce_tax_rate_locations: Daten: 0.00MB + Index: 0.00MB
wp_woocommerce_shipping_zones: Daten: 0.00MB + Index: 0.00MB
wp_woocommerce_shipping_zone_locations: Daten: 0.00MB + Index: 0.00MB
wp_woocommerce_shipping_zone_methods: Daten: 0.00MB + Index: 0.00MB
wp_woocommerce_payment_tokens: Daten: 0.00MB + Index: 0.00MB
wp_woocommerce_payment_tokenmeta: Daten: 0.00MB + Index: 0.00MB
wp_woocommerce_log: Daten: 0.00MB + Index: 0.00MB
hb_config: Daten: 0.02MB + Index: 0.03MB
hb_documents: Daten: 0.02MB + Index: 0.00MB
hb_login: Daten: 0.02MB + Index: 0.00MB
hb_trash: Daten: 0.00MB + Index: 0.00MB
wp_adtribes_my_conversions: Daten: 0.00MB + Index: 0.00MB
wp_affiliate_wp_affiliatemeta: Daten: 0.00MB + Index: 0.00MB
wp_affiliate_wp_affiliates: Daten: 0.00MB + Index: 0.00MB
wp_affiliate_wp_creatives: Daten: 0.00MB + Index: 0.00MB
wp_affiliate_wp_customermeta: Daten: 0.00MB + Index: 0.00MB
wp_affiliate_wp_customers: Daten: 0.00MB + Index: 0.00MB
wp_affiliate_wp_payouts: Daten: 0.00MB + Index: 0.00MB
wp_affiliate_wp_referrals: Daten: 0.00MB + Index: 0.00MB
wp_affiliate_wp_rest_consumers: Daten: 0.00MB + Index: 0.00MB
wp_affiliate_wp_visits: Daten: 0.00MB + Index: 0.00MB
wp_commentmeta: Daten: 0.00MB + Index: 0.00MB
wp_comments: Daten: 0.00MB + Index: 0.00MB
wp_failed_jobs: Daten: 0.00MB + Index: 0.00MB
wp_imagify_files: Daten: 0.00MB + Index: 0.00MB
wp_imagify_folders: Daten: 0.00MB + Index: 0.00MB
wp_links: Daten: 0.00MB + Index: 0.00MB
wp_mailchimp_carts: Daten: 0.00MB + Index: 0.00MB
wp_options: Daten: 0.94MB + Index: 0.00MB
wp_pmxe_exports: Daten: 0.16MB + Index: 0.00MB
wp_pmxe_google_cats: Daten: 0.26MB + Index: 0.00MB
wp_pmxe_posts: Daten: 0.09MB + Index: 0.00MB
wp_pmxe_templates: Daten: 0.04MB + Index: 0.00MB
wp_pmxi_files: Daten: 0.00MB + Index: 0.00MB
wp_pmxi_history: Daten: 0.00MB + Index: 0.00MB
wp_pmxi_images: Daten: 0.07MB + Index: 0.02MB
wp_pmxi_imports: Daten: 0.79MB + Index: 0.00MB
wp_pmxi_posts: Daten: 0.10MB + Index: 0.04MB
wp_pmxi_templates: Daten: 0.06MB + Index: 0.00MB
wp_postmeta: Daten: 4.78MB + Index: 0.00MB
wp_posts: Daten: 0.68MB + Index: 0.00MB
wp_queue: Daten: 0.00MB + Index: 0.00MB
wp_redirection_404: Daten: 2.76MB + Index: 0.00MB
wp_redirection_groups: Daten: 0.00MB + Index: 0.00MB
wp_redirection_items: Daten: 0.02MB + Index: 0.00MB
wp_redirection_logs: Daten: 0.01MB + Index: 0.00MB
wp_termmeta: Daten: 0.02MB + Index: 0.00MB
wp_terms: Daten: 0.01MB + Index: 0.00MB
wp_term_relationships: Daten: 0.01MB + Index: 0.00MB
wp_term_taxonomy: Daten: 0.02MB + Index: 0.00MB
wp_usermeta: Daten: 0.02MB + Index: 0.00MB
wp_users: Daten: 0.00MB + Index: 0.00MB
wp_wc_admin_notes: Daten: 0.00MB + Index: 0.00MB
wp_wc_admin_note_actions: Daten: 0.00MB + Index: 0.00MB
wp_wc_customer_lookup: Daten: 0.00MB + Index: 0.00MB
wp_wc_download_log: Daten: 0.00MB + Index: 0.00MB
wp_wc_order_coupon_lookup: Daten: 0.00MB + Index: 0.00MB
wp_wc_order_product_lookup: Daten: 0.00MB + Index: 0.00MB
wp_wc_order_stats: Daten: 0.00MB + Index: 0.00MB
wp_wc_order_tax_lookup: Daten: 0.00MB + Index: 0.00MB
wp_wc_product_meta_lookup: Daten: 0.05MB + Index: 0.00MB
wp_wc_webhooks: Daten: 0.00MB + Index: 0.00MB
wp_wfblockediplog: Daten: 0.00MB + Index: 0.00MB
wp_wfblocks7: Daten: 0.00MB + Index: 0.00MB
wp_wfconfig: Daten: 0.04MB + Index: 0.01MB
wp_wfcrawlers: Daten: 0.00MB + Index: 0.00MB
wp_wffilechanges: Daten: 0.00MB + Index: 0.00MB
wp_wffilemods: Daten: 0.00MB + Index: 0.00MB
wp_wfhits: Daten: 0.00MB + Index: 0.00MB
wp_wfhoover: Daten: 0.00MB + Index: 0.00MB
wp_wfissues: Daten: 0.00MB + Index: 0.00MB
wp_wfknownfilelist: Daten: 0.00MB + Index: 0.00MB
wp_wflivetraffichuman: Daten: 0.00MB + Index: 0.00MB
wp_wflocs: Daten: 0.00MB + Index: 0.00MB
wp_wflogins: Daten: 0.00MB + Index: 0.00MB
wp_wfls_2fa_secrets: Daten: 0.02MB + Index: 0.02MB
wp_wfls_settings: Daten: 0.02MB + Index: 0.00MB
wp_wfnotifications: Daten: 0.00MB + Index: 0.00MB
wp_wfpendingissues: Daten: 0.00MB + Index: 0.00MB
wp_wfreversecache: Daten: 0.00MB + Index: 0.00MB
wp_wfsnipcache: Daten: 0.00MB + Index: 0.00MB
wp_wfstatus: Daten: 0.00MB + Index: 0.00MB
wp_wftrafficrates: Daten: 0.00MB + Index: 0.00MB
wp_wpmelon_advbedit_temp: Daten: 0.00MB + Index: 0.00MB
wp_yith_wcwl: Daten: 0.00MB + Index: 0.00MB
wp_yith_wcwl_lists: Daten: 0.00MB + Index: 0.00MB
wp_yoast_seo_links: Daten: 0.02MB + Index: 0.00MB
wp_yoast_seo_meta: Daten: 0.01MB + Index: 0.00MB
### Post Type Counts ###
attachment: 1315
blocks: 7
custom_css: 1
customize_changeset: 2
invoice: 2
nav_menu_item: 28
page: 34
post: 1
product: 191
product_variation: 191
scheduled-action: 121
shop_coupon: 2
shop_order: 1
sidebar: 1
wpcf7_contact_form: 3
ywtm_tab: 2
### Security ###
Secure connection (HTTPS): ✔
Hide errors from visitors: ✔
### Active Plugins (26) ###
Redux Framework: von Team Redux – 3.6.15
Action Scheduler - Disable WP Cron Queue Runner: von Prospress Inc. – 1.0.0
AffiliateWP: von AffiliateWP
LLC – 2.2.17
AffiliateWP - Affiliate Area Tabs: von AffiliateWP – 1.2.7
BackUpWordPress: von XIBO Ltd – 3.8
Webcraftic Clearfy – WordPress Optimierungs-Plugin: von Webcraftic – 1.5.3
Contact Form 7 MailChimp Extension: von Renzo Johnson – 0.4.51
Contact Form 7: von Takayuki Miyoshi – 5.1.3
Custom Menu Wizard: von Roger Barrett – 3.3.1
Enhanced E-commerce for Woocommerce store: von Tatvic – 2.1.9
Imagify: von WP Media – 1.9.2
Mailchimp for WooCommerce: von Mailchimp – 2.1.16 – Nicht getestest mit der aktiven WooCommerce-Version
Redirection: von John Godley – 4.2.3
Vendidero Helper: von Vendidero – 1.2.1
WooCommerce Advanced Bulk Edit: von George Iron – 4.4.1 – Nicht getestest mit der aktiven WooCommerce-Version
WooCommerce Stripe-Gateway: von WooCommerce – 4.1.16
WooCommerce Germanized Pro: von Vendidero – 1.9.7 – Nicht getestest mit der aktiven WooCommerce-Version
WooCommerce: von Automattic – 3.6.4
WooSidebars: von WooCommerce – 1.4.5
Yoast SEO: von Team Yoast – 11.3 – Nicht getestest mit der aktiven WooCommerce-Version
WP All Import Pro: von Soflyy – 4.5.6
WP Crontrol: von John Blackbourn & Mitwirkende – 1.7.1
WP All Import - WooCommerce Add-On Pro: von Soflyy – 3.0.7
YITH WooCommerce Tab Manager: von YITH – 1.2.13
YITH WooCommerce Wunschliste: von YITH – 2.2.10
WP All Import - Yoast WordPress SEO Add-On: von Soflyy – 1.1.8
### Inactive Plugins (11) ###
Advanced Database Cleaner: von Younes JFR. – 2.0.0
Facebook for WooCommerce: von Facebook – 1.9.12 – Nicht getestest mit der aktiven WooCommerce-Version
Germanized for WooCommerce: von Vendidero – 2.3.0
Media Cleaner: von Jordy Meow – 5.2.4
Nextend Social Login: von Nextendweb – 3.0.20
Product CSV Import Export (BASIC): von WebToffee – 1.6.1
Product Feed PRO for WooCommerce: von AdTribes.io – 5.6.8
Regenerate Thumbnails: von Alex Mills (Viper007Bond) – 3.1.1
Wordfence Security: von Wordfence – 7.3.2
WP All Export Pro: von Soflyy – 1.5.6
WP Staging: von WP-Staging – 2.5.9
### Dropin Plugins (1) ###
maintenance.php: maintenance.php
### Must Use Plugins (1) ###
WP Staging Optimizer: von René Hermenau – 1.1
### Settings ###
API Enabled: ✔
Force SSL: –
Currency: EUR (€)
Currency Position: right_space
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-Basis: #6 - /shop/
Warenkorb: #7 - /cart/
Kasse: #8 - /checkout/
Mein Konto: #9 - /my-account/
Allgemeine Gesch?ftsbedingungen: #12 - /hilfe/agb/
### Theme ###
Name: Flatsome Child
Version: 3.0
Author URL:
Child Theme: ✔
Parent Theme Name: Flatsome
Parent Theme Version: 3.8.3
Parent Theme Author URL: https://www.uxthemes.com/
WooCommerce Support: ✔
### Templates ###
Overrides: flatsome/woocommerce/archive-product.php
flatsome/woocommerce/cart/cart-empty.php
flatsome/woocommerce/cart/cart-shipping.php
flatsome/woocommerce/cart/cart.php
flatsome/woocommerce/checkout/form-checkout.php
flatsome/woocommerce/checkout/form-coupon.php
flatsome/woocommerce/checkout/thankyou.php
flatsome/woocommerce/content-product.php
flatsome/woocommerce/content-product_cat.php
flatsome/woocommerce/content-single-product.php
flatsome/woocommerce/content-widget-product.php
flatsome/woocommerce/global/breadcrumb.php
flatsome/woocommerce/global/quantity-input.php
flatsome/woocommerce/global/wrapper-end.php
flatsome/woocommerce/global/wrapper-start.php
flatsome/woocommerce/loop/loop-end.php
flatsome/woocommerce/loop/loop-start.php
flatsome/woocommerce/loop/pagination.php
flatsome/woocommerce/loop/result-count.php
flatsome/woocommerce/loop/sale-flash.php
flatsome/woocommerce/myaccount/form-login.php
flatsome/woocommerce/myaccount/navigation.php
flatsome/woocommerce/notices/error.php
flatsome/woocommerce/notices/notice.php
flatsome/woocommerce/notices/success.php
flatsome/woocommerce/product-searchform.php
flatsome/woocommerce/single-product/photoswipe.php
flatsome/woocommerce/single-product/price.php
flatsome/woocommerce/single-product/product-image.php
flatsome/woocommerce/single-product/product-thumbnails.php
flatsome/woocommerce/single-product/rating.php
flatsome/woocommerce/single-product/related.php
flatsome/woocommerce/single-product/review.php
flatsome/woocommerce/single-product/sale-flash.php
flatsome/woocommerce/single-product/share.php
flatsome/woocommerce/single-product/short-description.php
flatsome/woocommerce/single-product/tabs/tabs.php
flatsome-child/woocommerce/single-product/title.php
flatsome/woocommerce/single-product/up-sells.php
flatsome/woocommerce/single-product-reviews.php
flatsome/woocommerce/single-product.php
LOG:
[01-Jun-2019 20:50:24 UTC] PHP Fatal error: Uncaught InvalidArgumentException: Unidentified action 0 in xxx/wp-content/plugins/woocommerce/includes/libraries/action-scheduler/classes/ActionScheduler_wpPostStore.php:488
Stack trace:
#0 xxx/wp-content/plugins/woocommerce/includes/libraries/action-scheduler/classes/ActionScheduler_wpPostStore.php(475): ActionScheduler_wpPostStore->get_date_gmt('0')
#1 xxx/wp-content/plugins/woocommerce/includes/libraries/action-scheduler/classes/ActionScheduler_wcSystemStatus.php(78): ActionScheduler_wpPostStore->get_date('0')
#2 xxx/wp-content/plugins/woocommerce/includes/libraries/action-scheduler/classes/ActionScheduler_wcSystemStatus.php(52): ActionScheduler_wcSystemStatus->get_action_status_date('pending', 'oldest')
#3 xxx/wp-content/plugins/woocommerce/includes/libraries/action-scheduler/classes/ActionScheduler_wcSystemStatus.php(27): ActionScheduler_wcSystemStatus->get_oldest_and_ne in xxx/wp-content/plugins/woocommerce/includes/libraries/action-scheduler/classes/ActionScheduler_wpPostStore.php on line 488
]]>We aren’t using comments on our website so what’s the implication to my WooCommerce store if I drop the wp_comments table?
]]>WordPress is not pulling up any data from my comments table. I tried to repair and optimize my database by addint this to my wp-config: define( ‘WP_ALLOW_REPAIR’, true ); then I ran Repair and Optimize, I received the following error message:
wp_posts: Key in wrong position at page 1521664
How do I fix that error? And will fixing that error also help wordpress to be able to “find” my comments data? People can leave comments, I see it in the table using phpmyadmin, but I cannot see the comments in wordpress.
Any help would be greatly appreciated. Thanks!
]]>#144 – Table ‘wp_options’ is marked as crashed and last (automatic?) repair failed
I can Import one of the older DB backups I have and the site will come back up – for a few days then will eventually crash again BC of this corrupt WP Options table.
OR when I import the DB Backup, as soon as I try to Optimize or Repair the table in PhpMyAdmin it crashes immediately.
I already added the Repair Table line in Php.config as suggested by the WP error message, and WP can’t repair the wp_options table either.
I installed the WP DB Manager Plugin and as soon as I hit Optimize the table crashed – I never made it to the Repair function.
Any ideas on why a database keeps crashing – and why if I Import a Backup the site will work for a while then crash? Should I delete(Drop) the crashed DB or WP Options Table then Import the Backup so it will be a fresh install rather than over writing the crashed DB table??
]]>Error
SQL query: Documentation
--
-- Triggers <code>wp_comments</code>
--
DELIMITER $$ CREATE TRIGGER <code>livenotification</code> AFTER INSERT ON <code>wp_comments</code>
FOR EACH
ROW IF( INSTR( new.comment_agent, 'Disqus' ) )
THEN INSERT INTO wp_livenotifications( userid, userid_subj, content_type, content_id, parent_id, content_text, is_read, time, username )
VALUES (
(
SELECT post_author
FROM wp_posts
WHERE ID = new.comment_post_ID
), new.user_id, 'comment', new.comment_ID, new.comment_post_ID, (
SELECT post_title
FROM wp_posts
WHERE ID = new.comment_post_ID
), '0', UNIX_TIMESTAMP( ) , new.comment_author
);
END IF $$
MySQL said: Documentation
#1142 - TRIGGER command denied to user 'xxxxxxxx'@'localhost' for table 'wp_comments'
Would be very happy about any help!
]]>This error message is coming up in my error logs after we had a MySQL crash. The hosting company is having some issues resolving this.
I have the Disqus plugin installed, which I have temporarily disabled. I have 2 questions:-
1) Does the wp_comments table belong to WordPress or the Disqus plugin
2) If we drop the table and create a brand new empty one, is this going to cause any issues bearing in mind I have no comments and don’t care if comments are saved or not.
]]>wp_comments: 3 clients are using or haven’t closed the table properly
wp_options: Table is marked as crashed
wp_commentmeta: 3 clients are using or haven’t closed the table properly
As I received some new comments during the day yesterday, I’m guessing that these files were active when the server was unstable and have been corrupted as a result.
I am a very basic level user and have no idea what the implications are. I was suprised to be able to go to my most recent blog post and add a comment without any difficulty, for instance.
Is there something I can do to fix these files? Do they need further fixing?
]]><div id="comment-area">
<h4><?php _e("Post Comment"); ?></h4>
<form action="<?php echo get_option('siteurl'); ?>/wp-comments-post.php" name="comment" id="comment-form" method="post">
<input type="text" name="author" id="author" placeholder="Your name (Required)" autocomplete="on" tabindex="1" class="txtinput" value="<?php echo $comment_author; ?>">
<input type="email" name="email" id="email" placeholder="E-Mail (Required)" autocomplete="on" tabindex="2" class="txtinput" value="<?php echo $comment_author_email; ?>">
<input type="url" name="url" id="url" placeholder="Website URL (Optional)" autocomplete="on" tabindex="3" class="txtinput" value="<?php echo $comment_author_url; ?>">
<input type="hidden" name="comment_post_ID" id="comment_post_ID" value="<?php echo $post_ID; ?>">
<input type="hidden" name="comment_parent" id="comment_parent" value="0">
<textarea name="comment" id="message-box" placeholder="Enter your comments here..." tabindex="4" class="txtblock"></textarea>
<a href="#comment-area" onclick="clearCommentFields();"><div id="reset-button"><?php _e('Reset!'); ?></div></a>
<input type="submit" name="submit" id="submit-button" tabindex="5" value="<?php _e("Submit!", "byrne-systems"); ?>" />
</form><!-- #comment-form -->
</div><!-- #comment-area -->
Now my issue is with ‘comment_parent’. For whatever reason I am unable to post the ‘comment_parent’ field within wp_comments via this method. Whenever I post a comment within wp_comments, the comment_parent field automatically defaults to zero, regardless of how it is set. Currently I have a js function that changes the ‘0’ value that you see above to a ‘1’, and after I submit a comment ‘0’ is always placed within comment_parent. In addition, I am unable to post anything to ‘comment_type’ either, which I would like to do if I want to pull off what I am attempting to do.
Ultimately, I am attempting to see if anybody out there is able to help me to understand ‘how’ to post to both ‘comment_parent’, and ‘comment_type’ within the ‘wp_comments’ table within the WordPress DB via a <form>. Thanks in advance.
]]>