Forum Replies Created
-
Use a plugin like Members to lock the forum to members only. Works fine
anointed – What plugins are you running?
If it’s working on some and not on others, the odds are plugins are to blame
I think you misunderstood. Using the class DISPLAY none tells CSS not to show the avatar
In the future I’ll look into adhering to the WordPress Discussion settings for restricting comments too.
Yeah, I’m gonna need that too
Akismet’s great for spam (yay!) but keepin’ out the troublemakers…
And the link to the forums in the menu bar suffers from the old breadcrumbs bug (yay for testing). It tries to link to “https://bbpress.org/forums/topic/forums/” which redirects to “https://bbpress.org/forums/topic/” which obviously isn’t real.
The problem is that the link for the forums is
<li><a class="current" href="forums/">Forums</a></li>It should be
<li><a class="current" href="/forums">Forums</a></li>instead
TextWrangler for Mac.
Original topic on BuddyPress: https://buddypress.org/forums/topic/how-to-create-forums-in-bbpress-within-buddypress
Windhamdavid’s awesome solution link: https://buddypress.org/forums/topic/how-to-access-to-bbpress-admin-from-buddypress
I’m an independent contractor and have worked as a PM/BA for the smallest to the largest companies; and you’re not wrong
That said, Project Management exists for a reason. Its a different skillset from development. And no matter the size of the company or organisation, holding a requirement gathering session and then ignoring the data is just daft.
You’re not wrong either! The thing is, I don’t think bbPress Dev is ignoring the data. They wanted to get an idea from the vocal sort (us) to what we wanted, what we feel is needed, then they agreed and went to design the project in the way that works best for them.
I’ve been VERY closely following the WP 3.0 move (I have two blogs I want to merge into one ‘MU’, and I want to see if I’m better off just sucking it up now or not – It’s a LOT of work to do and not lose users), reading IRC logs daily, monitoring tickets. In doing so, I feel I’ve learned a lot about how the process works. For a moment, I really wanted to piss myself. I’d get really excited about a topic, and then someone would raise valid concerns, talk about goats, and they’re off on a new topic.
Seriously terrifying to watch, when you’re invested.
But.
I’ve had experience herding cats like this before. And I realized this looked exactly like the organizing my old community group used to go through, three to four times a year, to put together a highly complicated event for multiple people, maintaining the element of surprise and yet still making all of the 10 to 50 people who were being rewarded feel special, and putting on a good show. Seriously, I have grey hairs from the 5 years I ran that boat. Glad to be off! The point is this stuff is scary to watch and partake in until you’re used to it. I wish there was another way, but I’ve never found it.
I am also in agreement that “it will turn out fine”, the problem with that is there is no time limit. It probably will turn out fine in the end, or eventually, but how do we, the community (sic) attempt to speed up that process?
Code: Join the IRC dev channel and start putting in tickets for what’s broke, fixes for what you can fix, and suggestions. Even a psudeo-code “This would possibly work better if there was a check for ‘If Admin, then foobar’.” can be helpful. Obviously don’t spam, but I’ve always been of the opinion that the best way to HELP an open source project is to get in and see how you can help. Posting here? A good way to vent worry. Joining the devs, even if, like me, you’re a total hack, is helping.
Documentation: Write a definitive ‘This is how you integrate WP and BB 1.x’ post. Or a good how-to on anything. Pull out the most common errors and make a post about how to resolve them. It’s not GREAT documentation, I admit, but it’ll get people started and, when the doc site picks up, the posts could be lifted and tossed in. It would be nice if TPTB would make a documentation site we could edit, but I understand the nightmare that is. Oy. Not everyone is nice
OpenSource Project ‘management’ is generally terrifying to people used to the rigid structure found in most medium to large businesses. It’s very similar to small company PM, though, and works well for what it is, even though it looks insane and weird and entirely ‘wrong’ to the outside viewer.
Of course the reverse is true as well. The very organized, rigid, PM plans for large companies and projects often are impossible to fit in an OpenSource project and make the people used to the larger ones cry.
It’s just how it is.
Can you share directions for other people?
