Re: [pLog-General] pLog 0.2 is out

[Oscar R. <os...@re...>]

Hi!

> I stand corrected.... there's more than I thought...

Well, first of all for such a nice and useful bug report... Somehow I 
completely forgot about this issues during development!

> So far:
>
> Deleting a Post does not Delete Comments.

First thing I must mention here is that users can never physically remove a 
post from the db. When a user removes a post, its status is set to 'DELETED' 
(as opposed to 'DRAFT' or 'PUBLISHED') so it remains in the database. 
Actually, there is no way for a user to remove a post forever in the 
database. 

The only way posts can be completely removed from the db is by removing the 
blog to which they belong. Or should we perhaps add a "purge" option to the 
admin interface, so that posts that have been set to a 'deleted' status are 
removed? I think that would do.

> Deleting a Blog does not remove the user access entries
> (plog_user_permissions)

fixed

> Deleting a user does remove the user from the user access list

what do you mean with this one?

> Deleting a Blog does not delete it's posts

Should be fixed too. Deleting a post has the cascade effect of deleting all 
its comments and trackbacks at the same time.

> Deleting a Blog does not delete it's Categories

Deleting a blog now does the following:

- Deletes its posts (which will trigger the deletion the trackbacks and 
comments)
- Deletes its article categories
- Deletes its links
- Deletes its links categories
- Deletes its permissions

> I'm betting that Deleting a Blog doesn't remove it's Links or Link
> Categories either, but I haven't made any to test with. ;)

See above :)

> Deleting posts through the Admin Interface causes it to count them as
> new posts for the month (Started out with 0 today and 10 total, deleted
> 6 and wound up with 6 today and 10 total)

I've fixed that too. Also, looks like nobody noticed but with the current 0.2 
version if you have a post which is in 'draft' or 'deleted' status for say, 
today, the calendar will still say that there is a post for today when in 
fact there isn't, since the post is not 'visible'.

> Granted most of these are trivial amounts of disk space for storage, it
> can pose a problem when you start looking at long duration / high volume
> use. The more things in the DB the longer the lookups, etc, etc. Given
> how fast we do them right now there should be no problems, but who knows
> where the future takes us... ;)

I think it was good that we did it now since it also helps to keep the 
database clear, even if we only have 2 blogs and 50 posts. So thanks again 
for the bug report :)

Oscar.