I use VersionX to back up templates, chunks, TVs, and resources on a relatively small site. However, the MySQL table used by VersionX to store resources (I assume this function based on the table's name -- modx_versionx_resource) is massive. About 370MB, to be exact, and this alone exceeds the dB size limit on the production server.
Two questions:
1. In the database, phpMyAdmin provides an empty command, which runs TRUNCATE. I'm a MySQL noob and just want to know that if I run this, it'll empty the table without "breaking" anything.
2. Anyone know of a way to limit how much data VersionX stores? I checked system settings but don't see anything there, or within its manager page.
EDIT
I have removed VersionX from the ModX install but its tables remain in the database. Adding this in the event that someone can tell my why this is. I would assume that removing a component from ModX would also remove the tables it uses from the database. Is this incorrect? Can anyone describe a good method for removing the associated tables manually?
EDIT #2
I dropped the VersionX tables from the database, and this reduced dB size from 420MB to ~4MB. VersionX is evidently indiscriminate with how much data it stores. In my case, a 9k+ word resource that was edited multiple times probably created the huge table size.
A big value-add for VersionX would be the ability to constrain # of versions it saves.
[ed. note: wpicotte last edited this post 10 years, 9 months ago.]
-
☆ A M B ☆
- 3,141 Posts
That's one of the features I've been looking to add pretty much since the first release - just never quite made it to the top of the priority list:
https://github.com/Mark-H/VersionX2/issues/4
There's a snippet you can use to clean it out as well here:
https://forums.modx.com/thread/86917/snippet-for-deleting-versionx-content-no-longer-required
☆ A M B ☆