[@anointed Participant 17 years ago]

@peterverkooijen –The supporter plugin is more than that. Basically what it does is simple. It allows you to select which plugins are available to supporters only. Meaning you can have plugins activated that everyone can use, and also have ‘premium’ plugins for your paying members. It even puts a nice little ‘info’ box in the plugins directory page that says ‘for supporters only’ so the people can see the value to ‘joining’.

[@anointed Participant 17 years, 1 month ago]

Do anyone know if the issue of installing buddypress into a blog with id other than #1 works yet?

I was running the older vs. and when I tried setting blog id#30 it never worked right so I wiped the system and started over. Simply waiting until a vs. of bp works in subdomain blog other than 1

If it does are there new instructions for getting it to work in blog other than 1?

[@anointed Participant 17 years, 1 month ago]

@David – you aren’t kidding about theming elgg…. major pain is putting it nicely. Frankly the theme engine is lightyears ahead of wp, if and only if you are a master at oop, php, css etc… There are serious advantages to having the ability to style each object independently but it comes with an obvious price.

@Jeff – Well if it’s not obvious already, I’m definitely interested in your full-scale RBAC as I am sure many others would be once they understand the power behind it. Simply pm me anytime you need someone to ‘tear it apart’ during beta LOL…. I’m a master at breaking things.

Between this plugin and Justin Tadlocks roll manager plugin that he just released my wpmu world is looking like it has a very bright future ahead.

[@anointed Participant 17 years, 1 month ago]

@David –

Quote:

Personally, I still prefer BuddyPress. The theming process in Elgg caused me great pain and I find the Elgg interface suffers from inconsistencies and poor usability.

I couldn’t agree more with you on the theming issues. Elgg is more like drupal, anything is possible, but the learning curve is beyond steep and straight up hill imo. Of course in it’s current state bp isn’t much easier, though that is going to change bigtime with 1.1. As to the interface, well that can be changed as well, but it’s a huge amt of work. We actually got about 90% finished making an exact ‘clone’ of the theme used for bp on this site. I just got sidetracked on other projects so didn’t complete it yet.

@Jeff – I’m definitely not trying to start a platform war. The only reason I even brought up elgg was as an example of what can be accomplished and a system that I absolutely fell in love with when I found it. In the case that you had not seen the code from elgg, I was simply trying to give an example is all.

My foundation is and will remain wpmu. That is why I keep coming back every few days to check on bp progress. Your privacy plugin is going to make bp usable in many instances where without it bp would not even be an option. I applaud you for the work on this, and the devs behind bp itself. I agree it’s an amazing platform considering how young it is.

I think my request for granular object control has been made pretty clear. I just wanted to get my 2cents in whether it’s accepted or not.

peace

[@anointed Participant 17 years, 1 month ago]

@markpea I am using 1.6.1 so I am not sure what was in or out of previous versions.

My understanding of the permissions system is it has both ‘general’ privacy settings on a per component basis, with the ability for granular override of any given object. Pretty much the best of both worlds. I can set my ‘overall preferences on an object set, and decide to override an individual object should I have the need to.

I can’t think of a single downside to having both systems in place with elgg. Complete privacy control is given to the user for every object, and since it’s in the core, any plugin can hook directly to the permission system to it’s extensible.

Your right, the system for elgg is absolutely brilliant and lightyears ahead of bp in this area. I found that on my network, once I showed everyone the power of granular permission control, that almost everyone started using it instantly. (I did a demo showing how my pages are completely different depending upon the viewers permissions and people loved it).

I would estimate that at least 80-85% of my members are using granular control in one fashion or another.

@Jeff

Quote:

So, for instance as you suggest, at this stage a user will not be able to assign an individual image discrete access rights. Why? Because photos (album objects) are not part of BP’s current core.

My understanding of bp is nowhere near my level of understanding of how elgg operates, so I use that as a base for my comments. I’m guessing bp is similar in it’s approach.

In elgg, it makes no difference if ‘album objects, or any other object’ is part of the core or not when it comes to privacy. All objects have to pass through the authentication system before they are added to the given page. In fact I’m not even certain a plugin would function properly without passing through the authentication system first, never tried that.

I guess I just don’t understand why this type of system would not work in bp. Is the core really that flawed?

Still I’m glad to see that your tackling the permission system for bp. Imo bp is pretty much useless fodder without permissions.

[@anointed Participant 17 years, 1 month ago]

Coming from an ‘elgg’ point of view, I’m curious if your privacy plugin is going to be similar.

When I create any new item in elgg, be it an image/video/audio/post/etc.. I have the ability to assign the object to a given group at the time of creation.

Meaning, if I upload a new picture, or a new blog post, I have a dropdown permission box where I can set the groups allowed to see the item. (I can select multiple groups if needed).

