Currently that was no other quickly way to delete those revision post from the composer.

I would suggest you increase the space from your database server.

Hey Arlex

2 questions

What is the exact MySQL data base query that I need to double check the size of the Blog Revisions?

Even after deleting Blog Revisions one by one in the EB interface is there some kind of trash or similar that needs to be emptied?

thanks

Paul

What is the exact MySQL data base query that I need to double check the size of the Blog Revisions?

I only found out this sql query to show out all of your existing database total size :

SELECT table_schema "database", 

	sum(data_length + index_length)/1024/1024 "size in MB" 

    	FROM information_schema.TABLES 

        GROUP BY table_schema

Even after deleting Blog Revisions one by one in the EB interface is there some kind of trash or similar that needs to be emptied?

if you delete that revision from the composer, you do not need to delete other thing, because once you delete one of the revision from composer, it will delete one of the revision record from this table #__easyblog_revisions

Hope this will help.

Hi Arlex

From Site Ground:

I have actually found out that there was a cache in the Cpanel and our tool, which was calculating the Database size.

I have run the following query and found out that you have successfully decreased the Database size:

Code:

SELECT table_schema "DB Name",

Round(Sum(data_length + index_length) / 1024 / 1024, 1) "DB Size in MB"

FROM information_schema.tables

GROUP BY table_schema;

the result was:

Code:

+--------------------+---------------+

| DB Name | DB Size in MB |

+--------------------+---------------+

| finalbug_nina | 499.4 |

| finalbug_sandbox | 265.1 |

| information_schema | 0.0 |

+--------------------+---------------+

I love Stackideas, the products the support pretty much every thing.

Buttttttt we all have a number one hate and this is it for me.

There should be some way to batch delete revisions.

Some how I managed to clear out 350MB of junk.

It was painful and scary and took about 5 hours but this time nothing got broken!!!

And I continue paying 155,40€ for hosting instead of upgrading and paying 287,40€ in a year!

I honestly do not understand why it is not possible to do some of the following in Easy Blog:

a) Set a Revision interval eg a copy made every 1/5/10 minutes
b) Set a limit to the number of revisions that are kept eg keep only the last 50?
c) Have some kind of way of selecting more than one revision at a time for deletion!

I sincerely hope this does not come across as being too cranky.
I mean it in a positive and constructive way...
If I misses any thing apologies in advance.

all the best

Paul

Hi Arlex

From Site Ground:

I have actually found out that there was a cache in the Cpanel and our tool, which was calculating the Database size.

I have run the following query and found out that you have successfully decreased the Database size:

Code:

SELECT table_schema "DB Name",

Round(Sum(data_length + index_length) / 1024 / 1024, 1) "DB Size in MB"

FROM information_schema.tables

GROUP BY table_schema;

the result was:

Code:

+--------------------+---------------+

| DB Name | DB Size in MB |

+--------------------+---------------+

| finalbug_nina | 499.4 |

| finalbug_sandbox | 265.1 |

| information_schema | 0.0 |

+--------------------+---------------+

I love Stackideas, the products the support pretty much every thing.

Buttttttt we all have a number one hate and this is it for me.

There should be some way to batch delete revisions.

Some how I managed to clear out 350MB of junk.

I only touched the Easy Blog Revisions table and maybe there was some junk left over from last time.

It was painful and scary and took about 5 hours but this time nothing got broken!!!

And I continue paying 155,40€ for hosting instead of upgrading and paying 287,40€ in a year!

I honestly do not understand why it is not possible to do some of the following in Easy Blog:

a) Set a Revision interval eg a copy made every 1/5/10 minutes
b) Set a limit to the number of revisions that are kept eg keep only the last 50?
c) Have some kind of way of selecting more than one revision at a time for deletion!

I sincerely hope this does not come across as being too cranky.
I mean it in a positive and constructive way...
If I misses any thing apologies in advance.

all the best

Paul

Sorry about the double posing this has happened to me before.
I go back to correct something and I think the quotes get mixed up and then this happens

Hello Paul,

You are not understanding the concept of revisions and this is why you have a hard time understanding the purpose of revisions. A revision, allows one to travel back time to change their copy of the blog post (If they have done some mistakes / incorrect changes). If revisions are purged automatically, don't you think this defeats the purpose of a revision altogether?

It's like creating a backup but the backups are automatically deleted after x days.

But should not not be able like Joomla revisions to purge and dont allow more than say 4-5 revision in a setting and the rest are automatically deleted? Should be an important and useful setting I belive too.

Cheers!

Hm, does Joomla allows you to truncate revisions and only store the recent "x" amount of revisions?

Hi Mark

I believe that I understand the concept of revisions.
Please see the screen shot below for how autosave worked in an older version of Final Cut Pro.
If I was working on a short form clip with many complex changes in a short time I cranked up autosave.
If I was working on some thing arty-farty with a couple of edits an hour I cranked down autosave.
This could even be dealt with in EB a simple slider rather than 100s of settings .
Slide for more safety and more revisions or less safety and less revisions.
Alternatively have some kind of cache clearing for revisions!

To compound matters I believe that even after clearing out the revisions there was some kind of cPanel / mySQL database cache issue.
I have no idea if this is just my database or if it happens with other people as well.
As of now I will continue to write as much as I can in a word processor and then copy and paste into the EB composer in the last minute.
As of now I want to stay on my current hosting plan and not pay 100€ extra a year for Revisions that I know I will never use.
I need to do the following every 6 months.
And I am not even a heavy blogger!

Best Case Scenario:
- 1000 times 3 clicks (2-3 hours)

Worst Case Scenario:
- mySQL data base truncation (1 min)
- cPanel Cache clear!
- Maybe an article rescue/clear up action (10 hours)

all the best

Paul

In EasyBlog 5.1, we'll be allowing the admin to configure the number of most recent revisions to save and also the ability to clear up previous revisions if the author / admin doesn't want it

Hello Mark

Thank you.
This will be amazing.

best

Paul

You are most welcome Paul