<?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/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: WP-MalWatch WordPress Security Plugin</title>
	<atom:link href="http://how-to-blog.tv/security/wp-malwatch/feed/" rel="self" type="application/rss+xml" />
	<link>http://how-to-blog.tv</link>
	<description>Blogging Tips, Tutorials, and WordPress Theme Guidance</description>
	<lastBuildDate>Sat, 08 Oct 2011 03:14:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Derick Schaefer</title>
		<link>http://how-to-blog.tv/security/wp-malwatch/comment-page-1/#comment-2038</link>
		<dc:creator>Derick Schaefer</dc:creator>
		<pubDate>Mon, 11 Oct 2010 17:51:39 +0000</pubDate>
		<guid isPermaLink="false">http://how-to-blog.tv/?page_id=935#comment-2038</guid>
		<description>So, WordPress has a default uploads directory of /wp-content/uploads .  The example in the plugin, using &quot;mydomain.com&quot; is just an example and clicking on that will definately render a 404 error as whomever owns mydomain.com definately doesn&#039;t have WordPress installed it.  Go to your options section from with the WordPress admin and make sure your uploads directory is correct.  In many cases, a hosting provider will feed this variable as a full path that will look something like /var/www/mydomain.com/wp-content/uploads .  No need for all of the internal hosting garb in that path as any plugin (or theme for that matter) will understand the value of /wp-content/uploads .

