[@mercime Participant 16 years, 5 months ago]

If you’re still a member, you should get the updated BP-fun theme from the theme authors.

[@mercime Participant 16 years, 5 months ago]

I laughed too, because is_super_admin is already being used in premium wpmu plugin which enabled one WPMU install to create sub-WPMU installs with own domains mapped (instead of usual sub-blogs). i did wonder when I saw the replacment name if decision for choosing is_super_admin was the “path of least resistance” and provided relief to those who used the plugin or maybe it really was just the Superman reference

[@mercime Participant 16 years, 5 months ago]

Thank you Andy for the reassurance.

I just saw last night that they deprecated is_site_admin() and replaced it with is_super_admin() for WP 3.0 … egads, I hope the search and replace works for me in customized stuff …

[@mercime Participant 16 years, 5 months ago]

WPMU 2.9 trunk, BP 12 trunk, internal bbPress intstall

.

1. In Forum – Group Forum Topic – Edit Topic

I can edit Topic Title, Content but nowhere to add/delete Tags of any topic. Just noticed it now that Tag edit was not available when I needed to add some tags to a forum post. Checking BP 1.1 beta folder, I now see I lost that functionality way back when i moved from external bbPress to internal forum in 1.1 beta

– Will form for editing tags be brought into Edit Topic Page in stable 1.2?

In the meantime, I have copied the edit.php from bp-default/groups/single/forum/ to my child theme and added the template tag to edit tags.

2. Groups Directory page shows “There were no groups found.” when there are groups in this install.

– Possibly because bp-default theme is still in construction?

Groups Directory page in child theme of bp-sn-parent is showing up the Groups listed in that page.

Thank you.

[@mercime Participant 16 years, 5 months ago]

Thank you DJPaul. That’s cool.

This worked for me only when the blogs tested used “BP-ready themes” or child themes of either bp-default or bp-sn-parent, which was to be expected.

Cheers.

[@mercime Participant 16 years, 5 months ago]

Bowe may be referring to this …

The issues with white screens will probably be because I’ve removed all deprecated code from BuddyPress. I’ll be supplying a backwards compatibility plugin that can be enabled on a site so old code can be supported.

From testbp.org

[@mercime Participant 16 years, 5 months ago]

And BuddyDev.com never claimed to be affiliated with BuddyPress.org And it’s $30 for 3 months. Per Brajesh, it will be released as free plugin within 3-6 months after it comes out. So you’ve got the premium members testing the gallery plugin and Brajesh improving on it before it’s released as a free plugin.

[@mercime Participant 16 years, 5 months ago]

There are two sides of the coin here

– MultiSite does not apply when the owner of a single WP install chooses not to enable the multi-blog feature in WP 3.0 and many won’t. Some would prefer to keep their hosting plan as well. Can’t imagine WP 3.0 multiblog in Yahoo hosting like what I see in WP forums for instance.

[@mercime Participant 16 years, 5 months ago]

Saw the thread about the “baptismal name” for the 3.0 version. My two cents for the branding of the new WP 3.0 – WordPress NW (for network and looks like new too but that’s up to the top honchos so I’m not going to sweat it. But we have to bear in mind that WPMU was not only used for multiple blogs and multiple sites using Donncha’s Domain Mapping plugin only.

I’ve also used WPMU as CMS for associations/organizations and the subblogs are used for mangement of either Departments or Sections areas including “Job sections” or “Prayer sections” – where each Admin/Editor is accountable for maintaining such, among other great things you can do with WPMU.

Looking at some of the changes in the merge specially with deprecating WPMU functions I see that it would be easier to upgrade single WP installs to WP 3.0 (as should be the case) than it would be upgrading WPMU installs to WP 3.0. – specially the WPMU installs with many customizations in frontend and backend including plugins hooking in wpmu_ (ouch!), tell me it ain’t so

[@mercime Participant 16 years, 5 months ago]

Facebook Connect is not working with BuddyPress trunk version so I had to delete it, but it worked in BP 1.1.3 set up in subdomain structure. Some couldn’t get it going on subdomain install but went well with subdirectory install of WPMU. Those are only some variables which might affect the install of the FB connect plugin..

“Connect URL in the application settings editor”

– somewhere in Facebook Config Page, 2nd step or so, make sure you have something like this:

Connect URL: http://yourbuddypress.com

Base domain: yourbuddypress.com

Maybe someone has gotten it to work with trunk already. Good luck.

[@mercime Participant 16 years, 5 months ago]

https://buddypress.org/forums/topic/when-asking-for-support

[@mercime Participant 16 years, 5 months ago]

Code in bp-custom.php is applied sitewide unless the function specifically targets certain blog/s much like if a MU-compat plugin is placed in mu-plugins folder. If you put the code in functions.php, , it would only affect only the blog using that specific theme. As of 1.2 bleeding, my bp-custom.php is still working sitewide.

[@mercime Participant 16 years, 5 months ago]

Bookmarked “Design Hell”, thanks David. Will be showing that to new clients even before they sign on dotted line. That’s why there needs to be a contract outlining scope of project among other things. Upgrades, design changes after specs have been approved, and other add-ons need additional payments – unless it’s a pro bono project where you have the option to bow out of the project or hand it over to someone else

[@mercime Participant 16 years, 5 months ago]

With BuddyPress being used now by/for different interest groups from colleges to niche organizations to purely social networking, etc. there is no doubt that there would be different opinions regarding importance of the friends component vis-a-vis groups component.

I’m surprised in the first place that the friends component could even be considered for deprecation since that’s a popular feature. How about a switch to enable or disable the friends component? In one install, e.g. for a professional organization, they don’t need “friends” and prefer “groups.” In another install, for a social club, they’d like “friends” and “groups.”

It would be great if we see categorization of friends (as Bowe mentioned above) as it makes a lot of sense and extend it so that you could send a message only to Friends-Family or send a message only to Friends-CollegeBuds.

However, should the friends component be deprecated, I would request devs to expand Groups component with a user function to have the ability to privately categorize the people within a Group he/she belongs. e.g. Group-Hiking-Friends, Group-Hiking-Pros, Group-Hiking-CollegeBuds, Group-Hiking-NeedsMoreTraining.

[@mercime Participant 16 years, 5 months ago]

@David Lewis – sorry about that, didn’t notice that there was a new custom header with options page in the trunk bp-default theme because I customized the header in my child theme

[@mercime Participant 16 years, 5 months ago]

Hi David. Works for me in all BP child themes. I presume you cleared cache/cookies and are targetting the correct selector , so

:

1. If there is !important after the background image url in parent theme, add it in your declaration in child theme – none !important

2. an alternative: create blank 1×1.gif file and use that for your background url(images/1×1.gif) to override parent theme

[@mercime Participant 16 years, 5 months ago]

#header { background: #f76d16 none; }

where “none” will equate to no background image in the child theme; it overrides

url(../images/default_header.jpg);} in parent theme. Works across all browsers.

