BuddyPress.org

This may help (thanks to Boone). It’s written for BP 1.1.3 which has the same problem with private posts/comments in the site wide activity stream. If you try this solution let us know if works on your BP 1.2 install.

https://buddypress.org/forums/topic/hidden-blog-posts-from-private-blogs-in-sidewide-activity-stream#post-32757

I guess your Blog will be “private” when you select “Privacy No” during Blog-setup ?

Not sure about this though….

@symm2112. Tried to access the ‘private’ forum but I guess you have to be a paid member. Most sites that require paid membership have pre-sale questions thread to address these type of things. Might be a good idea.

NEway, I’d be interested in seeing these efforts merged. They seem too similar to keep separate. If Brajesh has a longer timeline, maybe the development help can change that. It also sounds like Brajesh will have incentive to keep it going due to being compensated.

Just a thought. We have so many other things that BP needs, I’d hate to see too much duplication. That said, if the functionality/use cases are different, maybe it’s justified.

the logic is to not use the blog but the interface… that’s why the blog is supposed to be set to private instead of public.

========== Continued ==========

Using 1.2 bp-default theme. Based on roles set in classified settings page, I allowed contributors upward to post classified ads.

Posting Classified Ads from BP frontend

1. Clicked on Classifieds on Main Nav.

2. In Classified Ads Directory Page – click on Create A Classified

2.1 – Classified Details – page has fields for Title and Description, then click on “Create Classified and Continue

2.2 – Classified Setttings – page has list of categories created per classified component instruction via special new blog and field box where you could add tags, and click on “Next Step”

2.3 – Classified Invites – page where you can send invites to other members re classifieds, click on “Finish”

Classified Ad Entry posted appears in Classified Ad Directory Page. The ad was also posted on the special new blog as post entry per my check. In addition, under member Profile Page, there’s now a link “My Classifieds” listing all entries posted in Classified Ads.

Posted Classified Entry from Special Blog Created for the plugin component

– Tested posting from the special blog to see if it appears in the BP-installed site. It Does.

Also, when you post the listing from the special blog, the tags show up in the Classified Directory Page and in single Classified Ad Entry page

Other Notes:

1. Classified Ad Entries do not appear in Activity Streams of Member nor Home Page

2. Site Admin should delete Hello World first post in new private blog set up for classifieds – if not configured to delete before

3, Created Blog for Classifieds plugin Settings > Privacy was set to Block Google but allow online visitors – but the special blog is showing up in Blogs Directory even when Site Admin is logged out.

4. Single page for a Classified Ad Entry – does not have navigation back to list of classifieds or have a “Reply” field box for possible interested clients.

5. Categories chosen and Tags added during set up of Classified Ad Entry, are not showing up anywhere in Classified Directory Page or single page of the Classified Entry.

6. Feature Request: ability to upload even a small single 150×150 image to go along with the classified ad entry.

Great job, Grosbouff. Thank you for continuing development on this component. Really Cool.

This may have been a bug in 1.1, but it’s definitely fixed in trunk/1.2.

Without knowing these answers https://buddypress.org/forums/topic/when-asking-for-support, we can but only make wild guesses.

Raise a ticket. This is a usability/privacy issue. It should be blatantly obvious to the user who is replying to a private message that they are sending to more than the sender.

Wonder if you could use this to create extra forums like a Miscellaneous or a General forum? I want to use the default install because I like the way it all integrated with the group forums, but I wanted to have some general forums for random stuff that I really don’t want to have to force people to sign up to that group just to post there. Right now, having to skin and deal with external bbpress installation seems more of a hassle than dealing with the random forum for me.

Using trunk + single wp; I’m set up on an external installs of bbPress + BuddyPress/internal install for groups

I use the bpGroups plugins (“forums” subdomain of the BP site) but the plug-in required some updating to get everything working smooth (activity notifications, public/private/hidden/ready only stuff)

Obviously this method won’t enable plugins on the buddypress/internal groups but this allows me to provide an advanced forum interface while creating outside forums (support, help, testing, etc) not associated with groups (group forums can be added to a specific forum category – i think default is “1”).

… i have re-theme’d bbPress to somewhat match the new default BP theme (well somewhat)

(screenshots:

http://files.etiviti.com/misc/bbpress-vwg-main.gif

http://files.etiviti.com/misc/bbpress-vwg-forum.gif

)

Works for me. You obviously have to be a member of the private group to see updates, and you only see them listed on the activity section of the Group page (not the list on the homepage of the site).

My guess is you are not quite understanding the way private messaging was intended to work. As the name implies, it is a private message. When you send a “private” message to 40 friends, it’s not quite “private” anymore, by some definitions. The same occurs in email when one of your 40 recipients hits “reply all” assuming they were not bcc’d.

As such, when you send a bp message to 40 people, you are, in a sense, establishing a 40 person thread. That’s the way it’s supposed to work (which is great for smaller numbers) In other words, expect 40 replies to the thread and all 40 will get 40 messages. Seems ripe for trouble when you send it to 40! (btw, I am impressed you were able to have the patience to pull off 40 as you had to remember and type 40 names or usernames since this is the only way to do it in BP at the moment.

Second, if you send a message that, upon reply, many members will deem the response as “spam” consider not starting the thread. Just remember, BP messaging was not meant to be like email.

They do.

getting someones attention by using “Private Message” and “Public Message” including sending a notification by e-mail is perfect.

But why do we need the letter “@” in order to get someones attention ?

If you want to hire someone to implement a captcha on the compose message page, please post in this group -> https://buddypress.org/groups/buddypress-job-board

I guess Jeffs Privacy-Plugin would help:

http://jeffsayre.com/2009/12/05/buddypress-privacy-component-released/

Too bad this plugin will not make it into BP 1.2 core !

@davidlewis

Funny you say that, because I’ve had two totally unrelated client sites that said the exact opposite. They were confused about the private message setup, and when they saw the persons name prepoulated as a link, they clicked that link to that person every time, went to their profile again, assumed private messages didn’t work, and complained. Strange how the world works eh?

Because Twitter has owned the @reply idea, if ours doesn’t work similar, it probably won’t work at all. Same with hashtags. All a hashtag is, is a tag to search through streams by. It’s like tagging activity, which can be done via a plugin now that there’s activity meta.

Right now the only place and the only time the @name works, is when you’re updating your status to directly mention specific users. That kind of makes it a technology that won’t get used too often. There is also only 1 place to automatically populate that users @name in the update box, and that’s when you’re viewing their profile already. Twitter makes the activity stream the central source for all things activity, including @ing people back and forth. Maybe if user names in the activity_content were all given a specific class we could use some jQuery to turn that class into a link that auto-populates the update box instead of making it a link to their profile? That would help fully endorse the @name idea in multiple places, rather than just 1.