[danf-1]

Travel-junkie – I would be very interested in this type of functionality.

Are you planning to do a plugin to accomplish this? Or would it just be part of your theme? If a plugin, any plans of sharing it?

Even if part of your theme, if you could share which hooks you used to accomplish this would be helpful.

Thanks

[danf-1]

although not an actual plugin, amember can integrate with the front end of buddypress and wpmu. So I don’t think it should be so easily discarded. If you explored it more I think you would be impressed at how well it can integrate and provide a much more stable and feature rich membership package.

But agreed, if it has to be a wpmu plugin then it won’t work for you.

Ps- I don’t work work for amember

[danf-1]

You can use amember.com (costs $170) – they have a wpmu plugin to handle single signon and handles recurring payments very well.

[danf-1]

I too would be interested in doing this.

[danf-1]

Yep – I will ask on wpmu as well.

But what about the buddybar question? I’ve read about how people implemented it in bbpress – but that still is in the same wordpress environment.

What about getting the buddybar on an application external to wpmu?

Can I set up a page template for a page that just spits out the buddybar html – then include that on my external subdomain either as a php include or as an iframe??

[danf-1]

I’ve had this concern as well. I hope to one day get to the point where this becomes an issue

For those that are concerned about the database structure but still want wpmu, there is an effort called lyceum at http://lyceum.ibiblio.org/ that modifies the wpmu codebase to use single tables instead of creating new tables for blogs.

One of the main drawbacks is that plugins that create their own tables need to be modified a bit to support this structure. This would include BP, for sure.

I still don’t have a good sense of how many people are actually using it as it doesn’t seem to have a very active community.

I’d be interested to see if bp could run on top of it and which is more scalable.

[danf-1]

unfortunately my site is just an internal install so not accessable online. But you can go to http://demo.shopplugin.net and see it in action. This is just a single wp install so not running on wpmu but it would be the same thing, just on two different blogs. You can even log into the backend as admin and see how to create everything

[danf-1]

I wanted to give an update here as I am continually impressed with this shopping cart (http://shopplugin.net/). I would recommend it to anyone needing a solution. (Im not the only one singing its praises: http://lbnuke.com/2008/12/30/wordpress-ecommerce-plugins-shopp-vs-wp-ecommerce/ )

Anyways, its now publicly available as a 1.0 release for $55 standalone, plus $25 for gateways ($300 for developer license – he doesn’t specify where wpmu falls on this)

So, with the latest 1.0 release, the developer behind shopp fixed the global database issue I had previously mentioned. I can now install it in a wordpressmu environment (with buddypress installed, too) and get it running on 2 different blogs, each with their own products/carts! It requires further testing to declare it production ready, but I could not find anything wrong with it from an hour of testing. The only issue I found was doing the automated upgrades causing an error in wpmu – so if/when upgrading the plugin, be sure to do it manually instead of through the automated process (but Im sure that will get fixed in future releases as well)

[danf-1]

I saw this problem before. It wasn’t a bp issue, it was an issue with a purchased theme from woothemes.com it was using an older version of jquery and not properly using wp_enque_script. Look at your outputted HTML and check what version of jquery is being used. I believe this function is in a newer version of jquery. Your problem may be your theme or other plugin referencing an older version

[danf-1]

FYI – you can test out shopp with admin access to test backend at demo.shopplugin.net – click on about link for login info

[danf-1]

I am looking at keeping the cart in the blog, but I could see using a shopping cart per group.

But where I really would like to see a shopping cart integration is for users to see their purchase history or subscription info as part of their bp account so they don’t have to go into wp dashboard to view that

[danf-1]

now that I look, I actually did have bp installed when I tested this and did not see any conflicts. But I did not test enough to be confident. Will try to test more next week

[danf-1]

I am currently a beta-tester for shopplugin.net. I think this is going to be a great solution. I’ve done some preliminary testing with it on wpmu(no testing with bp) and it worked for the most part, except it installed db tables as global instead of using blog prefix. But that should be an easy fix. I would highly recommend looking at it as I believe it to be well written software and have been impressed with the developer behind it (I have no relation to him). One thing though, it’s not free- it costs about $55

[danf-1]

I confirmed via javascript debugger that indeed the javascript ‘show_options’ function is not defined. This function is in the bp-xprofile/js/admin.js file used to create the drop down options for new fields.

So I had to add the following to the bp-xprofile/bp-xprofile-cssjs.php file in order for it to work. This may not be where it is suppose to go, but it works for me. I assuming this worked at some point, but somehow got removed???? Hopefully this gets added back in for next trunk. Its not in r577.

function xprofile_add_admin_js() {

if ( strpos( $_GET, ‘xprofile’ ) !== false ) {

echo ‘<script type=”text/javascript” src=”‘ . site_url() . ‘/wp-content/mu-plugins/bp-xprofile/js/admin.js”></script>’;

}

}

add_action( ‘admin_head’, ‘xprofile_add_admin_js’ );

[danf-1]

DanielFelice – double check where your member-themes folder is. It should not be in the themes folder but in the wp-content folder at same directory level as the themes and plugin folders. You get the blank drop down when member-themes not in right place.