BuddyPress.org

??? isn’t is_site_admin in the bp-core-wpabstraction? I’ll check if it uses it before bp-init

I’m a bit offended at having some of my work in this “Hall of Shame”; a message or email to the plugin developers would have been more polite.

I’ll update my plugins as and when I get time; client work continues to take priority.

Not sure why ‘offended’, this matter cuts to the core of the issue of third party plugins causing potential damage to projects such as BP, I would have thought experienced plugin authors would have got this matter dealt with straightaway if as Andy says it’s a matter of 5 minutes work.

I understand the pressures of work and time constraints having, as I do, to work 7 days a week to hold a small web dev company together but comments like ‘I’ll update my plugins as and when I have time’ ?! is a comment like that really necessary?

OK, you can take me off the Shame List. I’ve just put new versions of Group Forum Subscription and Enhanced BuddyPress Widgets into the repo that use the loader method. HIGH FIVE FOR MYSELF!!

Hem…

Is it possible to have BP updating without wipping out the previous version .mo file from bp-languages ?

Or at least a warning message telling “bp was succesfully updated, but thi erased your language file. You can upload a new language file at https://i18n.trac.buddypress.org/browser

It is a bit annoying for us foreigners, to suddenly have all in english after each BP update.

Ihttps://i18n.trac.buddypress.org/browser

I know, this should be on trac under Future enhancement, but not only 3rd party plugins authors need to be remembered to correct their work.

BuddyPress External Group Blogs

DOES NOT WORK! It still pulls in the same blog posts over and over again.

haha fair enough Sorry, just want to use that plugin. *removing match from your ass*

“Remove The Stone of Shame… and attach The Stone of Triumph!”

Most of all, I would like to see:

– BuddyPress Album+

– Welcome Pack

…in the “good plugins” list. Many of the other BP-crashing plugins don’t even work Now which is better: not working at all in BP 1.2.x or BP crashing in 1.2.x? I say: not working at all may be better for BuddyPress reception – because it is clear that the problem is a plugin problem and not BuddyPress.

The first time I got a “white-out” I was frustrated with BP, didn’t immediately think of the plugin developers.

My offer to bring this a step further: for “Welcome Pack” and “BuddyPress Album+” – based on an hourly rate of $60 and the 5 minutes needed to correct the plugin, I will donate $5 via PayPal each if they get corrected by the end of the month (2 or 3 days). Even though I have already updated to BP 1.2.3 by deactivating those plugins temporarily.

You know maybe the problem is us lowly users. If we didn’t depend on plug in developers so much to keep their projects functioning then it wouldn’t be an issue.

I never saw this as an issue with Single user WP plug ins so this is all new to me.

What I don’t understand is, I always assumed that plug in developers had other services that were paid services and creating plug ins was a way to not only contribute to the platform, but to show their expertise and make their names known in the community.

If a plug in goes unfixed and crashes a users or a company’s website, and support for it goes unanswered..how does that help you as a professional ?

And when you do release a premium paid plug in in the future, why would I take a chance that you won’t go missing in action again when it comes to support?

And why would I contribute to a plugin that doesn’t work and hasn’t been updated or answered support questions since late 2009?

Unfortunately some of what could have been/would have been some of the most used plug ins are on that list with no sign of the original developer updating them.

So now, instead of contributing to that developer for their hard work, I have to hire someone else to make it function correctly or build me a new one.

That really sucks.

I’m with Magganpice. I’d be more than happy to make a contribution to Buddypress Registration Options and Ahjira Recent Sitewide Articles, if they would just update them so they actually work.

Hi guys.

Try to use the new way to check that BP is active.

But, I got this problem :

Before, I had :

function bp_maps_init() {

require( dirname( __FILE__ ) . ‘/bp-maps.php’ );

}

if ( defined( ‘BP_VERSION’ ) )

bp_maps_init();

else

add_action( ‘bp_init’, ‘bp_maps_init’ );

now, with

function bp_maps_init() {

require( dirname( __FILE__ ) . ‘/bp-maps.php’ );

}

add_action( ‘bp_init’, ‘bp_maps_init’ );

The plugin brokes. Seems the hooks aren’t fired as it should or something like this :

My file bp-maps.php loads a file called “bp-maps-members-map.php”.

In this file, several functions are hooked

add_action( ‘bp_before_directory_members_content’,’bp_maps_members_map_link’); // this one fires

add_action( ‘plugins_loaded’,’bp_maps_members_map_screen’); // this one not

the function bp_maps_members_map_screen isn’t fired…What’s the problem ?

Tnx.