One thing I absolutely love is I can assign the privacy settings to groups of users.

For instance, I have multiple ‘friends’ groups, ‘coworkers/family/friends/etc’ so when I make a post, I can say that only ‘friends’ are allowed to see it. Or, if I am a member of different ‘groups’, I can assign the permission to members of the given group (that part is really cool)

Basically the permission system is so extensive, that my profile page looks completely different depending upon the permissions of the user visiting my page. (I’ve even managed to take it to the level of custom styles/css on a ‘per permission’ basis)

Of course I can edit permissions on any object after creation should I choose to edit it later.

Is this type of system basically the same as what you are talking about?

[@anointed Participant 17 years, 1 month ago]

I believe that the first huge step towards each buddypress install having it’s ‘own’ members is now complete. In order to accomplish this, we needed to start out where each blog can have it’s own members.

I just uploaded a new plugin to wpmudev.org that may be useful to you. I know many have complained about this.

It allows people to register for an individual blog using the normal registration process. In WPMU all registrations are forwarded to wp-signup.php, so it is impossible for a visitor to register for only a sub-blog. This plugin overrides WPMU and restores the default WordPress registration page for sub-blogs (sub-blog.domain.com/wp-login.php?action=register).

Features:

* Compatible with plugins like Register Plus to control registrations.

* You can edit the default user role sitewide (subscriber, author, etc.).

* You can also control whether users can adjust their own blog registration settings.

* If users can control their own registration settings, a menu with that option appears under Users->User Registrations.

* Does not affect main blog. Registrations there are maintained at wp-signup.php.

Check it out: http://wpmudev.org/project/wpmu-blog-registrations

I would be curious to hear from the bp devs if this is the right plan of attack for laying the groundwork for individual blogs to have their own buddypress.

My idea being that once we have ‘separated’ the wpmu members so each member actually registers and belongs to an individual blog, we can then start filtering the bp widgets to only show activity/members/groups/etc.. that belong to the blog which is displayed.

[@anointed Participant 17 years, 1 month ago]

@John – I had a similar question, so I might as well attach it to this post.

I have my wpmu setup and running. I have already registered a number of users and accounts. I did create a ‘placeholder’ subdomain blog for my future buddypress install. I also set the wpmu admin to automatically add all new users to that blog.

So the question is simple:

When I add buddypress to the subdomain, will buddypress automatically recognize all the members of that subdomain blog?

I was told in another post awhile back that buddypress actually does not have it’s own registration system but uses wpmu. So by that theory I would expect buddypress to recognize everyone once it’s turned on….

[@anointed Participant 17 years, 1 month ago]

@chargertech – When bp 1.1 final is released I will reinstall it on my system and go to town trying to figure it all out.

Who knows, maybe Andy or someone will chime in someday and give us an example as to how to apply user filters to activity streams and listings.

I’ve still got to guess that they already have something even better up their sleeves. With automatic behind buddypress, one has to figure that they plan on adding it to wordpress.com someday, which would require this type of functionality.

[@anointed Participant 17 years, 1 month ago]

@DJPaul – Wow I wasn’t intending to start a debate about premium stuff in this thread. I simply paid to have a plugin developed for myself and thought it would be a nice thing to give it away. I have no idea if Aaron is going to offer it on the premium site or the regular site, I’ll leave that up to him.

[@anointed Participant 17 years, 1 month ago]

I can’t provide buddypress specific code as I have not yet read through it, but here is the code that I use to have pages automatically created for new blogs when they are setup.

Anyone with bp experience who knows the function names could easily change my code to bp appropriate code. [replicate the code as often as needed in the custom function file for as many pages as you need]

Code:

function change_newblog_defaults( $blog_id, $user_id ){
global $wpdb, $current_site, $wp_rewrite;
//–change to new blog
switch_to_blog($blog_id);
//make page
$wpdb->insert( $wpdb->posts, array(
‘post_author’ => $user_id,
‘post_date’ => $now,
‘post_date_gmt’ => $now_gmt,
‘post_content’ => __(‘This is the content’),
‘post_excerpt’ => ”,
‘post_title’ => __(‘Pagetitle’),
‘post_name’ => __(‘Pagename’),
‘post_modified’ => $now,
‘post_modified_gmt’ => $now_gmt,
‘post_status’ => ‘publish’,
‘post_type’ => ‘page’,
‘to_ping’ => ”,
‘pinged’ => ”,
‘post_content_filtered’ => ”
) );
//inserted id
$page_id = $wpdb->insert_id;

//change template inserted page
$wpdb->query(“insert into $wpdb->postmeta (post_id,meta_key,meta_value) values ($page_id,’_wp_page_template’,’templatefile.php’)”);
//restore blog
restore_current_blog();
}
add_action(‘wpmu_new_blog’, ‘change_newblog_defaults’ );

