Forum Replies Created
Nevermind, I’m a retard.
Got everything right, spelled .htaccess wrong.
Excuse me while I wipe the egg from my face.
I would eventually like to see more ability incorporated into the BuddyPress navigation bar, but until then I agree. While “News” does tend to set an expectation that the main site blog is only about site related news and updates, it isn’t necessarily a “blog” as the word means to most people either.
And I’ve found that the instructions to change the link text really haven’t worked for me either. I’ll see about that in RC1 tho.
I guess what I’m trying to find out is if the major difference is database related or file structure related. I ask this because I’ve got a blog with about 50 posts, 300 comments, and 200 registered users that I somehow installed with domain instead of subdirectory. Now if you ask me, I am 99% certain I didn’t choose subdomain because I know better and know that my host doesn’t allow for it, but because I now see that it’s setup for subdomains (now that I want to make a second blog) I feel like 1% margin for error just isn’t enough.
I digress… I’m really just looking for a little guidance as to what makes the installs so unique that it requires a full reinstall that cannot be patched in some way.
Well, haha… I’ve searched over there and no one seems to have answered other than “You can’t do it, follow the instructions retard.” Ha! BuddyPress users are just nicer overall.
But hey, you’re right and I’ll give it a shot.
Wow kudos for the in depth reply. I’m super excited to give this a shot, I’m actually waiting to go live until I see how this works.
I think it’s a great idea to keep things all synced up also. I made the mistake of adding a group forum in BuddyPress and deleting it in bbPress. Boy did that make things angry ha!
I’ve noticed even if I use what bbPressers call “deep integration” (including wp-load.php in bb-config.php) on the bbPress side, bbPress still seems to blast out the BuddyPress specific content. I’ve echoed the files and I know they are all getting included, they’re just not doing anything once bbPress gets a hold of it.
Mr. Adsit sir, no rush of course but I’m curious if you have an ETA on this plug-in? I’ve got things nicely integrated now, and feel like this would be a great finishing touch.
This is what is called “deep integration” over on the bbPress side of things. It is often times shied upon but I feel is very much a requirement for making things look all nice and pretty.
I know for sure it is possible on the WordPress.org side of things as I’ve done it several times, but I am going through my first MU/BuddyPress attempt tonight and tomorrow.
I’ll do my best to see if there are any differences, and report back with what I find.
Slightly off topic, and correct me if I’m wrong, but “Blog” is basically just a direct link to the wp_1_ blog, right?
Is there any working way to change that URL and link?
My guess is that may get pushed back, judging by the tickets currently in the trac.
Can’t wait! I was surprised to find that it didn’t work this way and am happy to assist with any effort to help it along.
Nice, that’s exactly what I was hoping for. I’d gladly test with you when the time comes.
Thanks Burt. That answered my question.
I realize now I didn’t really phrase my question clearly. I have been using bbPress integrated with WordPress.org for a few months now and am very comfortable with how it works, however it obviously integrates much differently with BuddyPress, with group forums and all.
So to confirm, there are group forums and then global forums, and anyone can post anywhere regardless of group membership?
I see I’m not the only one thinking in this direction. Basically a uniform default pre-widgeted blog layout for new users to use, that matches the existing site, creating a “facebook” like experience for lack of a better term, where everything fits nicely in its box.
I think the next step would be once you’ve got that done, to remove the “Appearance” area from the user admin entirely, that way they don’t go breaking it, or seeing a menu that they can’t use.
I’ve thought about making a default theme that wasn’t widgetized, with a hard coded sidebar.php; that would work, but it’s more of a work-around than a resolution.
So the above little blog to news function doesn’t work for me.
I’m not using the trunk, just the most recent beta. Could that be the problem?
That’s the response I anticipated getting, but it doesn’t answer the questions.
Unless I’m missing something, and I definitely could be, doing that alone makes the default theme set and still allows for editing of widgets. I would like a pre-made widgetized blog setup so that my users can’t/won’t have to do it themselves.
Does Milwaukee know this?
Hmm… I suppose not…
But then again, how many people can you say made it out of the Midwest alive?
I will go out on a limb to say that what looks like a bug at first is often times just normal user error.
I consider myself a seasoned PHP/SQL/Linux/WordPress/bbPress veteran, and to be honest it took me installing and reinstalling MU/BuddyPress 4 times before I was able to follow the instructions correctly. Each time I would have sworn on my undead mothers grave that I did everything right, but alas…
So a tip to you all, if it isn’t working, it just might be because of something you don’t know you didn’t do…
I am experiencing the same issue, and it seems like it is less about which plug in, and more about how many.
I’ve gone through and added/removed all of the buddy press components, and as soon as I have more than about 5 of them, I get 500 errors no matter what page it tries to load.
The fix for me was to make a file named php.ini, and within that file put:
…and upload it to the wp-admin folder.
Basically 1and1′s PHP limit is probably set to like 8mb or 16mb, and BuddyPress is just too big for those britches. Of course, you can increase your memory size to whatever makes it work for you, but 20MB should be plenty.
I also put:
AddType x-mapp-php5 .php
AddHandler x-mapp-php5 .php
…in my .htaccess file at the root directory to make sure 1and1 knew to give it php5 and not the 4 that it tries to give by default. Silly 1and1…