<?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: Limit Login Attempts</title>
	<atom:link href="http://devel.kostdoktorn.se/limit-login-attempts/feed" rel="self" type="application/rss+xml" />
	<link>http://devel.kostdoktorn.se</link>
	<description>Wordpress odds and ends</description>
	<lastBuildDate>Sat, 13 Mar 2010 10:29:16 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Erik</title>
		<link>http://devel.kostdoktorn.se/limit-login-attempts/comment-page-1#comment-40</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Sun, 28 Feb 2010 02:04:59 +0000</pubDate>
		<guid isPermaLink="false">http://devel-test.kostdoktorn.se/?page_id=3#comment-40</guid>
		<description>Hey, 
I use wordpress mu(2.9.1.1) and I just spent some time reworking the plugin(1.4.1) to be more MU friendly. I will mention that this plugin works FANTASTICLY with wordpress mu 2.9.1.1.... Other Mu users may find this usefull... A couple things...

first, I set the variables at the top of the plugins .php file i wanted to be global. The file is very well noted by the author, OMG thank you! Very easy to control what variables the plugin activates with thanks to great coding and thoughtful notation.

Then I changed the function that mails lockout notification to the administrator, so that it will email the super site admin(me) rather than that particular sub blogs admin.. what i did was modify the get_option in line394 to say:
@wp_mail(get_site_option(&#039;admin_email&#039;), $subject, $message);


Then, i changed the code where it constructs the plugins dashboard submenu. I changed it so that it would show under the site admin menu instead of settings. that way only the super site admin can see it and not the sub blog administrators. I changed Line 607 to:
add_submenu_page(&#039;wpmu-admin.php&#039;, &#039;Limit Login Attempts&#039;, &#039;Limit Login Attempts&#039;, 10, &#039;limit-login-attempts&#039;, &#039;limit_login_option_page&#039;);

Then I used the plugin manager to auto-activate the plugin for all users sitewide.. that way any newly generated blogs will automatically activate the plugin with the settings I want, and having moved the menu, users cant modify them.

It is important to note, that if the plugins menu is accessable to your users, they can deactivate the plugin. Rather than attempt to solve this, i will just hope that my users are not that stupid.

hope this helps...

oh, the settings I changed to my likeing were; 
login attempts moved to 5,
lockout time decreased to 15 min.
lockout log settings changed to &#039;log, email&#039;
and notify email after 1 lockout</description>
		<content:encoded><![CDATA[<p>Hey,<br />
I use wordpress mu(2.9.1.1) and I just spent some time reworking the plugin(1.4.1) to be more MU friendly. I will mention that this plugin works FANTASTICLY with wordpress mu 2.9.1.1.... Other Mu users may find this usefull... A couple things...</p>
<p>first, I set the variables at the top of the plugins .php file i wanted to be global. The file is very well noted by the author, OMG thank you! Very easy to control what variables the plugin activates with thanks to great coding and thoughtful notation.</p>
<p>Then I changed the function that mails lockout notification to the administrator, so that it will email the super site admin(me) rather than that particular sub blogs admin.. what i did was modify the get_option in line394 to say:<br />
@wp_mail(get_site_option('admin_email'), $subject, $message);</p>
<p>Then, i changed the code where it constructs the plugins dashboard submenu. I changed it so that it would show under the site admin menu instead of settings. that way only the super site admin can see it and not the sub blog administrators. I changed Line 607 to:<br />
add_submenu_page('wpmu-admin.php', 'Limit Login Attempts', 'Limit Login Attempts', 10, 'limit-login-attempts', 'limit_login_option_page');</p>
<p>Then I used the plugin manager to auto-activate the plugin for all users sitewide.. that way any newly generated blogs will automatically activate the plugin with the settings I want, and having moved the menu, users cant modify them.</p>
<p>It is important to note, that if the plugins menu is accessable to your users, they can deactivate the plugin. Rather than attempt to solve this, i will just hope that my users are not that stupid.</p>
<p>hope this helps...</p>
<p>oh, the settings I changed to my likeing were;<br />
login attempts moved to 5,<br />
lockout time decreased to 15 min.<br />
lockout log settings changed to 'log, email'<br />
and notify email after 1 lockout</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alla Taomoto</title>
		<link>http://devel.kostdoktorn.se/limit-login-attempts/comment-page-1#comment-39</link>
		<dc:creator>Alla Taomoto</dc:creator>
		<pubDate>Mon, 22 Feb 2010 13:16:09 +0000</pubDate>
		<guid isPermaLink="false">http://devel-test.kostdoktorn.se/?page_id=3#comment-39</guid>
		<description>Though I would&#039;ve loved it much more if you added a relevant video or at least pictures to back up the explanation, I still thought that your write-up quite helpful. It&#039;s usually hard to make a complicated matter seem very easy. I enjoy your weblog and will sign up to your feed so I will not miss anything. Fantastic content</description>
		<content:encoded><![CDATA[<p>Though I would've loved it much more if you added a relevant video or at least pictures to back up the explanation, I still thought that your write-up quite helpful. It's usually hard to make a complicated matter seem very easy. I enjoy your weblog and will sign up to your feed so I will not miss anything. Fantastic content</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: realesegame</title>
		<link>http://devel.kostdoktorn.se/limit-login-attempts/comment-page-1#comment-37</link>
		<dc:creator>realesegame</dc:creator>
		<pubDate>Fri, 12 Feb 2010 21:49:54 +0000</pubDate>
		<guid isPermaLink="false">http://devel-test.kostdoktorn.se/?page_id=3#comment-37</guid>
		<description>How in work rhis plugin in wordpress 2.9.1?</description>
		<content:encoded><![CDATA[<p>How in work rhis plugin in wordpress 2.9.1?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Kamp</title>
		<link>http://devel.kostdoktorn.se/limit-login-attempts/comment-page-1#comment-35</link>
		<dc:creator>Daniel Kamp</dc:creator>
		<pubDate>Wed, 20 Jan 2010 09:40:30 +0000</pubDate>
		<guid isPermaLink="false">http://devel-test.kostdoktorn.se/?page_id=3#comment-35</guid>
		<description>Very cool Plugin ! Thanks!</description>
		<content:encoded><![CDATA[<p>Very cool Plugin ! Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ds281</title>
		<link>http://devel.kostdoktorn.se/limit-login-attempts/comment-page-1#comment-34</link>
		<dc:creator>ds281</dc:creator>
		<pubDate>Wed, 13 Jan 2010 20:04:11 +0000</pubDate>
		<guid isPermaLink="false">http://devel-test.kostdoktorn.se/?page_id=3#comment-34</guid>
		<description>Would love better support for MU if possible!  Loving what this plugin provides so far on the main blog!  Thanks for your work.</description>
		<content:encoded><![CDATA[<p>Would love better support for MU if possible!  Loving what this plugin provides so far on the main blog!  Thanks for your work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Particularlywarn</title>
		<link>http://devel.kostdoktorn.se/limit-login-attempts/comment-page-1#comment-33</link>
		<dc:creator>Particularlywarn</dc:creator>
		<pubDate>Thu, 07 Jan 2010 07:33:15 +0000</pubDate>
		<guid isPermaLink="false">http://devel-test.kostdoktorn.se/?page_id=3#comment-33</guid>
		<description>Importance Lose,essential difficulty nod i play visit elsewhere person human onto front second leader youth local well part me hit loss yourself team your module occasion outside prime variety gold measure desk society reader around enough commitment afternoon necessary mother industrial draw bed index aware whilst radio blow association studio truth put immediate care responsibility benefit sorry demand end very lawyer who by protect thin express priority today relevant ball recommend perform middle instance maybe consist exactly confirm die owner hence variety version commitment teacher capital indeed bridge party significance</description>
		<content:encoded><![CDATA[<p>Importance Lose,essential difficulty nod i play visit elsewhere person human onto front second leader youth local well part me hit loss yourself team your module occasion outside prime variety gold measure desk society reader around enough commitment afternoon necessary mother industrial draw bed index aware whilst radio blow association studio truth put immediate care responsibility benefit sorry demand end very lawyer who by protect thin express priority today relevant ball recommend perform middle instance maybe consist exactly confirm die owner hence variety version commitment teacher capital indeed bridge party significance</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Wong</title>
		<link>http://devel.kostdoktorn.se/limit-login-attempts/comment-page-1#comment-32</link>
		<dc:creator>Jason Wong</dc:creator>
		<pubDate>Wed, 06 Jan 2010 08:31:48 +0000</pubDate>
		<guid isPermaLink="false">http://devel-test.kostdoktorn.se/?page_id=3#comment-32</guid>
		<description>Amazing plugin.

However, I wish that it can work well with Login with Ajax plugin/widget, as I noticed that the error message produced by the Limit Login Attempts plugin isn&#039;t immediately displayed on the Login with Ajax widget.  It appears that&#039;s a loop delay ...  Strange??

Please keep me posted if there&#039;s a possible solution to this &#039;hiccup&#039; ...

Cheers ... Jason</description>
		<content:encoded><![CDATA[<p>Amazing plugin.</p>
<p>However, I wish that it can work well with Login with Ajax plugin/widget, as I noticed that the error message produced by the Limit Login Attempts plugin isn't immediately displayed on the Login with Ajax widget.  It appears that's a loop delay ...  Strange??</p>
<p>Please keep me posted if there's a possible solution to this 'hiccup' ...</p>
<p>Cheers ... Jason</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan Eenfeldt</title>
		<link>http://devel.kostdoktorn.se/limit-login-attempts/comment-page-1#comment-27</link>
		<dc:creator>Johan Eenfeldt</dc:creator>
		<pubDate>Sat, 14 Nov 2009 09:54:15 +0000</pubDate>
		<guid isPermaLink="false">http://devel-test.kostdoktorn.se/?page_id=3#comment-27</guid>
		<description>Thanks for the feedback.

I&#039;ve been looking at MU recently and hope to add real support for it once I get 2.0 out the doors.</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback.</p>
<p>I've been looking at MU recently and hope to add real support for it once I get 2.0 out the doors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jim</title>
		<link>http://devel.kostdoktorn.se/limit-login-attempts/comment-page-1#comment-25</link>
		<dc:creator>jim</dc:creator>
		<pubDate>Thu, 12 Nov 2009 00:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://devel-test.kostdoktorn.se/?page_id=3#comment-25</guid>
		<description>&lt;blockquote&gt;Please report any success or failure!&lt;/blockquote&gt;

Just thought I&#039;d provide some MU / Simple:Press feedback... using our dev. environment, v2.0b3 seemed to work perfectly on our main blog running WPMU 2.8.5.2. It also seems to play nice with Simple:Press since any login errors are shown on the WP login screen, not inline on the Forums page.

I may or may not install this on our production site quite yet though, for the following reason. Limit-Login must be placed in the Plugins folder to work, and then it only works for the blog on which it is activated. We do not want to give all users this level of control. Using WMPU Plugin Manager, I limited activation to the main blog only, and this solves half the problem – sub blogs no longer have access to the plugin, but then it no longer limits/logs login attempts on those blogs either.

Since our primary concern is users locking themselves out after 5 failed logins (via our firewall settings) when signing in on the Forums page, this plugin &lt;strong&gt;may&lt;/strong&gt; very well meet our needs, since only a few users may be logging in directly via their own blog. 

I like the ample warning it provides, and how it logs IP addresses. A nice feature would be the ability to remove ban from specific IPs, instead of all at once.

Thanks again, kep up the good work!</description>
		<content:encoded><![CDATA[<blockquote><p>Please report any success or failure!</p></blockquote>
<p>Just thought I'd provide some MU / Simple:Press feedback... using our dev. environment, v2.0b3 seemed to work perfectly on our main blog running WPMU 2.8.5.2. It also seems to play nice with Simple:Press since any login errors are shown on the WP login screen, not inline on the Forums page.</p>
<p>I may or may not install this on our production site quite yet though, for the following reason. Limit-Login must be placed in the Plugins folder to work, and then it only works for the blog on which it is activated. We do not want to give all users this level of control. Using WMPU Plugin Manager, I limited activation to the main blog only, and this solves half the problem – sub blogs no longer have access to the plugin, but then it no longer limits/logs login attempts on those blogs either.</p>
<p>Since our primary concern is users locking themselves out after 5 failed logins (via our firewall settings) when signing in on the Forums page, this plugin <strong>may</strong> very well meet our needs, since only a few users may be logging in directly via their own blog. </p>
<p>I like the ample warning it provides, and how it logs IP addresses. A nice feature would be the ability to remove ban from specific IPs, instead of all at once.</p>
<p>Thanks again, kep up the good work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Davis</title>
		<link>http://devel.kostdoktorn.se/limit-login-attempts/comment-page-1#comment-23</link>
		<dc:creator>Keith Davis</dc:creator>
		<pubDate>Tue, 10 Nov 2009 17:40:46 +0000</pubDate>
		<guid isPermaLink="false">http://devel-test.kostdoktorn.se/?page_id=3#comment-23</guid>
		<description>@Johan

Sent details of your plugin to Shinephp and the guy over there did a review... see link below:
http://www.shinephp.com/limit-login-attempts-1-4-1-wordpress-plugin-review/

He recommended your plugin over Login lockdown

I will install on my live site.</description>
		<content:encoded><![CDATA[<p>@Johan</p>
<p>Sent details of your plugin to Shinephp and the guy over there did a review... see link below:<br />
<a href="http://www.shinephp.com/limit-login-attempts-1-4-1-wordpress-plugin-review/" rel="nofollow">http://www.shinephp.com/limit-login-attempts-1-4-1-wordpress-plugin-r...</a></p>
<p>He recommended your plugin over Login lockdown</p>
<p>I will install on my live site.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
