<?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>loading problem &#8211; A Learning Journey</title>
	<atom:link href="https://slc4u.org/wp-new/tag/loading-problem/feed/" rel="self" type="application/rss+xml" />
	<link>https://slc4u.org/wp-new</link>
	<description>Views &#38; Musings of Dr. CHOW Yong Neng 周永能博士的观点与思考</description>
	<lastBuildDate>Fri, 15 Jun 2018 11:55:31 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>What to do when your WordPress just refuses to load?</title>
		<link>https://slc4u.org/wp-new/2018/06/15/what-to-do-when-your-wordpress-just-refuses-to-load/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=what-to-do-when-your-wordpress-just-refuses-to-load</link>
					<comments>https://slc4u.org/wp-new/2018/06/15/what-to-do-when-your-wordpress-just-refuses-to-load/#respond</comments>
		
		<dc:creator><![CDATA[Chow YN]]></dc:creator>
		<pubDate>Fri, 15 Jun 2018 11:55:31 +0000</pubDate>
				<category><![CDATA[Learning]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[Elementor]]></category>
		<category><![CDATA[loading problem]]></category>
		<category><![CDATA[plugins]]></category>
		<category><![CDATA[wordpress]]></category>
		<guid isPermaLink="false">https://slc4u.org/learning/?p=3334</guid>

					<description><![CDATA[What should you do if your WordPress site just stops loading? This article shares the writer's experience with this issue where a step-by-step solution for the problem is given. Also highlighted is the usage of Page Builder plugins &#38; their associated supporting plugins. Never update plugins en mass is the key message.]]></description>
										<content:encoded><![CDATA[<p>[show_post_categories show=&#8221;category&#8221; hyperlink=&#8221;yes&#8221;]</p>
<p>[show_post_categories show=&#8221;tag&#8221; hyperlink=&#8221;yes&#8221;]</p>
<p><span style="font-weight: 400;">Just under four days ago, I found out to my horror that my website-blog running on WordPress just refused to load. This was after I did the routine updating of plugins and themes. So I Googled what one is suppose to do (and what could have gone wrong). I tried several “remedies” found on Google and am sharing my learning on this with my readers.</span></p>
<h2><span style="font-weight: 400;">Don’t click the “Update” button!</span></h2>
<p><span style="font-weight: 400;">Previously, as advised by many experts, I dutifully would go to the “Plugins” page to manually update each affected plugin. I was getting lazy and lately had been clicking the “Update” tab found at the top menu of my Dashboard. That was the key to all my woes (as shall be divulged below).</span></p>
<p><span style="font-weight: 400;">There were several plugins to be updated. I clicked the Update button, the updating proceeded, but it then STOP! The screen of my website (aka this one that you are reading) went totally blank!</span></p>
<p><span style="font-weight: 400;">My website went &#8216;dead’! Panic set in! “What the devil did I do?”, I asked myself.</span></p>
<h2><span style="font-weight: 400;">Frantic search for the solution</span></h2>
<p><span style="font-weight: 400;">Off I went to Google “wordpress site won&#8217;t load after update of plugins” and found several useful sites.</span></p>
<p><span style="font-weight: 400;">The best of these was one with a good </span><a href="http://pintsizedsites.com/fixing-wordpress-broken-plugin/"><span style="font-weight: 400;">advisory</span></a><span style="font-weight: 400;"> which gave more or less this message: “Don’t trust the Update button, do your plugin update one by one so that if you hit trouble, at least you can easily identify the culprit.”  So I learned that I had to do a lot more to overcome this outage. I followed the instructions given and here are the steps I took.</span></p>
<ol>
<li style="font-weight: 400;"><span style="font-weight: 400;">I accessed the control panel (cpanel) of my website hosting.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Using “File Manager” I traced my path to the public.html and found the folder with my WordPress installation.<br />
<a href="https://slc4u.org/learning/wp-content/uploads/2018/06/cpanel-slc4u-edited.jpg"><img fetchpriority="high" decoding="async" class="aligncenter size-full wp-image-3337" src="https://slc4u.org/learning/wp-content/uploads/2018/06/cpanel-slc4u-edited.jpg" alt="" width="750" height="635" srcset="https://slc4u.org/wp-new/wp-content/uploads/2018/06/cpanel-slc4u-edited.jpg 750w, https://slc4u.org/wp-new/wp-content/uploads/2018/06/cpanel-slc4u-edited-300x254.jpg 300w" sizes="(max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px" /></a></span><span style="font-weight: 400;"><br />
</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Diving deeper, inside my WordPress folder, I located the subfolder “wp-content” where it has a sub-subfolder called “plugins”.<br />
<a href="https://slc4u.org/learning/wp-content/uploads/2018/06/cpanel-filemgr-public-html-edited.jpg"><img decoding="async" class="aligncenter size-full wp-image-3336" src="https://slc4u.org/learning/wp-content/uploads/2018/06/cpanel-filemgr-public-html-edited.jpg" alt="" width="930" height="423" srcset="https://slc4u.org/wp-new/wp-content/uploads/2018/06/cpanel-filemgr-public-html-edited.jpg 930w, https://slc4u.org/wp-new/wp-content/uploads/2018/06/cpanel-filemgr-public-html-edited-300x136.jpg 300w, https://slc4u.org/wp-new/wp-content/uploads/2018/06/cpanel-filemgr-public-html-edited-768x349.jpg 768w" sizes="(max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 1362px) 62vw, 840px" /></a></span><span style="font-weight: 400;"><br />
</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">I renamed “plugins” to “brokenplugins”. Then created a new folder which I named “plugins”.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">I opened another tab on my web browser and tried my luck in accessing my website.  And it was back on! But as the “plugins” folder was empty, none of the plugins worked.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">I then went back to the “File Manager” and copied the plugins from “brokenplugins” to “plugins”, doing so one at a time. For each plugin that I copied over, I would go back to my website and reload to see if the newly copied in plugin caused any problematic files (aka corrupted files) that would crash the website.  All the plugins seemed to have uncorrupted files. But in this way of copying, all the plugins are still inactivated.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Next step was for me to activate each one of the plugins, one by one. And I found the culprit! It was Caldera Forms. WordPress was good that it detected the problem and did not allow me to activate Caldera Forms.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">I deleted Caldera Form from the “plugins” sub-subfolder and I thought my problem was solved.</span></li>
</ol>
<h2><span style="font-weight: 400;">Removal of a plugin, removed content associated with it too!</span></h2>
<p><span style="font-weight: 400;">Of course when you remove a plugin, the associated features and content would be removed too! In my case it was the contact form and order form. The latter actually was put in as “shortcode” on multiple pages of my website. </span></p>
<p><span style="font-weight: 400;">Once bitten, twice shy. I realized that I should have just used the “default” contact form from WordPress instead. I could also create a simple order form that served my needs from this too.</span></p>
<p><span style="font-weight: 400;">However, I noticed another issue!</span></p>
<h2><span style="font-weight: 400;">I couldn’t load Elementor, the page builder plugin!</span></h2>
<p><span style="font-weight: 400;">During earlier updating of </span><a href="https://elementor.com/?ref=2226"><span style="font-weight: 400;">Elementor</span></a><span style="font-weight: 400;"> and the third-party supporting plugins, I presume somehow the main Elementor editor was prevented from loading. Elementor is a very useful page builder plugin that takes that pain out of having to learn html coding for WordPress users like me. It allows users to do lots of web page design work using its standard elements which are supplemented by many third-party’s plugins too.</span></p>
<p><span style="font-weight: 400;">With Elementor not loading, although all the content I created using it was still showing, I was prevented from editing any content created with it. Hence I could not replace the forms previously made using Caldera Forms (and the ‘shortcodes” for these forms which remained after Caldera Forms was removed as a plugin were very glaring on the affected pages!).</span></p>
<h2><span style="font-weight: 400;">Lot’s of advise on Google but ….</span><span style="font-weight: 400;">.</span></h2>
<p><span style="font-weight: 400;">I found a lot of advisory via Google to tackle the Elementor plugin not loading issue. Well, at least I was not alone. One of these was from Elementor itself which gave</span><a href="https://docs.elementor.com/article/184-cant-edit-with-elementor"><span style="font-weight: 400;"> instructions</span></a><span style="font-weight: 400;"> to change some settings. This did not work for me!</span></p>
<p><span style="font-weight: 400;">I then found </span><a href="https://docs.elementor.com/article/189-having-problems-using-elementor-start-here"><span style="font-weight: 400;">another page</span></a><span style="font-weight: 400;"> from Elementor which advised that increasing the memory allocated to WordPress may solved the issue. But I would have to edit the associated php file, </span><i><span style="font-weight: 400;">wp-config.php</span></i><span style="font-weight: 400;"> which was found in the main WordPress installation folder. I was a bit apprehensive about messing around with a php file but the instructions given by a different web </span><a href="http://www.wpbeginner.com/wp-tutorials/fix-wordpress-memory-exhausted-error-increase-php-memory/"><span style="font-weight: 400;">page</span></a><span style="font-weight: 400;"> seemed to be showing that this was just a one-liner addition. So I increased my WordPress allocated memory to 128 Mb. But this did not bring back Elementor’s editor either.</span></p>
<p><span style="font-weight: 400;">I went back to Elementor’s support</span><a href="https://docs.elementor.com/article/189-having-problems-using-elementor-start-here"><span style="font-weight: 400;"> page</span></a><span style="font-weight: 400;"> and followed its advisory and proceeded to deactivate and reactivate each plugin in turn to see if any one of these was stopping Elementor editor from loading. I found out that the culprit was indeed a supporting plugin for Elementor, “Premium Addons for Elementor”. I could not even deactivate this plugin (after it was activated earlier). As such it would not be possible for me to just delete it via Dashboard of WordPress. I ended up having to remove the culprit using “File Manager”. However a warning message kept showing up at the Dashboard which warned about the missing “Premium Addons for Elementor”. Emptying the cache several times did not remove this message. </span><i><span style="font-weight: 400;">[But after a reload of the website, on the next day, this message was gone!] </span></i></p>
<p><span style="font-weight: 400;">Again, I had to rewrite all the content that was created by the elements provided by “Premium Addons”.</span></p>
<h2><span style="font-weight: 400;">Lessons Learned</span></h2>
<ol>
<li style="font-weight: 400;"><span style="font-weight: 400;">Never update plugins on WordPress en mass! Do it one at a time so that if something fouls up, at least you can pinpoint the culprit!</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">If you create forms using a third-party plugin, such as Caldera Forms, it is best to have at least a screenshot of the form so that you can recreate the content if things go wrong and you have to remove the offending plugin.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Always keep a copy of the content that you create with Page Builder and its supporting addons plugins. You will lose the content if you have to delete the addon plugins or the  main Page Builder plugin.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">You should keep life simple. Non-design heavy content, such as a blog page like this should be presented using the “native” WordPress editor. This will save you from a lot of headache and work which using a Page Builder will cause should the same page building plugin has to be deactivated or removed.</span></li>
</ol>
]]></content:encoded>
					
					<wfw:commentRss>https://slc4u.org/wp-new/2018/06/15/what-to-do-when-your-wordpress-just-refuses-to-load/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
