I've deleted all the records anyway and restart.

When I tried to add an existing blog to a space in Blog Setting page it showed Blog added successfully, but the blog didn't show in the aggregated blog list. However, the blog id was saved in jiveCommunityBlog

Yes, I think I've discovered a few things towards what you're saying while waiting for your response. It indeed relates to blog access permission. I could understand about limited access to view blogs when you specifically block the access from users. However, it doesn't make sense when I login as admin (with full admin previlege) into the admin console that I couldn't see the blocked blog in the blog aggregation list in Space::Settings::Blog Settings.

Apologies that it was (kind of) hard to describe how to reproduce the error because I was moving and clicking here and there in the admin console when wierd things suddenly happened, not knowing when they actually did. FYI, basically I have an open access at the root space and a fair number of private and restricted sub-spaces and blogs. I also have multiple groups and users permission settings.

I've come up with a way to reproduce the error, and I hope it will reproduce at your end:

1. Login as full admin into the admin console.

2. If you haven't, make read access to spaces for anonymous and registered user.

3. Create a new blog from the Blog::Create Group Blog page, say "test" blog, and add "admin" as the author.

4. Go to the blog permission edit page for "test" and make sure that "Anyone" and "Registered Users" have read access.

5. Jump to Spaces::Settings::Blog Settings and you'll see that "test" is automatically added in the root's aggregated blog list.

6. Go back to blog permission edit page for "test" and explicitly block read access to "Anyone" and "Registered Users".

7. Jump back to Spaces::Settings::Blog Settings page for root. Now the "test" is no longer listed in the aggregated list. Wierdly, if you look at the database, the id for "test" is there. This is where things start to become confusing.

8. Assuming you're like me last time, thinking that this should not happen... Enter "test" in the "Aggregate new blog" and hit the "Add Blog" button.

9. Now you'll see that Blog added successfully. However, you can't see it in the aggregated list. How would I ever delete the "test" blog later if I couldn't see it in the list? Ok, for now, lets move on...

10. From this space page, click on the (change space) link and jump to any other spaces. Do you see that the Blog added successfully icon is always there when you didn't actually aggregate more blogs in the other spaces?

11. What made it more confusing is that there is nothing informative in the jive.error.log and jive.debug.log that might give a clue.

If you don't see the error (...argh!!!) please try to spend some time playing with the permissions and blog aggregation by adding users and groups with conflicting group member permission, and changing their blog access permissions.

The admin console doesn't give the full view of my clearspace setup, but the database do. Funny eh? User access to Clearspace is as laid out in the database, luckily.

Now that I know that it might just be an admin console display-related problem, I've established some workaround. To get back to the invisible "test" blog in the Spaces::Settings::Blog Settings, I have to temporarily allow open access to the blog in the edit permission page, then jump back to Spaces::Settings::Blog Settings, and do what ever I want with the blog and spaces. Finally, I have to remember to reset the blog permission to its original setting. This workaround is by no means perfect because during the time, I will have to allow the side effect of exposing sensitive information.

I really hope that the given steps above will help you reproduce the error in your system. Please let me know if you still can't get it, so that worse comes to worst, I might need to reluctantly force myself to do a fresh reinstallation, thinking that I may have accidentally tempered some of the files and database tables .