Search Results for 'buddypress'
-
AuthorSearch Results
-
August 5, 2009 at 7:41 pm #50652
In reply to: Scaling down/Centering complete Buddypress
David Lewis
ParticipantLet me know if that works. It would go in wp-content/themes/bphome/css/site-wide.css
When I saw you all talking about using Javascript just to center a theme and give it a fixed width… I sensed someone somewhere along the line went down a rabbit hole
LOL.
August 5, 2009 at 6:58 pm #50650In reply to: Scaling down/Centering complete Buddypress
hatiro
ParticipantThanks, that’s a better suggestion, not really much of a coder, just stumble across solutions..
If I find something that works I try and share that, but more often than not someone else has a much better idea, so not sure if its a help or hindrance……try to steer clear of javascript where possible though
August 5, 2009 at 6:22 pm #50649In reply to: Scaling down/Centering complete Buddypress
David Lewis
ParticipantJavascript?! Good lord. Just make a site-wide.css file with one line of code in it
body {width: 970px;}
Does that not work?
August 5, 2009 at 5:57 pm #50647In reply to: Tables not created on reinstallation
Paul Wong-Gibbs
KeymasterHave a look in your sitemeta table. There are some buddypress records you need to remove.
August 5, 2009 at 5:36 pm #50646In reply to: Scaling down/Centering complete Buddypress
hatiro
ParticipantAs there was no solution provided here and its been some time ago maybe this has been resolved, but its a problem that I encountered.
I haven’t fully tested this but after a hunt around I found a couple of techniquues.
Using javascript to refresh on resize between the <head> tags causes infinite loops in IE in some cases so that will not solve the problem.
I found out though that if you include position:relative in all of your main outer divs including body and body.directory in the IE fixes css files in the bphome and bpmember themes your problems should go away…
Let me know if this works for you….as I’ve only tested it locally and on IE7…
August 5, 2009 at 5:34 pm #50645Tore
ParticipantYou have to edit it by hand. You can use the Firebug addon to Firefox to get help with which CSS-code to change.
As far as I know, you only need to do the editing in custom.css. It should override the original settings.
August 5, 2009 at 12:39 pm #50639In reply to: After connection, its only redirecting
Paul Wong-Gibbs
KeymasterThat might be the problem. You need to get WPMU working before worrying about BuddyPress.
Looking at the URL, it thinks you are trying to register a new hosted blog at “http://waapsols.com/”.
When you installed WPMU, in the installation screen it asks you for a server name to use. What did you enter? I am guessing you entered your server’s IP address?
If that’s the case, delete .htaccess and wp-config.php and drop the database, and try reinstalling, but enter “waapsols.com” during the installation.
August 5, 2009 at 12:02 pm #50637marcaurel75
ParticipantThe thing is: I only thought I had deactivated the bp-plugin completely (via backend).
I guess it was removed from the active_sitewide_plugins-field in the sitemeta-table in the database – but it was not removed from the wpmu_sitewide_plugins-field in the same table.
So the site still worked (no HTTP-500-error), and the umlaut-issue with the p2-theme remained.
When I then removed the bp-plugin-entry via phpmyadmin from both fields, the “main blog” didn’t appear anymore (error 500), but the two “sub blogs” I have still functioned. And the one sub blog with the P2-theme worked then without the umlaut-issue.
I hope this clears things up a bit.
So for me it is pretty clear that the bp-plugin somehow interferes with the P2-editor and causes the umlaut-issue.
August 5, 2009 at 11:41 am #50636Paul Wong-Gibbs
KeymasterI deactivated the BP-plugin. Problem remains. So it’s probably an issue with WordPress MU and the P2-theme?!
?
August 5, 2009 at 11:35 am #50634marcaurel75
ParticipantI deactivated all plugins via phpmyadmin – in the sitemeta-table as well as in the options-table of the single blogs (there are 3 in my installation right now).
So the HTTP-500-Error disappeared. And all of a sudden the P2-theme worked properly as well.
This means: the regular deactivation via backend of the buddypress-plugin didn#t really work. The umlaut-issue with P2-theme seems related to buddypress.
August 5, 2009 at 10:01 am #50632marcaurel75
ParticipantHELP! Since I tried to reactivate the BP plugin I receive a HTTP 500 error when I try to reach the site… mpf!
August 5, 2009 at 8:57 am #50631marcaurel75
ParticipantI’ll check it. Thanks for the support!
August 5, 2009 at 8:36 am #50629Paul Wong-Gibbs
KeymasterYou have said that the problem occurs on WPMU, and that it does not occur on regular WP. You have also said this problem is not caused by BuddyPress.
I haven’t got an install of regular WP to test this on, so I am going to assume it is either a WPMU issue *or* you are using an old version of the P2 theme.
August 5, 2009 at 8:29 am #50627marcaurel75
ParticipantDoing more research I found the following thread in the wp-forum:
https://wordpress.org/support/topic/273413?replies=2:
—-
Mippe: P2 brokes äÄ öÖ åÅ letters when editing. That pretty much sums it all up.
noel (Administrator): We’re aware of the issue and will fixing this in the next release.
But I am still unsure: This problem then occurs only with WordPress MU?
August 5, 2009 at 8:24 am #50625marcaurel75
ParticipantI deactivated the BP-plugin. Problem remains. So it’s probably an issue with WordPress MU and the P2-theme?!
August 5, 2009 at 7:39 am #50624In reply to: External Blogs
Paul Wong-Gibbs
KeymasterYou can view the roadmap at https://buddypress.org/about/roadmap and find for yourself. As Jeff Sayre posted a couple of months back, if you have a question for Nicola, send him a message on this site.
This post would be two or three months old and out-of-date if it hadn’t kept being bumped by people asking “is it out yet?”. I am tempted to close this thread.
August 5, 2009 at 7:35 am #50623Paul Wong-Gibbs
KeymasterTry removing or disabling BuddyPress. Does this problem still occur on WordPress MU?
August 5, 2009 at 5:18 am #50618In reply to: Make width fixed to 900px?
Mike
Participantyep, you can with some css. the parts you wanna tweak are #header and #main, if i remember correctly. you can also download the Avenue K9 theme from this page https://buddypress.org/extend/themes/ to help you get started, which is optimized for those pesky 1024×768 screens.
August 5, 2009 at 4:38 am #50617mumbler
MemberThanks so do you change it in both? Can’t you have them all the same?
Also, I believe the css is changable via GUI or on the admin webpage can this be done or do I have to directly edit the css code by hand?
TIA!
August 4, 2009 at 10:55 pm #50609In reply to: How do I edit widgets?
Mohit Kumar
ParticipantRoscosys – Please be clear what you want to edit. You can definitely edit the slugs just read this
https://codex.buddypress.org/how-to-guides/customizing-labels-messages-and-urls/
and the core hack is not advisable – it means we dont advise editing the widget file as it will be overridden when you upgrade.
August 4, 2009 at 7:54 pm #50603In reply to: Update status
belogical
Participantor you could download the latest trunk
August 4, 2009 at 7:27 pm #50600In reply to: Update status
Paul Wong-Gibbs
KeymasterThat’s a new feature coming in the next release of BuddyPress, which I believe to be coming in a couple of weeks.
August 4, 2009 at 5:25 pm #50597hatiro
ParticipantI’m having the same issue as described above in that when I add pages to the blog that buddypress is active on they are being highlighted as member pages in the navigation bar, even though according to the is_page rules the member page should only highlight when the BP_MEMBER_SLUG is identified. For some reason all .com/######/ are being highlighted as member pages (well those that are not main blog, groups or blogs anyway
…I will try and mess around with the bp_is_page vs is_page as r-a-y suggests. I also use dreamweaver for editing code but have never rewrite code on phph enabled so can’t see that as being the issue.
August 4, 2009 at 4:41 pm #50594In reply to: External Blogs
peterverkooijen
ParticipantWas this functionality now part of the roadmap for Buddypress? Did Andy or other Buddypress developers get Nicola Greco’s code?
I’ll bring this up on the WPMU forum as well.
August 4, 2009 at 4:34 pm #50593In reply to: How to get a section identifier in the body tag?
peterverkooijen
ParticipantThe default templates have body_class() in the body tag. The function body_class() is in post-template.php in the wp-includes folder:
function body_class( $class = '' ) {
// Separates classes with a single space, collates classes for body element
echo 'class="' . join( ' ', get_body_class( $class ) ) . '"';
}Function get_body_class() is in the same file:
/**
* Retrieve the classes for the body element as an array.
*
* @since 2.8.0
*
* @param string|array $class One or more classes to add to the class list.
* @return array Array of classes.
*/
function get_body_class( $class = '' ) {
global $wp_query, $wpdb, $current_user;
$classes = array();
if ( 'rtl' == get_bloginfo('text_direction') )
$classes[] = 'rtl';
if ( is_front_page() )
$classes[] = 'home';
if ( is_home() )
$classes[] = 'blog';
if ( is_archive() )
$classes[] = 'archive';
if ( is_date() )
$classes[] = 'date';
if ( is_search() )
$classes[] = 'search';
if ( is_paged() )
$classes[] = 'paged';
if ( is_attachment() )
$classes[] = 'attachment';
if ( is_404() )
$classes[] = 'error404';
if ( is_single() ) {
$wp_query->post = $wp_query->posts[0];
setup_postdata($wp_query->post);
$postID = $wp_query->post->ID;
$classes[] = 'single postid-' . $postID;
if ( is_attachment() ) {
$mime_type = get_post_mime_type();
$mime_prefix = array( 'application/', 'image/', 'text/', 'audio/', 'video/', 'music/' );
$classes[] = 'attachmentid-' . $postID;
$classes[] = 'attachment-' . str_replace($mime_prefix, '', $mime_type);
}
} elseif ( is_archive() ) {
if ( is_author() ) {
$author = $wp_query->get_queried_object();
$classes[] = 'author';
$classes[] = 'author-' . sanitize_html_class($author->user_nicename , $author->user_id);
} elseif ( is_category() ) {
$cat = $wp_query->get_queried_object();
$classes[] = 'category';
$classes[] = 'category-' . sanitize_html_class($cat->slug, $cat->cat_ID);
} elseif ( is_tag() ) {
$tags = $wp_query->get_queried_object();
$classes[] = 'tag';
$classes[] = 'tag-' . sanitize_html_class($tags->slug, $tags->term_id);
}
} elseif ( is_page() ) {
$classes[] = 'page';
$wp_query->post = $wp_query->posts[0];
setup_postdata($wp_query->post);
$pageID = $wp_query->post->ID;
$classes[] = 'page-id-' . $pageID;
if ( $wpdb->get_var( $wpdb->prepare("SELECT ID FROM $wpdb->posts WHERE post_parent = %d AND post_type = 'page' LIMIT 1", $pageID) ) )
$classes[] = 'page-parent';
if ( $wp_query->post->post_parent ) {
$classes[] = 'page-child';
$classes[] = 'parent-pageid-' . $wp_query->post->post_parent;
}
if ( is_page_template() ) {
$classes[] = 'page-template';
$classes[] = 'page-template-' . str_replace( '.php', '-php', get_post_meta( $pageID, '_wp_page_template', true ) );
}
} elseif ( is_search() ) {
if ( !empty($wp_query->posts) )
$classes[] = 'search-results';
else
$classes[] = 'search-no-results';
}
if ( is_user_logged_in() )
$classes[] = 'logged-in';
$page = $wp_query->get('page');
if ( !$page || $page < 2)
$page = $wp_query->get('paged');
if ( $page && $page > 1 ) {
$classes[] = 'paged-' . $page;
if ( is_single() )
$classes[] = 'single-paged-' . $page;
elseif ( is_page() )
$classes[] = 'page-paged-' . $page;
elseif ( is_category() )
$classes[] = 'category-paged-' . $page;
elseif ( is_tag() )
$classes[] = 'tag-paged-' . $page;
elseif ( is_date() )
$classes[] = 'date-paged-' . $page;
elseif ( is_author() )
$classes[] = 'author-paged-' . $page;
elseif ( is_search() )
$classes[] = 'search-paged-' . $page;
}
if ( !empty($class) ) {
if ( !is_array( $class ) )
$class = preg_split('#s+#', $class);
$classes = array_merge($classes, $class);
}
return apply_filters('body_class', $classes, $class);
}So I guess I could just add this to the code:
if ( bp_is_page( BP_MEMBERS_SLUG ) )
$classes[] = 'members';Etc.
Should I copy this function to functions.php in the template, perhaps rename it, and add the lines for ‘members’ and ‘groups’ etc.?
Or should I aim for a shorter function that only adds something to what this code generates? Would that be possible?
Trying the blunt approach first…
Edit: I’ve tried with that BP_MEMBERS_SLUG line added directly to post-template.php, with $bp in global, but nothing shows up in the body tag.

What am I missing? Is Buddypress bypassing post-template.php anyway? The only class is “directory”.
-
AuthorSearch Results