[@mercime Participant 16 years, 5 months ago]

switch_to_blog — when abused to get numerous queries from other blog/s, or get all widgets of the main site’s sidebar, or get sets of posts, etc — is going to be a “slow function” to run. But when used for main navigation which has what, 5 to 8 links, switch_to_blog runs in a split second wherever it is placed – I just prefer to place my main nav in header.php.

If one is wary of switch_to_blog “overhead” for navigation, then easiest method is to look at source code of main site’s navigation and copy the navigation links there and paste to sub-blogs theme’s header.php or wherever they want to place it. Caveat to this method is, you’ll miss the automatic generation of new links when new plugins/components hook to bp_nav_items. This won’t happen when you use switch_to_blog and add restore_current_blog after the bp_nav_items block.

[@mercime Participant 16 years, 5 months ago]

1. If I remember right, Jeff’s BP Privacy Options Plugin will allow the user to make profiles private. Just need to wait for the plugin upgrade for BP 1.2

2/3/5A. cosmic buddy theme – I would suggest asking Brajesh, the theme author about how to do that

5B. Yes you can create a Sitewide/global navigation bar in your blog’s themes, by using WPMU’s native switch_to_blog and restore_current_blog functions. Therefore, if you want the navbar of main site (blog_id_1) to be shown in you sub-blogs, you add the code below to your blog’s theme’s header.php

<ul id="nav"

<?php switch_to_blog('1') ?>

//copy the code from header.php of either bp-default/bp-sn-parent theme

//or the code used in main site plus any customized links you added in main site

<?php do_action( 'bp_nav_items' ); ?>

<?php restore_current_blog(); ?>

</ul>

You’ll get the correct URL’s which point to main site’s respective BP components.

[@mercime Participant 16 years, 5 months ago]

WPMU trunk-r2041 and BP trunk-r2222

Can’t Create Blog

– had to go in again and do the bp-core > bp-core-adminbar.php fix of 1stAngel to make it work.

[@mercime Participant 16 years, 5 months ago]

I’ve always used the subdomain structure myself.

However, I can see the logic of recommended subdirectory structure for BP – you could install BuddyPress in the main blog OR in a subblog (e.g. blog_id_2) instead of the main site.

e.g. if BP installed in sub-blog, http://mysite.com/members/ . When your members create a blog, the URL would look like this – http://mysite.com/members/username/

On the other hand, using subdomain structure, right now you have to install in main site (blog_id_1) http://mysite.com/ so that when your members create a blog, the URL would look like this – http://username.mysite.com

Otherwise, if you install in a sub-blog at blog_id_2 or blog_id_3 etc e.g. http://members.mysite.com , when users create a blog, URL would look like this http://username.members.mysite.com – arggh.

[@mercime Participant 16 years, 5 months ago]

“able to create users, install plugins and themes, etc.”

That would be a WPMU function. Go to your dashboard – Site Admin > Options and go down the panel to Administration Settings – Site Admins and add the username of person you want to add as Site Admin. Be aware that the other Site Admin can kick you out of the install

[@mercime Participant 16 years, 5 months ago]

The bp-default and bp-parent-themes are theme frameworks for the BuddyPress plugin. They show what can be done with the BuddyPress plugin and I appreciate that a lot.

For a current project with WPMU as CMS plus BP for an organization, I went with creating a customized child theme using the bp-sn-parent throughout the site including all blogs for a consistent look and feel.

Aware of the time I could allocate for this project and my average skillset, creating a child theme was the path of least resistance during continuous trunk upgrades of WPMU and BP since I started this project late September for a tentative launch mid to late January. And I would say the time I invested in creating customized child themes was worth it, 10x over.

At this time, all I have to watch for in my child themes are code changes in the files from upgraded parent themes – header.php, footer.php, sidebar.php, home.php, functions.php, style.css, and some new page templates I created.

When the new bp-default theme came out for BP 1.2 trunk, I made a new child theme based on that for blog_id_1 (BP install) specifically because of the new forums layout My only question for the new bp-default parent theme is:

why is it that the only way I could find to avoid getting a white screen when I activate my bp-default’s child theme (with own home.php) is by consistently copying the code of bp-default/activity/index.php over bp-default/home.php ?

[@mercime Participant 16 years, 5 months ago]

https://wordpress.org/showcase/flavor/buddypress/

Maybe developers of those sites can be contacted or interviewed to give more info.

[@mercime Participant 16 years, 5 months ago]

Andy said he will be looking into that per this this thread in testbp.org