I want the user to be full admin of the blog he gets.

so that's the starting point

However from within vbulletin I want to be able to push new settings to all blogs that were created. (update engine)

this sounds excellent stony. Did you know that wordpress has Wordpress-MU (multiple-users)? Only thing about it is that it's not supported on the wordpress support forums and at this time, there are no themes created for it. So I'm assuming it's rather new?

I hope you get this up and going soon stony, my members are rather anxious to blog

C'mon.. there has to be more people interested in this hack...

I hope some more people would show interest in this. I think it would be a major addon.

I'm sure they will when it is released. I've talked to several people on other sites who don't come to vb.org often and they are definitely interested.

How soon do you think this could conceivably be released stony?

Stony, the idea is great and you would get a ton of installs once it were complete. Most people, myself included, don't normally respond to these types of threads because the work doesn't always prevail after everyone has voiced their "support".

Blog software integrated completely with vb would be great and used by many.

I'm currently testing some of the basic functions but there is a lot to tackle in this one

- Core functions
- tables in mysql database (too much will kill the service)
- password generation
- automatic php config file edit on assignment
- wp update engine from within vb
- admincp functions
- wp style functions
- new version control
- integration in postbit/member pages
- ...

The use of MU isn't an option for these functions. I want users/blogadmins to have enough freedom and only manage it from vb on high level.

Timeline is as always with my mods ASAP because I need the functionality too.

Also should I go for seperate databases or use the vbulletin one. Not everyone has access to more than one DB on the server.

You should have it use the existing db and why do you need password generation if it is going to use the users permissions? If they have an account already, no password required. I haven't used wordpress yet so I don't know if they have "profiles". If they do, I would drop them and use the default vb profiles.

The profiles isn't a real big issue.

Wordpress is a fully seperate application so it would remain like that.

I want to make so that vbulletin installs a wordpress for a specified users so that the user has it's own blog application on a subdir.

It's 1 user 1 wordpress and not N users on 1 wordpress.

My mod is creating a blogfarm not a single blog.

If the users need to register for the blog and the forum, it won't be as popular as I initially stated. I was under the impression you were integrating it. Basically, when a user joins your forums they also have registered with the blogs. The blogs would be controlled via user permissions like Drupal is.

X usergroup can have a blog
X can't have a blog

Basically I thought this was going to become a vBlog type application. One wordpress that allows multiple blogs based on who has the right permissions.

1 MU isn't far enough to support that
2 the core version of WP should be used as that's the one that is supported

I want

1 manageable blogs from admincp wordpress based but fully functional.
2 1 user 1 blog or 1 usergroup 1 blog principle
3 no seperate registration (the database/datamodel I currently made is integrated)
4 file update and version control on all the installed blogs so you can push a certain page/ad/update/style/patch to all blogs at once
5 vbulletin becomes the dashboard/management console of the wordpress farm
6 best of both
7 compatible with updates of wordpress (push from within vbulletin update engine)
8 ....