[@burtadsit Participant 17 years, 10 months ago]

The standard text widget strips out code and only allows ‘approved’ html. Anything other than basic html in posts and widgets is going to be stripped. Can’t have just anybody putting active code all over the place now can we? Security thing. WP thing.

[@burtadsit Participant 17 years, 10 months ago]

Howdy Vida. I don’t know if you are ‘off’ or not but perhaps your installation and configuration isn’t exactly ‘on’ yet.

Did you upload a custom avatar? Tell us what’s in your apache error log.

[@burtadsit Participant 17 years, 10 months ago]

The 404s when logging out indicate some kind of configuration problem. How do you have mu installed? Can you do all the normal things like create a new blog and access it? Post articles on your non-home blogs? View them again?

Is everything working ok except the logout?

[@burtadsit Participant 17 years, 10 months ago]

I stuck that ticket in there as part of something else then forgot about it. Normally I fix things I find but got sidetracked with other things. Feel free to track it down and fix it.

[@burtadsit Participant 17 years, 10 months ago]

@elishahong The logout redirects the user to the blog they are on when they logout, not the home blog. This is not a bug. It’s normal behavior.

[@burtadsit Participant 17 years, 10 months ago]

Mornin’ wardeh! @martin47 this is ‘our’ tool. Andy built it for ‘us’. The boys and girls at Automattic are letting us play with it. Us includes you.

[@burtadsit Participant 17 years, 10 months ago]

Trent’s got WP schwag! Is it swag, shwag or schwag?

[@burtadsit Participant 17 years, 10 months ago]

The above instructions on how to ‘solve’ the whacky chars and format stripping that is going on is just a stopgap solution really. We need to filter the text that goes into a post and that comes out of a post. We need to filter the text coming over and going to bbpress.

We need that. This stuff is in core and we shouldn’t be screwing with it like this. I’m gonna just create a ticket that outlines the problems with text i/o in and around bp, mu and bbpress.

The bbpress side of things needs some additional filtering. When stuff comes thru xmlrpc lots of things are escaped out and they are going directly to the db like that. Bad. Then when they come back out and get sent to bp, bp un-escapes them on this side. That leaves those of us who use bbpress as bbpress with trash in the db from the xmlrpc transport.

Gotta fix that too.

[@burtadsit Participant 17 years, 10 months ago]

@elishahong Can you explain where this logout link is? Home theme, member theme, admin bar… Exactly where does it take you and what version of mu are you running?

[@burtadsit Participant 17 years, 10 months ago]

What I usually do is have several browser tabs open at the same time. One where I’m working, perhaps editing a blog article and one for nav and tooling ’round.

[@burtadsit Participant 17 years, 10 months ago]

Howdy. This is a know bug running on windows. Patience. I have the same problem with my dev windows box.

[@burtadsit Participant 17 years, 10 months ago]

Oh ya. In my travels for the above, I found the magic little function in bbpress for magic links:

bb-includes/functions.wp-core.php

function make_clickable()

line 274

I gladly stole it, copied it over to my favorite php file today ‘bp-forums-filters.php’ renamed it my_damn_make_clickable() and hooked it up to the bp universe with this underneath it:

add_filter( ‘bp_the_topic_post_content’, ‘my_damn_make_clickable’);

We got bbpress magic urls in posts!

You of course would want to put that fn in a little utility plugin that runs in mu-plugins.

[@burtadsit Participant 17 years, 10 months ago]

Hey Mike. bp does a whole bunch of filtering before the post is sent to bbpress. About 1/2 dozen wp filters, then some bp filtering then it gets sent to bbpress. There is the bp helper plugin over on the bbpress side that does some more filtering, bbpress gets it finally and stores it. Evidently xmlrpc doesn’t want normal <> type tags so they get stripped out, replaced with [] tags instead for the trip to bbpress. To be replaced on the bbpress side with normal <> tags. Evidently we can’t have special chars such as single quotes, double quotes, ampersands and other things making the trip so bp escapes or converts them to something else for the xmlrpc trip.

When these whacky little escaped and converted chars get to bbpress they are just stored.

Viewing a bp created post in bbpress is ugly.

But we’re not in bbpress were in bp where when we send our post from bp to bbpress it gets the post from bbpress unconverts, unfilters and unescapes all that stuff to display as the post we just sent.

During this process the html markup that should be allowed like paragraphs and bold are stripped out somewhere along the line for display in bp even if they have successfully made this round trip unscathed.

Now we’re gonna talk about excerpts which have another filtering process applied to them. No we’re not. No I’m not. If you really care, which I don’t anymore, after 4 hrs of tracking this wp action, filter insanity across two pieces of software and several transport mechanisms then you could:

Comment out line: 741 in bp-core.php bp_create_excerpt()

‘strip_tags()’

Comment out line: 41 in bp-forums-filters.php bp_forums_filter_decode()

‘wp_filter_kses()’

You get excerpts in group forums and posts in group forums that look normal. You could probably copy these fns and do the approved action/filter thing. You could. I personally take great pleasure in deleting the offending lines at this point.

[@burtadsit Participant 17 years, 10 months ago]

It’s difficult to really determine this but from what I can gather about what you are trying to do

