[@hnla Participant 12 years ago]

You show the link but no img elements for avatars at all.
You need to provide details of your setup, but also run some simple tests, is this a media upload issue, does your WP install correctly handle media (likely not the issue as one would expect default avatars) Is this a plugin issue? de-activate all but BP plugin establish if some other plugin is causing an issue. Activate one of the stock WP themes to establish if avatars show then if they do we have a theme issue.

[@hnla Participant 12 years ago]

There you go shanebp’s given you an easier option 🙂

[@hnla Participant 12 years ago]

Is this an IIS server , almost pretty permalinks? url structures are odd, members seems to work activity and groups not.

[@hnla Participant 12 years ago]

Implementing a user membership ID is a question for the plugin authors.

Hiding a WP user ID if you are going to display it is simple enough, wrap the display in a ‘if’ conditional that checks current_user_can(‘update_plugins’) or similar admin only capability (look them up on the WP codex)

You could also check what role the user has assigned which is a slightly more complex procedure better suited to functions, prefer it personally but not in templates.

[@hnla Participant 12 years ago]

In switching theme though you had the answer this is a theme issue; as to what the issue might be with this Gantry theme is one can only speculate as there is insufficient information to debug and it’s a third party theme most of us probably are unfamiliar with.

The actual issue lies in the class ‘rt-container’ and it’s position:relative used in this manner without containing it’s floated elements it’s wreaking havoc, as a fix you could add overflow: hidden; to it’s ruleset or if the stylesheet describes a clearfix ruleset apply that class to the elements with class ‘rt-container’ other than that you must take the issue back to the theme authors as they need to account for what is happening and provide a long term solution in thier styles.

[@hnla Participant 12 years ago]

? required field checking on what it’s a simple user/pass login both are required no

if the site templates header puts the document into full standards mode that html5 understands then you can use html5 form atts like ‘required=”required”‘

If you want an implementation of the BP login form but slightly extended you can grab mine on gitbub either run it as a plugin or grab the class function and run that from your functions.php or bp-custom.php you could then customize that.
https://github.com/hnla/hnla-bp-sidebar-me

[@hnla Participant 12 years ago]

If you are going to modify a template to add a call to the_widget() function you might as well make it a dynamic_sidebar call, then you have a little more flexibility.

[@hnla Participant 12 years ago]

If you allow your users to create groups, they have to follow the 3 creation steps, because it is intended so in BuddyPress. Thinking that this might be to complicated, implies that you think that your users are not able to do this. Mabe you’re right, but maybe not.

About this i have worked with other plugins to tell more about groups, media ability and add location etc. So i now have 7 steps in a group creation. This is the main reason why i am requesting for this topic.

This doesn’t really make any sense how can you think you need to limit creation steps if you add plugins that extent the group creation api in offering necessary user choices in the setup process, are they not presented as ‘steps’ because they are choices a user needs to select.
However if you would simply prefer that a default choice is initially set and setup screen for that option hidden then it sounds like you need to modify those plugins behaviour which may mean hacking filtering into the plugin or contacting the author for a modification to remove that setup tab – but preserving edit screens if available.

[@hnla Participant 12 years ago]

What update are you after?

You say in OP that you are sure this is a 5min job! the two replies you received suggest not though! What you are asking is not straightforward, there is no non technical approach to this as Paul says maybe something will be built out but until then you would need to hook in to the BP menu functions and create custom implementation but this would not be straightforward.

[@hnla Participant 12 years ago]

> I suggest you post this question over on the bbpress forum.

Yet you are posting on the buddypress help forum! 🙂

This is a bbPress issue and there is a trac ticket and resolution over on bbp site, likely that will in the next bbp release.

You could apply the fix manually in the interim if you wished the trac ticket is located here:
https://bbpress.trac.wordpress.org/ticket/2690

[@hnla Participant 12 years ago]

Yep, but not sure if this is going to work, essentially you would need a function that passes in $user_name & $user_email then run your user_name checks as the bp function does but omitting the underscore check then pass those two variables into the $results array as bp does but the $user_name will be based on your checks with the $user_mail & $errors just passed into that array as is and $result returned in the function, then you add_filter(‘bp_core_validate_blog_signup’, ‘your_function_name’, 2)

Note though likely I have got most of that wrong 🙂 WP has codex pages on working with filters that you probably should read for a better understanding of how to use them.

[@hnla Participant 12 years ago]

> I asked this question previously and didn’t get a useful answer

What post and why are you not continuing in that thread rather than creating a new one? Perhaps the advice was don’t do this?

If you want to modify core functionality then the WP approach is via hooks and filters, BP adds filters on a liberal basis where they would help in allowing devs to modify or interact with functions so you’ll need to check the functions in core see what filters are available for you to work with.

