<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Implementing the WordPress Shared Users Table Trick</title>
	<atom:link href="http://xentek.net/articles/528/implementing-the-wordpress-shared-users-table-trick/feed/" rel="self" type="application/rss+xml" />
	<link>http://xentek.net/articles/528/implementing-the-wordpress-shared-users-table-trick/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=implementing-the-wordpress-shared-users-table-trick</link>
	<description></description>
	<lastBuildDate>Mon, 30 Jan 2012 14:02:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-alpha-19827</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Eric Marden</title>
		<link>http://xentek.net/articles/528/implementing-the-wordpress-shared-users-table-trick/#comment-1617</link>
		<dc:creator>Eric Marden</dc:creator>
		<pubDate>Fri, 30 Dec 2011 18:21:13 +0000</pubDate>
		<guid isPermaLink="false">http:/xentek.net/?p=528#comment-1617</guid>
		<description>I don&#039;t see why not. Subdomains just map to virtual hosts (most likely) on the server. But as long as they can all talk to the same MySQL instance, you&#039;ll be able to pull this off just fine. However, I would recommend taking a look at the network feature in WordPress 3.0+ too, to see if that wouldn&#039;t better solve your needs.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t see why not. Subdomains just map to virtual hosts (most likely) on the server. But as long as they can all talk to the same MySQL instance, you&#8217;ll be able to pull this off just fine. However, I would recommend taking a look at the network feature in WordPress 3.0+ too, to see if that wouldn&#8217;t better solve your needs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike the Lawyer</title>
		<link>http://xentek.net/articles/528/implementing-the-wordpress-shared-users-table-trick/#comment-1616</link>
		<dc:creator>Mike the Lawyer</dc:creator>
		<pubDate>Fri, 09 Dec 2011 17:50:23 +0000</pubDate>
		<guid isPermaLink="false">http:/xentek.net/?p=528#comment-1616</guid>
		<description>Eric - great article. Does this &quot;trick&quot; work on subdomains? In addition, here&#039;s a complex question - if you&#039;ve got an existing subdirectory based install, could you synch separate installs on subdomains using this? It would be super grand if that was in the affirmative!</description>
		<content:encoded><![CDATA[<p>Eric &#8211; great article. Does this &#8220;trick&#8221; work on subdomains? In addition, here&#8217;s a complex question &#8211; if you&#8217;ve got an existing subdirectory based install, could you synch separate installs on subdomains using this? It would be super grand if that was in the affirmative!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Marden</title>
		<link>http://xentek.net/articles/528/implementing-the-wordpress-shared-users-table-trick/#comment-1615</link>
		<dc:creator>Eric Marden</dc:creator>
		<pubDate>Tue, 01 Nov 2011 21:13:31 +0000</pubDate>
		<guid isPermaLink="false">http:/xentek.net/?p=528#comment-1615</guid>
		<description>I&#039;ve never done this, but I would copy the user tables over and once you&#039;ve confirmed the two blogs are separate, just use wp-admin to remove the users you no longer want on the second site (or just set them all as subscriber).</description>
		<content:encoded><![CDATA[<p>I&#8217;ve never done this, but I would copy the user tables over and once you&#8217;ve confirmed the two blogs are separate, just use wp-admin to remove the users you no longer want on the second site (or just set them all as subscriber).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Marden</title>
		<link>http://xentek.net/articles/528/implementing-the-wordpress-shared-users-table-trick/#comment-1614</link>
		<dc:creator>Eric Marden</dc:creator>
		<pubDate>Tue, 01 Nov 2011 21:12:20 +0000</pubDate>
		<guid isPermaLink="false">http:/xentek.net/?p=528#comment-1614</guid>
		<description>Something like this *is* possible, but not with this plugin.</description>
		<content:encoded><![CDATA[<p>Something like this *is* possible, but not with this plugin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Marden</title>
		<link>http://xentek.net/articles/528/implementing-the-wordpress-shared-users-table-trick/#comment-1613</link>
		<dc:creator>Eric Marden</dc:creator>
		<pubDate>Tue, 01 Nov 2011 21:11:38 +0000</pubDate>
		<guid isPermaLink="false">http:/xentek.net/?p=528#comment-1613</guid>
		<description>Its possible, but outside of the scope of this plugin/technique. However, you might want to check out WordPress 3.0&#039;s network features. It supports that scenario out of the box more or less.</description>
		<content:encoded><![CDATA[<p>Its possible, but outside of the scope of this plugin/technique. However, you might want to check out WordPress 3.0&#8242;s network features. It supports that scenario out of the box more or less.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Svenson</title>
		<link>http://xentek.net/articles/528/implementing-the-wordpress-shared-users-table-trick/#comment-1612</link>
		<dc:creator>Svenson</dc:creator>
		<pubDate>Tue, 18 Oct 2011 08:37:28 +0000</pubDate>
		<guid isPermaLink="false">http:/xentek.net/?p=528#comment-1612</guid>
		<description>Hi, 
Nice info, Thx.
Did anyone find an easy way to stay logged in for users on all sites (site1.com, site2.com,...) ex: logged in on site1 goes to site2 and don´t need to login again?
How to share cookies between those sites?

Thank you, 

Svenson</description>
		<content:encoded><![CDATA[<p>Hi,<br />
Nice info, Thx.<br />
Did anyone find an easy way to stay logged in for users on all sites (site1.com, site2.com,&#8230;) ex: logged in on site1 goes to site2 and don´t need to login again?<br />
How to share cookies between those sites?</p>
<p>Thank you, </p>
<p>Svenson</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dimis</title>
		<link>http://xentek.net/articles/528/implementing-the-wordpress-shared-users-table-trick/#comment-1611</link>
		<dc:creator>dimis</dc:creator>
		<pubDate>Wed, 05 Oct 2011 09:52:56 +0000</pubDate>
		<guid isPermaLink="false">http:/xentek.net/?p=528#comment-1611</guid>
		<description>Hello,I have already a user table at my site.Can I use it for the user management of a word-press blog?It has a different schema .
How can user login with these credentials?(of the existing table)</description>
		<content:encoded><![CDATA[<p>Hello,I have already a user table at my site.Can I use it for the user management of a word-press blog?It has a different schema .<br />
How can user login with these credentials?(of the existing table)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max</title>
		<link>http://xentek.net/articles/528/implementing-the-wordpress-shared-users-table-trick/#comment-1610</link>
		<dc:creator>Max</dc:creator>
		<pubDate>Thu, 15 Sep 2011 00:56:21 +0000</pubDate>
		<guid isPermaLink="false">http:/xentek.net/?p=528#comment-1610</guid>
		<description>Hey, it works! Thanks! Just added a 2nd blog on a subdomain which shares users with an existing main site. Tricky, but doable.</description>
		<content:encoded><![CDATA[<p>Hey, it works! Thanks! Just added a 2nd blog on a subdomain which shares users with an existing main site. Tricky, but doable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefhan</title>
		<link>http://xentek.net/articles/528/implementing-the-wordpress-shared-users-table-trick/#comment-1609</link>
		<dc:creator>Stefhan</dc:creator>
		<pubDate>Tue, 13 Sep 2011 12:28:28 +0000</pubDate>
		<guid isPermaLink="false">http:/xentek.net/?p=528#comment-1609</guid>
		<description>These instructions worked brilliantly for implementing a shared user table. Unfortunately I now need to reverse the process - ie create two separate user and user meta tables from the one. 

Presumably I remove: 

define(‘CUSTOM_USER_TABLE’, ‘wp_users’);
define(‘CUSTOM_USER_META_TABLE’, ‘wp_usermeta’);

from wp-config.php but will I then be locked out of the second blog as it will no  longer have a usertable? 

I don&#039;t need to copy all the user data across to the second blog, but I&#039;m concerned about being unable to login.

Any top tips for reversing the process would be much appreciated!

Thanks

Stefhan</description>
		<content:encoded><![CDATA[<p>These instructions worked brilliantly for implementing a shared user table. Unfortunately I now need to reverse the process &#8211; ie create two separate user and user meta tables from the one. </p>
<p>Presumably I remove: </p>
<p>define(‘CUSTOM_USER_TABLE’, ‘wp_users’);<br />
define(‘CUSTOM_USER_META_TABLE’, ‘wp_usermeta’);</p>
<p>from wp-config.php but will I then be locked out of the second blog as it will no  longer have a usertable? </p>
<p>I don&#8217;t need to copy all the user data across to the second blog, but I&#8217;m concerned about being unable to login.</p>
<p>Any top tips for reversing the process would be much appreciated!</p>
<p>Thanks</p>
<p>Stefhan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hotchkissmade!</title>
		<link>http://xentek.net/articles/528/implementing-the-wordpress-shared-users-table-trick/#comment-1608</link>
		<dc:creator>Hotchkissmade!</dc:creator>
		<pubDate>Thu, 07 Jul 2011 18:06:22 +0000</pubDate>
		<guid isPermaLink="false">http:/xentek.net/?p=528#comment-1608</guid>
		<description>[...] as it designed so that deployment of a finished product is quick and painless. At first I wanted to share user tables, but the orphan problems created by that hack were complicated and the solutions were not secure [...] </description>
		<content:encoded><![CDATA[<p>[...] as it designed so that deployment of a finished product is quick and painless. At first I wanted to share user tables, but the orphan problems created by that hack were complicated and the solutions were not secure [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

