<?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>Wordpress Archives - SCD Information Technology</title>
	<atom:link href="http://blog.scdit.com/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>We fix IT and you benefit...</description>
	<lastBuildDate>Tue, 27 Jul 2021 17:38:21 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>
	<item>
		<title>WordPress 5.8 Update Could Not Be Verified</title>
		<link>http://blog.scdit.com/wordpress-5-8-update-fix/</link>
					<comments>http://blog.scdit.com/wordpress-5-8-update-fix/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Thu, 22 Jul 2021 16:11:39 +0000</pubDate>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Wordpress]]></category>
		<guid isPermaLink="false">http://blog.scdit.com/?p=14705</guid>

					<description><![CDATA[<p>While working on a WordPress site we were prompted to update to 5.8, but the manually pushing the button to update keep failing. The process would start, but would run into errors and stop. We tried just manually moving the directories &#8220;wp-admin&#8221; and &#8220;wp-includes&#8221; from a downloaded zip of the latest version, but this didn&#8217;t [&#8230;]</p>
<p>The post <a href="http://blog.scdit.com/wordpress-5-8-update-fix/">WordPress 5.8 Update Could Not Be Verified</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/wordpress-5-8-update-fix/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>WordPress 5.6.2 Update to 5.7 Failed &#8211; Solved</title>
		<link>http://blog.scdit.com/wordpress-5-6-2-update-to-5-7-failed-solved/</link>
					<comments>http://blog.scdit.com/wordpress-5-6-2-update-to-5-7-failed-solved/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Wed, 10 Mar 2021 16:05:01 +0000</pubDate>
				<category><![CDATA[Divi Theme]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[XAMPP]]></category>
		<guid isPermaLink="false">http://blog.scdit.com/?p=13865</guid>

					<description><![CDATA[<p>We do love the ease of WordPress except when it goes wrong. While working on a new site we got the 5.7 update notification, and we hit the button to update. Well it didn&#8217;t go like planned. We had try to update manually, and not something we have done often. It went pretty easy, and [&#8230;]</p>
<p>The post <a href="http://blog.scdit.com/wordpress-5-6-2-update-to-5-7-failed-solved/">WordPress 5.6.2 Update to 5.7 Failed &#8211; Solved</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/wordpress-5-6-2-update-to-5-7-failed-solved/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>wp-admin “redirect_to”  old wrong URL after migration</title>
		<link>http://blog.scdit.com/wp-admin-redirect_to-wrong-url-after-migration/</link>
					<comments>http://blog.scdit.com/wp-admin-redirect_to-wrong-url-after-migration/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Fri, 05 Mar 2021 15:43:32 +0000</pubDate>
				<category><![CDATA[Divi Theme]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Wordpress]]></category>
		<guid isPermaLink="false">http://blog.scdit.com/?p=13790</guid>

					<description><![CDATA[<p>We recently used Akeeba Backup to migrate a WordPress site for testing purposes; however, whenever we after enter our credentials into the new URL&#8217;s admin area we got redirected the old URL admin area. This was frustrating because we didn&#8217;t notice at first and started experimenting on the good site. A search lead us to [&#8230;]</p>
<p>The post <a href="http://blog.scdit.com/wp-admin-redirect_to-wrong-url-after-migration/">wp-admin “redirect_to”  old wrong URL after migration</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/wp-admin-redirect_to-wrong-url-after-migration/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>DIVI Theme 2 Map Modules Not Working</title>
		<link>http://blog.scdit.com/divi-theme-2-map-modules-not-working/</link>
					<comments>http://blog.scdit.com/divi-theme-2-map-modules-not-working/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Thu, 09 Jan 2020 16:18:05 +0000</pubDate>
				<category><![CDATA[Divi Theme]]></category>
		<guid isPermaLink="false">http://blog.scdit.com/?p=4509</guid>

					<description><![CDATA[<p>We recently started a new site using a purchased Child Theme for Elegant Theme&#8217;s DIVI theme, but when needed two map modules on the same page the map module wasn&#8217;t working. Not working in the sense the module won&#8217;t &#8220;find&#8221; the second maps addresses. It was putting the starting location way out in the ocean. [&#8230;]</p>
<p>The post <a href="http://blog.scdit.com/divi-theme-2-map-modules-not-working/">DIVI Theme 2 Map Modules Not Working</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/divi-theme-2-map-modules-not-working/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Godaddy Managed WordPress SSL Installation</title>
		<link>http://blog.scdit.com/godaddy-managed-wordpress-ssl-installation/</link>
					<comments>http://blog.scdit.com/godaddy-managed-wordpress-ssl-installation/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Mon, 06 Jan 2020 20:47:34 +0000</pubDate>
				<category><![CDATA[Godaddy Web Hosting]]></category>
		<category><![CDATA[Managed Wordpress]]></category>
		<category><![CDATA[Wordpress]]></category>
		<guid isPermaLink="false">http://blog.scdit.com/?p=4439</guid>

					<description><![CDATA[<p>We recently completed a Godaddy Managed WordPress site using the Elegant Themes DIVI builder. The site launched but we found that the site wasn&#8217;t ranking high in Google. The SEO strategy seemed good; however, simply adding a SSL may help. Being short on time we decided to let Godaddy install the SSL. The manual method [&#8230;]</p>
<p>The post <a href="http://blog.scdit.com/godaddy-managed-wordpress-ssl-installation/">Godaddy Managed WordPress SSL Installation</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/godaddy-managed-wordpress-ssl-installation/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Gantry WordPress Post Titles Not Linking</title>
		<link>http://blog.scdit.com/gantry-wordpress-post-titles-not-linking/</link>
					<comments>http://blog.scdit.com/gantry-wordpress-post-titles-not-linking/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Thu, 24 May 2018 16:13:42 +0000</pubDate>
				<category><![CDATA[Gantry]]></category>
		<category><![CDATA[Wordpress]]></category>
		<guid isPermaLink="false">http://blog.scdeval.com/?p=275</guid>

					<description><![CDATA[<p>We switched our theme to Gantry and were very pleased; however, the blog post titles were no longer linking to the post. I quick search got me to Gantry&#8217;s site and an explanation on how to fix. http://docs.gantry.org/gantry5/configure/content In the WordPress Dashboard go into Gantry Theme area on the left sidebar. At the top of [&#8230;]</p>
<p>The post <a href="http://blog.scdit.com/gantry-wordpress-post-titles-not-linking/">Gantry WordPress Post Titles Not Linking</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/gantry-wordpress-post-titles-not-linking/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Gantry 5 Hydrogen WordPress Module Position Not Showing</title>
		<link>http://blog.scdit.com/gantry-5-hydrogen-wordpress-module-position-not-showing/</link>
					<comments>http://blog.scdit.com/gantry-5-hydrogen-wordpress-module-position-not-showing/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Mon, 23 Apr 2018 15:10:59 +0000</pubDate>
				<category><![CDATA[Gantry]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Wordpress]]></category>
		<guid isPermaLink="false">http://blog.scdeval.com/?p=264</guid>

					<description><![CDATA[<p>We were working with Gantry 5 Hydrogen theme in WAMP and couldn&#8217;t get the module positions to show in the Widget area. We added the Module Position to the template; however, when we went into the Widgets area that position didn&#8217;t show. We have done this feat before, but for some reason not working this [&#8230;]</p>
<p>The post <a href="http://blog.scdit.com/gantry-5-hydrogen-wordpress-module-position-not-showing/">Gantry 5 Hydrogen WordPress Module Position Not Showing</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/gantry-5-hydrogen-wordpress-module-position-not-showing/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Report Abusive IP Address</title>
		<link>http://blog.scdit.com/report-abusive-ip-address/</link>
					<comments>http://blog.scdit.com/report-abusive-ip-address/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Tue, 06 Feb 2018 16:29:38 +0000</pubDate>
				<category><![CDATA[Drupal]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[Joomla]]></category>
		<category><![CDATA[Web Form]]></category>
		<category><![CDATA[Wordpress]]></category>
		<guid isPermaLink="false">http://blog.scdeval.com/?p=197</guid>

					<description><![CDATA[<p>With certain websites we have seen an increase with incomplete form submissions that are getting past the ReCaptcha, so in each form we capture the IP address of the end user. We have been using the following website to report these IP addresses. https://www.abuseipdb.com/ Let us know if this helped you&#8230;. &#160;</p>
<p>The post <a href="http://blog.scdit.com/report-abusive-ip-address/">Report Abusive IP Address</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/report-abusive-ip-address/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Solved &#8211; WordPress &#8211; Fatal error: Allowed memory size of</title>
		<link>http://blog.scdit.com/180-2/</link>
					<comments>http://blog.scdit.com/180-2/#respond</comments>
		
		<dc:creator><![CDATA[Dwayne Grimes]]></dc:creator>
		<pubDate>Wed, 24 Jan 2018 17:15:51 +0000</pubDate>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Wordpress]]></category>
		<guid isPermaLink="false">http://blog.scdeval.com/?p=180</guid>

					<description><![CDATA[<p>We had a Godaddy domain IP address change and afterwards we unable to access sites we had in a sub-domain. After the IP issue was resolved the sites still didn&#8217;t come up. The page read Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2348617 bytes) in This article solved our issue. [&#8230;]</p>
<p>The post <a href="http://blog.scdit.com/180-2/">Solved &#8211; WordPress &#8211; Fatal error: Allowed memory size of</a> appeared first on <a href="http://blog.scdit.com">SCD Information Technology</a>.</p>
]]></description>
		
					<wfw:commentRss>http://blog.scdit.com/180-2/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
