Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 20 replies - 1 through 20 (of 20 total)
  • Wow. The codex directs here as a resource, but in here we’re pretty much blind leading blind!

    Seems like maybe a more open approach to the documentation is in order? Like a mediawiki or something like that? I could be wrong; just a feeling.

    Sure enough, @peeld, your code A) set FORUMS as the default tab, and B) broke the activity updates! Thanks for the help!

    I don’t actually mind losing the activity updates, but I’m sure most folks’ projects could benefit from a solution here that didn’t break that function.

    Anyone have input here?

    I read a couple replies back that this broke; can we get an update?

    I really think this needs an update in the core; in blog posts, the title of the post always comes first. same should be true here with the topic title.

    Why would you want to set a body ID?

    Wouldn’t you want to set the title?
    `my buddypress title`

    My problem is that no matter where I am in forums and conversations, the page title is always just Groups.

    My final code, usable for any who desire:

    `
    FACEBOOK SHARE CODE
    `

    they appear unused and not working.

    right. One way they’re not working is that they don’t even report the right info. I don’t recall which it was, but I ran one of those functions, and it was printing Private in a public group.

    I’m not sure what you mean “are you sure you’ve setup your $group variable correctly?”. In my thinking, BuddyPress sets it up, not me; I’m just trying to reference it. I copied that $group->status setup out of the definition for bp_get_group_type() in bp-groups-template.php.

    I’ll give a whirl to the `bp_get_group_type()`, since that demonstrably at least produces the correct group visibility level; my trick will be to use its output in a conditional.

    Ok, so `bp_group_type` is what prints text to the page, `bp_get_group_type` seems to summon the text as a returned value (which bp_group_type() uses for its printing)


    SUCCESS!


    `<?php if (bp_get_group_type()== "Public Group")
    print “foo”
    ?>
    <?php if (bp_get_group_type()== "Private Group")
    print “bar”
    ?>`

    On a private group, I saw foo outputted and no bar. So it works.

    It feels less than elegant. It would be more elegant to just use the variables that bp_get_group_type() calls. But for now, it works.

    Thanks, @RogerCoathup, for the guidance :-)

    Also I’ve tried
    `status == “public”) {
    some facebook sharing buttons
    } ?>`
    and that doesn’t work either.

    With that, I just keep getting nothing outputted.

    I’m also having this same issue.

    On a fresh install, (http://dsjprojects.com/buddypress) post comments are indeed logged into the activity stream.

    But on my main sites, (http://anawimcc.org, http://signsofsafetyusa.com/activity/) post comments aren’t logged in the activity stream. Not even after reverting to Default theme and disabling all plugins, and even updating to the most recent BuddyPress. Not sure what it could be…

    I don’t know what @r-a-y means by “setting my activity stream filter”. I’ve looked around a bit and not found a whole lot on this specific issue; This Thread seems to have a bit of good material but I think I’m in over my head a bit.

    Any help? Or, anyone having the same problem?

    Thanks much,

    I’m noticing that my activity stream isn’t showing ANY post comments as activity. Ideas why? I’ve disabled activity-stream-commenting on posts, but I would have thought that normal post comments would still appear.

    That sounds like a potentially viable fix, actually;

    Namely, if you created a required extra field that groups had to fill out, and then made it the update box conditional based upon that.

    Of course, that wouldn’t block people posting there from their own “What’s New” box on root.com/activity… but I doubt most people would do that anyway.

    @Hugo, you seem like a pretty active and experienced voice in this community, whereas I’m fairly noobish (I don’t speak PHP)… any chance we could work together on moving this forward, either with something as simple as a trac improvement request or even maybe putting a patch together? I’m decent at design but not code.

    @ Everyone else… are others experiencing this / agreeing? This is the biggest issue that has hit me in the face on my first serious BP project…

    @mercime,

    Sorry I wasn’t more clear.

    I’ve already got that disabled. But that doesn’t stop somebody from posting in “What’s New In This Group?” when they see in the stream a question that I asked within a forum . All it does is remove the “reply” button from the stream notice.

    The overall issue here (of which the above is just an example) is of the confusion created where there’s two places in a group (forum, stream) to create conversations.

    So in simplest terms, I need a way to prevent or discourage stream-posting in groups where I want a forum enabled.

    This is now in the core of BP, no?

    Whoa! Like Charlie, I just found that my load button doesn’t work when Activity is my homepage (reading settings)…

    any ideas? (http://anawimcc.org)

    @pasen — Ooh good idea; i didn’t think of that — it would require allowing a bunch of moderators! but it would work :-)

    @hugo @mercime Oops! Sorry, never saw any of these replies, and didn’t know/think to add the trac link. Will in the future. Thanks!


    dannyjimmy
    Member

    @dannyjimmy

    polite friendly bump


    dannyjimmy
    Member

    @dannyjimmy


    dannyjimmy
    Member

    @dannyjimmy

    This sounds good. I think the projects I’m working on could benefit from this also.


    dannyjimmy
    Member

    @dannyjimmy

    Sounds like a fun idea!


    dannyjimmy
    Member

    @dannyjimmy

    It’s certainly an issue of concern. There are workarounds but they’re not always easy:

    http://premium.wpmudev.org/forums/topic/admin-approval-required-for-new-users

Viewing 20 replies - 1 through 20 (of 20 total)
Skip to toolbar