I get the SQL error:
#1118 - The size of BLOB/TEXT data inserted in one transaction is greater than 10% of redo log size. Increase the redo log size using innodb_log_file_size.
and
INSERT INTO 'wp_postmeta' ( 'meta_id', 'post_id', 'meta_key', 'meta_value') VALUES
(951, 102, 'tdc_history', 'W3sidGltZXN0YW1wIjoxNTk2NT....
Do you regognise this?
-
This topic was modified 5 years by
andxtagdiv.
-
This topic was modified 5 years by
andxtagdiv.
-
This topic was modified 5 years by
andxtagdiv.
Ok, I see from the past threads here that this is a know problem with databases and tdc_history.
I do not use ctrl-z. So, can I switch off history? So that my database does not get spammed!
I have just gone though and deleted that manually. My DB was 205MB and now is 21MB.
That is a 180MB database overhead for history!!??
That is madness and I would call that a bug.
-
This reply was modified 5 years by
andxtagdiv.
I have continuously updated and am now on Version: 10.3.9.1.
What version did you say this was corrected on?
If my information is correct, version 10 started on November 6th, 2019.
So, I can confirm that I had the issue for one and a half years, after you claim that the bug had been addressed.
I am not sure what you mean.
I had just cleaned it manually so it is small now. And I have not done any edits since, so there would not be any history.
Hi,
We are sorry for the problem created. A similar was a discussion on this topic -> https://forum.tagdiv.com/topic/huge-tagdiv-composer-entries-in-database/ I hope it helps you.
Also, you can try a plugin to clear your database -> https://www.wpbeginner.com/plugins/how-to-clean-up-your-wordpress-database-for-improved-performance/
Thank you for your understanding and sorry for the inconvences.
Have you even read what I wrote? If yes, why are you giving a link to clean the database? I did write that I had cleaned my database already.
What’s worse, the first link to the other discussion, confirms that standard database cleaning strategies do not work with the bug that your theme has.
This is a terrible attitude. First you, quite obviously discover the but and try to correct it with version 10. But you tell no one about it. Now you continue to cover this up.
What you should have done one and a half years ago, is to write to all customers with a pre version 10 and tell them about your problems. You should have a offered to that your developers clean the databases manually.
Today, whenever a customer comes to you with a huge database, you should tell them straight that you had a bug – a bug that persists if you come from a pre version 10 – and then you should offer that you do the manual cleaning.
This leaves you in a very bad light. And with WordPress 5.8 there should be little reason for us to be at the behest of your terrible business practices.
I have spent, literally the last year and a half, hunting errors that where caused by you. Only now, I was able to find the culprit. You have caused me hours and hours of misery, that you will never pay me back.
Only to save your own neck, so that you do not have to admit to a bug.
Hi andxtagdiv,
I think that here is a big misunderstanding.
The problem with tdc_history (tagDiv Composer history) has been passed to our developers and this has been improved/fixed in Newspaper v10.3.8 https://i.imgur.com/1cgGYSq.png -> https://themeforest.net/item/newspaper/5489609 therefore if you had a version under that you had the problem, but now that you have Newspaper v10.3.9.1 this problem should no longer appear (just for curiosity what theme version you had before theme update?). But to be sure for this you can keep an eye on it.
What Anamaria mean was that we know about this problem that theme has and she provide a link where the problem was discussed. On that time the theme version I think that was 10.3.1 or 10.3.2.
Also the suggestion to clear the database I think that was made because you said that you “cleaned it manually” and Anamaria suggested that you can use a plugin for this, is no need to do it manually (is good if you have those skills).
I hope I didn’t upset you and that I managed to express myself correctly about the above situation.
Sorry for all the inconvenience that were caused!