BuddyPress.org

I’ve tried that as well. I’m using firefox and it has a function for selecting and deleting individual cookies. I’ve also tried moving the constants to the bottom of wp-config.php since I wondered if wp-settings.php which is loaded at the bottom of wp-config.php is somehow overriding the constants.

Does bbPress actually load wp-config.php for integration to pick up settings??? I haven’t had a chance to trace through and find out what files are loaded.

John, I tried commenting out that setting and there was no joy. I’ve been focusing on the cookie domain:

on the wordpress side, on logging in the wordpress_logged_in_* cookie has the cookie *Domain* ‘.bz.dev‘, whereas on the bbpress side the cookie has the *Host* ‘bz.dev‘.

So on the wordpress side there is an extra ‘.’.

It does this irrespective of whether COOKIE_DOMAIN in wp-config.php is:

define( ‘COOKIE_DOMAIN’, ‘.bz.dev’ );

or

define( ‘COOKIE_DOMAIN’, ‘bz.dev’ );

My understanding is that if cookie handling is the same on the wordpress and the bbpress sides of the integration, then the login state should be retained.

It seems to me that the problem is may be related to this COOKIE_DOMAIN constant and how it is being handled (or ignored) by wordpress (and/or bbpress).

@anointed check your permission and be sure that the dir owner is not root

Is anyone having any success determining the steps for a fresh install of WP MU 2.8.1, bbPress 1.0.1 and buddypress 1.0.2?

I can’t get the WP MU 2.8.1 and bbPress 1.0.1 integration playing together. I’ve tried the bbPress Integration plugin for wordpress. This plugin shows one section with wordpress constants COOKIEHASH, COOKIE_DOMAIN, SITECOOKIEPATH and COOKIEPATH under the “Save Changes” button:

define( ‘COOKIEHASH’, ‘8601cf66cb0dd7bfc31ae5a1499a18a4’ );

define( ‘COOKIE_DOMAIN’, ‘.bz.dev’ );

define( ‘SITECOOKIEPATH’, ‘/’ );

define( ‘COOKIEPATH’, ‘/’ );

I’m working on an offline development server on my Mac (XAMPP running php 5.3.0). I was using MAMP Pro but stopped using that when I found out their was an incompatibility with the libxml / php versions it was using.

Currently I have to logout of one backend to access (login) to the other (or clear cookies) to access either backend. I can’t be logged into both at the same time. It’s sharing usernames and password okay …

Are there any tricks that people have been using to try and debug this?

I’m quite keen to work from a fresh install of latest releases of all the components rather than working through upgrades of previous versions (which are also tricky to integrate).

I’ve tried stirring in newt’s eyes and frogs legs into the cauldron but they don’t seem to help.

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

r-a-y

The new widget API has totally changed making some widgets inoperable.

Are BP’s widgets working in MU 2.8.1? Probably not, right?

I have not yet tried BP’s widgets with WPMU 2.8.1, but I do know that they have not yet been ported to the new widget API. However, I believe that in theory WPMU 2.8.1 allows for widget backwards compatibility. So, they should work.

We should begin building a list of any issues we have with the default BP widgets in this thread. Then, we can add solutions to trac.

Actually, I’m going to hold off MU 2.8.1 for awhile.

The new widget API has totally changed making some widgets inoperable.

Are BP’s widgets working in MU 2.8.1? Probably not, right?

– 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’ve just done a successful upgrade, with a few minor issues which are now noted in the original post.

Link to John’s WPMU ticket regarding bbPress for reference (just if some want to refer to it):

https://trac.mu.wordpress.org/ticket/1032

I’m going to try upgrading to WPMU 2.8.1 on my testbox and see what happens as well.

You know, John, I wasn’t even thinking about the Back to the Future reference when I typed it

I think your patch made the cut, as I don’t see it in the active tickets in the MU trac.

Great scott! Just when I thought all the craziness of bbPress was done!

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.

@thebigk, if your DB for one reason or another needs repair or optimization, the best way to do that is with a human eye and phpMyAdmin. This should rarely happen however, so you shouldn’t have problems going forward.

The suggested way of upgrading the core is to deactivate all plugins first before you press go. Otherwise those other plugins are trying to load even as WordPress hasn’t fully upgraded itself, which can cause conflicts if the tables or indexes change even slightly.

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.

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.