Today I found out that a fellow schoolmate had lost his battle with depression. While five years younger than myself, I did not know him personally, we both had graduated from the same small rural school. Think Hoosiers but just a tad larger, total school population was around 500 for kindergarten through 12th grades. It was theRead more about It’s time to talk Mental Health[…]
Occasionally, after installing a new WordPress plugin you can get a 500 internal server error. This problem is compounded by being unable to access any page on the site. This includes both the front facing pages as well as the back-end administration section used to install and uninstall plugins.
I recently had this issue after installing W3 Cache plugin. I did a quick google search and came across a lot forums asking for help on this exact issue. It took a lot of shifting through different forums to determine that it was not going to be as simple as just deleting the specific plugin folder. Turned out the repair was almost that easy.
While setting up an e-commerce part of a multi site WordPress installation, I stumbled upon a “glitch” that took a rather long time to figure out and I want to pass on this information so that others do not lose valuable time. This “glitch” was nothing that was crippling for the entire operation rather just a very puzzling and frustrating experience. Upload file size was set to 1MB.
Full disclosure, I have a dislike of the command line interface especially on Windows machines. In my humble opinion, the main advantage Windows has over Linux is the world wide acceptance of the graphical user interface (GUI). That being said when I started using GitHub I tired a couple of different GUI clients designed to assist in the use of GitHub. The learning curve was steep and would require more time then I am willing to dedicate. This left the command line. It turns out that the command line is much easier then I had expected and I was pleasantly surprised.
Here’s how you do it.