[@johnjamesjacoby Keymaster 16 years, 3 months ago]

This plugin is going to get a good nudge soon, I promise. The solution with removing the ampersand actually cropped up recently and I just patched it in the trunk, so it’s correct and won’t hurt anything.

I’m going to make a UI in wp-admin to allow you to select which fields are searchable, and it will include a bundled template to get you by to start with. ETA on this is a week or two at least.

[@johnjamesjacoby Keymaster 16 years, 3 months ago]

I currently develop BuddyPress locally using Windows IIS7 and PHP 5.3; haven’t experienced these issues at all, but it’s possible a combination of .htaccess and web.config files might be gumming something up.

Not sure if this is helpful, but this is currently the web.config that I’m using.

https://codex.buddypress.org/developer-docs/iis7-web-config/

[@johnjamesjacoby Keymaster 16 years, 3 months ago]

@bennadler The problem with doing it that way (in BuddyPress core) is for installs where /wp-content/ is moved out of the WordPress root and located somewhere else, which is a common configuration for the more security minded folks.

That fix will work for most everyone else however.

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

@xrun, so this issue is resolved for you?

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

Fixed in 1.2 branch and will be fixed in 1.2.6. See r3129 for the fix.

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

The pictures aren’t physically lost or deleted. There is something in the configuration that is causing it to miss where the image is, and it’s falling back on the gravatar.

I’m mobile right now, but I’d like to personally help one of you fix this, so that we can get avatars resolved asap.

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

You’ve got to be kidding. Ugh.

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

BuddyPress avatars have been a constant thorn in everyone’s sides because there are so many possible configurations available for where uploads will go, and how they are displayed.

The more eyes we can get on this code is the better. Both Andy and myself have patched, adjusted, and repatched this code for the past few versions, fixing some issues and creating others.

I suspect these issues stem from the WP-singlesite to WP-multisite conversion. Where there is still a setting for singlesite domain.com/uploads/ when multisite is looking for domain.com/files/, but I’m unable to duplicate the bug so far.

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

Would be awesome to at least have a nice iPhone ready theme available. I know someone (@modemlooper?) was working on an iPhone theme recently. You might want to hook up with him to check his progress.

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

And you are using BuddyPress 1.2.5?

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

We we’re ever at a WordCamp together, I’ll buy everyone a round of cake.

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

Do you have a link to your site I can see?

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

The cake is a lie.

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

Boone scored like 40 points on the word “ox”

No lie.

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

This works the same way as if you registered from within WordPress. If I remember correctly, WordPress purges unactivated sign-ups after a certain number of days, but I will need to research this to make sure.

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

2144 lines in 1.2.5
https://trac.buddypress.org/browser/tags/1.2.5/bp-core.php#L2144

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

@denisjanis If you need to revert you should just be able to download the old version from trac.buddypress.org and replace the files.

But, it would be awesome if we could try and figure out what’s causing it. Looks like you have a custom child theme, so it might be a plugin conflict or something.

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

Can you give me an example? Chances are this is for readabilities sake. There shouldn’t be any /extra/ spaces anywhere. The WordPress coding standards do ask us to put spaces in before and after such things as closing and opening brackets, after commas, and things like that. The BP code isn’t minified in anyway, and we’ll probably look into doing that for CSS and JS in future versions, but the PHP code will continue to stay the way it is.

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

Fixed in branch. Thanks!

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

Seems you’ll need to bump up the amount of available memory in your installation. There are lots of documented ways to do this if you do a quick search of the web.

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

You all rock

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

Can we get a ticket for 1.2.6 about this if there isn’t one?

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

Usually missing template files will cause something like this to happen.

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

1.2.5 has an almost totally rewritten bp_core_fetch_avatar function that should fix these issues. Can you confirm that all files are up to date and try again?

[@johnjamesjacoby Keymaster 16 years, 4 months ago]

Just upgraded two sites, one a subdirectory, the other a subdomain, two separate hosts and environments, neither of which showed this issue. Phew!

Again, doesn’t mean it doesn’t exist, but so far I really can’t duplicate it.