[Mark]

OpenX isn’t exactly novice friendly – but it is powerful. Not sure about Google’s Adserver.

[Mark]

I’d be willing the write the code for about 3/4 of that amount Seriously.

[Mark]

Probably can be done via a small custom plugin that removes the relevant hook. I didn’t check into, but I recall doing something similar in the past.

[Mark]

All of it is possible. Most of it is done via custom theme code, but some might need some plugin code.

[Mark]

Looks like Javascript problems. I’d be checking the CSS id’s and class names (in the theme HTML code) to make sure they are what they should be in order to work with BP.

[Mark]

My advice is to forget about chat tools for BP until the next round of major Web browser releases. That means Firefox 3.7 and IE 9, not sure about Chrome and Safari and Opera. Reason being, there are MAJOR changes coming with HTML 5 and some of those changes will make chat tools far more powerful (if developers take advantage of the new capabilities). So basically, if you spend a lot of time on getting chat working today, in six months you might want to toss it all in favor of newer more robust tools.

But that’s just my perspective.

[Mark]

Instead of making a lang file you could hook into nav item creation, then alter the group items to be labeled how you want. That’s what I do in some instances

[Mark]

@twodeuces: I modified your plugin code so that it depends only on BP, not WPMU. And I also made it so that it doesn’t matter if the site is single blog or multiblog.

PM me your email addy and I’ll send it to you.

[Mark]

Is this software based on true Comet technology or is it simply using the same name without actually using the actual Comet technology?

I ask because true Comet technology requires a server-side listener service, which isn’t possible with 99% of all hosting companies out there.

[Mark]

Interesting:

http://socialriver.org

[Mark]

Actually it’s been happening for at least 2 days that I know of.

[Mark]

The first mistake they’re making is building it from the ground up.

The second mistake they’re making is writing the code in Ruby.

[Mark]

How about enabling activity streams and then editing the theme files so that it doesn’t display stuff you don’t want to see?

[Mark]

Possibly due to browser page caching? Force a page refresh. In IE hold CTRL and click the reload button. In Firefox hold SHIFT and click the reload button.

Browser cache is a site operator’s nightmare. Disable it even if that turns out not to be the problem in this case, because it will be in other cases.

[Mark]

The easiest way is to view the patch at the link you posted, then look for the green lines and edit the relevant file to add what is different from the red lines. Then modify your template to take advantage of the new “order” parameter.

That’s safer and more direct than trying to use the ‘patch’ command line tool, unless you’re familiar with that and have it on a system somewhere. Or, you can do a Google search on using ‘patch’ and try it that way.

[Mark]

Nobody is forcing you to do anything

* For clarity’s sake – everyone is completely free to learn to write PHP code and work with the WP / BP code. All it takes is a little time and focus.

* If it were for sale their would be a fixed price… but there is no fixed price, because it’s not for sale. Read the GPL license for clarity.

* I find it interesting that some people (not indicating you @hnla) will trot right over to Starbucks or some other coffee shop one or more times a day and dump $5 to $7 on a cup of caffeine, but they won’t drop a dime on software that furthers their own special interests.

[Mark]

@Puanthanh – On your theme demo site you have a post titled “Duis eros est, mattis vel pulvinar id” – the image of that girl might be offensive to some of the ladies that might happen to see it

[Mark]

Here’s a plugin that does exactly that:

http://simplercomputing.net/2010/04/19/buddypress-remove-friendship-notices/

[Mark]

Here’s something much less robust than what Jeff is creating. This one lets users control privacy settings of their profile information, and admins have no overriding control. Sort of like Facebook does, and privacy settings appear when someone signs up, plus when they edit their profile data. You might have to adjust or add CSS to work with your particular theme. Works with the latest version of BP:

http://simplercomputing.net/2010/03/18/simple-buddypress-profile-privacy/

[Mark]

@techguy – you might want to get a beta copy of WP 3.0 and work with that instead on this tweak – reason being that WPMU code is merging with WP code starting with WP 3.0

[Mark]

What version of PHP are you using on the site?

[Mark]

I’m really enjoying the reduced functionality, increased navigation clicks, and general inability to quickly review the newest forum posts. Awesome

[Mark]

@MrMaz:

e_loader.toggle() references a class called “ajax-loader” and that class is in fact used in various spots within the HTML. But, there’s no CSS tied to the class (v0.4.1), and I don’t see any code that would inject a message or image into that span. So it appears to me that something is missing, which would explain why simply toggling the span visible/non-visible via e_loader.toggle() doesn’t do anything on my test platform.

Or maybe I’m wrong? Does anyone else see some kind of message or image while the plugin fetches page information when posting a new link? It should appear right by the “URL” label above the input field.

[Mark]

ah – well in 0.4.1, on my test platform, it never appears.

[Mark]

Another suggestion: Add a “processing” icon that is temporarily displayed when fetching remote page data so people know that something is happening after they click the button to “fetch page details”.

An easy way to add that feature is to add a div to the default theme form (bp-links-default/single/forms/details.php) right under the nonce field, like so:

<?php wp_nonce_field( 'bp_links_save_link-auto-embed', '_wpnonce-link-auto-embed' ) ?>

<div id="waiting"> </div>

Then add some CSS for the div in the bp-links-default/_inc/css/forms.css file:

#waiting {

background: transparent url('../images/loading.gif') no-repeat scroll 0 0;

height: 33px;

width: 33px;

margin: 0 auto;

text-align:center;

display:none;

}

Next, drop a loading.gif image into the _inc/images folder. (here’s one as an example: http://www.minimelive.com/images/nav/processing5.gif — not sure whose site that is though)

And finally, modify the forms.js file to show and hide the div at the appropriate time. Somewhere around line 190 [ right before jQuery.post(ajaxurl… ] add this:

jQuery('#waiting').show();

And somewhere around line 240 [ after e_loader.toggle() ] hide the div:

jQuery('#waiting').hide();

That ought to do it