Hi
I’ve got a client that is after a community website that has the ability to buy and download a members contact details.
So Buddypress is the obvious answer to run the community with the great member profile options, but does anyone have a clue of how I could integrate a “Shopping cart” for the members contact details.
Here is the working for what my client needs:
Member1 signs up and fills in all the fields of their profile. This includes the contact details that are hidden from general view (this I can do)
Member2 finds Member1’s profile and wants to get in touch with them. They click the button on Member1’s profile “add to cart”. This adds to the contact details to the cart. Member2 then searches and adds more contact details from other members to the cart. They then checkout using PayPal and the contact details that Member2 has requested are emailed to them.
I’ve looked at http://www.mals-e.com and know that it uses code to create the add to cart buttons on the page, could I call hidden fields out from the profile using this??
I know this sounds like the impossible but has anyone got any ideas or know of a plugin that could be adapted to fit?
Cheers
@larrysmith1000, @Arwym, @FitzUCF, @janismo, @hnla
I don’t know if anyone is still looking at this, but I think it is a topic that is worth pursuing. What seems to be getting lost though is what it takes to do the job.
A facility like Justin Tadlock’s members plugin is a big help. It provides a mechanism to define and edit roles and apply them to users. That covers a lot of territory. However, unless the content management part of the software looks for and enforces those roles, it is meaningless. Justin provides a facility to do that if what you are talking about posts/pages and potentially custom post types. That is fine for WP content or even things like BuddyPress Docs where Boone implemented it as a custom content type (although I haven’t look at the details of his implementation relative to permissions). However, BP adds additional content types. And it is not just FORUMS. Groups are a content type. Private messaging is a content type. etc.
That is where the current_user_can() checks make sense. Users should have permission to perform actions. That doesn’t necessarily mean new roles, but it does mean distinct capabilities. Those capabilities can then be assigned to any role that makes sense. But the capability list needs to be published like it is for WP https://codex.wordpress.org/Roles_and_Capabilities
The mechanism for assigning capabilities to roles and roles to users and doing the actual check is all WP. It’s already there. Justin provides UI to access it. What I am seeing missing in BP is published string literals that have meaning in terms of capability sets and I assume the current_user_can() checks that actually make it happen. (I looked for it on Google and this is where I was directed!)
@DJPaul you talked here in terms of BP1.3, which is now 1.5 I believe. Did any of this actually make it into the code? If not, it sure would make sense to me to find it’s way on to a revised RoadMap.
My 2 cents!
As for BuddyPress, delete spammers and spams with links leading to viagra, etc. Re SEO plugins and sitemaps, these are supposed to help with Google ranking not the other way around. Site URL?
https://codex.buddypress.org/home/
Currently setting up and updating docs for BP 1.5 – feel free to list down specific information you need here and/or even submit articles as well.
I was posting on a StudioPress forum about their efforts to upgrade their Genesis Connect plugin for compatibility with v1.5 and asked about the recommended install process (uninstall/re-install). The answer in part was:
“There are BP 1.2.9 functions calls in GC 1.0.7 that are not in the BP 1.5 beta-2. If you leave GC 1.0.7 active and upgrade BP, you end up with call to undefined function errors both in the front end and in the admin area of your site.”
BP 1.5 seems like a major move and, from what I’ve seen as I begin to look at it, a very beneficial move. However, it also seems, from the discussion in this forum, to be a move with big impact in terms of plugins. I’m new here, but on that basis I have a question:
Would it have been possible or make sense to ease the transition in some cases by providing some adapter functions that would translate old replaced functions with re-directions to their new counterparts? The old functions could then be identified as deprecated and removed at a later date, but in the immediate horizon some plugin modules might continue to work rather than needing to be modified or abandoned? Simply dropping stuff without fair warning seems drastic.
It might not be possible in all cases, but it might help with the transition. I know a lot of people want to move forward to the new v1.5 and this type of code strategy might help.
Just a thought.
BTW – I’m beginning to play with beta 5029 and it looks fantastic! Great job … you guys did a lot of good work!
Thanks a lot. In our case each site on the network will be using buddypress, but they won’t be sharing posts / comments between them. Also, all of these sites are sharing a single child theme. I suppose I could add a condition to the function to whitelist only the current site id, preventing updates streaming in from any of the other sites. Will give it a shot.
Hi, Can BuddyPress do this? in an ecommerce set up with domain.com, domain.com/site1, domain.com/site2, domain.com/site3 etc., how do I set it up so that domain.com subscribers or buddypress peeps need to be approved individually by domain.com/site1, domain.com/site2, domain.com/site3 etc. before they can get access to custom posts which are wholesale ecommerce prices?
Is there a plugin, role, permission that I need to use?
Suggestions appreciated!!!
Hello,
We would like the buddypress options to appear on the site admin page of each site on our network, instead of on the network admin page. One of the main reasons we need this is because some of the sites on the network are in non-english languages. The ability to define specific titles and slugs for each bp component page per site is thus necessary.
I would try activating the buddypress plugin per site, but it appears that the plugin can only be network-activated. (doesn’t appear on site admin / plugins ).
Is it possible to display the bp options per site? Using WP 3.2.1 and latest BP 1.5b2.
Thanks,
Thanks 4ella. I think this is a common sense extension of BuddyPress, so I’m looking at sponsoring a plugin for the community. If I do, any advice on how let the community know in addition to putting it on WordPress?
It *should* change it. That setting’s implementation in 1.2.9 had a few issues, so I spent a bunch of time in 1.5 making it better, but that doesn’t help you. When it’s set, you are trying to pick a user from the member directory rather than copy/paste the same URL, right?
Is there any user documentation for BuddyPress? I’m thinking of things like an overview of how groups and forums work. I’m going to have to write something for a site I’m developing, and it would be good to be able to point the users to something else, and explain the peculiarities of the site in question, rather than reinvent the wheel entirely.
How can I add custom fields to Groups in BuddyPress?
I’ve search all available plugins for a way to add custom fields to Groups. The BuddyPress Group Extras plugin lets my group administrators add their own extra fields, but there is nothing that just makes it easy for me to add custom fields as an Admin.
A code snippet that creates a custom field is welcome. A plugin is desired. I’d be happy to put money towards it.
I’m using BuddyPress, a child theme of bp-default and s2Member (which rocks).
Why is it when I click on ‘my topics’ – or on anything in the ‘hot tags’ – I get a 404
And the two rss feed links also give errors?
Hi
I have a website running on WP and using the BP plugin and I have created a form to collect data using xmlrpc.php to post to WP as a blog so that I can in turn use <?php query_posts to pick up the posted inforamtion. I have everything in place and the query_posts is working as it should (having tested it with manually entered posts, but the SUBMIT on the post from BP requires the password included in the post. I would have thought that as the user has already logged into BP (same login details as WP) they shoudn't have to authenticate twice. Would you have any idea if there is an easy way of doing this or has someone a working method of posting the user details?
regards
dónal
I have a lot of spam signups. I was using bp-registration-options but now I’ve upgraded to WP1.5 it’s broken. However I have, at Boone’s advice, changed the name of the bp register page to ‘welcome’ and that seems to be working. The other problem is that I still get bogus signups via wp-login and I can’t find any good way to stop them – I tried SABRE but that is broken too. Right now I have “Disable BuddyPress to WordPress profile syncing?” set to no, and “New User Default Role” set to blocked.
Any further suggestions?
Hey Paul,
Yeah that was my very first port of call a couple of days ago. It didn’t seem to do the trick 
It’s got me stumped. It’s the last bug left for phase 1 of the project and it’s got me stumped!
Did you try setting the name compatibility constant as per that codex page you linked to in your post?
Thanks @modemlooper. I had been considering having to do an option like that. I’ll give that one a whirl tomorrow and see how I go.
Hey @djpaul, yeah they all have spaces in them. All the existing users come in with spaces in their name in a First Name, Last Name kind of way. I tried changing the ‘Nickname’ and ‘Display Name publicly as’ fields in my own profile to see what would happen yesterday and that obviously doesn’t have anything to do with it as you can see here: http://edgeqld.org.au/members/Bronson%20Quick/
I know the site was originally WordPress MU then it went to WP 3.0 then up to WP 3.2 and installed the BP theme and plugins on top of that. I didn’t have any existing users on my staging site so didn’t hit this problem til we went live….now I’m cowboy coding fixing bugs and I’m completely stuck with this one!
do the “broken” user names all have spaces in them? (in general)
Okay, all of my pages like this are also not being found. All of my logged-in admin dashboard stuff works ideally…then when I go to the actual site, the links all go to a “ERROR 404 – PAGE NOT FOUND”
I am hosted on hostgator, and I am not sure I created the blog.dir correctly when I went multi-site.
Thanks anyone who can help!