[@anointed Participant 17 years, 1 month ago]

@Andrea-r – I believe I have the ‘first part’ solved already. That being that each blog has it’s own users. Aaron was kind enough to spend the time building a custom plugin for me that allows users to signup on a subdomain blog without leaving the subdomain. *Aaron rocks!*

This way each subdomain has ‘it’s own’ members, though all members are automatically added to the primary blog and the bp blog behind the scenes. [expect this plugin to be released on the premium dev site sometime soon so everyone can have it]

Now that each ‘blog’ will have it’s own users, I have an idea to attack this problem.

1. As most everything displayed by buddypress is via widgets, I may be able to duplicate the widgets and then write some custom filters to only output what the ‘subdomain blogs’ users have been up to.

e.g. filtering the activity stream to only show activity from the blogs users which is being displayed.

2. for those displays that are not widgets, like the members list/groups list/ etc…

That may take a bit more filtering.

Anyhow, I have to imagine that buddypress is already thinking about this type of stuff already. I personally just can’t see how they can even begin to implement buddypress on wordpress.com type of sites without this ability.

[@anointed Participant 17 years, 1 month ago]

@dwpers – Actually I want it the other way around. I don’t want my users blogs integrated into the bp site, but want bp integrated into my user blogs. While it sounds like a ‘trivial’ difference it is not.

I’m trying to figure out how to give each blog owner their own buddypress sub-community. With the new theme system for bp coming out, it should be much easier to integrate bp into my current website themes. Then I would like to only display members/groups/forums/etc that ‘belong’ to that particular blog.

Think of it from ‘how would wordpress.com integrate buddypress?’

If they simply just had a ‘huge’ community that everyone was a member of, kind of how ning did it on their ‘home’ site, then no one would ever really be interested. I’m more suspecting that buddypress would become a plugin that each blog would activate on their own to build their own ‘sub-community’. Though I am pretty sure that wordpress.com would follow the ning example and automatically have all members of all blogs become part of a larger community behind the scenes. Whether they know it or not.

Am I off base here?

[@anointed Participant 17 years, 1 month ago]

btw.. the only reason I don’t have buddypress installed right now is I got sick of all the problems trying to upgrade wpmu from 2.7.1 to 2.8.4a with buddypress involved.

So I took the nuclear route and wiped everything out with a fresh install of 2.8.4a

I am waiting until next week when buddypress 1.1 is finally official before I install it again.

