BuddyPress.org

well i didn’t go anywhere near the php.ini file as this is a dedicated server and I don’t separate them out on a per site basis.

the .htaccess file was not overwritten, left that intentionally.

I’m going to try it one more time and see if it helps.

I did have one problem that I forgot about. I accidentally deactivated buddypress before I deactivated all the plugins that rely upon it. That resulted in a 500 error. I had just removed the offending plugins that rely upon buddypress via ftp, figuring that would solve the problem. Which it ‘appeared’ to do, but obviously not.

So I reactivated buddypress, then reupped the other plugins via ftp, and then did the deactivation the right way. Now all are properly deactivated and I’m replacing files again.

will report back.

John: reminds me:

burt actually asked me to send you a pm regarding an ‘issue’ i am having as he is to busy with his move. I’ll send it after this final attempt.

I have had no luck at all trying to upgrade from 2.7.1 to 2.8.1

Here are the steps I am following:

1. backup all files and db – done

2. deactivate all plugins on the main blog

3. remove all plugins from the mu-plugins folder

4. delete wp-admin and wp-includes folders from server

5. upload all new 2.8.1 files to the server

Then when I try to reach any page on the server I get a 500 error which is as follows:

PHP Fatal error: Call to undefined function wp_clone() in /website.net/wp-includes/cache.php on line 380

The only thing I can do at this point is to delete all the new files I uploaded and replace them with the old 2.7.1 files…

I have tried this 4 times so far with no luck. I have made absolute certain that all the files are properly overwritten, but still end up with the error.

Is there a solution to this problem, or am I the only one with it?

I’ve read the upgrade docs, and as far as I can tell I am not missing a step, so I’m really stumped here…..

btw

my buddypress install is NOT on the primary blog, so I did not have to change the theme. It is a wp standard theme on the primary blog

@Russell:

HOWEVER…

I lose the forums function in BuddyPress groups

Remember you also need the XMLRPC call in your bb-config.php as well for group forums.

$bb->bb_xmlrpc_allow_user_switching = true;

(goes right before ?> in bb-config.php)

Do this again and make sure you have the XMLRPC line in bb-config.php

JJJ’s method, it looks like /home/public_html/…

But that way will get BuddyBar in bbPress to work and my forums integration from BuddyPress breaks.

The only way to keep the forums integration in BuddyPress is to leave it as http://mywebsite.com/wp-blog-hear.php

I just have no idea why that works…

– Understanding how these 3 pages works in general. Do they belong to the bp-member or bp-home theme or both.

They are styled in the bpmember theme, which is a BuddyPress theme.

The bphome theme is a WordPress theme.

– Figuring out how I create a copy of lets say the Member page, then give that page an entire new name/slug.

Not sure about creating interior BP pages… I know certain BP plugins create their own slug and pages (eg. bpEvents, bpContents).

But depending on what type of page you are planning on creating, I would just create a new page in WP and assign a WP page template that is setup almost identical to the bpmember component in question. This would be the easiest route if you want total control of the page.

However, before you do, you might want to consult with a mod who has more experience with BP than I do!

I followed r-a-y’s advice and used the ABS path in my bb-config.php file.

I can activate and use the BuddyBar in bbPress normally.

HOWEVER…

I lose the forums function in BuddyPress groups, but if I go back to bb-config.php and use the URL for the include_once line I get the forums functionality back and BuddyBar stops working, i.e. it disappears from bbPress.

I guess I don’t REALLY have deep integration working, but the forums functionality works as I would expect and right now that is what I am concerned about.

I’m going to have to sit out and watch this play out and hopefully an easy to follow guide comes out to integrate the latest versions of WPMU, BP, and BB.

My setup may not be “right” but it works as I want it so that’s all I can ask for right now.

Just tried this for one of our groups and you’re right. It doesn’t work. Like you, I hope this bug gets squashed since email notifications to group members is the very essence of the functionality of Buddypress.

@Indojepang