Let me know if this corrects it for you.</description>
		<content:encoded><![CDATA[<p>So, WordPress has a default uploads directory of /wp-content/uploads .  The example in the plugin, using &#8220;mydomain.com&#8221; is just an example and clicking on that will definately render a 404 error as whomever owns mydomain.com definately doesn&#8217;t have WordPress installed it.  Go to your options section from with the WordPress admin and make sure your uploads directory is correct.  In many cases, a hosting provider will feed this variable as a full path that will look something like /var/www/mydomain.com/wp-content/uploads .  No need for all of the internal hosting garb in that path as any plugin (or theme for that matter) will understand the value of /wp-content/uploads .</p>
<p>Let me know if this corrects it for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BlogGrrl</title>
		<link>http://how-to-blog.tv/security/wp-malwatch/comment-page-1/#comment-1990</link>
		<dc:creator>BlogGrrl</dc:creator>
		<pubDate>Tue, 05 Oct 2010 22:52:40 +0000</pubDate>
		<guid isPermaLink="false">http://how-to-blog.tv/?page_id=935#comment-1990</guid>
		<description>I get same problem as NVO Logistic above.  Can you help to make the plugin work properly.  When I click on the link it gives a 404 Error.  Thanks</description>
		<content:encoded><![CDATA[<p>I get same problem as NVO Logistic above.  Can you help to make the plugin work properly.  When I click on the link it gives a 404 Error.  Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derick Schaefer</title>
		<link>http://how-to-blog.tv/security/wp-malwatch/comment-page-1/#comment-1975</link>
		<dc:creator>Derick Schaefer</dc:creator>
		<pubDate>Sun, 03 Oct 2010 16:08:16 +0000</pubDate>
		<guid isPermaLink="false">http://how-to-blog.tv/?page_id=935#comment-1975</guid>
		<description>Can you provide a little more detail?  Drop an email to our info  [AT]  how-to-blog account</description>
		<content:encoded><![CDATA[<p>Can you provide a little more detail?  Drop an email to our info  [AT]  how-to-blog account</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SD</title>
		<link>http://how-to-blog.tv/security/wp-malwatch/comment-page-1/#comment-1967</link>
		<dc:creator>SD</dc:creator>
		<pubDate>Thu, 30 Sep 2010 22:30:44 +0000</pubDate>
		<guid isPermaLink="false">http://how-to-blog.tv/?page_id=935#comment-1967</guid>
		<description>I&#039;m having the same problem as NOV LOGISTICS, above.  The plugin is working fine on my sub-domain site, but not on my main domain.  Can you tell me how to fix?  Thanks.</description>
		<content:encoded><![CDATA[<p>I&#8217;m having the same problem as NOV LOGISTICS, above.  The plugin is working fine on my sub-domain site, but not on my main domain.  Can you tell me how to fix?  Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derick Schaefer</title>
		<link>http://how-to-blog.tv/security/wp-malwatch/comment-page-1/#comment-1891</link>
		<dc:creator>Derick Schaefer</dc:creator>
		<pubDate>Fri, 24 Sep 2010 02:46:37 +0000</pubDate>
		<guid isPermaLink="false">http://how-to-blog.tv/?page_id=935#comment-1891</guid>
		<description>What is your current upload folder?  (send it without your domain name. . .meaning http://domain.com/wp-content. . . .)</description>
		<content:encoded><![CDATA[<p>What is your current upload folder?  (send it without your domain name. . .meaning <a href="http://domain.com/wp-content" rel="nofollow">http://domain.com/wp-content</a>. . . .)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://how-to-blog.tv/security/wp-malwatch/comment-page-1/#comment-1881</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Wed, 22 Sep 2010 10:14:57 +0000</pubDate>
		<guid isPermaLink="false">http://how-to-blog.tv/?page_id=935#comment-1881</guid>
		<description>Hi, Derick, I got the same problem. The plugin asked me to turn back the default upload folder. But it seems a bit difficult. I wonder whether I have any good way to use the great plugin. Thanks so much.</description>
		<content:encoded><![CDATA[<p>Hi, Derick, I got the same problem. The plugin asked me to turn back the default upload folder. But it seems a bit difficult. I wonder whether I have any good way to use the great plugin. Thanks so much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emerald</title>
		<link>http://how-to-blog.tv/security/wp-malwatch/comment-page-1/#comment-1714</link>
		<dc:creator>Emerald</dc:creator>
		<pubDate>Mon, 30 Aug 2010 12:04:08 +0000</pubDate>
		<guid isPermaLink="false">http://how-to-blog.tv/?page_id=935#comment-1714</guid>
		<description>I installed this (version 2.1.2) on my Wordpress blog (3.0.1) and am unable to see the detailed report. I click the &#039;see detailed report&#039; link from the mini-report which is flagging suspicious files on the dashboard, and I can see the headings, but no information on any of the files is visible.</description>
		<content:encoded><![CDATA[<p>I installed this (version 2.1.2) on my WordPress blog (3.0.1) and am unable to see the detailed report. I click the &#8216;see detailed report&#8217; link from the mini-report which is flagging suspicious files on the dashboard, and I can see the headings, but no information on any of the files is visible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OpenCamp Dallas &#8211; Photos and Session Coverage &#8211; Online Marketing Consultant Mark Barrera</title>
		<link>http://how-to-blog.tv/security/wp-malwatch/comment-page-1/#comment-1709</link>
		<dc:creator>OpenCamp Dallas &#8211; Photos and Session Coverage &#8211; Online Marketing Consultant Mark Barrera</dc:creator>
		<pubDate>Sun, 29 Aug 2010 20:30:04 +0000</pubDate>
		<guid isPermaLink="false">http://how-to-blog.tv/?page_id=935#comment-1709</guid>
		<description>[...] first page of Digg and other popular sites.  Jerod also mentioned a great Wordpress plugin called WP-Malware that will monitor your Wordpress installation for malware attacks which have been very common [...]</description>
		<content:encoded><![CDATA[<p>[...] first page of Digg and other popular sites.  Jerod also mentioned a great WordPress plugin called WP-Malware that will monitor your WordPress installation for malware attacks which have been very common [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bowei</title>
		<link>http://how-to-blog.tv/security/wp-malwatch/comment-page-1/#comment-1545</link>
		<dc:creator>bowei</dc:creator>
		<pubDate>Sun, 01 Aug 2010 18:43:08 +0000</pubDate>
		<guid isPermaLink="false">http://how-to-blog.tv/?page_id=935#comment-1545</guid>
		<description>Following up on my previous post, in the wordpress admin interface, I go to 
Super Admin -&gt; Sites -&gt; click on &#039;Edit&#039; for a site -&gt; scroll down to &#039;Upload Path&#039;.  By default, it shows &quot;wp-content/blogs.dir/index-number-here/files&quot;, which is specific for that site.  I don&#039;t think it would be wise to change this to &quot;wp-content/uploads&#039;.  

Yet, the readme.txt for the latest version says:

Sub-domain installations and &quot;One Click&quot; installations have been found to put a fully qualified file system path in the &quot;Miscellaneous -&gt; Store Uploads In This Folder setting&quot;.  The default is &quot;wp-content/uploads&quot;.  WP-MalWatch WILL NOT activate if the uploads folder is not set to the default setting. 

Does this mean that WP-Malwatch isn&#039;t meant for a multisite wordpress install?</description>
		<content:encoded><![CDATA[<p>Following up on my previous post, in the wordpress admin interface, I go to<br />
Super Admin -&gt; Sites -&gt; click on &#8216;Edit&#8217; for a site -&gt; scroll down to &#8216;Upload Path&#8217;.  By default, it shows &#8220;wp-content/blogs.dir/index-number-here/files&#8221;, which is specific for that site.  I don&#8217;t think it would be wise to change this to &#8220;wp-content/uploads&#8217;.  </p>
<p>Yet, the readme.txt for the latest version says:</p>
<p>Sub-domain installations and &#8220;One Click&#8221; installations have been found to put a fully qualified file system path in the &#8220;Miscellaneous -&gt; Store Uploads In This Folder setting&#8221;.  The default is &#8220;wp-content/uploads&#8221;.  WP-MalWatch WILL NOT activate if the uploads folder is not set to the default setting. </p>
<p>Does this mean that WP-Malwatch isn&#8217;t meant for a multisite wordpress install?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bowei</title>
		<link>http://how-to-blog.tv/security/wp-malwatch/comment-page-1/#comment-1543</link>
		<dc:creator>bowei</dc:creator>
		<pubDate>Sun, 01 Aug 2010 06:57:12 +0000</pubDate>
		<guid isPermaLink="false">http://how-to-blog.tv/?page_id=935#comment-1543</guid>
		<description>I get the same thing. I had this when I was on Wordpress 2.9.x, and now as well after I&#039;ve upgraded to Wordpress 3.0.1.  The WP-Malwatch plugin is also upgraded to the latest (2.1.2).  

I downloaded a fresh copy of wordpress 3.0.1 from wordpress.org, unzipped it, and searched for options-misc.php, but found nothing.  Looking at the WP-Malwatch code, I see that administrative-warning.php is the source of the error message, where it calls &lt;a href=&quot;&#039; . admin_url(&#039;options-misc.php&#039;) . &#039;&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.&#039;   I find the definition of the function in load_scripts.php, but it doesn&#039;t have parameters defined.  Maybe there&#039;s something with inheritance in the code or something, but could it be that administrative-warning.php requires a code change to admin_url() (i.e. no parameters) instead?  I tried changing this, and it just goes to the default admin page.  Not sure where I&#039;d actually make the change for WP-Malwatch.

I think the options-misc.php page is from an older version of Wordpress - perhaps WP-Malwatch needs to be updated?  As I note above, I&#039;m not sure what that would change to.</description>
		<content:encoded><![CDATA[<p>I get the same thing. I had this when I was on WordPress 2.9.x, and now as well after I&#8217;ve upgraded to WordPress 3.0.1.  The WP-Malwatch plugin is also upgraded to the latest (2.1.2).  </p>
<p>I downloaded a fresh copy of wordpress 3.0.1 from wordpress.org, unzipped it, and searched for options-misc.php, but found nothing.  Looking at the WP-Malwatch code, I see that administrative-warning.php is the source of the error message, where it calls <a href="' . admin_url('options-misc.php') . '" rel="nofollow">here</a>.&#8217;   I find the definition of the function in load_scripts.php, but it doesn&#8217;t have parameters defined.  Maybe there&#8217;s something with inheritance in the code or something, but could it be that administrative-warning.php requires a code change to admin_url() (i.e. no parameters) instead?  I tried changing this, and it just goes to the default admin page.  Not sure where I&#8217;d actually make the change for WP-Malwatch.</p>
<p>I think the options-misc.php page is from an older version of WordPress &#8211; perhaps WP-Malwatch needs to be updated?  As I note above, I&#8217;m not sure what that would change to.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Object Caching 681/696 objects using apc

Served from: how-to-blog.tv @ 2012-05-17 19:17:37 -->
