[stonyarc]

Originally Posted by Annapurna

Just a theoretically question: In the beginning you'll never know if an new feature gets lot of attention or not, so just a 'normal' integration into vB would be fine. But in case it turns into an hurricane and 100s of users apply for it, would it be possible to change to a mysql farm later?

Another feature question: will it easily be possible to import vBJournal articles?

Andreas

journalistID and userid are linked so in theory it would be possible to write a migration script.

Originally Posted by rob30UK

Could this not work from one set of tables? I was thinking the addition of a userid or siteid columns to each table so the data could be 'per site' but still within the realms of managability. This way would also make changes across all sites easier, and in addition it would make permissions handling from vBulletin easier.

Obviously, I dont know exactly whats involved with the above, I'm sure its a fair amount of slog...but I'm thinking that once you've gone the full distance on your current path, it may have been less work going the alternate way I mention.

That was indeed also my first architecture but the impact on wordpress in that case is rather high and it would require several changes to wordpress. Moreover that creates an installation where there can no longer be an easy upgrade to future versions of wordpress.

the vbulletin part is slightly easier but the wordpress part becomes a drag in creation and maintainability.

Moreover I would bump into the same issues as wordpress MU and would have to give up the flexible management and admin has on his own blog.

There is still a long way to go to make this a full featured thing.

It might even be better to write a blog system from scratch with the features of a true blog in vbulletin itself.

Time will tell and I'll certainly let you know.