BuddyPress.org

oEmbed for BP does one thing very simple – it utilizes WordPress’ own oEmbed class — type in a plain-text oEmbeddable URL and voila! — there are no plans to do anything special in the future (like categorization, etc).

I wholeheartedly endorse MrMaz’s BP Links plugin; I have stated this in other posts and I”ll say it again – BP-Links will be the definitive rich embedding plugin for BP.

We have briefly talked privately about manipulating the activity stream for embedding content (btw MrMaz, let me know if you need a sounding board for the next version of BP-Links!).

He has some neat things planned including plugging into the “What’s New” box, which will solve the “quick and easy embedding” issue Mike has talked about above.

At the end of the day, the cool thing is you have choices!

it all depends on your BP network’s needs.

Are you running the backwards compatibility plugin?

I’ve installed Cimy User Extra Fields plugin. Pluses and minuses.

yep – please!!!

I don’t know why that should be so hard. Isn’t it exactly the function we already have with private messaging? There it works? Couldn’t it be possible to adapt that functionality as soon as someone types @ with anything in front of it (like an Emailadress)?

+1 for that!

Well, crap!

I thought I might be able to fade away in my cave, living a private life. But I can see that some of you actually want privacy features in BuddyPress. I guess I will have to get to work.

So, if I vote a -7 will that cancel everyone’s votes out?

If the blog is set to private (not visible to search engines) then it won’t show in activity streams.

Take a look at the BP MPO ACTIVITY FILTER plugin. Just be aware that if you’re logged in as Site Admin you’ll see ALL private posts in the activity stream which may lead you to believe it’s not working. Log out and the posts should not be visible. I am getting the following in my error log with this plugin activated (on wpmu 2.9.1/bp 1.2): “WordPress database error Table doesn’t exist for query”

http://teleogistic.net/code/buddypress/bp-mpo-activity-filter/

Public. Set it to private and then to public again.

@disbas – Can you confirm that the blog in question is public or private?

That reminds me… my guess is that people spend 99% of their time on this site in the forums and as a result (since we rarely view profiles)… we don’t know where we’re all from. I was talking to Andrea_r last week by private message and it was only then that I realized that she’s also an Atlantic Canadian… living in just the next province over!!!!!!!! Ha! Which got me to thinking… location should be part of the forum avatar… right under name.

I might be less busy in a month or so. Feel free to drop me a private message with details and I’ll let you know if/when I’m likely to be able to do anything.

Don’t think anyone’s really gonna develop until 1.2 is out, you could wait or try sending the more populair developers a private message (brajesh, mr maz, etc).

please post this as an enhancement-ticket in trac:

https://trac.buddypress.org/timeline

“- What is the best way to populate a ‘live’ (on a public server) site, view/test it online, but keep it hidden/private for non-admins (to prevent copycats, leaking, Google indexing etc)? The ‘privacy settings do no offer this choice? do I need a plugin for that?”

The simply brilliant way: edit your computer’s hosts file.

Slap MU up wherever, even on an IP address, but change your own host file to show the old domain at the new location. Proceed as usual. You & your computer is the only person to see the site “live”.

(oo bad construct there – computers aren’t people. yet.)

You won’t need any google-fu or the more privacy plugin. When the time comes, all you need to do is remove your own hosts file edit, update the DNS to the new server, and wait.

“- Which way to Chenge the Site url is working best (see https://codex.wordpress.org/Changing_The_Site_URL ), are the 2 ‘defines’ enough currently?”

in MU? Oh heck no. Nowhere near enough. The url is saved in a multitude of places. That’s why I suggested the hosts file way.

Yes, you have to keep editing it to go back to the live site, but it’s way less painful.

You will have to license your work under some version of the GPL that at minimum offers the freedoms that the WP GPL offers.

What others have said above is basically correct. The GPL does not say anything about free as in cost. It is about freedoms of the end user. In fact, the GPL does not discourage developers or theme designers from making money off of their work or someone else’s work.

However, the GPL is very specific in how this is to be done: either by charging a distribution fee, a support fee, or both. So, in effect, you are not charging for the code itself. The vast majority of Premium plugin shops simply charge a distribution and support fee. If their plugins are not GPLed, then something is wrong.

Here are two great links from the GNU website that explain this very clearly:

Selling Free Software

The Free Software Definition

By the way, IMO there should not be a double standard in the WordPress community. Premium theme designers abound. Premium plugin developers should also be afforded the same respect and opportunity. The crucial point is that their work, like premium themes, must remain licensed under the GPL.

Of course, as Matt Mullenweg has stated on numerous occasions when discussing the issue of premium themes, although the PHP must be GPLed, the CSS and JS of the theme can be copyrighted. The same holds true with plugins. But, in my opinion, doing so is just too picky. I prefer to GPL everything–the PHP, CSS, JS, etc.

Now, you could choose to license your work under the AGPL, which is considered to offer more freedoms to the community. The basic difference from the GPL is that any changes made to your plugin, even if for private use, must be returned back to the community. Under GPLv1 through GPLv3, it is acceptable for any code changes to a plugin to remain private if the plugin is never distributed.

One final thought. I’ve stated this before in other places. Many people in the WordPress community seem to be moving beyond the spirit of the GPL, to a more utopian, share and share alike vision. There’s nothing wrong with that if it happens. But the GPL has never been about free as in cost.

There are two ways of thinking about that, Erich. On one hand, insofar as the problem is mainly caused by a third-party plugin, there’s no real reason for it to be in the core. On the other hand, the core code is a little funny in that it doesn’t record private blog activity at all – IMO it’s better to record the activity and filter it out according to user roles. So something like what this plugin does might be appropriate for the core, but only the cases where privacy equals 0 or 1.