Skip to:

Re: BuddyPress Future w/o MVC: Big Deal?



Member management in WPMU/Buddypress seems patchy as hell to me, with member data spread out over several database tables that aren’t synchronized between xprofile and wpmu, mixing different methods to store data. The registration process is horribly inflexible. Basic things like styling the registration form or editing system emails require hacking core files.

Not sure if this would have been better if WordPress/Buddypress followed an MVC architecture. Wikipedia’s description of MVC:

Model-view-controller (MVC) … isolates business logic from the user interface, permitting one to be freely modified without affecting the other. The controller collects user input, the model manipulates application data, and the view presents results to the user …

I like the sound of “isolating business logic”. I want the end user functionality that WPMU/BP provides (“… WordPress’s usability …”), but have serious concerns about having to rely on WPMU/BP for central member management and registration, the foundation of my project. Unfortunately I can’t have one without the other.

Please don’t dismiss the criticism.

if there’s someone moaning about how any particular bit of software is not written following MVC, they have two options – write their own, or shut up.

They did. They are developing Anahita Social Engine on Joomla. I may have to check it out. :-(

Skip to toolbar