Forum Replies Created
-
There is a forums user looking for help in Turkish. Perhaps you could take a look at this thread: https://buddypress.org/forums/topic.php?id=3433
Not sure what you mean. You want to display the user and group tags under the avatar? That’s always possible. Just because I remove that from the distribution doesn’t mean it can’t be done. What I think I will do is include the code for the tags/cats display for members and groups and then allow people to turn it on. It’ll be off by default.
I’ll include that in 1.1 which I have planned for release by next Friday 7/10.
I can’t make assumptions about the parent/child relationship between categories. Specifically what use that relationship will be put to. Perhaps in some environment the parent category will not be displayed for selection and only the children will.
The relationship still exists even selecting just the child.
Actually I had intended to eliminate the profile tag display altogether. I just forgot to do it. I don’t want to force the display of something in a theme. It was a design decision to omit the category profile display and an omission to omit the tag display. Huh?

I’d prefer to leave the inclusion of those things up to theme authors and site admins.
The alpha 2 issue you mention will go away. bpc 1.0 doesn’t use the bp directories anymore.
There is no upgrade path from alpha 2 to 1.0. It doesn’t use any of the same low level code or any of the tables. Complete re-write of the underlying core code using wp’s taxonomy tables instead.
Hello.
1) Doesn’t really matter what you were upgrading from. Just install bbpress 1.0.
2) I don’t trust the auto upgrade process so I manually upgrade
3) No buddypress enable plugin is needed. You do have to be running the right version of php though. See:
http://josephscott.org/archives/2009/03/conclusion-of-libxml2-issues-use-php-529-libxml2-273/
http://josephscott.org/archives/2009/03/wordpress-libxml2-episode-iv-a-new-plugin/
4) Don’t know what the issue is there
5) Yes this user switching is needed.
Don’t forget to enable pingbacks and xmlrpc. Also my test group forum didn’t work right away. I disabled the group’s forum component in the group admin page, saved the settings and then re-enabled it. Worked after that.
The automatic sitewide plugin upgrade process in 2.7.1 is trash. Try manually upgrading. Deactivate the plugin, manually upgrade and then reactivate it.
You aren’t going to get much, if any, response without bp version info, what theme you are using and a link to your site.
Hey Erwin. I’m implementing blog posts right now. That will serve as a guide.
I added the .pot file and manojkumar is helping me out on irc right this here moment. Mornin’ jjj!
Ok. The download and trunk have updated language function calls and I’ve added the bpcontents.pot file to both. Let me know if I’ve done it all correctly.
socialpreneur, yep working on it. It seems that the wp plugin repo has a ‘pot’ generator utility hooked up to each plugin. I’m gonna test that today.
It’s all kinda hazy as to what the solution was in the middle of the WTF event. Upgrading to the current ver of bp’s themes and clearing everything out worked. I’d bet money on Andy though.
I don’t know what to tell you then. I upgraded my themes also to the trunk version of the themes because I’m running trunk bp.
Haha.
Clear your ff cache. The’re hiding it under Tools > Clear Recent History > Details. Same thing happened to me. Panic city because I just installed trunk bp. I broke out IE 8 and it was fine. OMG it looks ok in IE?! This just can’t be happening. I’ve taken a turn into some horrible alternate reality.
Got something to do with the new font handling, new render engine, new something I’m guessing.
I’ve run into this before. That code snippet above only works if the $foo’s are created in the template. The code underneath that contains $foo’s is a different scope.
Just putting a $var in the template doesn’t mean that the $var is available in that scope. Unless you are generating the value of $var in the template itself it will resolve to 0 and be passed along to bp.
You’ll have to learn how to use the linux shell and how to do maintenance on your server. Either that or partner with somebody who knows it. Managing a dv and the sites on it are not for the faint of heart. It requires a certain level of experience that everyone eventually develops.
You need to setup root access so that you can edit your hosts file. From MT Account Center > Domains > (your domain) > Root Access & Developer Tools.
Enable root access. I don’t know what that screen looks like anymore since it’s enabled in my dv already. I don’t know what operating system you’ll be using but then you have to have a telnet client for SSH access. I’m on windows and use puTTY.
Login as ‘root’ and edit the hosts file according to the thread above. Worked for me.
I haven’t been able to get anything but bbpress alpha 6 to work with group forums. Perhaps others have a different result. I’m running on MT dv also. I banged my head against it for some time and realized finally that it was an issue with my hosts file. See: https://buddypress.org/forums/topic.php?id=426
bpc alpha 5 will have a tag and category maintenance feature. Add, Delete, change Name and Description by taxononomy. Working on that now.
Well I was mostly prompting so that others can play and look for the issue you were having problems with.
alpha 4.2
Release notes
alpha 4.2 CSS fixes. Thanks to John James Jacoby
alpha 4.1
Release Notes
alpha 4.1 – Fixed a template bug in blog category maintenance . Missing the check for the user has selected a blog. It just dropped into an unrelated form. That template also read ‘Group’ instead of ‘Blog’.
Well, I can’t do that at the moment Paul. I reverted my dev site to wpmu 2.7.1 due to widget problems in the wpmu back end. Running trunk wpmu developed various issues in the back end widget area. I was testing the bpc alpha 4 widgets and couldn’t change the titles. What?! Moving back to 2.7.1 solved this. I have to test and develop with what most people are running.
DJpaul, what’s the issue? It seemed to work ok when I played with it. You just needed to implement persistence right?