You are trying to get mu installed in a subdirectory called /blog/blogs under the document root of a live, existing wp 2.6.5 install.

The existing live install has the it’s domain mapped to /blog (not /blogs) where the wp 2.6.5 actually resides.

I didn’t see any evidence of buddypress so you must have been successful in uninstalling it while you get mu up and running.

It looks like you have chosen the subdirectory install option for mu.

Is all this guessing right? I don’t know. I hope your live site stays up and running throughout this and I look forward to you reporting back with success.

[@burtadsit Participant 17 years, 10 months ago]

There’s no admin bar in the login form no.

I’m not sure what email link you are referring to. After signing up a user gets an email with an activation link and then a password and then logs in with a temp password to their blog.

To get to the admin backend (dashboard) of any blog you use: myblog.mysite.com/wp-admin/ or after logging in, the user has the option of using the menu bar’s ‘my blogs’ > ‘my new blog’ ><flyout menu> ‘dashboard’

That’s also the admin area of the blog.

There isn’t a ‘bbpress bar’ that I’m aware of. There’s a buddypress bar that has a ‘my account’ menu where you can visit your profile and other options.

[@burtadsit Participant 17 years, 10 months ago]

I’m kinda guessing you are talking about getting bbpress and mu configured to share user tables and sessions.

https://mu.wordpress.org/forums/

https://bbpress.org/forums/

EDIT: the above was also posted in what seemed to be a topic at random on the bbpress forums.

[@burtadsit Participant 17 years, 10 months ago]

Evidently not. Why don’t you post the specifics of your install. Is this wire in profile or groups?

[@burtadsit Participant 17 years, 10 months ago]

The theme has to call wp_footer() for the bar to display. If you are running wpmu 2.7 trunk then you have to disable the mu admin bar if you want to see the bp admin bar. It’s one or the other.

[@burtadsit Participant 17 years, 10 months ago]

You seem to have solved your problem. It’s showing now.

[@burtadsit Participant 17 years, 10 months ago]

wardeh, sorry it took so long to get back to you. Been busy. From what I gather all wpmu and bp functions are available. However none of the actions and filters on the mu side are in effect. I’m still not sure what that means. Just something I’ve read.

I don’t know if this deep integration is even what I want. I know it’s problematic at the moment. I think it’s going to take some time for sambauers and the gurus at bbpress to work out the kinks. I generate enough problems on my own. I’d like to keep the problems to *me*. I have a chance of fixing those.

I do know that xmlrpc works *now*. That’s what bp is using for the bp-forums component. Loading all of mu just to get at a few functions is kinda overkill. I think what I’m gonna do is create a couple of more xmlrpc methods on the wpmu side that will be called from bbpress. Such as:

‘get_all_group_forums’ – gets all bp groups that have forums and the forum id so that read-only-forums and hidden-forums can be automagicly configured. My plan is to configure all public group forums read-only and private and hidden groups hidden-forums.

‘get_all_group_members’ – Foreach group with forums get the members of that group and automagicly configure an override for each group member in that forum.

So from the bbpress side to configure read-only and hidden-forums, we get all the groups that have forums and then all the members of those groups and make the two bbpress plugins work with that info. Should be enough.

Using xmlrpc is better than loading all of wpmu just to do those two things. Especially since this deep integration is still flaky.

xmlrpc has added benefits. It’s way cooler. My forums don’t have to reside on the same server as my bp/wpmu install. I keep hearing rumblings, rumorings and hintings about xmlrpc. It’s kinda like sleeping and lurking. Getting ready for something. Comments by wpmu gurus about xmlrpc privately, Andy relying on it for forums. Something’s brewing.

[@burtadsit Participant 17 years, 10 months ago]

If both of you are experiencing this then one of you should report it in trac.

[@burtadsit Participant 17 years, 10 months ago]

I don’t know what the purpose of leaving it there is. Gotta be a reason. You might ask over at the mu forums. Perhaps it gets removed after a period of time? As a site admin I don’t want people signing up getting deleted by me and then signing up again? Dunno.

This is off topic for this thread. Sorry.

[@burtadsit Participant 17 years, 10 months ago]

There is something wrong with your configuration. No files should be going to /wp-content/<files>

Where is your ‘uploads’ directory go to? Looks like wp is trying to write to your /wp-content directory. Bad idea. Very bad idea.

[@burtadsit Participant 17 years, 10 months ago]

In bp-core-classes.php is BP_Core_User

/**

* BP_Core_User class can be used by any component. It will fetch useful

* details for any user when provided with a user_id.

*

* Example:

*    $user = new BP_Core_User( $user_id );

*    $user_avatar = $user->avatar;

*	  $user_email = $user->email;

*    $user_status = $user->status;

*    etc.

*

* @package BuddyPress Core

*/

Lots of stuff in that class. You need a user id to instantiate one.

[@burtadsit Participant 17 years, 10 months ago]

@gpo1 That’s what doesn’t work. The bp member theme isn’t a normal theme. That seems to be the problem. A normal theme does a bunch of *something* that the bp member theme doesn’t. The mu widget stuff is confused. Doesn’t know what blog id it’s on. Doesn’t like registering a sidebar in it. Dunno what it is, but it’s something.