<?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 for WPMU Ldap Plugin</title>
	<atom:link href="http://wpmuldap.tuxdocs.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://wpmuldap.tuxdocs.net</link>
	<description>LDAP Server Authentication for Wordpress MU</description>
	<lastBuildDate>Mon, 09 Jan 2012 07:49:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Call for Issues by Jussi Sivonen</title>
		<link>http://wpmuldap.tuxdocs.net/2011/08/21/call-for-issues/#comment-8689</link>
		<dc:creator>Jussi Sivonen</dc:creator>
		<pubDate>Mon, 09 Jan 2012 07:49:17 +0000</pubDate>
		<guid isPermaLink="false">http://wpmuldap.tuxdocs.net/?p=325#comment-8689</guid>
		<description>When enabling WordPress&#039; debug mode, I get 2 different errors from the WMPU-LDAP plugin:

Notice: WP_User-&gt;id was called with an argument that is &lt;strong&gt;deprecated&lt;/strong&gt; since version 2.1! Use &lt;code&gt;WP_User-&gt;ID&lt;/code&gt; instead. in /home/testiwp/www/wp-includes/functions.php on line 3551

Notice: has_cap was called with an argument that is &lt;strong&gt;deprecated&lt;/strong&gt; since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /home/testiwp/www/wp-includes/functions.php on line 3551

