Forum Replies Created
-
In reply to: EMERGENCY!!! – new avatar images
It sounds like it might be a permissions issue.
Just to be clear: When I try to view http://point2angler.com/wp-content/uploads/avatars/19/c70472e199daa3d2a55276a8eedea0b5-bpfull.jpg in a browser, I get a 404. But you can see that file via FTP, right? (You said ‘image.jpg’ above – not sure if you’re using that as shorthard for the hashed image name, or if you literally mean that there’s a file called ‘image.jpg’)
If this file is indeed there, see if your FTP client has a way to look at permissions. Report back with what you find. If it turns out to be a permissions problem, then it’s beyond the scope of WP/BP, and you’ll have to take it up with your host.
In reply to: EMERGENCY!!! – new avatar imagesThe people who answer questions in this forum are volunteers. Please be patient.
Did some aspect of your configuration change? What other plugins are you using? Have you verified that the new avatars are actually being uploaded to wp-content/uploads/avatars/? What happens when you try to visit the URL of one of the images directly?
Can you switch to bp-default to see if the problem persists?
In reply to: Members loop has bug (BP 1.5.1)I don’t see anything in the code which would have caused such a change, but it’s possible. Please open a bug ticket at http://trac.buddypress.org
I can’t reproduce either issue on my local installations.
– Hidden/private group activity does not show for logged-out users
– Hidden/private group activity does not show on the Friends activity tabAre either of you running plugins that affect the way that activity works? Or is there something in your custom theme that modifies the activity loop?
In reply to: Disable Private GroupsI don’t know an easy way to do this at the moment, but it’s a reasonable enhancement request. At the very least, we could provide a filter that would allow plugins to modify which group types are permitted. http://trac.buddypress.org
In reply to: Multisite Buddypress – New Users, Sites, Admin BarThe original issue has been resolved: https://buddypress.trac.wordpress.org/ticket/3755#comment:8
@iblbuilder Your issue sounds distinct. Can you post a bug ticket at http://trac.buddypress.org, with specific steps to reproduce? (Including BP and WP versions)
In reply to: Possible bug with plugins.php and saving user metaNo, don’t use a template file. plugins.php is not the issue.
Move your `if ( isset( $_POST ))` stuff up into `bp_privacy_screen_settings_menu()`. Then change it to
`if ( isset( $_POST ) {
if (isset($_POST)) {
update_user_meta($bp->loggedin_user->id, ‘bp-profile-privacy’, ‘1’);
} else {
update_user_meta($bp->loggedin_user->id, ‘bp-profile-privacy’, ‘0’);
}bp_core_add_message( ‘Settings updated!’ );
bp_core_redirect( bp_displayed_user_domain() . $bp->settings->slug . ‘/privacy’ );
}`In reply to: Possible bug with plugins.php and saving user metaHm. I’d have to see the code to see why it’s causing a problem. I don’t see why using plugins.php would make a difference, unless you’re catching the $_POST submit inside of the bp_template_content function.
In reply to: Possible bug with plugins.php and saving user metaYeah, I don’t even need to look, and I already know what’s happening.
The problem is that you’re catching the form submit too late – the page has already started loading, and your settings have already been cached by WP. You can work around it by doing a bp_core_redirect() after you have run your save routine – that is, save the submitted settings, and instead of letting the page load, bp_core_redirect() back to your settings page.
In reply to: Google reader and sitewide activityI’m afraid I don’t know how Google selects which RSS feed to display. It probably just picks the first one it finds. Make sure there is a line like the one that @modemlooper suggests, and make sure it appears high in header.php – immediately after the `
` tag. Whether/whenever theme compatibility is fully implemented in BP, bp-default will have to stay around, in some form or other, for the purposes of backward compatibility. If the kind of rewrite that you’re talking about is able to maintain this backpat, I don’t see any reason why what you’re proposing couldn’t become part of bp-default itself.
“Decisions not options” is a nice general strategy, but I’m unwilling to dismiss the possibility of including some well-chosen theme options just because of that strategy. If you can come up with some simple options that help you achieve your goals, please feel free to pitch them.
As for your last question, bp-default is licensed under the same GPL as the rest of BP, so you can do whatever you’d like with it
In reply to: Multi users profile: development direction please!The essence of what you want is to store a piece of usermeta called something like ‘user_type’, where each user is either ‘player’ or ‘team’. The tricky part for your purposes will probably be that BuddyPress (or WordPress for that matter) is not designed to allow one user to act “on behalf of” another user – or, as you put it, “players interact only through their respective teams”. I take it that means that player1 would be able to send a message and have it come from team1. But this is going to be quite tricky, as it’ll mean, essentially, filtering the current user id in hundreds of places throughout BuddyPress.
In reply to: Preview of Pages and Posts not working with BP 1.5.1@henrybcn Thanks for the bug report!
> I have to ask why would you advise against doing it?
Because if you go and mess up your database because you’ve got your sticky fingers in there, I don’t want you to come and blame me!
<– Note that this will delete all activity items related to blog id 1. If you need only to delete new blog post notifications:
`DELETE FROM wp_bp_activity WHERE type = ‘new_blog_post’ AND item_id = ‘1’;`Here’s what you’ll need, though I will also say that you should not do this, and I accept no responsibility for what goes wrong:
`DELETE FROM wp_bp_activity WHERE component = ‘blogs’ AND item_id = ‘1’;`
Oops – make that update_site_option and get_site_option. Might be worth pinging @wpmuguru about this as well.
Search the SWT for update_sitemeta or get_sitemeta. That will give you a start. I will take a look myself when I get a chance.
Sorry, I have a million things on my plate.
Look through SWT and see how they are storing the tags blog id. Then change BP so that it looks for that piece of sitemeta.
In reply to: Do Not Understand BuddyPressGroup forums allow forum discussions to be group-specific. Is that too vapid an answer?
Groups are more than just forums. They allow other kinds of collaboration. Take http://commons.gc.cuny.edu/groups/digital-humanities-initiative/ for example. In addition to forums, they have an Announcement space, a shared Files upload space, a shared blog.
As I suggested above, if you find a given feature “confusing and all over the place”, you should shut that feature off. Not everyone needs every feature turned on, and not every feature makes sense for every application.
Could you open a ticket on trac.buddypress.org pointing to the line that I linked above? I’ll have to install SWT and see how they changed it.
It’s possible that SWT was updated so that the settings key is different. Can you check your database to see if you have an item in wp_options with the name ‘tags_blog_id’?
I’m a bit confused about this whole thing. BuddyPress is supposed to block SWT posts out of the box: https://buddypress.trac.wordpress.org/browser/trunk/bp-blogs/bp-blogs-functions.php#L163 If it’s not working, then there’s a bug in BP.
What do you expect it to do? The point of that specific code, as discussed in the accompanying thread, is to remove individual activity items that correspond to comments on one’s own top-level activity items.