[@burtadsit Participant 17 years, 9 months ago]

Well, here’s an even better idea. Don’t create a file called just anything. Call it bp-custom.php and put it in there. Drop that in /mu-plugins. I looked at the SVN log and as of rev 1012 if that file exists in /mu-plugins it gets run before anything else in bp.

Cool. Thanks Andy!

Now I know how to launch all my little tweaks. The official way.

[@burtadsit Participant 17 years, 9 months ago]

I found a little filter hook in wp-login.php that seemed just right for this. It is buried in that mass of stuff in that file on line 436 (wpmu 2.7).

---

$redirect_to = apply_filters('login_redirect', $redirect_to, isset( $_REQUEST['redirect_to'] ) ? $_REQUEST['redirect_to'] : '', $user);

---

So I built a little plugin that hooks this filter.

---

function oci_login_redirect($redirect_to, $set_for, $user){

$redirect_to = bp_core_get_userurl($user->ID);

return $redirect_to;

}

add_filter('login_redirect', 'oci_login_redirect', 10, 3);

---

Create a file with the above code and drop it into /mu-plugins. It sends the user to their profile after logging in. You can send them wherever you want them to go by changing $redirect_to.

[@burtadsit Participant 17 years, 9 months ago]

That email is generated in wpmu-functions.php part of the wpmu core. It’s called during the signup process and that function is wpmu_welcome_user_notification(). The function that is used for blog signup notification is right above that called wpmu_welcome_notification(). The blog signup email can be modified in the wpmu backend, not the user signup email. It’s just plain harded coded.

My hope rose when I saw at the top of the fn a filter. The filter is just for the username, pass and some other info that is irrelevant to the body of the email. I don’t see any way to change it except by modifying that fn itself.

[@burtadsit Participant 17 years, 9 months ago]

The bp admin bar gets called and generated in the footer by a add_action( 'wp_footer', 'bp_core_admin_bar', 8 ); call. When the action ‘wp_footer’ is triggered it gets generated. You might try sneaking your ad in with a priority of 7. Then it will get generated before the admin bar’s priority of 8. I don’t know what’s gonna happen with the css for the admin bar. You might have to modify that. Not sure.

[@burtadsit Participant 17 years, 9 months ago]

You selected the ‘subdomain’ option for wpmu installation. What it was asking you during the install process was how do you want future blogs to be created. As subdomains or subdirectories. Install wpmu and choose the subdirectory option.

[@burtadsit Participant 17 years, 9 months ago]

Well, well. Maybe we’re getting somewhere trying to understand why 1and1 doesn’t work well with bp. Thanks for this.

[@burtadsit Participant 17 years, 9 months ago]

Got anything to add to the trac discussion Karl? https://trac.buddypress.org/ticket/436

Just disabling the filters is not a good idea. The filtering of content is bound up with stripping sensitive data. Maybe Andy can decouple those two and enable the content filters for those users that get bitten by the libxml2 problem.

[@burtadsit Participant 17 years, 9 months ago]

Howdy people. I’m gonna take a look at the rss feed problem today. Took two days off for the first time in months. Feeling all irresponsible. I accepted this ticket in trac and I guess I better go hunt down the problem with feeds in bp.

On my way.

[@burtadsit Participant 17 years, 9 months ago]

I’ve been looking at this problem and getting frustrated. I realized finally that the filter function actually does two things:

$content = htmlentities( $content, ENT_COMPAT, "UTF-8" );

$content = str_replace( '&', '/amp/', $content );

From http://loadaveragezero.com/app/drx/Data_Formats/Character_Encoding

[…] But there are a number of other issues to deal with. In particular, because UTF-8 is a multibyte encoding, meaning one character can be represented by more one or more bytes. This causes trouble for PHP, because the language parses and processes strings based on bytes, not characters, and makes mincemeat multibyte strings – for example, by splitting characters ‘in half’, bodging up regular expressions, and rendering email unreadable.

Karl can you just comment out the following lines please:

Line 46 $content = str_replace( '&', '/amp/', $content ) in bp-forums-filters.php

and line 52 $post_text = str_replace( '/amp/', '&', $post_text ); in buddypress-enable.php on the bbpress side.

I’d like to narrow this down to the htmlentities fn.

I’m gonna help solve this or just move to a planet where only ASCII is spoken.

[@burtadsit Participant 17 years, 9 months ago]

The ‘news’ button which has mutated to the ‘blog’ button in the trunk, isn’t a widget. It just uses your theme’s index.php template to list the recent blog posts on your blog. Whatever ‘index.php’ does in your theme that’s what you see.

Updating to the most recent trunk gets you updates for everything in the bp universe. This is wide and vast as you know. Your dishwasher will probably run quieter also.

[@burtadsit Participant 17 years, 9 months ago]

Comment out line 47 in bp-blogs-widgets: <?php $counter++; ?>

That will get you excerpts for all posts.

[@burtadsit Participant 17 years, 9 months ago]

If you are running a wp theme on your blog there was a problem with ‘news’ or not listing the recent blog posts. This has been fixed in the recent trunk. I don’t think it made it to the beta 2 release.

Try updating to the recent trunk.

[@burtadsit Participant 17 years, 9 months ago]

I put in a ticket in trac on this. It’s become and ‘official’ problem.

[@burtadsit Participant 17 years, 9 months ago]

Haven’t run across this as an issue with bp before.

[@burtadsit Participant 17 years, 9 months ago]

It’s the combo download for the whole beta 2 package.

[@burtadsit Participant 17 years, 9 months ago]

Run, don’t walk to http://getfirebug.com/ and click download. You don’t want to modify the widget identities themselves. The idea is that you create css that works with the existing html/css ids and classes.

[@burtadsit Participant 17 years, 9 months ago]

Two conflicting versions of jquery will give you major headaches. I solved the problem by disabling my plugin’s reliance on it’s own jquery lib altogether. I just relied on bp’s jquery lib which was newer. I don’t know of any other way to solve the issue. Apps that rely on js do not play well together.

[@burtadsit Participant 17 years, 9 months ago]

I posted a ticket in trac about this for you.

[@burtadsit Participant 17 years, 9 months ago]

We’ve had some experience with people having problems getting wpmu and bp up and running on that particular host. There are *always* issues when you try to run wpmu on shared hosting.

[@burtadsit Participant 17 years, 9 months ago]

http://kb.siteground.com/article/internal_server_error_500.html

[@burtadsit Participant 17 years, 9 months ago]

Howdy. If you are playing in mu and new blog defaults and sidebars and bp and you actually succeed in accomplishing that, you certainly are a programmer.

[@burtadsit Participant 17 years, 9 months ago]

You know I’m gonna say this. I updated to rev 1636 wpmu and bp rev 941. I can’t reproduce this problem. Donncha commited some changes to mu that broke bp when mu detected a 404. Broke lots of links in bp. Andy sent in a patch for wpmu. Donncha fixed the problem. This has happend over the past couple of days.

This happens at wpmu 1636 and bp 941?

[@burtadsit Participant 17 years, 9 months ago]

Ok. I’ll go investigate with latest mu trunk and bp revs 941 and down.

[@burtadsit Participant 17 years, 9 months ago]

@advinchi fix for this is in latest trunk

[@burtadsit Participant 17 years, 9 months ago]

From the readme.txt in /buddypress-themes:

2. Move the /member-themes/ directory into /wp-content/member-themes/