<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Emmense Technologies, LLC - WordPress Consulting &#187; buddypress — Emmense Technologies, LLC - WordPress Consulting</title>
	<atom:link href="http://emmense.com/blog/tag/buddypress/feed/" rel="self" type="application/rss+xml" />
	<link>http://emmense.com</link>
	<description>Just another Emmense.com weblog</description>
	<lastBuildDate>Sat, 05 Jun 2010 14:13:33 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0-alpha</generator>
		<item>
		<title>Can&#8217;t Access BuddyPress links Anymore? Try This Power Tip</title>
		<link>http://emmense.com/blog/2009/11/23/cant-access-buddypress-links-anymore-try-this-power-tip/</link>
		<comments>http://emmense.com/blog/2009/11/23/cant-access-buddypress-links-anymore-try-this-power-tip/#comments</comments>
		<pubDate>Mon, 23 Nov 2009 19:50:44 +0000</pubDate>
		<dc:creator>Aaron Brazell</dc:creator>
				<category><![CDATA[How To]]></category>
		<category><![CDATA[buddypress]]></category>
		<category><![CDATA[wpmu]]></category>

		<guid isPermaLink="false">http://emmense.com/?p=227</guid>
		<description><![CDATA[Quick documenting of a little known edge-case fix. If you head to the BuddyPress forums to find out why users can&#8217;t access BuddyPress links anymore, you&#8217;re likely to find answers involving a change in how BuddyPress handles themes between version 1.0.3 and version 1.1. The answer typically goes something along the lines of, &#8220;Make sure [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Femmense.com%2Fblog%2F2009%2F11%2F23%2Fcant-access-buddypress-links-anymore-try-this-power-tip%2F"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Femmense.com%2Fblog%2F2009%2F11%2F23%2Fcant-access-buddypress-links-anymore-try-this-power-tip%2F" height="61" width="51" /></a></div><p>Quick documenting of a little known edge-case fix. If you head to the <a href="http://buddypress.org/forums/">BuddyPress forums</a> to find out why users can&#8217;t access BuddyPress links anymore, you&#8217;re likely to find answers involving a change in how BuddyPress handles themes between version 1.0.3 and version 1.1. The answer typically goes something along the lines of, &#8220;Make sure that if you upgrade from BuddyPress 1.0.3 to BuddyPress 1.1, you delete any evidence of the wp-content/bp-themes folder&#8221;.</p>
<p>While generally this is the case, there is another gotcha that I discovered today with some help from Andy Peatling. This seems to be a result of a series of actions and &#8220;features&#8221; in WordPress MU. Let me paint the picture.</p>
<p>1) If you import usernames with spaces in them from a WordPress import into WordPress MU, you will find it impossible to perform some functions in WordPress MU with those &#8220;spaced out&#8221; users. This is due to an oddity between the two platforms where WordPress allows usernames with spaces in them but WordPress MU does not. The importer in WordPress MU doesn&#8217;t respect this fact so it will happily import (or rather create) usernames with spaces. This will need to be ironed out in the merge as there should be consistency between the two platforms.</p>
<p>2) Having imported all content from WordPress into WordPress MU, you need to run some SQL along the lines of</p>
<div class="codecolorer-container text mac-classic" style="overflow:auto;white-space:nowrap;border: 1px solid #9F9F9F;width:435px;"><table cellspacing="0" cellpadding="0"><tbody><tr><td style="padding:5px;text-align:center;color:#888888;background-color:#EEEEEE;border-right: 1px solid #9F9F9F;font: normal 12px/1.4em Monaco, Lucida Console, monospace;"><div>1<br /></div></td><td><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">UPDATE wp_users SET user_login = REPLACE('wp_users',' ','-');</div></td></tr></tbody></table></div>
<p>This of course is not ideal but will do a SQL search and replace of usernames replacing spaces with hyphens effectively sanitizing the username for use in WordPress MU.</p>
<p>3) If you&#8217;ve done this with BuddyPress 1.0.3 active, then you should be functional but it creates an orphaned data potential that gets ugly later. Upgrading to BuddyPress 1.1 creates a new problem. Username sanitization is in BP 1.1. It is not in BP 1.0.3. Now there&#8217;s an incompatibility, in some cases, with user slugs. Try this solution. Add the following line to your wp-config.php file to enforce compatibility of usernames.</p>
<div class="codecolorer-container text mac-classic" style="overflow:auto;white-space:nowrap;border: 1px solid #9F9F9F;width:435px;"><table cellspacing="0" cellpadding="0"><tbody><tr><td style="padding:5px;text-align:center;color:#888888;background-color:#EEEEEE;border-right: 1px solid #9F9F9F;font: normal 12px/1.4em Monaco, Lucida Console, monospace;"><div>1<br /></div></td><td><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">define( 'BP_ENABLE_USERNAME_COMPATIBILITY_MODE', true );</div></td></tr></tbody></table></div>
<p>This is not a perfect solution but it does fix the crazy edge case. Verification should show you that accessing BuddyPress links for users works again. Starting from scratch, though, you should be on <a href="http://mu.wordpress.org">WPMU</a> with <a href="http://buddypress.org">BuddyPress</a> 1.1.2 at minimum.</p>
]]></content:encoded>
			<wfw:commentRss>http://emmense.com/blog/2009/11/23/cant-access-buddypress-links-anymore-try-this-power-tip/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
