Forum Replies Created
-
In reply to: BuddyPress Dev Chat –
Bumping this up -^-^-
In reply to: Problems with BuddyPress permalinksYou might just need to re-run Dashboard > Settings > Permalinks and save to other than default. Also, BP 1.2.4.1 does not fully support WP 3.0 yet. Upcoming BP 1.3 will.
Thank you @nuprn1 – “bookmarking” it now
In reply to: BuddyPress.org Changes: (Action Plan)Re: blog tracking – I may have overlooked something, but I recall that once you’re a member of BP community in main site or where BP is defined in install, you already have one blog counted in the site. And when a member creates a blog within the install, the member has now two blogs to his/her credit.
So wouldn’t it be logical to have `if ( bp_blogs_total_blogs_for_user() == 1 )` instead in the function?In reply to: Guestbook for User-Profile ?@erich73, you’re welcome. Do share how it’s working with you in WP 3.0
In reply to: Is bp dying a slow death?In line with the topic @anointed started a week++ ago, methinks that BP is facing a big mountain made of different WP/MU versions and making it work for all. In that line, might I suggest that Automattic allow @apeatling to concentrate on BuddyPress and be more informative about the direction of BuddyPress – less surprises the better

At this time, with BP 1.2.4.1, there are at least 11 configurations of WP/MU versions to make pretty with:
New Installs
1. WP 3.0 (Single site)
2. WP 3.0 (Multisite – Subdomain)
3. WP 3.0 (Multisite – Subdirectory)
Existing Installs
4. WP 2.9.2
5. WP 2.9.2 upgraded to WP 3.0 (Single Site)
6. WP 2.9.2 upgraded to WP 3.0 (Multisite – Subdomain)
7. WP 2.9.2 upgraded to WP 3.0 (Multisite – Subdirectory)
8. WPMU 2.9.2 Subdomain
9. WPMU 2.9.2 Subdirectory
10. WPMU 2.9.2 Subdomain upgraded to WP 3.0 (Multisite auto)
11. WPMU 2.9.2 Subdirectory upgraded to WP 3.0 (Multisite auto)Notes:
a. Add Server/OS to the mix – Windows, Linux, shared hosting vs VPS hosting, etc.
b. Add configuration where BP is installed in subsite other than main site
c. Add single WP configs (per wp.org forums) where WP is in directory and index.php in root – have to tell them whether that config will work with BP at all or not.
d. Media uploads – WP 2.9.2 and new WP 3.0 (main site) installations upload media to wp-contents/uploads folder while WPMU 2.9.2 and WP 3.0 (subsites) installations upload media to wp-contents/blogs.dir folder. Member and Group Avatar uploads – same as above (a) but in respective /avatars/ and /group-avatars/ folders.
e. Many plugin and theme developers would rather wait for BP 1.3 where components will be rendered as Pages so that time won’t be wasted on plugin or theme development which will be considered “obsolete” in a few weeks or so, pretty much like what happened to plugins and themes from BP 1.1.3 to BP 1.2
e. I’m sure many would be able to add some more here, etc. etc. etc.So when BP 1.3 rolls out and it requires WP 3.0, there’ll only be six configurations left from above list as per a thread I read not to expect WP 3.1 anytime soon. Add to that the major changes in how BP renders components as Pages which mixes with “regular” WordPress Pages, BuddyPress has become a test of endurance that requires a lot of willing developers to go through the angst of getting a BP site just as one wants it for specific installation. Otherwise, Elgg or Drupal or phpFox et al would have been installed in the first place. Just my 2 cents.
In reply to: Guestbook for User-Profile ?@erich73, have not tested this with WP 3.0 but @sbrajesh has a free plugin for BP 1.2 – The bp-wire for putting the Buddypress wire back to Buddypress 1.2 or method by which you could Use Activity as Wire as well
In reply to: How to get users to post blogsNing defines blogs differently than how we at WordPress/BuddyPress do. A Ning site member can click on a link “Blog” and Ning’s post panel. You can try using Jet QuickPress – https://wordpress.org/extend/plugins/jet-quickpress/ which adds “a “Quickpress” submenu you can find in bp admin bar > My Accounts > Blogs > QuickPress from which you can easily add a post to any of your blogs
Just a thought: the plugin, in effect, can render a Multi-Author BP site without adding subsites and without allowing access to the dashboard because members can post from the front and click on categories and add tags there as well. Then, one can create a customized member profile page to have that link to blog posting and then render the latest posts of each individual member .
In reply to: Make admin bar take its own space and stay staticadd top:0; to @r-a-y‘s snippet
#wp-admin-bar {position:absolute !important; top: 0; }In reply to: Header Too Low in SafariThe URL you gave leads to subsite with the old WordPress default theme. Going to your main site with bp-default theme, there’s no big gap at top of the page using IE 6/7, Safari 4.0.4, and Google Chrome.
@rossagrant I have WP 3.0 and BP 1.2.4.1 and clicking on another member’s avatar or display name goes to their profile not mine. Maybe a factor or not, but my WP 3.0 install was and upgrade from WPMU 2.9.2 subdomain structure.
EDIT – thanks @r-a-y, curious now if that happened to new WP 3.0 installs and/or to child themes which don’t already have own header.php and sidebar.php files.
just delete blogs.php file from wp-content folder in your server, then you can run yoursite.com/wp-admin/upgrade.php script or dashboard > upgrade
In reply to: User signs up from blog, gets removed from main blog@holgria – don’t know what WP/MU version you’re using … dsader’s code below from mu.wordpress.org forums is working for me in WPMU 2.9.2 (subdirectory and subdomain structures) placed in mu-plugin folder
http://wordpress.pastebin.com/7dcWBXtp
As always, backup your DB first.In reply to: The Chemistry Book@LPH2005 good see you’ve fixed the headers already sent error earlier. I just checked out ExamView and and it looks like a great add-on for a school site. Thank you

