Forum Replies Created
-
I’ve tried to replicate but can’t. I’ve successfully uploaded and cropped the image as a “member” and “group” subscriber/admin. BP 1.5 on Safari, using child of bp-default.
I’ve upgraded from RC1 to 1.5, changed the values in that first field (Name) as an Admin and as a Subscriber and have had no issues. The value persists to whatever content I had entered.
@adam, this may help:
Thank you for taking the time to put this together. Much appreciated.

Thanks, Paul!

@tnd, you’re welcome. Actually, the links are one of the most “awesome” features of Buddypress. Let’s say that one of your family member’s plays the violin, where Buddypress has applied a “link” for “violin”. Guess what happens when that link is clicked? Buddypress searches your entire community for members who have that attribute and lists them for further perusal, friendship building, etc. It’s a “community” building feature. Saying that, there’s a way to tell Buddypress not to establish a link for a particular word/element, etc. For example, a phone number would be a silly element to have a link for, right?
Since I’m new to all of this, I cannot remember what the tags/punctuation is that one would surround the word with that you wouldn’t want Buddypress to provide a link for.
@DJPaul, I went back to my profile and tried a several different combinations. This shows up when the field group has a multiselect box where an item has been selected then saved. When viewed in Public, the Group field heading shows up as well as the field’s value. After clearing that multiselect field and saving, Public still shows the Group heading with no values. This happens in testbp as well. Thanks.
Hhhhm @tnd, not sure what your goal is. Based on my interpretation of what your trying to accomplish, I would do this instead. Create a Smith Family group, and add Smith family members to the Group. You could set permissions on it to “hidden”: that is, the admin gives permission to those who want to join AND the group is listed in the group directory; or, “private”, where the previous applies except, no one sees it (not listed in the group directory, but only seen by Smith group members as part of their profile).
That way, in XProfile, you could be specific about defining the role (through a field group), that a Smith Family group member would choose to complete, and that info is what would be displayed when Public is selected.
The “name” issue that you mentioned… if by filling out “Name”, you’re referring to the “Name” in the “Base”, then every time that’s changed, that logged in member’s profile name will change. If you actually added a field called “name” to a field group and when editing the profile, specifically, that field group’s field called “name” and by doing so, somehow changes the “Base” field “name” content, then I have no idea how to help. That shouldn’t happen.
So far, so good. Thanks, guys!!!!!
@4ella, I believe this is post to which you are referring (near the bottom of the page): https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-add-fields-to-group-creation-with-group-extension-api-please-read/?topic_page=4&num=15
It’s from modemlooper. And it’s a follow-on to modemlooper/jorges plugin. One has to go into the php file to add/modify fields but it solves the need. Plus, whatever html tags have been placed in the php file to organize the fields, one can just add IDs/Classes and style them in your child theme’s style.css. No need for inline styling.
With that being said, @slaffik will your update allow for Group types and/or categories? For example, for a specific group type, the admin could create/apply a form containing fields specific to that Group type. With the application of categories/sub-categories, the user would be able to filter across an exhaustive list of Groups. I am looking forward to trying your updated plugin.
@boonegorges, you rock! I added the additional css and nervously hovered over that infamous drop down field, crossed my fingers, and clicked on it. It worked!
I have to say that was even better than my first bite of a slice of New York pizza!!!!!!! Thank you so much for digging into this!@boonegorges, thanks. I commented out that block. No change. I went back to Font Squirrel and instead of uploading my fonts to their font generator, I just downloaded one of their free kits: Calligraffiti. I then commented out all of the old @face-fonts, added in this new one to my style.css, went through the same routine, and got the same result. This is strange. Could you try with that font or any font kit from Font Squirrel? I assume the Date picker field is in the same genre as a “drop down” field…picking either one results in the total reload of Safari.
@boonebgorges, okay Boone, I’ve spent the last 6 hrs 16 minutes on this. I have determined where the issue is occurring but I do not know how to fix it. But first here’s the calibration I eventually got to: I re-installed WordPress and Buddypress (yep, I’m getting faster reinstalling this stuff).
I created a new child theme; that is, a new style.css file and a new functions.php file to enqueue the child’s style.css file. Here’s the code for my functions.php file:`<?php
function bp_dtheme_enqueue_styles() {
// Bump this when changes are made to bust cache
$version = ‘20110804’;// Default CSS
wp_enqueue_style( ‘bp-default-main’, get_template_directory_uri() . ‘/_inc/css/default.css’, array(), $version );wp_enqueue_style( ‘bp-child-style’, get_stylesheet_directory_uri() . ‘/style.css’, array(), $version );
// Right to left CSS
if ( is_rtl() )
wp_enqueue_style( ‘bp-default-main-rtl’, get_template_directory_uri() . ‘/_inc/css/default-rtl.css’, array( ‘bp-default-main’ ), $version );
}add_action( ‘wp_print_styles’, ‘bp_dtheme_enqueue_styles’ );
?>`
Should be no issue there. With the new stylesheet I started adding back my old code starting at the very top. I didn’t have to go very far at all. It failed at the body selector (at the very bottom of this post); specifically, the @font-face font that the stylesheet loaded. I took it out; I replaced it with verdana or helvetica. No issues. I cycled through all of the @font-face fonts and each one produced the error. Note: The @font-face fonts rendered properly on every page but failed when I clicked on a “dropdown-style” field as described in my first post. Do you have any recommendations? Am I supposed to enqueue the fonts just as I had the stylesheet? If so, how would that be done? Thanks!
Note: I commented out a few declarations in the body selector to help narrow down which declaration could be the issue. And just like Firefox, this works fine in Chrome 13.0.782.220.
`/*
Theme Name: My BP Default Child Theme 1
Theme URI: http://folio.com
Description: This is my first Buddypress Default Child Theme
Author: Quint A. Rahaman, Jr.
Template: bp-default
Tags: buddypress, two-column, grey, dark
*//* RESET – http://meyerweb.com/eric/tools/css/reset/ | v1.0 | 20080212 */
/*
*/body,html{height:100%;}
html,body,div,span,applet,object,iframe,h1,h2,h3,h4,h5,h6,p,blockquote,pre,a,acronym,address,big,cite,code,del,dfn,em,font,img,ins,kbd,q,s,samp,small,strike,strong,sub,sup,tt,var,b,u,i,center,dl,dt,dd,ol,ul,li,fieldset,form,label,legend,table,caption,tbody,tfoot,thead,tr,th,td{border:0;outline:0;font-size:100%;vertical-align:top;background:transparent;margin:0;padding:0;}
body{line-height:1;}
ol,ul{list-style:none;}
blockquote,q{quotes:none;}
blockquote:before,blockquote:after,q:before,q:after{content:none;}
:focus{outline:0;}
del{text-decoration:line-through;}
table{border-collapse:collapse;border-spacing:0;}/* Floating & Alignment */
.fl{float:left;}
.fr{float:right;}
.ac{text-align:center;}
.ar{text-align:right;}/* Clear Floats */
.col-full:after{content:”.”;display:block;height:0;clear:both;visibility:hidden;}
.fix{clear:both;height:1px;overflow:hidden;margin:-1px 0 0;}
html body * span.clear,html body * div.clear,html body * li.clear,html body * dd.clear{background:none;border:0;clear:both;display:block;float:none;font-size:0;list-style:none;overflow:hidden;visibility:hidden;width:0;height:0;margin:0;padding:0;}/* Generated by Font Squirrel (http://www.fontsquirrel.com) on September 8, 2011 */
@font-face {
font-family: ‘FontSiteSansRoman’;
src: url(‘includes/fonts/includes/fonts/fontsitesans-roman-webfont.eot’);
src: url(‘includes/fonts/fontsitesans-roman-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/fontsitesans-roman-webfont.woff’) format(‘woff’),
url(‘includes/fonts/fontsitesans-roman-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/fontsitesans-roman-webfont.svg#FontSiteSansRoman’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘BergamoStdItalic’;
src: url(‘includes/fonts/bergamostd-italic-webfont.eot’);
src: url(‘includes/fonts/bergamostd-italic-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/bergamostd-italic-webfont.woff’) format(‘woff’),
url(‘includes/fonts/bergamostd-italic-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/bergamostd-italic-webfont.svg#BergamoStdItalic’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘BergamoStdRegular’;
src: url(‘includes/fonts/bergamostd-regular-webfont.eot’);
src: url(‘includes/fonts/bergamostd-regular-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/bergamostd-regular-webfont.woff’) format(‘woff’),
url(‘includes/fonts/bergamostd-regular-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/bergamostd-regular-webfont.svg#BergamoStdRegular’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘FontSiteSansCondensed’;
src: url(‘includes/fonts/fontsitesans-cond-webfont.eot’);
src: url(‘includes/fonts/fontsitesans-cond-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/fontsitesans-cond-webfont.woff’) format(‘woff’),
url(‘includes/fonts/fontsitesans-cond-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/fontsitesans-cond-webfont.svg#FontSiteSansCondensed’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘FontSiteSansUltraLight’;
src: url(‘includes/fonts/fontsitesans-ultralight-webfont.eot’);
src: url(‘includes/fonts/fontsitesans-ultralight-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/fontsitesans-ultralight-webfont.woff’) format(‘woff’),
url(‘includes/fonts/fontsitesans-ultralight-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/fontsitesans-ultralight-webfont.svg#FontSiteSansUltraLight’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘StMarieThin’;
src: url(‘includes/fonts/stmarie-thin-webfont.eot’);
src: url(‘includes/fonts/stmarie-thin-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/stmarie-thin-webfont.woff’) format(‘woff’),
url(‘includes/fonts/stmarie-thin-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/stmarie-thin-webfont.svg#StMarieThin’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘BergamoStdItalic’;
src: url(‘includes/fonts/bergamostd-italic-webfont.eot’);
src: url(‘includes/fonts/bergamostd-italic-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/bergamostd-italic-webfont.woff’) format(‘woff’),
url(‘includes/fonts/bergamostd-italic-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/bergamostd-italic-webfont.svg#BergamoStdItalic’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘BergamoStdItalic’;
src: url(‘includes/fonts/bergamostd-italic-webfont.eot’);
src: url(‘includes/fonts/bergamostd-italic-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/bergamostd-italic-webfont.woff’) format(‘woff’),
url(‘includes/fonts/bergamostd-italic-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/bergamostd-italic-webfont.svg#BergamoStdItalic’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘BergamoStdRegular’;
src: url(‘includes/fonts/bergamostd-regular-webfont.eot’);
src: url(‘includes/fonts/bergamostd-regular-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/bergamostd-regular-webfont.woff’) format(‘woff’),
url(‘includes/fonts/bergamostd-regular-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/bergamostd-regular-webfont.svg#BergamoStdRegular’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘BergamoStdRegular’;
src: url(‘includes/fonts/bergamostd-regular-webfont.eot’);
src: url(‘includes/fonts/bergamostd-regular-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/bergamostd-regular-webfont.woff’) format(‘woff’),
url(‘includes/fonts/bergamostd-regular-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/bergamostd-regular-webfont.svg#BergamoStdRegular’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘FontSiteSansCondensed’;
src: url(‘includes/fonts/fontsitesans-cond-webfont.eot’);
src: url(‘includes/fonts/fontsitesans-cond-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/fontsitesans-cond-webfont.woff’) format(‘woff’),
url(‘includes/fonts/fontsitesans-cond-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/fontsitesans-cond-webfont.svg#FontSiteSansCondensed’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘FontSiteSansCondensed’;
src: url(‘includes/fonts/fontsitesans-cond-webfont.eot’);
src: url(‘includes/fonts/fontsitesans-cond-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/fontsitesans-cond-webfont.woff’) format(‘woff’),
url(‘includes/fonts/fontsitesans-cond-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/fontsitesans-cond-webfont.svg#FontSiteSansCondensed’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘FontSiteSansRoman’;
src: url(‘includes/fonts/fontsitesans-roman-webfont.eot’);
src: url(‘includes/fonts/fontsitesans-roman-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/fontsitesans-roman-webfont.woff’) format(‘woff’),
url(‘includes/fonts/fontsitesans-roman-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/fontsitesans-roman-webfont.svg#FontSiteSansRoman’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘FontSiteSansRoman’;
src: url(‘includes/fonts/fontsitesans-roman-webfont.eot’);
src: url(‘includes/fonts/fontsitesans-roman-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/fontsitesans-roman-webfont.woff’) format(‘woff’),
url(‘includes/fonts/fontsitesans-roman-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/fontsitesans-roman-webfont.svg#FontSiteSansRoman’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘FontSiteSansUltraLight’;
src: url(‘includes/fonts/fontsitesans-ultralight-webfont.eot’);
src: url(‘includes/fonts/fontsitesans-ultralight-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/fontsitesans-ultralight-webfont.woff’) format(‘woff’),
url(‘includes/fonts/fontsitesans-ultralight-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/fontsitesans-ultralight-webfont.svg#FontSiteSansUltraLight’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘FontSiteSansUltraLight’;
src: url(‘includes/fonts/fontsitesans-ultralight-webfont.eot’);
src: url(‘includes/fonts/fontsitesans-ultralight-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/fontsitesans-ultralight-webfont.woff’) format(‘woff’),
url(‘includes/fonts/fontsitesans-ultralight-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/fontsitesans-ultralight-webfont.svg#FontSiteSansUltraLight’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘StMarieThin’;
src: url(‘includes/fonts/stmarie-thin-webfont.eot’);
src: url(‘includes/fonts/stmarie-thin-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/stmarie-thin-webfont.woff’) format(‘woff’),
url(‘includes/fonts/stmarie-thin-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/stmarie-thin-webfont.svg#StMarieThin’) format(‘svg’);
font-weight: normal;
font-style: normal;}
@font-face {
font-family: ‘StMarieThin’;
src: url(‘includes/fonts/stmarie-thin-webfont.eot’);
src: url(‘includes/fonts/stmarie-thin-webfont.eot?#iefix’) format(’embedded-opentype’),
url(‘includes/fonts/stmarie-thin-webfont.woff’) format(‘woff’),
url(‘includes/fonts/stmarie-thin-webfont.ttf’) format(‘truetype’),
url(‘includes/fonts/stmarie-thin-webfont.svg#StMarieThin’) format(‘svg’);
font-weight: normal;
font-style: normal;}
#sidebar{display:none;}
div#content .padder{margin-right:0px; border-right-width:0px;}body { font-family: ‘FontSiteSansRoman’, helvetica, sans-serif;
/* font-size: 0.75em;
line-height: 1.5em;*/
color: #3e3e3e;
background: url(“images/bg.png”) repeat fixed 0 0 #f6f0d6;
/* max-width: none;
width: 100%;*/
/* position: relative;*/
}`modemlooper, works great! Thanks, again.
@boonebgorges, I cleared the browser cache and got the same results. I reset Safari, other than my passwords, and got the same results. My parent theme is bp-default. I changed from my child theme to bp-default and the dropdown behaves properly. I haven’t changed any core files. So, now I’m a bit stuck. My child theme works in Firefox but not Safari (for the dropdown). Could you point me in some direction that I can troubleshoot where this could be happening?
In my child’s folder, I have the header, footer, and functions php files, the style.css file, an images folder, and an “includes/fonts” folder for the @fontface fonts that style.css loads. I have not edited any of the parent’s files.
Thanks!
@modemlooper, maybe it’s there as a placeholder for future functionality?
IMHO at the moment, providing a “template” option across all Pages (incl. Component pages), is somewhat misleading.So given your last post, are you saying that I could hide the sidebar through code in my child’s style.css? If so, how would I do that? If not, which files and how should I do it? I can figure out how to change the width on the “content”, so that shouldn’t be an issue. Sorry about asking so many questions. I am still pretty new to this. Thanks.
FYI: I’m running BP 1.5 Beta 3
@dains, your enclosed link no longer works. The following should:
@mercime, thanks for confirming. I’ve placed the ticket.
@tommyhoang, the major benefit of creating a child theme is so that when the parent theme gets updated, the customizations that were made won’t be lost. The child theme’s style.css is where the CSS customizations are being defined. That’s where you would have styled the header.
By the way, the child theme’s style.css is intended to override the targeted styling in default.css which resides in the parent theme. I’m new at this but I don’t see the purpose of you creating a default.css for your child theme.
@modemlooper, I’m too new at this to help you but I just wanted you to know that your group announcement plugin that could broadcast across the stream from the “group” itself is a fantastic idea! Here’s a thought. What if there is so much activity in the stream that a observer/member (not of that group) misses it? Do you think providing a subscription feature for a specific group’s Group Anouncements would be something folks would want?
@modemlooper, thanks for replying. I saw I could do that right after I posted my question. I tried what you suggested for each of the component pages but it didn’t work. I created a new page and selected the appropriate template, and that worked. So then, I tried associating the Members component page with that newly created page. No go. Even though it mapped to the new page, the sidebar still shows up. Am I missing a step or do you think this could be a bug?
@mercime, I know this is a somewhat old thread but I would appreciate your advice on how to remove the sidebar and make the content area full width (for all the component directories: Activity, Forums, Groups, Members) from a markup/php standpoint for Buddypress 1.5. I am running Beta 3.
Per @modemlooper plugin, I’ve been able to add fields to groups. So what I’ve asked you is the next step; that is, to make room for all the content.
Thanks @modemlooper. I went hunting for an answer and there it was. Your plugin works like a charm!!

@linick, why is the default theme that comes with BP 1.5 (in beta) not sufficient? It’s probably the highest quality Buddypress theme out there. Have you found a gap in features/functionality in the old vs new or vice versa?
@ewebber, thanks for the info.
@harty, in response to ewebber’s recent post, I would consider what she did with her site: establish terms and conditions per her About page, and for those businesses that want to advertise, provide a mechanism for that to happen. This will be inline with a “pull” vs “push” strategy which is what I believe you’re going for.
@ewebber, thanks. That looks like it would work. Hopefully, it’s compatible with BP 1.5.