[@anonymized-96400 Inactive 16 years, 1 month ago]

Alright, I updated the plugin to version 1.4. The only new addition is a date of birth check.

[@anonymized-96400 Inactive 16 years, 1 month ago]

Well, now that you brought it up, I kind of agree. It never occured to me that some users might be put off by the ‘Mismatch’ from the off, but I guess you can never be too carefull, when it comes to your users JS isn’t really my strength and the JS I did use is straight from WP core, but I’ll have a look anyways. MIght learn something along the way…

I think we need a built-in (wp-core) way to concatinate all scripts (and styles) added through wp_enqueue_script ( or wp_enqueue_style respectively). There are some plugins that do that, but none of em have ever worked 100% for me. I am pretty sure Drupal has a way of doing it. You are right, these requests keep building up…

[@anonymized-96400 Inactive 16 years, 1 month ago]

Cheers, hnla,

at the moment the plugin uses 2 js files (1 for the username availability and 1 for the password strength), which i’m not too happy with. Downside of this is that if both options are activated it means the inclusion of one more js file and one more http request, so I’ll look into changing that in the next version or so…

[@anonymized-96400 Inactive 16 years, 1 month ago]

No worries, Bowe Glad you like it!

Most social networks only accept users over the age of 13, so the next release will include a date of birth check. Should be online within a day or two…

[@anonymized-96400 Inactive 16 years, 1 month ago]

Just updated the plugin to v1.3.1 in the repository.

New in this release is the suggestion of a username, if the desired username is taken already and the support for usernames in the signup table used only on WP MS installs.

[@anonymized-96400 Inactive 16 years, 1 month ago]

You can only turn email notifications off via that settings page. Notifications in the admin bar are different. You’d have to code it into the above functions if you only want notifications on specific events.

[@anonymized-96400 Inactive 16 years, 1 month ago]

When you setup the globals of your plugin you can specify a notification function like so:
`function log_setup_globals()
{
global $bp;

// some stuff here

$bp->logbooks->format_notification_function = ‘log_format_notifications’;

// some more stuff here
}
add_action( ‘bp_setup_globals’, ‘log_setup_globals’ );`

This function might look something like this then:
`function log_format_notifications( $action, $item_id, $secondary_item_id, $total_items )
{
global $bp;

if( ‘new_dive’ == $action )
{
if ( (int)$total_items > 1 )
return apply_filters( ‘log_multiple_verifications_notification’, ‘loggedin_user->domain . ‘logbook/verifications/” title=”‘ . __( ‘Verifications’, ‘logs’ ) . ‘”>’ . sprintf( __(‘You have %d new logbook verifications’, ‘logs’ ), (int)$total_items ) . ‘‘, $total_items );
else
return apply_filters( ‘log_single_verification_notification’, ‘loggedin_user->domain . ‘logbook/verifications/” title=”‘ . __( ‘Verifications’, ‘logs’ ) . ‘”>’ . sprintf( __(‘You have %d new logbook verification’, ‘logs’ ), (int)$total_items ) . ‘‘, $total_items );
}

do_action( ‘log_format_notifications’, $action, $item_id, $secondary_item_id, $total_items );

return false;
}`

You can then remove these notifications with a function like this:
`function log_remove_screen_notifications()
{
global $bp;

bp_core_delete_notifications_for_user_by_type( $bp->loggedin_user->id, $bp->logbooks->name, ‘new_dive’ );
}
add_action( ‘log_verifications_screen’, ‘log_remove_screen_notifications’ );`

For this to work you have to place the do_action call to log_verifications_screen on the page that is linked in the notification.

To record a notification you call this function like so:
`bp_core_add_notification( $dive_id, $user_id, ‘logbooks’, ‘new_dive’ );`

I copied the above from a plugin I’m working on at the moment. Also, have a look at the skeleton component and the various BP functions.

Enjoy!

[@anonymized-96400 Inactive 16 years, 1 month ago]

Wrap the photo description variable in stripslashes().

[@anonymized-96400 Inactive 16 years, 1 month ago]

Am still working on another big release. Will go online within a few days. Then I have more time to spend on this plugin.

[@anonymized-96400 Inactive 16 years, 1 month ago]

The string doesn’t get escaped properly. It’s very easy easy to fix. Contact the plugin author to let him know.

[@anonymized-96400 Inactive 16 years, 2 months ago]

Just checked and it works just fine on my profile page.

[@anonymized-96400 Inactive 16 years, 2 months ago]

Yep, 1.3 does use wp pages, but that doesn’t mean that it will work with just any theme. All it does is tell WP to use a certain template file when a certain page is called. The markup is still BP template files.This also only works with root level pages like directories.

[@anonymized-96400 Inactive 16 years, 2 months ago]

Once again, GPL does not mean that something is for free. Programmers can charge for their work. Once the end-consumer has the code he or she can do whatever they want with the plugin, because the code is GPL. I would argue that you will get a an even better and healthier plugin environment with paid for add-ons in the mix. These programmers try to live from their work and it will be in their best interest to provide first-class support, whereas authors of free plugins might only fix bugs if they have the time to do it. One of the best examples for this is Gravity Forms. Excellent plugin, great support, fair price.

Just some food for thought…

[@anonymized-96400 Inactive 16 years, 2 months ago]

have a look at the single.php file of another theme. it’s all in there. your template seems kinda ancient. also, your question has nothing to do with buddypress, so there’s no reason not to activate it.

[@anonymized-96400 Inactive 16 years, 2 months ago]

well, you could check against usermeta for example:

`global $bp;
$meta = get_usermeta( $bp->displayed_user->id, ‘member_status’ );
if( $meta == ‘premium’ )
{
//do stuff, like showing a badge
}
else
{
//show something else or do nothing
}`

doing something like this in a loop will add a lot of database calls though. also in a loop you won’t be able to use $bp->displayed_user->id.

you could also check against profile field data.

[@anonymized-96400 Inactive 16 years, 2 months ago]

Ever thought about this plugin?
http://www.oiopublisher.com/

It’s something like USD50 and really easy to set up and skin. Comes as a WP plugin, so will work just as well with BP. As far as I remember all you need to do is include the call to the ads wherever you want them to show up.

Btw, I’m not affiliated with this plugin, just a user of it…

[@anonymized-96400 Inactive 16 years, 2 months ago]

MIght sound like a no-brainer, but have you declared the globals?
`global $wpdb, $bp;`

You also have FROM twice in your query.

Also, I don’t see why you’d need the inner join. All you need to do is this:
`$result = $wpdb->get_results( $wpdb->prepare( “SELECT group_id, meta_value FROM {$bp->groups->table_name_groupmeta} WHERE meta_value = ‘United States’ AND meta_key = ‘state’ GROUP BY meta_value” ) );`

Haven’t actually tried the above query, but should be alright.

[@anonymized-96400 Inactive 16 years, 2 months ago]

hmm, not sure if it is a proper plugin. all you need is to set up a ‘current location’ profile field and then geocode the location using the google maps api.

[@anonymized-96400 Inactive 16 years, 2 months ago]

I actually think that a (child-) theme should just be generic and not network specific. That should be the job of one or maybe even more plugins. If those plugins all use the normal BP default theme markup, you can use any kind of plugin to create exactly the kind of community you want with exactly the kind of look you want. A theme should stay away from adding functionality as far as possible. The only exception I can think of is a mobile theme.

[@anonymized-96400 Inactive 16 years, 2 months ago]

@rossagrant
All of that would be quite straightforward. Let me think bout how to do that…

@eisenwasser
My solution doesn’t have to deal with roles at all. Every member on the site is a potential employee (even a ceo gets fired occasionally . Some of your members can also be employers just by being a group admin. Just by changing the language file around, group moderators could be set up to be staff. The good thing is that you can swap out group admins and group mods, so a group could even be matched to an existing company if you wanted to do that. Every site member then obviously gets a profile, just like on a standard BP installation.

All it really took were a few custom loops that interact with the group extension API. Lot’s of code, but all quite straightforward. Loads of hooks and filters then make the plugin really extensible.

[@anonymized-96400 Inactive 16 years, 2 months ago]

@thekmen
fair enough, mate! Anything is only worth whatever someone is willing to pay for it. If that is below whatever I think it is worth, then I’m not gonna sell it and you’re not gonna buy it. If I don’t sell it, you don’t have anything to buy and we’re both fine in the end!!

I only develop software I will use myself.If you don’t buy it and nobody else will use it, I’m fine with that. I’ll happily depose of whatever i wrote if I don’t have any use fot it…

[@anonymized-96400 Inactive 16 years, 2 months ago]

It would be very easy. It almost is a standalone component already. If I chose option 2, JobBoardr would most likely get cheaper as well. The price for both components will probs be only 15-20 EUR more altogether. Just because of the extra time it would take to maintain 2 plugins instead of just 1.

Tell you what:
Within this week I’ll get it all sorted in my head. The week after that I’ll make the changes (stand-alone and customisation-wise). After that week I’ll send you the CV-plugin and we’ll get it to where we want it to be. You suggesting and me implementing. For a CV component there’s only so much you can get from your users. Once I declare the plugin stable, you send EUR 70 my way. This will get you a lifetime of upgrades for both plugins (CV and JobBoardr) for any of your sites (own or client). It won’t get any better, mate

[@anonymized-96400 Inactive 16 years, 2 months ago]

I’ve actually been thinking about what to do with the CV part of the component. I’ve basically got 3 choices right now.

1. Leave it as it is right now. CVs are part of the main component and can be deactivated, but do not work as a stand-alone plugin. Not a big fan of this.

2. Make the CV bits a stand-alone plugin. If JobBoardr is present, then integrate it. Downside of that option is, that you’d have to purchase 2 plugins instead of just 1 if you want the job bits as well.

3. Build a cheapish web service with an API that integrates with JobBoardr.

I quite like option 2 for better flexibility. Option 3 will only be viable if the CV component grows too big (which it might do…). To be honest, option 1 probably won’t last…

What do you think?

[@anonymized-96400 Inactive 16 years, 2 months ago]

The jobboard component is group specific. That means that each group has it’s own jobboard and group admins can only admin their own jobboard. Jobboard creation, as of now, can’t be interfered with. Making a jobboard opt-in and then giving certain users/admins/groups the rights to create a jobboard should be quite trivial though. That’s actually a really good idea and I’ll add that to version 1.1. That’d be really usefull for sites that are not only a jobboard.

Posting jobs on a group jobboard is limited to only the group admins. You could easily extend that to group mods as well, but anything else doesn’t really make any sense.Every user can apply to any job, though, obviously.

[@anonymized-96400 Inactive 16 years, 2 months ago]

Just checked on my test install and it seems that right now only uploaded avatars get displayed. Shouldn’t be too hard to include gravatars as well. I’ll upload the trunk version onto the test site within the next couple of days.

The work for the customisable CV fields is actually done already, just for a different plugin I’ve been working on. All I need to do is adjust it for the CV component. It’s not a lot of work, but right now I’m tied up in another project. Might be another couple weeks for a stable release…