Not to mention that prior versions of buddypress just didn’t like being installed onto a blog id other than 1. (I tried every ‘hack’ on these forums to get buddypress to place nice on blog id#30 but it never took)

I’m seriously hoping that buddypress has solved the issue of installing it onto a blog other than id#1 in the new buddypress 1.1

[@anointed Participant 17 years, 1 month ago]

@Jeff – It’s ‘similar’ to what I am talking about, but not really.

I guess the best way to put it is: ‘How do I turn buddypress into buddypress-mu?’

Believe me, I was trying to avoid asking the question like that because it’s a little deceptive. Obviously if there were a buddypress-mu then all of my problems would be solved out of the box.

I seriously doubt we’ll see buddypress-mu anytime soon, enless there is information I am not aware of.

In the meantime, I was thinking of taking a different approach with bp.

With my new plugins, each blog has it’s own member base. (members are transparently added in the background to the root blog as well as the future bp blog behind the scenes through the wpmu admin)

Now since each blog has it’s own member base, I would then have to figure out how to tell buddypress to only display information pertinent to those members who belong to the blog in question.

example: I create buddypress pages on a subdomain blog xyz.blog.com and add the bp widgets

members list would only show members belonging to that blog via filters

activity would only show activity from those members of that blog

etc….

All that part would be possible if we can figure out how to dump the buddypress registration, and have buddypress use the built in wpmu registration system. That’s because wpmu already knows which blogs a member belongs to.

Seriously… why in the world does buddypress have a separate user system in the first place, when wpmu has a world class user system already available to use………

anyhow, I hope that makes more sense.

[@anointed Participant 17 years, 2 months ago]

I can get into the admin just fine, even thought maybe it was the theme, but when i try the theme browser and select another theme, the theme popup even says wrong host….

this is the only site on the server with this issue, and is the only site running wpmu/bp

[@anointed Participant 17 years, 3 months ago]

ok maybe this would be easier if i ask the question like this.

what is the ‘bp variable’ I use if i want to display ‘the current logged in username’ in any code that I write?

meaning I need command that says ‘logged in user’ says hello

what is the variable for ‘logged in user’ ?

also:

what is the variable used to display the ‘username’ of the member whose profile I am viewing?

I don’t mean the ‘pretty username’ but the actual login username….

thanks

hope this results in replies as it may be easier to understand my question when put this way.

[@anointed Participant 17 years, 3 months ago]

John:

I have been having the same problem since moving my bp install from id1 to id30.

I tried all the ‘suggestions’ on the forums and patched the files, but bp still seems to save all files like avatars, photo album plugin pics etc in id1 instead of id30…

Looking at the ticket, it looks like it’s assigned to 1.0.4… is this the case?

If so I am guessing that it would be best for me to wait for 1.0.4 to come out instead of trying to hack it together to fix it?

It seems really strange to me that buddypress only works on the primary blog. What I don’t understand is why this would be the case. Buddypress is so far away from what I would call ‘production’ ready status, that it makes no sense to me to run it on my primary mu blog. Isn’t buddypress in it’s current state better to keep in the background, away from others until it’s more stable?

not ranting here, luv buddypress, I just can’t use it as primary but do want it running ‘in the background’ so I can keep adding features and testing etc…

btw

(gave up on trying to update to 2.8 series.. never did stop spitting out errors, so prob just going to wait for 1.0.4 anyhow.. thanks for your time answering emails on it)

[@anointed Participant 17 years, 3 months ago]

One thing that may help in the meantime is using gmail.

for example, I have account ‘myaccount@gmail.com’

you can use others that will all resolve to that account such as

‘username1.myaccount@gmail.com’

‘username2.myaccount@gmail.com’

‘username3.myaccount@gmail.com’

gmail will route all the ‘sub’ accounts to the same email account for you. For me at least it makes it really easy for me to manage all of my accounts, and it’s really simple to remember as I use ‘username1’ as the username1 for my wp account in question….

[@anointed Participant 17 years, 3 months ago]

well i didn’t go anywhere near the php.ini file as this is a dedicated server and I don’t separate them out on a per site basis.

the .htaccess file was not overwritten, left that intentionally.

I’m going to try it one more time and see if it helps.

I did have one problem that I forgot about. I accidentally deactivated buddypress before I deactivated all the plugins that rely upon it. That resulted in a 500 error. I had just removed the offending plugins that rely upon buddypress via ftp, figuring that would solve the problem. Which it ‘appeared’ to do, but obviously not.

So I reactivated buddypress, then reupped the other plugins via ftp, and then did the deactivation the right way. Now all are properly deactivated and I’m replacing files again.

will report back.

John: reminds me:

burt actually asked me to send you a pm regarding an ‘issue’ i am having as he is to busy with his move. I’ll send it after this final attempt.

[@anointed Participant 17 years, 3 months ago]

I have had no luck at all trying to upgrade from 2.7.1 to 2.8.1

Here are the steps I am following:

1. backup all files and db – done

2. deactivate all plugins on the main blog

3. remove all plugins from the mu-plugins folder

4. delete wp-admin and wp-includes folders from server

5. upload all new 2.8.1 files to the server

Then when I try to reach any page on the server I get a 500 error which is as follows:

PHP Fatal error: Call to undefined function wp_clone() in /website.net/wp-includes/cache.php on line 380

The only thing I can do at this point is to delete all the new files I uploaded and replace them with the old 2.7.1 files…

I have tried this 4 times so far with no luck. I have made absolute certain that all the files are properly overwritten, but still end up with the error.

Is there a solution to this problem, or am I the only one with it?

I’ve read the upgrade docs, and as far as I can tell I am not missing a step, so I’m really stumped here…..

btw

my buddypress install is NOT on the primary blog, so I did not have to change the theme. It is a wp standard theme on the primary blog

[@anointed Participant 17 years, 3 months ago]

The install went fine, works as advertised.

The only request I can think of would be the ability through the bp group blog admin to give users the ability to become ‘moderators’ for the group blog so that they are also able to post to the blog.

Idea being, I created a support group blog which worked just fine. However I don’t want to be the one that has to update the blog all the time. I know that I can manually assign people as contributors to the blog itself in the blog admin, but it would be nicer to add them in the bp admin area. This way I can separate out regular members who sign up to the blog, but are not part of the support group.

anyhow, thank you, it’s a nice plugin

[@anointed Participant 17 years, 3 months ago]

thank you.

I will install it tomorrow and get back to you with the results.

Is there a demo link avail?

[@anointed Participant 17 years, 4 months ago]

I had the same question:

I went into the main admin ‘blogs’ chose the blog in question and changed the upload value.

However it keeps reverting back to the old value when I ‘submit’ the changes.

No matter what number I try, it always reverts back to the ‘default’ value…..

ideas?

[@anointed Participant 17 years, 4 months ago]

The BP_ENABLE_MULTIBLOG option works fine on my install using subdomains.

where is this setting located?

It’s the first I have heard of this function