Hi!
After upgrade to 10 theme I met a problem – a rapid increase in database volume.
I have checked the database and found the following:
1) The increase is associated with only one table – wp_postmeta which increase about 3-fold during one month with approximately 10 posts added to the site during this period.
2) The wp_postmeta has huge volume associated with tdc (tagdiv composer, I guess) key:
https://clip2net.com/s/46IIv4N
3) There are 14 entries in the table with tdc_history key, which occupy over 50% of table volume.
4) This is one of them, which is associated with post ID 9286:
https://clip2net.com/s/46IMOOs
However, I do not find the post with this ID at my site, as well as other 13 post IDs.
My questions are:
1) What is the reason of appearance of so enormously huge entries associated with tagdiv composer?
2) How to avoid them in future?
3) Is it safe to delete these entries?
Hi,
1. The wp_postmeta stores the datas for pages, posts, custom post type (cloud templates).
2. Unfortunately we do not have a guide for this, but you can try the suggestions from these articles:
How to clean wp_commentmeta and wp_postmeta tables?
Better Optimize WordPress Database – All in One Guide
wp_postmeta help
3. We do not recommend to delete them, but if you want to do it, please make first a full backup you your website and database.
Hope this will help you!
Thank you!
Dear Calin!
It’s really a pity you do not want to understand a problem. You give me articles with general recomendations about clining standard wp entries (like transients, revisions etc.). Belive me, I know all these recommendations. And this is not the case here.
I show you with scrennshots, that there is definitely a SPECIFIC problem related to tagdiv composer.
Once again – there are enormously huge entries with key TDC_HISTORY in database. In any case 14 entries related to 14 posts that are absent at the site should not occupy over 40 mb of space in database. This is clearly a bug. Do you agree with this?
I suggest that we can together try to understand the reason for such huge entries. I can just delete them, but I would like developers to answer we, why that happened and how is it safe to delete them and what is the best way to do this. I can send you the database to analyse it.
This is what I payed for (36 USD for support renewal). I am not nearly satisfied with recommendation “I do not recommend to delete, but try to delety and lets see what will happens”. This is not the support. Please, take it seriously and let’s find a solution.
Hi,
I contacted one of our developers to for some more information about the TDC_HISTORY from database and for what it is use for.
In TDC_HISTORY are store all the steps made using tagDiv Composer on all pages and cloud template that you used tagDiv Composer (and you have in cloud template ->https://i.imgur.com/0NbEObD.png), in this way you can use the undo and redo options -> https://i.imgur.com/p9074lE.jpg and you can restore backups from them panel -> https://i.imgur.com/QqX33GE.png also you have the ability to edit the pages/templates from any terminal and different desktops by having the same history.
In TDC_HISTORY are stack all the movements made with tagDiv Composer to can revert to a prev version (for example if you accidentally delete a different element from the one you want, you can use the undo).
Therefore, if you want to delete the data from TDC_HISTORY, you can do it, but you need to know that we do not recommend this, because it can affect the theme options.
Also I’ve got a spam from developer about the coming updates, in one of them, will be add an on/of option for those who do not want to use all these savings options.
Thank you for your understanding!
Hi, Calin!
Thank you very much for a valuable information.
Do I make a right conclusion that if I delete e.g. the following tdc_history entry
https://clip2net.com/s/46IMOOs
this should eliminate only the history of changes of post with id 9286?
May you also ask developers what is the best (sefest) way to clean these entries – to delete whole entry or to set its meta_value to “0” or to any other recommended value. I would really appreciate this information.
That would be great to have a button to clean the history of changes at any moment. I appreciate having the history of changes at the period of active redesign, but since it is finished I would defenitely prefer to clean history from database. All the more, it can not be cleaned by common plugins.
Hi,
Yes, that right, deleting this should -> https://clip2net.com/s/46IMOOs remove all the historic for the post with id 9286.
Unfortunately for the moment if you’ll replace all the rows rows database that have an tdc_history with meta_value to “0” will appear some problems, the developers said that the data from meta_value filed need to be analyzed and removed only the part that belongs to the historic in this way we website will not be damage, unfortunately for this they need some time to investigate the code.
The provide me a code that should remove all the content from meta_value field, but before you try it. please make a full backup to your website and database because the code is texted only localhost and for new installed demos, also we do not recommend this.
The code is -> https://i.imgur.com/z77JeBP.png you can get it from here https://pastebin.com/FMNxdEDD
Thank you for your understanding!
Thank you, Calin! I try this code. Hopefully it helps. And hopefully in next update we get the button “Clear the history of changes” in theme admin panel.
Hi, Calin!
I want to share the results, which I’ve got.
1) The request you recommended deleted over 800 entries from wp_postmeta table. As a result, header menu and bottom menu were ruined, all images disappeared at least from the homepage. I didn’t invesigate futher issue. Verdict: this method doesn’t work good.
2) I have seleted tdc_history entries with the following sql request:
SELECT post_id, meta_key
FROM wp_postmeta
WHERE meta_key LIKE ‘tdc_history’
ORDER BY post_id DESC
LIMIT 100;
After that I deleted all found entries and optimized the table.
As a result wp_postmeta table volume reduced from 43 to 7 mb. And as far as I can see, everything works fine.
Hopefully, my experience may be helpfull to anybody else who struggles with database volume growth.
Hi,
Thank you for letting us know the experience you have with database, our developers will check this topic too.
Thank you for the message!
Have a nice day!
Hi,
I would like to append my experience. Yes, your TDC really generates HUGE wp_postmeta entries. I imported and customized some cloud templates – that means a lot of steps in TD Composer, and my wp_postmeta was above 200 MB! Main problem was that table was so big that it broke down whole WP, because in some operation with DB it exhausted 256 MB limit.
So this is really bad bug and I suggest you to repair it as soon as possible too. At least add Clear history button/option as well as add this feature to “Newspaper system status” – show size of TDC backup records with warning above some limit.
Finally I tried method Sandman mentioned and deleted ‘tdc_history‘ rows manually in phpMyAdmin. So far it looks problem is solved and WP works OK.
Hi pavel_t,
I added your suggestions on our list and hope our developers will add those options in our theme.
Thank you for your understanding!
Trying to do the same, but for request (below) having error: #1054 – Неизвестный столбец ‘‘tdc_history’’ в ‘where clause’. What we do wrong?
SELECT post_id, meta_key
FROM wp_postmeta
WHERE meta_key LIKE ‘tdc_history’
ORDER BY post_id DESC
LIMIT 100;
Hi,
Yes, if you place some code on forum and you do not mark it as code https://i.imgur.com/MfNbV9Z.png then this will get some apostrophes that will not work when are use as code.
Thank you!
Thank you pavel_t. Is found entries have to look like this? Do i need gust to delete it. Did you do the same?
https://c.radikal.ru/c27/2012/16/98ee45c326e8t.jpg
Yes, this is correct. You should see also in meta_value very very huge field with code like “W3sidwdas….” For sure of course before deleting copy wp_postmeta table as backup.
