[@burtadsit Participant 17 years, 10 months ago]

@gogoplata wonderful! Glad to hear a forums success story once in awhile.

[@burtadsit Participant 17 years, 10 months ago]

the fate of the universe hangs on the results of this thread and she’s making popcorn.

[@burtadsit Participant 17 years, 10 months ago]

ok. ya. it works better if im just talking to myself.

[@burtadsit Participant 17 years, 10 months ago]

(sigh) she did it again…

There is also one for groups directory in ../bp-groups/css/directory-groups.css

[@burtadsit Participant 17 years, 10 months ago]

Do you have irc? We keep posting around each other. Go to #buddypress on irc.freenode.net server. That will work better.

[@burtadsit Participant 17 years, 10 months ago]

This is the members directory you are talking about? The css for that is in:

/wp-content/mu-plugins/bp-core/css/directory-members.css

Exactly what are you two doing? Creating a new home or member theme skin or skinning the css so that it works within a standard wp theme?

[@burtadsit Participant 17 years, 10 months ago]

I’m confused. We got 2 themes to work with here. The members theme and the home theme. Both have the ability to be skinned through the use of a custom.css file that overrides all css in bp for that theme. That theme only.

Each theme has a seperate custom.css file. One in the member theme area and one in the home theme area.

Everyone agree on that? This is what we’re working with right? Which theme are you two working on?

[@burtadsit Participant 17 years, 10 months ago]

lol. Ok, I kinda get what the hack is supposed to do and you can do the same style of thing in the /bp-core/bp-core-activation.php file. It contains the bp replacement functions that mu normally does. Some of the functions are also in bp-xprofile-signup.php.

That post is kinda confusing as to what to modify and where. I get the gist though. Telling someone else how to modify a bunch of functions and why they are doing it isn’t real easy. It’s hard to be clear.

Have fun.

[@burtadsit Participant 17 years, 10 months ago]

Boy are you *not* living in reality wardeh. I’m a noob with a text editor and the desire to know how bp, mu and bbpress work.

Lemme go look at that hack you mentioned.

[@burtadsit Participant 17 years, 10 months ago]

Lemme take a look at that area.

Yep, bp does snag the ‘wpmu_signup_user_notification’ event and doesn’t allow mu to do it’s thing. Looks like bp takes over the email to the user with the user’s activation link. Sorry, I just thought bp just added some xprofile stuff.

Wonder why it traps the email activation to the user? Gonna go look.

[@burtadsit Participant 17 years, 10 months ago]

bp just relies on the mu registration and login stuff wardeh. It adds a few fields by hooking some wp things to add extra profile info but it relies on the settings in site admin > options for ‘allow new registrations’. Thems the standard options in mu. Anything else is a mod or plugin.

If it works for mu (the moderation plugin you found) then it works for mu/bp. Any mu or wp plugin should work for ya. Unless there is some bizarre conflict with bp which I haven’t run into yet.

bp is just another mu plugin like all the rest. Well, more wildly cool and useful than all the rest, but it’s still YAMP. (Yet Another Mu Plugin)

[@burtadsit Participant 17 years, 10 months ago]

Any css you put in custom.css overrides *all* css. Unless groups css is being loaded after custom.css and in that case it’s a bug and should be reported in trac. Don’t think it is though.

Example:

ul#group-list li, ul#member-list li, ul#blog-list li, ul#comment-list li, ul.item-list li { background: url(../images/message_thread_back.gif) top left repeat-x;}

That’s in ../member-themes/buddypress-member/css/groups.css. In your custom.css file you can change the ‘message_thread_back.gif’ to something else by overriding it in custom.css

ul#group-list li, ul#member-list li, ul#blog-list li, ul#comment-list li, ul.item-list li { background: url(../images/my_fav_message_thread_back.gif) top left repeat-x;}

This what you need?

[@burtadsit Participant 17 years, 10 months ago]

function site_url() is a mu 2.6+ thing. I saw a post from you about what ver mu for buddypress. The answer is 2.6+.

[@burtadsit Participant 17 years, 10 months ago]

Are you running on a shared host or a dv?

[@burtadsit Participant 17 years, 10 months ago]

Thanks Andy. I tuned in at the tail end of things when they were putting chairs on tables and sweeping the floor.

[@burtadsit Participant 17 years, 10 months ago]

Ya, my prob wasn’t media temple. It was me. I didn’t realize that /etc/hosts was consulted first when looking up an ip address. Thought it all went thru a name server. So it was finding a generic 127.0.0.1 address for my domain. First, and using it of course. Just stupidity on my part.

[@burtadsit Participant 17 years, 10 months ago]

Thanks, I can’t access your group avatar file directly and I should be able to. I’m getting the mu login form. If your configuration is right I should just be able to view your group avatar with the full url to it. I can’t.

If I can’t get to it then neither can bp.

[@burtadsit Participant 17 years, 10 months ago]

I think he’s talking about *how* domain names get resolved on a shared hosting provider. I ran into problems with domain resolution on my DV. In my case it was just a matter of changing the /etc/hosts file. Since I don’t know what I’m doing in root, it took days to figure out what I needed to change to get xmlrpc working.

I think he’s saying that domain resolution on a shared host can be difficult to control by the user. Me or you as the user on a shared host. Simply because I have a domain hooked up to an ip address doesn’t mean that I have control over *how* that ip address is determined.

1. Lookup ip here in the internal net of the shared provider

2. Lookup ip there in the provider’s name servers

(Return the first ip that I find above)

I think what he’s saying is that the above process will not return the correct ip for the low level stuff that is happening in xmlrpc.

I’m just kinda hazy at the moment as to why the internal ip address is not valid for xmlrpc.

[@burtadsit Participant 17 years, 10 months ago]

What versions of mu, bp are you using?

Is this from the home theme?

Is this from the member theme?

[@burtadsit Participant 17 years, 10 months ago]

I prob have mult posts up there. bbpress flaking out this morn.

[@burtadsit Participant 17 years, 10 months ago]

You seem to have mu configuration problems. None of your subdomains can be reached. It’s best to get mu setup, configured and working properly before installing bp. Test mu blog creation and reachability, create and edit posts, make comments. Get comfortable with mu first.

It will make installing and configuring bp a whole lot easier. I played with mu for a month before I felt comfortable with it.

What type of host are you on? Shared, DV? Looks like you need to do some DNS tweaking for your subdomains to work.

[@burtadsit Participant 17 years, 10 months ago]

You seem to have mu configuration problems. None of your subdomains can be reached. It’s best to get mu setup, configured and working properly before installing bp. Test mu blog creation and reachability, create and edit posts, make comments. Get comfortable with mu first.

It will make installing and configuring bp a whole lot easier. I played with mu for a month before I felt comfortable with it.

What type of host are you on? Shared, DV? Looks like you need to do some DNS tweaking for your subdomains to work.

[@burtadsit Participant 17 years, 10 months ago]

I can duplicate a problem like yours on windows but not on linux.

What version of buddypress is everyone in this thread using?

[@burtadsit Participant 17 years, 10 months ago]

@bloggerhistory Check the permissions in /wp-content/themes/buddypress-home/css

Those 3 files and the css dir should be 755.

[@burtadsit Participant 17 years, 10 months ago]

The (admin) thing is the role that user plays on that blog. A user may have multiple roles on different blogs. It annoyed me too so I took it out.

/bp-core/bp-core-adminbar.php line #137, $role, get rid of it. I was hoping somebody would complain about it.