[gogoplata]

This is likely related to a major flaw in MU 2.8.1 that will hopefully be fixed soon where a lot of the upgrade functionality is broken or otherwise off. I was able to upgrade to 2.8.1 using the automatic upgrade but it’s still telling me to upgrade. The same goes for plugins, I’ve upgraded them but they still say there’s updates available plus there’s no prompt to upgrade when new plugin versions like BuddyPress 1.0.3 is released.

Manual upgrade is the only option I know of right now.

[gogoplata]

Posted this late last night and wanted to bump it up now that there’s some more people around. Any and all help is appreciated.

This weekend I’ll be removing the extra stored avatars and watching to see if the issue continues, though it appears to still be occurring after upgrading to 1.0.1 earlier this month.

Thanks in advance!

[gogoplata]

There is likely a better way to do this but this should fetch the username:

<?php

global $current_user;

if ( isset($current_user) ) {

echo $current_user->user_login;

}

?>

Not sure why there’s a need to re-arrange the URL structure but hopefully that code helps.

[gogoplata]

Any more ideas?

I’m planning on applying the above patch, cleanly installing the trunk tonight to make sure there’s no older files lingering on the server, and am also going to analyze the database to see whether it’s a problem with the events being recorded to the DB or whether it’s with the output.

Hopefully it’s as simple as that but I’m afraid it’s likely more serious.

[gogoplata]

Didn’t realize avatar sharing was part of that plugin, will check it out. Thanks!

[gogoplata]

Thanks for the link, I’ll give that a try but I still think there’s a larger issue here.

After letting it sit overnight I re-checked the activity feed this morning and though it has a few new items in now goes back over 3 weeks. In non-technical terms, it appears to not be recording most items and leaking the items it does record, eventually causing them to disappear from the feed.

[gogoplata]

I ended up dropping bbPress all together tonight. I’ve got respect for everyone who’s developing it but it progresses too slowly and SimplePress is a lot more advanced right now, particularly for non-technical end-users. I ended up just installing simplepress and getting rid of group forums until bbPress adds more advanced functionality or the community takes off and pumps out additional plugins.

Personally I’d like to see Automattic acquire simplepress and merge the two products.

[gogoplata]

For a general chat for logged in users I used these instructions and it worked perfectly.

[gogoplata]

Thanks for the instructions, I’ll give this a go tomorrow.

I’ll probably post an enhancement ticket for the search toggle as well as the link field type as they both seem like they’d be useful.

Thanks again!

[gogoplata]

The linked plugin does not work so I’d pursue another solution. I’m also interested in finding a way to do this.

[gogoplata]

Try this. It hasn’t been updated in a while by the looks of things but I have it installed in /mu-plugins and it works well.

[gogoplata]

If you dig around the forums you’ll find the rationale behind this, which is that it’s much easier to scale a site with this database structure than storing all user information in a limited number of tables.

[gogoplata]

Yes, it’s loading for me.

[gogoplata]

Update: This is semi-invalid. Member search and directory are working, just not as expected. Because I allow users the ability to remain semi-anonymous by not requiring a full name and instead displaying their username it is largely impossible to find members using the username they comment and post with around the site. Because the majority choose never to fill out my “Display Name” field, instead opting to publicly display their username, most appear in no searches for their username. I’ve made “Display Name” a required field so users will be forced to provide a name which will be searchable.

Ultimately I’d like to see usernames be searchable but until then this will suffice.

Hopefully this helps others struggling with this issue…

[gogoplata]

Try changing default role here (domain.com/wp-admin/wpmu-blogs.php?action=editblog&id=1) and here (domain.com/wp-admin/options.php) to “contributor” then do a test registration to see if the new user is a contributor or subscriber.

If that doesn’t work in wp-includeswpmu-functions.php change this:

add_user_to_blog(‘1’, $user_id, ‘subscriber’);

to this:

add_user_to_blog(‘1’, $user_id, ‘author’);

That should take care of all future signups, however existing users will be unchanged. If you don’t have too many users yet you can simply manually change them to authors, however, if you have a lot of signups check out this thread for a way to mass add users as authors.

[gogoplata]

Yeah, this problem should be as easy as having wpmu-functions fetch the user-specified role whereas right now “subscriber” is hardcoded into the file.

Good luck with getting a function working Mike, if all else fails the technique above is verified to work and is as easy as modifying a single file. Shouldn’t take more than 2 minutes max. Then, when upgrading, just re-modify it. Simple as that.

[gogoplata]

Go to the AccountCenter and enable root access then login to plesk as root using the password you set and then there will be a file manager in Virtuozo.

[gogoplata]

Just tested and this is still present in the latest revision. I’ll make a ticket.

[gogoplata]

Not sure if it’s a problem on my install only, but I modified default_role at /wp-admin/options.php and /wp-admin/wpmu-blogs.php?action=editblog&id=1 but new signups were still subscribers, not authors. I remember working on this previously and the only way I was able to change it was to do as I outlined above, though others may be able to simply change default_role in the dashboard.

[gogoplata]

In wp-includeswpmu-functions.php change this:

add_user_to_blog(‘1’, $user_id, ‘subscriber’);

to this:

add_user_to_blog(‘1’, $user_id, ‘author’);

That should take care of all future signups, however existing users will be unchanged. If you don’t have too many users yet you can simply manually change them to authors, however, if you have a lot of signups check out this thread for a way to mass add users as authors.

[gogoplata]

Did users 1, 2, and 3 each publish the posts or did user 1 publish all of them and attribute the second and third posts to the other users? I believe there’s a bug in buddyPress where whoever actually publishes a post (or approves a comment) is considered the author, not the attributed author or commenter. I’m running code from a few weeks ago so some of this may be corrected in the latest trunk (I’m upgrading now) but as of the files I’m running this was a bug.

[gogoplata]

I don’t think a Twitter-like functionality will be added to the BP core but this can be done now with around 10 minutes of work.

All you’d need to do is create a blog such as whereareyou.domain.com. Then add all existing users as authors and auto-add new users as authors to the blog (see this post for details on doing this, it only takes a minute). Finally install and tweak the prologue theme to suit your site. The updates users post to the blog will automatically show up on their profile like other blog posts.

This is a really basic implementation of a “Twitter-like” functionality, but with a little tweaking this setup works really well.

[gogoplata]

I’d just add a custom profile field called “Public Email” or the like, which would allow users to optionally provide an email to display publicly and also allow it to be different from the one they used for registration.

[gogoplata]

It’s only available to site admins and adds a message at the very top of the inbox for all users.

[gogoplata]

It works for the main blog too, thought the search function isn’t all that useful given there would only be a single blog but all the other functions work with the main blog.

All you’d need to do to get this setup is to change the default role for the main blog from subscriber to contributor and disable blog registration. Also, you may want to hack at the code to remove things such as the blog directory, the list of user blogs, etc. but this is optional.