<?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/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	>

<channel>
	<title>Wordpress &#8211; BrilliantCode.net</title>
	<atom:link href="https://en.brilliantcode.net/category/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>https://en.brilliantcode.net</link>
	<description></description>
	<lastBuildDate>Wed, 08 Apr 2020 20:01:57 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.2.3</generator>

<image>
	<url>https://i2.wp.com/en.brilliantcode.net/wp-content/uploads/2017/06/cropped-icon-2.png?fit=32%2C32&#038;ssl=1</url>
	<title>Wordpress &#8211; BrilliantCode.net</title>
	<link>https://en.brilliantcode.net</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">172940998</site>	<item>
		<title>WordPress DB went too large</title>
		<link>https://en.brilliantcode.net/1347/wordpress-db-went-too-large/</link>
				<comments>https://en.brilliantcode.net/1347/wordpress-db-went-too-large/#comments</comments>
				<pubDate>Thu, 02 Apr 2020 15:19:54 +0000</pubDate>
		<dc:creator><![CDATA[Andy Wang]]></dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[MySQL]]></category>

		<guid isPermaLink="false">https://en.brilliantcode.net/?p=1347</guid>
				<description><![CDATA[<p>It's my first time dealing with this kind of problem. The situation was the entire 160GB of server storage was totally used up by MySQL database files, and due to insufficient storage restart MySQL was also failed. Finally, I found the problem is caused by wp_options and binary log of MySQL.</p>
<p>This article <a rel="nofollow" href="https://en.brilliantcode.net/1347/wordpress-db-went-too-large/">WordPress DB went too large</a> made a debut on <a rel="nofollow" href="https://en.brilliantcode.net">BrilliantCode.net</a> .</p>
]]></description>
						<wfw:commentRss>https://en.brilliantcode.net/1347/wordpress-db-went-too-large/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
						<post-id xmlns="com-wordpress:feed-additions:1">1347</post-id>	</item>
		<item>
		<title>WordPress wp-admin https redirect loops</title>
		<link>https://en.brilliantcode.net/1296/wordpress-wp-admin-https-redirect-loops/</link>
				<comments>https://en.brilliantcode.net/1296/wordpress-wp-admin-https-redirect-loops/#respond</comments>
				<pubDate>Tue, 24 Mar 2020 08:50:46 +0000</pubDate>
		<dc:creator><![CDATA[Andy Wang]]></dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[SSL]]></category>

		<guid isPermaLink="false">https://en.brilliantcode.net/?p=1296</guid>
				<description><![CDATA[<p>Unfortunately you found this post. That means you must meet some trouble like as I met before. The tricky issue is your wp-admin of Wordpress will be traped into a redirect loop until browser show an error called ERR_TOO_MANY_REDIRECTS.<br />
Let's leave the root cause behind first and give you the answer that you could try to resolve this issue.</p>
<p>This article <a rel="nofollow" href="https://en.brilliantcode.net/1296/wordpress-wp-admin-https-redirect-loops/">WordPress wp-admin https redirect loops</a> made a debut on <a rel="nofollow" href="https://en.brilliantcode.net">BrilliantCode.net</a> .</p>
]]></description>
						<wfw:commentRss>https://en.brilliantcode.net/1296/wordpress-wp-admin-https-redirect-loops/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
						<post-id xmlns="com-wordpress:feed-additions:1">1296</post-id>	</item>
		<item>
		<title>Jetpack error &#8220;SSL Failed: WordPress reports no SSL support&#8221;</title>
		<link>https://en.brilliantcode.net/1251/wp-issues-jetpack-error-ssl-failed-wordpress-reports-no-ssl-support/</link>
				<comments>https://en.brilliantcode.net/1251/wp-issues-jetpack-error-ssl-failed-wordpress-reports-no-ssl-support/#respond</comments>
				<pubDate>Fri, 07 Feb 2020 16:56:05 +0000</pubDate>
		<dc:creator><![CDATA[Andy Wang]]></dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[SELinux]]></category>

		<guid isPermaLink="false">https://en.brilliantcode.net/?p=1251</guid>
				<description><![CDATA[<p>"SSL Failed: WordPress reports no SSL support" this error message may show up when you enter the dashboard of Jetpack. It let users quite hard to understand what happened right now...<br />
Fortunately, If you just use CentOS or Fedora as your server's operating system, then I congrats that you find the right post for dealing with this issue in wordpress.</p>
<p>This article <a rel="nofollow" href="https://en.brilliantcode.net/1251/wp-issues-jetpack-error-ssl-failed-wordpress-reports-no-ssl-support/">Jetpack error &#8220;SSL Failed: WordPress reports no SSL support&#8221;</a> made a debut on <a rel="nofollow" href="https://en.brilliantcode.net">BrilliantCode.net</a> .</p>
]]></description>
						<wfw:commentRss>https://en.brilliantcode.net/1251/wp-issues-jetpack-error-ssl-failed-wordpress-reports-no-ssl-support/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
						<post-id xmlns="com-wordpress:feed-additions:1">1251</post-id>	</item>
	</channel>
</rss>