It could be an issue with rewrite rules. Read these two threads. Please not that Nginx does not (read cannot) use a .htaccess file.

https://buddypress.org/forums/topic/404-errors-using-yahoo-to-host#post-16797

https://buddypress.org/forums/topic/nginx-re-write-rules

Hey amweiss,

If you can’t wait for Jeff’s component, there is another one out in the wild by Sandra Petronic:

http://devbox.computec.de/2009/06/buddypress-xprofile-privacy-plugin/

Hope that helps!

Of course not, that wasn’t my point. The registration functionality in WPMU is quite restrictive and cumbersome right now. That will improve though. If you’re concerned about this, then don’t consider BuddyPress as we’re only on version 1.0.

I was going to take the gamble that it would improve over time. Hearing most developers here dismissing any architectural criticism and only singing the praises of WordPress is not encouraging though.

You know why people that join fraternities rarely ever leave? Because once you’ve gone through the hazing, you’re more likely to stay.

Right, once you’ve decided on a platform it’s very hard to go anywhere else. You’re stuck.

Every couple of years I reevaluate what to use for my websites. I started on Nucleus. The current version of my project Web2NewYork is built on WordPress with a members registration system based on code taken from PunBB.

I switched to WordPress reluctantly only because it was becoming the standard. I’m now trying to consolidate on Buddypress, if I can everything working before September. If member management/registration does not improve I will have to switch to something else next year.

Not at this point. Look at the BP roadmap (v1.2) and look at this.

No one can answer on Nicola’s behalf, but it sounds like he’s abandoning development on this project to me, in lieu of it being a core feature eventually.

This would work not unlike the way wordpress.com allows you to map your blog to another domain. I suspect that would basically end up being this, or vice versa? That being said, it sounds like a WPMU feature that would have a piggy back panel for BuddyPress to me.

Does that mean I have to keep my mouth shut about the crappy patched together membership management mess that will now become the foundation of my project?

Of course not, that wasn’t my point. The registration functionality in WPMU is quite restrictive and cumbersome right now. That will improve though. If you’re concerned about this, then don’t consider BuddyPress as we’re only on version 1.0.

Since my opinion counts too, I’m going to jump into the fray…

The reason why people like WordPress, is because it unknowingly found the PERFECT balance of challenge, and ease of use. In order to become proficient at using WordPress as a development tool, you have to go through a rigorous 6 month hazing period of being totally lost in the code. Not because it’s badly written, or sloppy, but because it’s just a lot to learn.

You know why people that join fraternities rarely ever leave? Because once you’ve gone through the hazing, you’re more likely to stay. You know how businesses earn repeat clients? They charge MORE money, because people are more likely to go back to a place they’ve already invested money into, rather than a place that gave them a $15 oil change. Strange eh? Make things too easy, and people won’t go back. Make it too hard, and they won’t even try it in the first place. There’s a balance, and WordPress, bbPress, and BuddyPress found it.

Once you learn it though, it’s like driving a 6 speed manual trans; you just glide through the gears without really even thinking about it. It’s like learning to juggle; or play baseball; or ride a bike. You just do it naturally.

My experience with things written with strict coding standards is that no one ever appreciates the time spent adhering to those standards anyways, and the codebase is basically ignored. phpBB is a great example, because the code is dead simple to use and understand, but how many people do you hear about using it to its full potential?

I used to code every single website I did to section 508 compliance. You know how many clients cared? 0. So, now I don’t. Haha!

WordPress, BuddyPress, and bbPress make you earn your keep. They are investments in time, energy, and they actually can give you back what you put in. Not EVERYONE can sit down and develop a good plugin for any of the platforms, but LOTS of awesome plugins are possible and with a little time, anyone can sit down and write one. Anyone can develop a theme with a little effort. WordPress works for everyone, not just newbies and not just professionals.

I can’t predict what tomorrow will bring. Maybe something will come along and totally blow the doors off of anything we could develop ourselves. That’s okay. But for right now, I don’t think there’s anything better than what WordPress, bbPress, and BuddyPress bring to the table.

