Comments on: Askimet 2.1.8 Issues http://www.realestatebloglab.com/real-estate-blogging/askimet-218-issues/ A Laboratory For Real Estate Blogging Fri, 30 Jul 2010 15:41:47 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Craig J Frooninckx http://www.realestatebloglab.com/real-estate-blogging/askimet-218-issues/comment-page-1/#comment-2179 Craig J Frooninckx Tue, 02 Sep 2008 03:08:21 +0000 http://www.realestatebloglab.com/?p=317#comment-2179 WP 2.6.1, I did do the automatic update from the plugin window. WP 2.6.1, I did do the automatic update from the plugin window.

]]> By: Jeff in Hawaii http://www.realestatebloglab.com/real-estate-blogging/askimet-218-issues/comment-page-1/#comment-2176 Jeff in Hawaii Tue, 02 Sep 2008 00:36:25 +0000 http://www.realestatebloglab.com/?p=317#comment-2176 I am running the most current version of both and had no problems when upgrading. I am running the most current version of both and had no problems when upgrading.

]]> By: Dave Smith http://www.realestatebloglab.com/real-estate-blogging/askimet-218-issues/comment-page-1/#comment-2173 Dave Smith Mon, 01 Sep 2008 16:02:09 +0000 http://www.realestatebloglab.com/?p=317#comment-2173 Craig, What version of WP are you running and did you download the new version of Askimet or use the automatic download and install from the plugin window? Craig,

What version of WP are you running and did you download the new version of Askimet or use the automatic download and install from the plugin window?

]]> By: Craig J. Frooninckx http://www.realestatebloglab.com/real-estate-blogging/askimet-218-issues/comment-page-1/#comment-2169 Craig J. Frooninckx Mon, 01 Sep 2008 14:27:29 +0000 http://www.realestatebloglab.com/?p=317#comment-2169 I had the same problem with my last upgrade, then I had another notice for an upgrade, once I did the last one (which is 2.1.8), the problem went away. So not sure if they discovered the problem and tried to push it as the same version or what. I had the same problem with my last upgrade, then I had another notice for an upgrade, once I did the last one (which is 2.1.8), the problem went away. So not sure if they discovered the problem and tried to push it as the same version or what.

]]>