BuddyPress.org

The issue of Avatars has been raised and looked at.

The links, tend to agree, they’re a lot of changes due for the site so maybe that will be considered as well.

I agree it’s difficult, I have the strange benefit of having started with php 4 so I recognise certain syntax as ‘Odd’ 🙂 or unfamiliar so would tend to use what I was used to. I’m raising the issue elsewhere to see what the other mods / core devs think, and whether it’s an issue […]

If scripts can be made as backwards compatible as possible they should be, all that happens if one writes to the latest version of something like PHP using newer syntax is that it will break in older versions and by older versions one refers to versions that will still be in use by many hosting […]

It’s essentially already being done, if you look at member-header.php you will see that ‘last activity’ and ‘latest updates’ for the member being displayed are fetched by passing in bp_displayed_user_id() that function returns the current displayed user so all you need to do is an if displayed user == ‘ID’ do some stuff else carry […]

Funny thought this issue was resolved, at any rate installed new versions recently on WP3.0.1 BP 1.2.5.2 and all was fine

Perhaps you could repost this in the appropriate group for seeking buddypress developers:

https://buddypress.org/community/groups/bp-jobs-board/

Thread closed.

!important might work but all in all it’s abused by the community If the specificity is matched then the ruleset coming last takes precedence and an adjusted rule should come after the one being trumped – !important also further compounds the issue of BP themes working or at least having a semblance of working with […]

And did you install Firebug? It may be a case that you need to increase the selector specificity by adding in parent selector elements , which might also be shown by firebug if you inspect the element and then look at the applied rulesets, it could show a number of antecedent selectors such as: #item-nav […]

It’s probably not a great idea to do something like this via client side scripting especially given the circs for wanting to do this. A filter function ought to be created to handle it. It’s worthy of looking at with a view to creating a plugin or functions.php function, shouldn’t be too difficult to do […]

@travel-junkie Just been having a play around, although can’t yet see an approach to change the mismatch notice when > 0 characters I did add in a stronger warning on username password matches. I changed //password1 == username to return ‘badPassUsername’ leaving ‘badPass’ to work for the score < 40 Added a new var badPassUsername = […]

You have already asked this, please be patient it’s the weekend and late, posting twice will not get any faster a response.

Closing this thread ;continue in the original please.
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-make-a-social-metwork-like-the-above-with-buddypress/

Oh ok fair enough, however some of those directives you are trying to state should in fact be set in httpd.conf already e.g FilesMatch should be set to deny access to .htaccess, and do you know then if AllowOverride ALL is set as I would expect a host to restrict that to a specific set […]

Do you not have access to your httpd.conf? Your .htaccess is starting to read like a primary conf file, as a rule use of ..htaccess should be avoided or be kept to a minimum where possible as it’s a big performance hit on a server.

@milordk can I ask what you mean by this comment: It makes no sense to prove that it is better I seriously hope it’s not directed at me 🙂 I am not trying to prove that one plugin or another is better or worse, nor did I start this thread or the two others laboriously debating these […]

Haven’t looked at Drupal in a while, probably worth checking how they handle things. I might try and grab a few minutes in the morning and see if there’s a better way of doing the matching, although my jQuery/JS skills have become sadly rusty over the last year. It’s easy for us to overlook how […]

One thing occurred to me, and purely from a user perspective, is the password matching; it would be nice if it would only compare the two passwords when the user had finished, on blur or something; to have the text display ‘Mismatch’ from the off might confuse some people who will think they have entered […]

These two additions to the signup are excellent, password strength always worries me and had been looking at the various scripts around, and it’s a nice UX to let the person know that their chosen name is already taken. All in all a really useful compact little plugin.

Start a group rather than dragging up old threads please!