<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Blogs for Photogs &#187; Alerts</title>
	<atom:link href="http://www.blogsforphotogs.com/category/alerts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blogsforphotogs.com</link>
	<description></description>
	<lastBuildDate>Wed, 28 Mar 2012 22:28:51 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Alert: WP-Spamfree plugin breaks WordPress 3.1</title>
		<link>http://www.blogsforphotogs.com/2011/03/24/alert-wp-spamfree-plugin-breaks-wordpress-3-1/</link>
		<comments>http://www.blogsforphotogs.com/2011/03/24/alert-wp-spamfree-plugin-breaks-wordpress-3-1/#comments</comments>
		<pubDate>Fri, 25 Mar 2011 05:20:07 +0000</pubDate>
		<dc:creator>Theresa</dc:creator>
				<category><![CDATA[Alerts]]></category>

		<guid isPermaLink="false">http://blogsforphotogs.com/?p=734</guid>
		<description><![CDATA[ATTENTION ALL BLOG CLIENTS: Please check your plugins list for the WP-Spamfree plugin. I installed this plugin for MANY of you. If you have it activated, please deactivate it. The plugin is no longer supported by the developers or WordPress. I&#8217;ve found that on some hosts, it actually breaks WordPress. A good alternative for an [...]]]></description>
			<content:encoded><![CDATA[<p>ATTENTION ALL BLOG CLIENTS:<br />
Please check your plugins list for the WP-Spamfree plugin.  I installed this plugin for MANY of you.  If you have it activated, please deactivate it.  The plugin is no longer supported by the developers or WordPress.  I&#8217;ve found that on some hosts, it actually breaks WordPress.  A good alternative for an anti-spam plugin is the SI Captcha Anti-Spam plugin.  Just go to Plugings&#8211;>Add New and search for that name and activate it.  You won&#8217;t need to do anything after that.<br />
Thanks!</p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.blogsforphotogs.com%2F2011%2F03%2F24%2Falert-wp-spamfree-plugin-breaks-wordpress-3-1%2F&amp;title=Alert%3A%20WP-Spamfree%20plugin%20breaks%20WordPress%203.1" id="wpa2a_2"><img src="http://www.blogsforphotogs.com/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.blogsforphotogs.com/2011/03/24/alert-wp-spamfree-plugin-breaks-wordpress-3-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Broken Inline Comment Forms with WordPress 3.1</title>
		<link>http://www.blogsforphotogs.com/2011/03/04/broken-inline-comment-forms-with-wordpress-3-1/</link>
		<comments>http://www.blogsforphotogs.com/2011/03/04/broken-inline-comment-forms-with-wordpress-3-1/#comments</comments>
		<pubDate>Sat, 05 Mar 2011 03:51:41 +0000</pubDate>
		<dc:creator>Theresa</dc:creator>
				<category><![CDATA[Alerts]]></category>

		<guid isPermaLink="false">http://blogsforphotogs.com/?p=704</guid>
		<description><![CDATA[I discovered this week that with all blogs (including this one) set up with inline commenting using the Ajax WordPress 2.8 plugin, the comment form will return an error message &#8220;ERROR RECEIVED:&#8221; in red when someone tries to submit a comment.  This only happens with the current upgrade of WordPress, which is now at 3.1.  [...]]]></description>
			<content:encoded><![CDATA[<p>I discovered this week that with all blogs (including this one) set up with inline commenting using the <a href="http://ajaxedwp.com/2010/06/ajaxed-wp-3-0-coming-soon/#awp::/" target="_blank">Ajax WordPress 2.8 plugin</a>, the comment form will return an error message &#8220;ERROR RECEIVED:&#8221; in red when someone tries to submit a comment.  This only happens with the current upgrade of <strong>WordPress, which is now at 3.1</strong>.  BUT, the comment does still go through and is received by the blog owner, although the person leaving the comment doesn&#8217;t know that it has gone through because of the error message.  I&#8217;ve been researching on the problem and haven&#8217;t found any documentation on it and the plugin developer has yet to respond to my message regarding the issue.</p>
<p>I&#8217;m currently trying to figure out an easy fix, but seeing as the plugin has cornered the market on the inline comments and comment forms functionalities, I have yet to find an alternative.  For now, my only suggestion is that you DON&#8217;T upgrade to WordPress 3.1 if you haven&#8217;t already, at least until the plugin developer comes back with a fix, which hopefully will be soon.  He announced <a href="http://ajaxedwp.com/2010/06/ajaxed-wp-3-0-coming-soon/" target="_blank">nearly 9 months ago</a> that an upgrade was imminent so I&#8217;m crossing my fingers and toes that it will be very soon.  Maybe my message to him about the plugin being broken will prompt him to release it sooner.</p>
<p>Again, inline comment forms (typically on the front page of blogs, not individual posts) are returning error messages with the current WordPress 3.1 upgrade.  Comments are still coming through though, but at least you know to inform your blog visitors that their comments are still being received.</p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.blogsforphotogs.com%2F2011%2F03%2F04%2Fbroken-inline-comment-forms-with-wordpress-3-1%2F&amp;title=Broken%20Inline%20Comment%20Forms%20with%20WordPress%203.1" id="wpa2a_4"><img src="http://www.blogsforphotogs.com/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.blogsforphotogs.com/2011/03/04/broken-inline-comment-forms-with-wordpress-3-1/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>PSA: Security Alert for Bludomain customers</title>
		<link>http://www.blogsforphotogs.com/2009/11/08/psa-security-alert-for-bludomain-customers/</link>
		<comments>http://www.blogsforphotogs.com/2009/11/08/psa-security-alert-for-bludomain-customers/#comments</comments>
		<pubDate>Sun, 08 Nov 2009 08:31:55 +0000</pubDate>
		<dc:creator>Theresa</dc:creator>
				<category><![CDATA[Alerts]]></category>

		<guid isPermaLink="false">http://www.blogsforphotogs.com/?p=421</guid>
		<description><![CDATA[Argh, really if you haven&#8217;t found out by now, there are blog hackers out there really screwing things up.  I&#8217;ve had quite a few old and new clients coming to me for help because their blogs are suddenly &#8220;missing&#8221;.  Luckily I&#8217;ve gotten them all back and running.  Oddly though, they&#8217;ve all been Bludomain customers.  Hmmm&#8230;wonder [...]]]></description>
			<content:encoded><![CDATA[<p>Argh, really if you haven&#8217;t found out by now, there are blog hackers out there really screwing things up.  I&#8217;ve had quite a few old and new clients coming to me for help because their blogs are suddenly &#8220;missing&#8221;.  Luckily I&#8217;ve gotten them all back and running.  Oddly though, they&#8217;ve all been Bludomain customers.  Hmmm&#8230;wonder why?  Well, (among other things) Bludomain is notorious for recycling passwords for their hosting customers.  I have no idea if they instruct their customers to change the passwords for the cpanels and ftp sites, but apparently a lot of people don&#8217;t bother changing them.  If you host with Bludomain and are just hearing about this for the first time, please please PLEASE CHANGE YOUR PASSWORDS.  You&#8217;ll thank me for it later (although obviously not paying me to fix your hacked-into blog&#8230;hmph).  Maybe you&#8217;ll remember that I was kind enough to post this little PSA and will hire me to do a little work on your blog in the future (wink wink nudge nudge). <img src='http://www.blogsforphotogs.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>While I&#8217;m on this mission to save-everyone&#8217;s-blog-from-biting-the-dust, I wanted to remind ALL of you (yes, I mean you, not just Bludomain customers) to have a database backup plugin running on your blog on at least a weekly basis.  ALSO, it&#8217;s a good idea to do a <a href="http://www.siteground.com/tutorials/cpanel/backup.htm">FULL BACKUP of your site&#8217;s content</a>.  Depending on your hosting company, this can be done through your control panel and/or your ftp site.  Why a full backup of the content?  Well, because a database backup only saves the blog&#8217;s content in code, but not all the zillions of  image files, videos, etc&#8230; that you undoubtedly have attached to your blog and you may very well lose in case of a server failure, which your host should take care of with their own backups, but it&#8217;s good to be safe.</p>
<p>M&#8217;kay, my job is DONE.</p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.blogsforphotogs.com%2F2009%2F11%2F08%2Fpsa-security-alert-for-bludomain-customers%2F&amp;title=PSA%3A%20Security%20Alert%20for%20Bludomain%20customers" id="wpa2a_6"><img src="http://www.blogsforphotogs.com/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.blogsforphotogs.com/2009/11/08/psa-security-alert-for-bludomain-customers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Old WordPress versions under attack &#8211; upgrade to 2.8.4</title>
		<link>http://www.blogsforphotogs.com/2009/09/05/old-wordpress-versions-under-attack-upgrade-to-2-8-4/</link>
		<comments>http://www.blogsforphotogs.com/2009/09/05/old-wordpress-versions-under-attack-upgrade-to-2-8-4/#comments</comments>
		<pubDate>Sat, 05 Sep 2009 19:10:59 +0000</pubDate>
		<dc:creator>Theresa</dc:creator>
				<category><![CDATA[Alerts]]></category>
		<category><![CDATA[Wordpress News]]></category>

		<guid isPermaLink="false">http://www.blogsforphotogs.com/?p=355</guid>
		<description><![CDATA[I just got wind of this moments ago (thanks Barbara!) and thought I should pass it on to everyone. If you&#8217;re still operating under older versions of WordPress, you may be susceptible to some recent and persistent attacks of your database. Sounds like some serious stuff! You can read more about it here: http://lorelle.wordpress.com/2009/09/04/old-wordpress-versions-under-attack/ If [...]]]></description>
			<content:encoded><![CDATA[<p>I just got wind of this moments ago (thanks Barbara!) and thought I should pass it on to everyone.  If you&#8217;re still operating under older versions of WordPress, you may be susceptible to some recent and persistent attacks of your database.  Sounds like some serious stuff!</p>
<p>You can read more about it here: http://lorelle.wordpress.com/2009/09/04/old-wordpress-versions-under-attack/</p>
<p>If you have version 2.8+, you may be able to upgrade easily through the built-in function.  If you are pre 2.8+ or have trouble using the function, you can contact me to do it for you.  Upgrades are $35.</p>
<p>If you want to try and install the upgrade yourself manually, instructions to do so are here: http://codex.wordpress.org/Upgrading_WordPress<br />
Just follow the &#8220;Three Step Manual Upgrade &#8221; instructions.</p>
<p>If your blog has already been attacked and need help with fixing it, contact me also and I can see how to go about fixing it.  According to that link, there may be a way to recover a clean database.</p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.blogsforphotogs.com%2F2009%2F09%2F05%2Fold-wordpress-versions-under-attack-upgrade-to-2-8-4%2F&amp;title=Old%20WordPress%20versions%20under%20attack%20%E2%80%93%20upgrade%20to%202.8.4" id="wpa2a_8"><img src="http://www.blogsforphotogs.com/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.blogsforphotogs.com/2009/09/05/old-wordpress-versions-under-attack-upgrade-to-2-8-4/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Backup now, Backup often!</title>
		<link>http://www.blogsforphotogs.com/2009/03/17/backup-now-backup-often/</link>
		<comments>http://www.blogsforphotogs.com/2009/03/17/backup-now-backup-often/#comments</comments>
		<pubDate>Tue, 17 Mar 2009 23:59:33 +0000</pubDate>
		<dc:creator>Theresa</dc:creator>
				<category><![CDATA[Alerts]]></category>

		<guid isPermaLink="false">http://www.blogsforphotogs.com/?p=283</guid>
		<description><![CDATA[Ok, so you guys are all photographers and know how important it is to backup your images. Well the same goes for your blog. I&#8217;m making this a general reminder to everyone to make sure and backup your database at least once a week. I had a client today e-mailing me frantically because she deleted [...]]]></description>
			<content:encoded><![CDATA[<p>Ok, so you guys are all photographers and know how important it is to backup your images.  Well the same goes for your blog.  I&#8217;m making this a general reminder to everyone to make sure and backup your database at least once a week.  I had a client today e-mailing me frantically because she deleted 3 months worth of posts by accident.  There were NO backups made of them.  Luckily, I had her blog on my reader so I was able to send them to her one by one, but she will have to manually rebuild her posts.  *sigh*  So sad&#8230;</p>
<p>So don&#8217;t let that happen to you!  The easiest way to backup your database is to install the <a href="http://wordpress.org/extend/plugins/wp-db-backup/">WP DB-Backup Plugin</a>.  You can specify how often to do the backup.  It will run the backup, and you can have it either e-mail you, save it on your server, or download it to your computer.</p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.blogsforphotogs.com%2F2009%2F03%2F17%2Fbackup-now-backup-often%2F&amp;title=Backup%20now%2C%20Backup%20often%21" id="wpa2a_10"><img src="http://www.blogsforphotogs.com/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.blogsforphotogs.com/2009/03/17/backup-now-backup-often/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Alert: for those who have the WordPress Upgrade Plugin and WP2.7</title>
		<link>http://www.blogsforphotogs.com/2009/01/23/alert-for-those-who-have-the-wordpress-upgrade-plugin-and-wp27/</link>
		<comments>http://www.blogsforphotogs.com/2009/01/23/alert-for-those-who-have-the-wordpress-upgrade-plugin-and-wp27/#comments</comments>
		<pubDate>Fri, 23 Jan 2009 07:46:32 +0000</pubDate>
		<dc:creator>Theresa</dc:creator>
				<category><![CDATA[Alerts]]></category>

		<guid isPermaLink="false">http://www.blogsforphotogs.com/?p=103</guid>
		<description><![CDATA[For anyone who is operating with Wordrpess 2.7+ and has the WordPress Upgrade Plugin (I installed them with the most recent packages), please delete this plugin from your plugin list. Since WordPress 2.7 already has an upgrade functionality built-in, the plugin conflicts with the upgrade and needs to be removed. I&#8217;ve found that it also [...]]]></description>
			<content:encoded><![CDATA[<p>For anyone who is operating with Wordrpess 2.7+ and has the WordPress Upgrade Plugin (I installed them with the most recent packages), please delete this plugin from your plugin list.  Since WordPress 2.7 already has an upgrade functionality built-in, the plugin conflicts with the upgrade and needs to be removed.  I&#8217;ve found that it also makes other plugins non-functional.</p>
<p>This has been a PSA from Blogs for Photogs.  Please go about your business&#8230;</p>
<p><a class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=http%3A%2F%2Fwww.blogsforphotogs.com%2F2009%2F01%2F23%2Falert-for-those-who-have-the-wordpress-upgrade-plugin-and-wp27%2F&amp;title=Alert%3A%20for%20those%20who%20have%20the%20WordPress%20Upgrade%20Plugin%20and%20WP2.7" id="wpa2a_12"><img src="http://www.blogsforphotogs.com/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.blogsforphotogs.com/2009/01/23/alert-for-those-who-have-the-wordpress-upgrade-plugin-and-wp27/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

