Forum Replies Created
-
As @sheffieldlad suggests, wp-fb-autoconnect delivers a good off the shelf solution, and provides some integration with BuddyPress profile fields
[ note: wp-fb-autoconnect is a facebook only solution, and everything is installed / controlled on your site; Pro version is a one off payment. Loginradius is a SaaS solution, with monthly payment plans to enable full features, remove labelling, etc. If you want a full SaaS solution, you should also look at Janrain, Gigya and Oneall. ]
Use the function I provided – there’s no need to try and construct the URL yourself (as Toby has tried).
It’s a dynamic URL — i.e. it changes for each user, so you can’t just type in a single link in html.
It’s easy to do with a bit of PHP code though — just call the function bp_loggedin_user_domain()
Yes, BuddyPress (in particular the profiles and messaging) would be a suitable base for your site.
If you need to get development help – you can advertise on the Jobs Board: https://buddypress.org/community/groups/bp-jobs-board/forum/
bp_is_user()
@djpaul – great… let me know how that pans out
@djpaul, @hnla, @r-a-y, @mercime et al,
I’ll move the conversation back over on to the trac ticket, as I think that’s the best place for this discussion to stop it becoming lost.
As @hnla points out bbPress whilst supporting template parts auto injected into page.php, also allows you to provide full templates for specific content where you want to override the automatic mechanism (TBC). As with the WordPress template hierarchy it’s based on the type and name of the content being displayed. So, for example — you could create a template archive-myforumxyz.php.
I suspect a similar hierarchy based system for BuddyPress would be best route — with template hierarchy names that recognise display of single groups, single profiles, directories, etc., and override the auto injection into page.php if defined.
Will elaborate my thoughts on the trac.
Cheers for the feedback guys.
The problem with plugin-buddypress.php will come on sites where we have a number of different layouts / irregular layouts depending on which component the site is displaying. It works OK for a small number of conditional includes, but would become cumbersome with many conditionals (as @hnla alludes to), and effectively become another layer of [edit] page routing [/edit] (as @r-a-y rightly points out we want to avoid).
I’ll take a look at the bp_get_query_template filter – but, guess that would just be pushing the same additional logic to a different area of code.
@neekolaus – you can build a directory site with reviews on top of BuddyPress.
http://plazaa.de (built by Poolie) and http://enterprisenation.com (our own work) are good examples built on BuddyPress.
You would use WordPress custom post types to model the studios, with BuddyPress handling the user accounts. The custom posts types can be integrated with BuddyPress based profiles giving you a seamless experience. For ratings / reviews, GD star rating is one of the more complete plugin solutions.
Unfortunately, it’s not something you could tackle with basic web development skills – it would require fairly advanced PHP, WordPress, BuddyPress knowledge. We’ve built a number of bespoke directory type sites, but I don’t know of anyone providing a good ‘off the shelf’ solution (yet!!).
@aphrodite – if you think they are violating / misrepresenting trademarks – you are probably best to contact Automattic directly http://automattic.com/contact/
@andrewgtibbets — try the function I’ve suggested in the thread: bp_member_profile_data()
sounds like you have something in your theme’s function.php (or perhaps a plugin) that’s using a groups function without checking whether it exists.
Try renaming the folder for your theme, and if that doesn’t work, check through your plugins folder for an obvious suspect and rename.
What function is stop()?
If you want to end the PHP execution try die() instead.
Are you sure you have your hook setup correctly, and that you are definitely calling the delete account code?
the bp_core_delete_account() function calls on to wp_delete_user() and should in all certains call the delete_user action.
Is the user getting deleted, i.e. can you confirm the delete routines are getting called correctly. Are you deleting from wp-admin and confirming the deletion?
If it’s just first and last names for your drop down – you can fetch those from the default WordPress fields / calls.
Is ‘role’ stored as an xprofile field or are you mapping across to WordPress roles? If the latter, you should also be able to achieve with the built-in WP functions.
@hnla – the problem we looked at yesterday – I noticed the domain name. If you check the trac ticket it’s because the image isn’t publicy accessible (as we’d suspected).
Look at the WordPress functions
Is_user_logged_in and get_currentuserinfoit’s custom code.
Advertise on the jobs board on this site if you need a similar system building: https://buddypress.org/community/groups/bp-jobs-board/
Yes, you can do this, but you need to write PHP code.
Have a look at some of the actions that are invoked when profile fields are saved, and hook on to those. It’s a little complicated because you aren’t told which fields have changed (just field groups), so you’ll probably also have to maintain previous value and compare to latest.
You could code this, but it would require strong dev skills. It’s not supported by the built in bp_has_members() search parameter.
[Edit: the solution would probably involve a search on wp_users first (perhaps with a custom sql statement) to get a list of the member IDs for the selected letter, and then passing that list of IDs to bp_has_members()]
You need to look at global.js
If you look for the calls to bp_filter_request you can find the sections where all screen filter requests are handled
If you copy / edit global.js into your own theme, make sure you don’t enqueue the bp-default file as well
@karmatosed – dynamic menu links is a generic WP issue, not something specific to BP
which is the second time you’ve created a duplicate of this same question:
Are you posting from front end or wp-admin?
Any idea why the plugin is creating its own user_meta and options tables, and not using the standard WordPress tables for this?