While the path points to the error message -generating bit of code instead of the actual error in the plugin, I&#039;d say these sound the kinda bugs that should be fixed :)</description>
		<content:encoded><![CDATA[<p>When enabling WordPress&#8217; debug mode, I get 2 different errors from the WMPU-LDAP plugin:</p>
<p>Notice: WP_User-&gt;id was called with an argument that is <strong>deprecated</strong> since version 2.1! Use <code>WP_User-&gt;ID</code> instead. in /home/testiwp/www/wp-includes/functions.php on line 3551</p>
<p>Notice: has_cap was called with an argument that is <strong>deprecated</strong> since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /home/testiwp/www/wp-includes/functions.php on line 3551</p>
<p>While the path points to the error message -generating bit of code instead of the actual error in the plugin, I&#8217;d say these sound the kinda bugs that should be fixed <img src='http://wpmuldap.tuxdocs.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Call for Issues by James Revillini</title>
		<link>http://wpmuldap.tuxdocs.net/2011/08/21/call-for-issues/#comment-7440</link>
		<dc:creator>James Revillini</dc:creator>
		<pubDate>Tue, 29 Nov 2011 15:23:37 +0000</pubDate>
		<guid isPermaLink="false">http://wpmuldap.tuxdocs.net/?p=325#comment-7440</guid>
		<description>I have a problem in that my AD does not contain e-mail addresses for all accounts, such as test accounts, as well as users in a certain OU.  I wrote a dirty fix which jams a fake e-mail into the account and immediately prompts the user to go update their e-mail.  It has &quot;allow users to fix their e-mail when it&#039;s blank&quot; as an admin option. How can I get this to you?</description>
		<content:encoded><![CDATA[<p>I have a problem in that my AD does not contain e-mail addresses for all accounts, such as test accounts, as well as users in a certain OU.  I wrote a dirty fix which jams a fake e-mail into the account and immediately prompts the user to go update their e-mail.  It has &#8220;allow users to fix their e-mail when it&#8217;s blank&#8221; as an admin option. How can I get this to you?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WPMU Ldap 3.1.1 Released by Jussi Sivonen</title>
		<link>http://wpmuldap.tuxdocs.net/2011/03/23/wpmu-ldap-3-1-1-released/#comment-5402</link>
		<dc:creator>Jussi Sivonen</dc:creator>
		<pubDate>Fri, 16 Sep 2011 07:41:14 +0000</pubDate>
		<guid isPermaLink="false">http://wpmuldap.tuxdocs.net/?p=319#comment-5402</guid>
		<description>Scratch that... I got mine working after reinstalling some php&#039;s ldap-modules again. :)</description>
		<content:encoded><![CDATA[<p>Scratch that&#8230; I got mine working after reinstalling some php&#8217;s ldap-modules again. <img src='http://wpmuldap.tuxdocs.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WPMU Ldap 3.1.1 Released by Jussi Sivonen</title>
		<link>http://wpmuldap.tuxdocs.net/2011/03/23/wpmu-ldap-3-1-1-released/#comment-5398</link>
		<dc:creator>Jussi Sivonen</dc:creator>
		<pubDate>Fri, 16 Sep 2011 06:44:05 +0000</pubDate>
		<guid isPermaLink="false">http://wpmuldap.tuxdocs.net/?p=319#comment-5398</guid>
		<description>Hi guys!

Yesterday I upgraded to php 5.3.3 and noticed (only after putting it to production) that LDAP-authentication doesn&#039;t work anymore! Local user (admin) is able to log in but all the regular users get a white screen after giving filling the WordPress login screen and pressing enter. In debug more, the white screen is complimented with this text:
DEBUG: Attempting to authenticate user: userxxx

The same white screen appears if I try to save changes to the LDAP-options screen in the network dashboard. I can view the option pages, but can&#039;t save. Everything else is working smoothly, this is the only plugin that made the upgrade go south...

I got 3 separate WP-installation (all got SSL enabled and are multi-user, not single blogs) versions 3.1.3, 3.1.4 and 2.9. None of them can be logged with LDAP anymore :/

I&#039;m rolling back to yesterdays snapshot (thank god for virtual servers) which has php version 5.1.6 but suggest you look into this, since the old version of php is preventing me from upgrading to WP3.2!

Thx in advance,
Jussi

Here&#039;s my preliminary question I posted about php upgrade in the WP forums: http://wordpress.org/support/topic/wordpress-and-php-53-question</description>
		<content:encoded><![CDATA[<p>Hi guys!</p>
<p>Yesterday I upgraded to php 5.3.3 and noticed (only after putting it to production) that LDAP-authentication doesn&#8217;t work anymore! Local user (admin) is able to log in but all the regular users get a white screen after giving filling the WordPress login screen and pressing enter. In debug more, the white screen is complimented with this text:<br />
DEBUG: Attempting to authenticate user: userxxx</p>
<p>The same white screen appears if I try to save changes to the LDAP-options screen in the network dashboard. I can view the option pages, but can&#8217;t save. Everything else is working smoothly, this is the only plugin that made the upgrade go south&#8230;</p>
<p>I got 3 separate WP-installation (all got SSL enabled and are multi-user, not single blogs) versions 3.1.3, 3.1.4 and 2.9. None of them can be logged with LDAP anymore :/</p>
<p>I&#8217;m rolling back to yesterdays snapshot (thank god for virtual servers) which has php version 5.1.6 but suggest you look into this, since the old version of php is preventing me from upgrading to WP3.2!</p>
<p>Thx in advance,<br />
Jussi</p>
<p>Here&#8217;s my preliminary question I posted about php upgrade in the WP forums: <a href="http://wordpress.org/support/topic/wordpress-and-php-53-question" rel="nofollow">http://wordpress.org/support/topic/wordpress-and-php-53-question</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Call for Issues by Sam Margulies</title>
		<link>http://wpmuldap.tuxdocs.net/2011/08/21/call-for-issues/#comment-5161</link>
		<dc:creator>Sam Margulies</dc:creator>
		<pubDate>Wed, 07 Sep 2011 21:25:26 +0000</pubDate>
		<guid isPermaLink="false">http://wpmuldap.tuxdocs.net/?p=325#comment-5161</guid>
		<description>When you go to the Users page, the &quot;Add New&quot; button that displays next to the heading links to the default WordPress Add Users page. 
If you are interested, I have a patch to redirect the user-new.php WordPress page to your plugin&#039;s version to avoid accidentally adding users locally.</description>
		<content:encoded><![CDATA[<p>When you go to the Users page, the &#8220;Add New&#8221; button that displays next to the heading links to the default WordPress Add Users page.<br />
If you are interested, I have a patch to redirect the user-new.php WordPress page to your plugin&#8217;s version to avoid accidentally adding users locally.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Changelog by Aaron Axelsen</title>
		<link>http://wpmuldap.tuxdocs.net/changelog/#comment-3948</link>
		<dc:creator>Aaron Axelsen</dc:creator>
		<pubDate>Wed, 13 Jul 2011 12:35:28 +0000</pubDate>
		<guid isPermaLink="false">http://wpmuldap.frozenpc.net/?page_id=30#comment-3948</guid>
		<description>I am not aware of any issues - what problems are you seeing?</description>
		<content:encoded><![CDATA[<p>I am not aware of any issues &#8211; what problems are you seeing?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Changelog by mtp</title>
		<link>http://wpmuldap.tuxdocs.net/changelog/#comment-3947</link>
		<dc:creator>mtp</dc:creator>
		<pubDate>Wed, 13 Jul 2011 12:31:04 +0000</pubDate>
		<guid isPermaLink="false">http://wpmuldap.frozenpc.net/?page_id=30#comment-3947</guid>
		<description>Can it be that this plugin no longer works in Wordpress 3.2? I just upgradet our multisite Wordpress installation from 3.0.1 to 3.2.1 and even though I upgradet WPMU-LDAP alongside, the LDAP option is missing in the admin interface. Furthermore, users can no longer log in to their blogs.</description>
		<content:encoded><![CDATA[<p>Can it be that this plugin no longer works in WordPress 3.2? I just upgradet our multisite WordPress installation from 3.0.1 to 3.2.1 and even though I upgradet WPMU-LDAP alongside, the LDAP option is missing in the admin interface. Furthermore, users can no longer log in to their blogs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WPMU Ldap 3.1.1 Released by James Revillini</title>
		<link>http://wpmuldap.tuxdocs.net/2011/03/23/wpmu-ldap-3-1-1-released/#comment-3252</link>
		<dc:creator>James Revillini</dc:creator>
		<pubDate>Wed, 08 Jun 2011 13:50:04 +0000</pubDate>
		<guid isPermaLink="false">http://wpmuldap.tuxdocs.net/?p=319#comment-3252</guid>
		<description>Cancel.  I&#039;m using 2.8.4.

&lt;a href=&quot;#comment-3250&quot; rel=&quot;nofollow&quot;&gt;@James Revillini &lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Cancel.  I&#8217;m using 2.8.4.</p>
<p><a href="#comment-3250" rel="nofollow">@James Revillini </a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WPMU Ldap 3.1.1 Released by James Revillini</title>
		<link>http://wpmuldap.tuxdocs.net/2011/03/23/wpmu-ldap-3-1-1-released/#comment-3250</link>
		<dc:creator>James Revillini</dc:creator>
		<pubDate>Wed, 08 Jun 2011 13:48:15 +0000</pubDate>
		<guid isPermaLink="false">http://wpmuldap.tuxdocs.net/?p=319#comment-3250</guid>
		<description>Is this still working under WPMU 3.1.3?  I&#039;m not seeing the settings panel for it anywhere.</description>
		<content:encoded><![CDATA[<p>Is this still working under WPMU 3.1.3?  I&#8217;m not seeing the settings panel for it anywhere.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WPMU Ldap 3.1.1 Released by Aaron Axelsen</title>
		<link>http://wpmuldap.tuxdocs.net/2011/03/23/wpmu-ldap-3-1-1-released/#comment-2255</link>
		<dc:creator>Aaron Axelsen</dc:creator>
		<pubDate>Mon, 28 Mar 2011 03:38:32 +0000</pubDate>
		<guid isPermaLink="false">http://wpmuldap.tuxdocs.net/?p=319#comment-2255</guid>
		<description>thanks - i fixed the link!</description>
		<content:encoded><![CDATA[<p>thanks &#8211; i fixed the link!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

