[@burtadsit Participant 17 years, 6 months ago]

Or you could use those handy passthrough functions that I wasn’t aware of.

[@burtadsit Participant 17 years, 6 months ago]

No this isn’t solved till we find out what was wrong and how it was fixed.

I’ve spent time on this issue and just blowing it of with ‘I fixed it’ isn’t good enough. I’ve PM’ed stu-art for the source of the problem and the solution.

[@burtadsit Participant 17 years, 6 months ago]

You know I was thinking about this another way Paul. New users need some handholding and encouragement. Perhaps you can detect that a group of users hasn’t met any of those criteria and do something to help things along.

Stick them in a group that others can pay attention to. Everyone knows that forum questions coming from that group should be cut some slack and patiently answered. New users may not feel comfortable asking questions in the main forums/groups. Questions that anyone has in a new environment. We still feel dumb asking them. I don’t feel quite as stupid if everyone in a particular group is as dumb as I am.

New users are eager to share their experience, even if limited, with others. It’s a group of people who fit together.

A ‘Welcome’ group they can graduate from by participating there. It’s 4am here. This might actually sound stupid after a couple of hours sleep. Ah, well. Too late to care.

[@burtadsit Participant 17 years, 6 months ago]

I’ve seen reports of this kind of error before and couldn’t figure out why BP_PLUGIN_DIR was not defined when they are running code that looks for it’s existence. Now I think I get it.

[@burtadsit Participant 17 years, 6 months ago]

BP_PLUGIN_DIR not being defined is a problem with that particular blog not running bp-core.php code where it’s defined. This is the code that is causing the error:

require ( BP_PLUGIN_DIR . ‘/bp-core/bp-core-signup.php’ );

BP_PLUGIN_DIR has to be defined before it gets to functions.php. I don’t think they can be running wpmu 2.7.1 beta and bp RC2.

Trying to run your theme on RC1 maybe?

[@burtadsit Participant 17 years, 6 months ago]

No sorry. I have no idea what those two things do. Who might ‘they’ be and how can ‘they’ just install plugins on your site? Does this sound like a good idea to you?

[@burtadsit Participant 17 years, 6 months ago]

1) What version of bp?

2) Are you using the bp home theme?

Any widget will work in the bp home theme. It’s just a normal wp theme that has places to stick widgets. You can download any number of widgets from the wp plugins directory to place in those widget enabled areas.

The bp home theme displays the recent blog posts for the main blog, if that is where it’s running, under the ‘News’ button.

[@burtadsit Participant 17 years, 6 months ago]

Whatever is going on it’s not the capabilities.php file that is the issue. What version bp and wpmu are you attempting to install. Install wpmu first and get that to run. If wpmu isn’t operating correctly then bp will not.

1) What version wpmu. Specifically wpmu 2.7 or wpmu 2.7.1 beta?

2) How are you configuring wpmu? subdirectory, or subdomain?

3) Are you installing wpmu in a subdirectory of the document root or in the document root?

4) When does this error occur?

5) Can you create blogs in wpmu and reach them?

6) Does creating new blog posts in each blog work and can you pull them up and view them?

7) Is this shared hosting or on a DV?

Have things been working all along just fine and now this error for no apparent reason?

9) Disable all plugins and try doing whatever it was that lead to this error. Does the same thing happen.

10) Disable buddypress and try doing whatever it was that lead to this error. Does the same thing happen.

We could use some more details.

[@burtadsit Participant 17 years, 6 months ago]

/buddypress-member/profile/profile-loop.php shows usage of the xprofile template tags.

[@burtadsit Participant 17 years, 6 months ago]

First it would be nice to know what version of bp you are using. The latest trunk has lots of template functions and a new template class for the xprofile component.

Frankly the profile component is complicated in that it uses three tables to organize and get access to profile field data. Fields are accessed first by field group then field id then field value.

I don’t think that anyone is going to waste time on a detailed tutorial for RC1 code. Look at the following files and you’ll get an initial idea of how to access the profile fields.

/bp-xprofile/bp-xprofile-templatetags.php

/bp-xprofile/bp-xprofile-classes.php

With the template tags file being the most useful probably and the classes showing you how things are organized.

[@burtadsit Participant 17 years, 6 months ago]

If you upgrade your theme to the version that is in RC2 you can take advantage of the new member template functions that are available to you. The directories now have their own little templates located in /buddypress-member/directories/<directorytype>/<directorytype>-loop.php file.

