Hi Chaon,

After investigating for quite some time, it appears that something is not right in your revisions table where a few posts had several thousands of revisions data. This happened because during the cron auto archiving process, when the system tried and fail to archive certain posts, it created new revisions of other posts. This process is repeated each time the cron executes, resulting in a high number of rows(8.9k rows in post table vs 55k rows) in the revisions table.

Due to this, we have helped you empty the revisions table and let the system generate back the revisions data. This issue may happen again so we ask you to keep an eye on the issue and let us know if it happens again. As a reminder, do not manipulate the revisions table in any way as it could cause issues like this one.

Hello,
please keep in mind that i got adviced by your team that there will be no problem if i truncate revisions block in this post https://stackideas.com/forums/clean-my-database

I just checked the database and the revisions table currently is 290mb so i don't think the issue is solved. Correct me if i'm wrong.

Hey Chaon,

Because of the new issue that occur due to the archiving process, truncating the revisions table is not guarantee to work anymore and investigation is now required first before anything is done to the data.

Regarding the revisions table size, this is normal because you have over 9000 posts(includes archived posts). Each post is tied to 1 or 2(if there is a draft) revisions. There is no other way to reduce the size other than increasing disk space allocation for your database, or by reducing the number of posts that you have.

Hello Raymond,
I don't think that deleting content is a realistic solution this is why archive option exists.
Why do i need the drafts of a post that was created for example back in 2018? Isn't there a way to clear those revisions? Is that issue caused because of the auto archive function?
Having a light databse is very crusial for a website. It helps with loading speed, backup speed and size and also disk space.

Hey Chaon,

There is an issue with the archiving process which caused the system add more rows in the revisions table. I have helped you apply the fix at the file below.
JoomlaFolder/administrator/components/com_easyblog/includes/post/post.php

Before the fix, your revisions table today was initially taking up 343mb and increasing with each cronjob.
After the fix, I have helped you remove the duplicate rows, so the end result at this moment is 303mb. Auto archive is also no longer archiving posts since all the old posts(older than 24months) have been archived.

As for drafts, I checked the revisions table and they consists about 1 or 2 rows only so that is not taking up space.

The rest of the data is basically what I mentioned previously which is, each post will have at least one revision data. Revisions table will always have a larger size than the post table because it contains raw data of posts.

Hello, my autopost exploded and posted more than 60 posts on my social media so I figured you were digging something. At the moment i have the autopost off to avoid further inconvenience is it safe now to turn it on again or it will post more old posts?

Also from now on will the setting of keeping no revisions at all be applied?

My apologies Chaon as I did not realize the autoposting triggred. The autoposting should not be triggered on archived posts. We will investigate this and address it if there is a bug here.

You may turn the autopost back on now.

Also from now on will the setting of keeping no revisions at all be applied?

To repeat from a previous thread, the following applies to the revision setting.

Revision disabled: revision for each post = 1 or 2(if there is a draft)
Revision enabled: revision for each post = 1 or more