Forum Replies Created
Done. #3630 & #3631. I didn’t know that regular users can report bugs on the trac site, neat.
I didn’t submit one about future years since you mentioned it is by design. But is there any way to make the form show up to the current year?
Josh, thanks for the link. It mentioned: “If you’re using any other conventional WordPress theme (TwentyEleven, BP-Default) and find the default template layout of bbPress acceptable, you don’t need to do anything at all – it should just work.”
So the message in Appearance isn’t an error just informational. I’ll just ignore it then.
I’m not sure if this is correct so you’d probably want to wait for a developer to answer, but the way I got it to work (because I also agree forums is the best name/slug) is to delete the Forums page that BP created. Initially I also got a blank page with just the title, but when I permanently deleted it the bbPress forums showed up as normal.
To answer your second question, the BP forums installation page went away after I disabled the group forums component in BP settings.
I’m not sure if this is the correct way to do it, but what I did was: disable the group forum component in BP settings; delete the forums page that BP installed (because I like to use /forums) but I found you can also use a different slug. If you go to WP Settings > Forums it has a bunch of bbPress settings.
One thing I cannot figure out so far is why I keep on getting the following error message in Appearance: “Your active theme does not include bbPress template files. Your forums are using the default styling included with bbPress.”
Otherwise it looks fine in the bp-default theme. Anyone know why that happens?
It also seems bbpress needs a bunch of plugins to make it work like nice sites I’ve come across.
I really like the site-wide forums though, was never really a fan of group forums. Thanks for the choice!
Also… I just wanted to comment that it would be really nice if the documentation for Buddypress is more organized. Currently there is information about 1.5 mixed in with 1.2 and even earlier. Is it that difficult to separate major versions and keep it organized?
I came across an article in the codex talking about enqueued CSS, with lines of complex code including instructions to update a variable when changes are made to bust cache.
I am sitting here waiting for some answers without working any further on this project, thinking to myself WTF does enqueue stylesheet and bust cache mean, I cannot even get comprehensible answers googling them, and hoping that I did not waste numerous hours working on a pre-1.5 project powered by BP.
i do appreciate all the hard work put into BP, but just because it is open source doesn’t mean there is no need for any logic behind it. Obviously there is no expectation for serious projects to use it out-of-the-box with the default theme and default components, so in my opinion, it is essential to explain to your users what the next version means and what needs to done for a smooth transition. Instead of publishing several articles about an unreleased version, perhaps it would have been wiser to have done that instead. If I had the knowledge, I would have gladly offered that.
I really hope I don’t move to another platform as I love WP and really liked BP’s usability when doing my research.
Oops, I meant user widget, not admin widget. Actually I’m not even sure what to call it exactly.
Oh and I should note that I would trust the default BP installation, but since I added several plugins and modified/modifying several areas which is why I want to test it in this manner.
Wow thanks that looks like a neat add-on.
As far as the coding goes, am I supposed to start from scratch or copy over all the files from the plugin / bp-default directory?
It’s quite a shame that the documentation is lacking considering Buddypress looks very powerful from the example sites I’ve researched.