Then all the template tags you find in /bp-core/bp-core-templatetags.php are available to you. That particular function you were using doesn’t exist anymore. The underlying call still works which is:

BP_XProfile_ProfileData::get_value_byfieldname( $field, $user_id );

so

BP_XProfile_ProfileData::get_value_byfieldname( ‘One Line Summary’, $user->user_id );

Should work. I encourage you to look at the new directory code and templates.

[@burtadsit Participant 17 years, 6 months ago]

You might want to investigate the use of class BP_Core_Members_Template also. Lots more flexibility there. /bp-core/bp-core-templatetags.php. However you’ll have to build your own output format and use the loop tags for that template.

There is also javascript that rules what’s going on in the members widget: /bp-core/js/widget-members.js

Also a css class=”selected” in the html output of the widget. Gotta take all into account and tie them all together.

[@burtadsit Participant 17 years, 6 months ago]

It gets the active members but the selected class is off on the active | popular | newest. It says not recently active as well

What does the above mean?

[@burtadsit Participant 17 years, 6 months ago]

Are you using the wpmu 2.7.1 beta and bp trunk? The error leads me to believe one or the other isn’t so. See in here: https://buddypress.org/forums/topic.php?id=2190 there’s a post about getting the most recent bp and wpmu.

You might want to talk to the theme author. Perhaps they have seen this error in relation to the theme before.

[@burtadsit Participant 17 years, 6 months ago]

Instead of talking, which we don\’t seem to be nicola created this while we were arguing on irc: http://buddypress.pastebin.com

I’m using that until whatever happens, happens. I started it with wpmu to wp abstraction functions. Functions that exist only in wpmu but have wp counterparts: get_blog_post($blog_id, $post_id) gets implemented as get_post($post_id). Things like that.

[@burtadsit Participant 17 years, 6 months ago]

It’s up to you of course Roger. There have been quite a few changes since RC1. Lots of new capabilities, you’ll have to run wpmu 2.7.1 beta. bp 1.0 is going to be out shortly here and the forums are going to get kinda nutty.

It might be best to upgrade now instead of after 1.0 and get your eventual problems solved now. Heads up.

[@burtadsit Participant 17 years, 6 months ago]

Roger that fn I wrote was 3 months old. Things have changed in bp. All you need to do is add a filter to change the logo now.

see: https://buddypress.org/forums/topic.php?id=1969&replies=2#post-10463

Sorry for the late reponse. Your post got ‘spammed’ by akismet because of number of links in the post. The plugins in /mu-plugins don’t need a plugin header like that. Your code will translate better in the forums with backticks before and after.

[@burtadsit Participant 17 years, 6 months ago]

Failed opening required ‘BP_PLUGIN_DIR/…

Not using latest trunk because BP_PLUGIN_DIR is not defined or just installed in some fashion that bp-core.php isn’t running on all blogs which means the latest 2.7.1 wpmu isn’t running and the bp plugins aren’t sitewide.

maybe so?

[@burtadsit Participant 17 years, 6 months ago]

Well, hell Andy. Where did all these template classes come from all of a sudden? Maybe I’m just noticing them. Looks like as soon as you say:

bp_has_<component type>() a template class is instantiated and we get an instant <component type> loop. I see them for all the components. That’s going to make creating and extending themes pretty easy.

Look in each component directory in the bp-<component>-templatetags.php file

Have I just been so buried in other stuff I never noticed them?

[@burtadsit Participant 17 years, 6 months ago]

The bp widgets aren’t designed to be called from templates. They don’t pay any attention to parameters passed to them yet.

[@burtadsit Participant 17 years, 6 months ago]

No I don’t see the problem. If there is a problem, only logged in users can see it. Can you give me a demo/test login username and password?

[@burtadsit Participant 17 years, 6 months ago]

Well, change what field? The user Full Name field?

[@burtadsit Participant 17 years, 6 months ago]

andrea_r seems to be on this one djpaul. https://mu.wordpress.org/forums/topic.php?id=12086

[@burtadsit Participant 17 years, 6 months ago]

That’s r1350 of the bp trunk

[@burtadsit Participant 17 years, 6 months ago]

I can usually recommend some solution that doesn’t require modifying the core. In this case I just can’t. It looks to me like the only way to get years beyond 2009 is to do this:

/buddypress/bp-xprofile/bp-xprofile-classes.php

Line # 567 is:

for ( $i = date( ‘Y’, time() ); $i > 1899; $i– ) {

Change that to:

for ( $i = date( ‘Y’, time() ) + 5; $i > 1899; $i– ) {