EDIT – per your 1st post re suggestions:
1. Changing too-wide login to horizontal login under header – here’s some HTML and CSS you could try – adjust accordingly or let me know if it needs some tweaking
2, The right column looks good in home page but takes over content space which is more important imho in the inside pages.In reply to: The Chemistry Book@LPH2005 Cool. What did you use to embed the Practice Tests at http://www.thechembook.com/practice-tests/ and what application did you use to create the tests? I’m liking it a lot. Just answered some questions and managed to guess some correctly

Probably caught this during your modifications – the link “Chemistry Text” leads to headers not sent page at http://www.thechembook.com/wiki/index.php/TCB:_Chemistry_Online_Textbook
Unless otherwise specified, BP will install in main site when you activate it. In order for BP to work in subsite, you have to add the following to your wp-config.php file
define ( ‘BP_ROOT_BLOG’, $blog_id );so if you want to install BP in site2, then do this
define ( ‘BP_ROOT_BLOG’, 2 );@DJPaul – I understand. However, having tested in dev installs to WP 3.0 RC2 and not getting the smooth experience I have on WPMU 2.9.2 with BP 1.2.4.1 and with all preferred BP plugins working; I can only recommend using WP 3.0 with BP 1.2.4.1 in test/dev installs and not in production/live installs.
There are 5 ways to test BuddyPress with WordPress 3.0 and I’ve tested four of those configs:
1) WP 3.0 single (new install) – “Page Not Found” for BP components. Preferred BP plugins not working as they have not been upgraded to work with WP 3.0.
2) WP 3.0 multisite subdomain (new install) – “Page Not Found” for BP components. Enable MULTIBLOG renders BP links in subsites to go to home page. preferred BP plugins not working as they have not been upgraded to work with WP 3.0
3) WP 3.0 multisite subdirectory – did not test – I’ve heard that this set up is working for some friends and per posting in WP.org forums
4) WPMU 2.9.2 subdirectory upgraded to WP 3.0 – same as #2 above
5) WPMU 2.9.2 subdomain upgraded to WP 3.0 – same as #2 aboveMaybe I’ll try to test the 4 configs I have for WP RC3 and see what happens this weekend or next.
Full support for WP 3.0 will be in BP 1.3 – https://buddypress.org/about/roadmap/
In the meantime, BP 1.2.4.1 working well in WP/MU 2.9.2In reply to: User blog creation with BuddyPress and WP3Full support for WP 3.0 will be in BP 1.3 – https://buddypress.org/about/roadmap/
In the meantime, BP 1.2.4.1 working well in WP/MU 2.9.2In reply to: “My Favorites” PluginJust “bookmarking” this
In reply to: Pass WordPress login to BuddyPress@seanbaugh What I posted above was for two single WP installs. I have to add that if you’re going to do the above, make sure that the 1st WP install and the 2nd WP install have the same versions. So if existing install is WP 2.9.2, then your second install must also be WP 2.9.2 – can’t guarantee it will work if you use different versions. Just backup your 1st install’s database first if you want to experiment with different versions.
In reply to: WPMU 2.9.2 or WP 3.0 RC2?@pjnu – I would use WPMU 2.9.2. You could already start developing and testing in WPMU 2.9.2./BP 1.2.4.1 where there are many versions-compatible BP plugins to play with. Furthermore, upgrading from WPMU to WP 3.0 is so much easier than setting up WP 3.0 and making it multisite (so many steps). Also, WP 3.0 rc2 with BP 1.2.4.1 is still quirky and many BP plugins do not work with the new set up as Pages will be used in rendering BP components. Just my 2cents to avoid frustration.
In reply to: Pass WordPress login to BuddyPressYour second WP install in subdomain should be installed in the same database (with different prefix) with your first WP install. Btw, backup your database before trying this. So in wp-config.php of the second WP install, just before “That’s it, you can stop editing” you should also add:
define(‘CUSTOM_USER_TABLE’, ‘wp_users’);
define(‘CUSTOM_USER_META_TABLE’, ‘wp_usermeta’);Having said that WP 3.0 is around the corner, when you upgrade you can make your install multisite and define BuddyPress in subsite in subdomain or subdirectory structure, and you have one log-in for members to access both areas.
@jamiewarren09 – ah, I just checked your profile and it seems I answered one thread before …
In any case, it has to do with your theme’s home.php and/or widgets you added in the home page’s widget areas. So you’re using the Church theme of studiopress. So open up home.php file and see if the member’s profile’s hardcoded into it, and if not, go to Appearance > Widgets and remove the possibly random member widget from home area.