If you are concerned with the way WordPress is programmed, then I would asses the value in being concerned. Look at the number of themes, look at the number of plugins, look at the number of users. Look at the companies that use WordPress. At what point does worrying about the coding style become moot?

That’s why I chose to build my new site on Buddypress. Does that mean I have to keep my mouth shut about the crappy patched together membership management mess that will now become the foundation of my project? It’s not a moot point. It’s a painful trade-off and if I could start over I’d probably give Joomla + Anahita Social Engine a go.

I’m perfectly entitled to not pay attention to the MVC-or-not structure of both WordPress and Buddypress, as I don’t work for Automattic and I’m not a core developer on either.

I was addressing the Buddypress development community in general.

There is no easy fix for ignorance. Clients will generally believe what they want to believe. I guess it’s everyone’s job here to build great sites using WP/BP… so get going!

Ha!

Andy, that’s basically what I said in my last paragraph!

Also – something to consider. If WordPress was completely object-oriented, fully MVC, and the most beautifully designed code imaginable – 90% of developers would not be able to understand it.

When trying to create a popular open source application you have to strike a fine balance with regards to entry level. You don’t want to make it so beautifully abstract and complex that only the level 70 geeks can develop on it.

Your application needs those people that program in their spare time for fun, but don’t necessary know what instantiation, encapsulation and polymorphism are. Those people are the most important if you want any sort of active developer community.

Here we go with MVC is the only approach. Having used the Codeigniter and Kohana PHP frameworks in the past, I know a little something about MVC.

MVC is a design principle that various frameworks implement so that others can then create their applications. WordPress is an application that offers a means to extended its functionality. It is not a framework. A framework is not an application. You create, code, applications (like WordPress) using various tools. A framework is just one of those tools.

I agree, from a plugin developer’s standpoint, that it might have been nice if WordPress had used a solid MVC framework with which to build its foundation. But, I don’t think there were any good MVC framework options at the time it was initially being developed. It would also be nice if WP were fully object based. But, this is all a moot point.

WordPress is and will be fine in its current state. There will not be issues “down the road”. Why?Because WordPress continues to improve and evolve (look at the powerful BuddyPress layer). It has been doing so for 6 years without reaching a point were it ceases to work.

As Paul said, since this is an open source project, anyone is free to fork it. WordPress, in fact, is a fork of another, older blogging system. So, if you don’t like what’s under the hood, then change away and create your own CMS!

It is interesting that the author of that slideshare fails to mention that Joomla, the application that their Anahita Social Engine requires, in not an MVC framework. Remember, Joomla is also an application, not a framework. A separate module/extension had to be created to offer some MVC-like functionality to those who wish to further extend Joomla in a manner somewhat reminiscent of a true MVC framework.

In my opinion, if WordPress were to be recoded from the ground up using one of the various PHP-based MVC frameworks, it would result in an application that while possibly being easier to create plugins for, would make it much harder for designers to create themes. This would make it harder for the average user to use.

I should also mention I was at this presentation, and BuddyPress was not mentioned for the slide in question. They repeated numerous times that BuddyPress was an exception and was actually a source of inspiration for their project.

You can take MVC however you like. If you are going to take it in a black and white sense then BuddyPress is not MVC. However, it follows a loose MVC style:

1. bp-[component]-classes.php contains all of the database access classes [ Modal ]

2. /bp-themes/[themename]/ contains all of the template files [ View ]

3. bp-[component].php contains all of the business functions [ Controller ]

BuddyPress is certainly not programmed top-down. In fact, if you try and program top-down with BuddyPress you will quickly become frustrated.

If you are concerned with the way WordPress is programmed, then I would asses the value in being concerned. Look at the number of themes, look at the number of plugins, look at the number of users. Look at the companies that use WordPress. At what point does worrying about the coding style become moot?

At the end of the day MVC is just another coding methodology, it is not “the right way” to program. The right way to program is subjective and very much based on your program’s function, audience and ideologies.