Forum Replies Created
-
Given that BP 1.7 introduced theme compatibility, and 1.8 will extend that considerably as we have now brought into play a new level of template hierarchy along with placement of assets CSS/JS in BP directories the question is moot, as you can do either but a child theme is always a child of whatever parent theme you have chosen to use – unless you decide to overload BP by adding bp directories directly to the top level of a theme in which case theme compatibility would be automagically disabled.
The rule of thumb is that if your chosen theme can be updated and you want to make custom changes to BP template files then you do so in a child of that parent theme, even if only containing the ‘buddypress’ ( or ‘community’ ) directory to ensure your changes are maintained in your own child theme.
Please check the codex for documentation first:
http://codex.buddypress.org/user/setting-up-a-new-installation/installing-group-and-sitewide-forums/If that doesn’t help then post back with current issues.
or you could study the DB tables and manually manipulate the fields, not really that difficult. as for emails you can send if you configure a program such as sendmail along with an email account set up with a catchall forwarding to the main email box.
@benjino before Henry or bp-help posted if you had searched and scrolled down you would have seen the post to which I referred, but no problem
. @sooskriszta those are point revisions of course there could possibly be a 1.7.3, if a bug of a serious enough nature comes along and needs fixing how do you think it’s numbered, the fix would be rolled into a point revision and released then merged into trunk so that the latest revision had it ?
Guys this has been covered! which is why I requested a site search, not to be mean but to follow a forum principle of not repeating itself and of using it’s archives.
the latter functions miss an important trick covered in a previous post on this by mercime and in the first example here by Henry and will be, in all likelihood, spitting out the link on all menus, possibly the desired effect?
You’re going to need to get some basic skills especially in the PHP area if working with WP/BP as ther is a need quite often for running up functions – in terms of files to hold that WP provides only one really in themes functions.php, BP provides bp-custom.php that can initiate functions for BP regardless of theme in use.
For the nav question do a quick search for ‘wp nav menu’ you’ll find previous threads, and also make use of the codex to see if any questions are covered there.
it always is the bloody issue in so many cases, wish people wouldn’t install the damned things unless there’s a real need.
As I said on the other thread this isn’t a BP issue. Blog is a somewhat generic term it doesn’t really refer to any WP component, BP can refer to ‘blogs’ but that is in the case of WP multi site activated. For BP to work out of the box you need do nothing, although if you want the registration process functioning that is a WP function managed from the setting>general page the only thing BP requires is blank pages created to cover it’s main components such as registration , activity, members etc, you can see all that though in the BP settings screens. The blog you refer to is the WP primary loop and it’s not BP that is managing that it’s part of WP core to have the loop query available to render.
You have caching plugins running so check those out as possible causes?
You would probably need to remove the link from the WP dashboard menu screen as it’s not really possible to apply any logic from that point and instead write a function to place a link to the register page if !is_user_logged_in() and then filtered through ‘wp_nav_menu_items’
Failing that approach you could take the slightly more cumbersome? approach of simply defining two wp nav menus and display them in their regions based on logged in/out checks.
Hey, I was hired to create this site, ha ha. ?
This is a WP issue it’s a WP loop so you need to find where it’s being generated from, not really a BP issue
@DJPaul Yep think it’s all good to go I’ve run it through a few tests and all feels great, the ticket had become so convoluted that it was suggested a line drawn under and any later enhancements to the principle started in new ticket, but personally I think we have the flexibility needed now with devs creating their own bp_get_template_part calls if they need to drill down further.
Well @DJPaul kicked it off with the initial patch based on feedback from a couple of devs on this ticket:
http://buddypress.trac.wordpress.org/ticket/4639
The codex entry needs a little additional editing and linking to my earlier page on 1.7 template compatibility.
and turn off any caching plugins!
What did you want? BP used to provide a hardcoded sidebar login bp-me function, you can still find that in bp-default and copy it over to your theme, or grab this upgraded & extended version:
https://github.com/hnla/hnla-bp-sidebar-me.Why are you linking to wpmu a commercial site. You should check the projects official Docs first

http://codex.buddypress.org/user/setting-up-a-new-installation/configure-buddypress-components/You need to check through the BP settings for the answer to this.
At what point is that ruleset appearing in the cascade? This is likely an issue of selector weight, try putting an id in that selector set, an id that is a parent of one of those elements.
And what solution were you looking for?
I found the styles in seconds using Firebug:
#friends-personal-li a span {}
or:
.item-list-tabs li a span {}
if you want to catch all the span numbers across bp screens navAnd then as I said earlier it is indeed a float containment issue, you need either overflow: hidden; or a clearfix class on the .inner_wrapper (please let no one suggest an empty clearing div at bottom of element)
It ought to be considered and think it was briefly mentioned once long ago but there’s always enough to do in each BP release cycle.
Ah that would have been useful info that the group hierarchy plugin was in use, as it does use it’s own templates that have to live in a folder /tree/ which can be a little confusing, also watch that plugin it is a clever one but as it changes so much about how groups work other plugins or actions on groups can run into issues so if experiencing issues with groups always look there first as possible reason.
well doubt it would be ‘get_page()’ try ‘is_page()’ with a name, slug, or id.
Did you find the div in question in that index page?