fwiw I’m not sure it’s wise to start messing around with the core WP signup process, these aspects are tricky, have you considered they may well be a reason underscores aren’t allowed, and regardless why would you think them useful?

[@hnla Participant 12 years ago]

This sounds as though you may be using old templates? We removed the old default action of pushing the group create button out into the heading tag in the 2.0.0 release, that change required existing themes to possibly make adjustments if they had perhaps overloaded the bp-functions.php file which had a new set of group create button actions. my memory is hazy on the issue but the trac ticket covering the change is at:

https://buddypress.trac.wordpress.org/ticket/5144

You will need to provide details of your theme as without any detail of your setup it’s difficult to help – as a check try activating one of the WP shipped themes i.e twentyfourteen, does the double entry of the button still happen, if not you know it’s a theme related matter.

[@hnla Participant 12 years ago]

It’s that time again isn’t it @sooskriszta for your wish list 😉 🙂

I would leave out the @mentions on individuals they can be irritating.

As you have created tickets for all your wish list items I’m sure they’ll receive consideration so perhaps these forum posts are unnecessary?

[@hnla Participant 12 years ago]

Not sure who this ‘john’ is to whom you keep referring 🙂 but yes he’s about right but this isn’t a defect it’s how BP provides theme compatibility in injected into page template files via the wp content function, this is run through a series of filters though and I would expect shortcodes to be stripped out.

Not really sure why you are trying to do this but it should be possible to circumvent this action and bypass the filters in a function suitably hooked.

[@hnla Participant 12 years ago]

This is really a bbPress question, buddyPress isn’t responsible for how bbPress handles it’s functionality. Try posting the question on bbPress forums.

[@hnla Participant 12 years ago]

This may be a memory issue, why are you running fastcgi? can you switch to php module for less memory usage?, believe this can be an issue with fastcgi, but other than that dealing with this sort of thing isn’t easy when one hasn’t the issue in front of one.

[@hnla Participant 12 years ago]

? what do your logs say

Server issues are somewhat outside the remit of this help forum really.

[@hnla Participant 12 years ago]

You probably ought to track back through the bpdevel site:
http://bpdevel.wordpress.com/
For development posts on Codex updates.

We actually have been putting in quite a bit of our time over the last year attempting to lend a little attention to this area, but it is an extremely time consuming and slow area to deal with but apart from some fairly hardcore re-structuring many new articles & guides have been submitted over the last few months.

You’re right though it is a community effort, all are welcome to chip and help, the codex index explains how people can contribute.

[@hnla Participant 12 years ago]

@1a-spielwiese if you are saying people should reply to old threads then no they shouldn’t and that is not a convention of this help forum but in general. Resurecting of threads is considered bad form especially on web tech forums, old threads are an archive for referring to and that may contain useful information and thus no they are never generally removed from search results but do not serve in being brought back into the main stream of current threads. A lot of forum apps can actually close them automatically after a set period of time sadly we can’t here.

[@hnla Participant 12 years, 1 month ago]

Your child theme should simply be the required stylesheet naming the main theme as template: the themes name’ picking up your themes styles if necessary – hopefully they are enqueued so will load up via the themes function.php file.

Now if you want to change any buddypress styles create a folder in child theme top level ‘buddypress/ in that a folder named /css/ so we have ‘buddypress/css/ in that css folder copy buddypress.css; now you have a full copy of the bp styles and BP will automagically find that file and use it instead of it’s original copy, you can now edit anything you care to in that file.

[@hnla Participant 12 years, 1 month ago]

No! Essentially the principle in overloading (copying templates) is one of replicating the name of the core file and ensuring the file is located in a directory that matches to the core one.

So we create a directory named either ‘buddypress’, or ‘community’ in our theme or child theme then anything that lives within the bp core directory /bp-legacy/’ we replicate over creating sub directories of same name, we copy over only the files we want to edit so buddypress.css gets copied over to /buddypress/css/.

bp-legacy directory is the only name we change transposing that name to ‘buddypress/ or ‘community’ thereafter follow what ever structure you see under bp-legacy in your theme.

[@hnla Participant 12 years, 1 month ago]

You’re using a premium plugin here, really the question should be posed to their support.

This question ir remarkably similar to this thread which is probably the route you need to follow.
https://buddypress.org/support/topic/filter-list-of-profiles-on-member-page/

[@hnla Participant 12 years, 1 month ago]

Looks to me as though you are missing a mandatory param – ‘$component’ is listed as being ‘required’ if ‘component’ param empty or if the component not active the class returns false, adding a known active component string kicks things into life.

But as you wrote your code you should be able to work out from the core class where things have broken and why:
bp-core-classes.php

[@hnla Participant 12 years, 1 month ago]

‘implode’?