Monthly Archives: November 2015

Deactivate WordPress plugin after 500 Internal Server Error

Date
Posted by
Comments0

This is not an expert article.
The goal of this article is to share my experiences related to problems and challenges I have had on my computer environment. I hope it can help people who are struggling with the same issues.

As a beginner of WordPress I set up a multi-site network with multiple domains and started my first post. Next I started installing some plugins to play around. The first plugins worked fine. However, when I installed the next plugin something went wrong. I noticed that I could still open the dashboard of the site I was working on, but I was not able to enter the Network Admin area to manage the WordPress Network. I got  a HTTP 500 Internal Server Error. On the internet I found the following link:

http://www.wpbeginner.com/wp-tutorials/how-to-fix-the-internal-server-error-in-wordpress/

Here it is explained that there could be several causes for this problem. Plugins could be one of the causes. If this is the  case then the plugin must be deactivated. The problem now is that due to the HTTP 500 Error I was unable to open the network plugins menu to disable the latest plugin that was installed. Then I found the following link:

http://www.wpbeginner.com/plugins/how-to-deactivate-all-plugins-when-not-able-to-access-wp-admin/

This article explains that all plugins can be deactivated by renaming the “../wp-content/plugins” map into a different name . Renaming can be done using FTP, but I used SSH in my linux terminal. After remote login I changed directory to the wp-content directory and renamed the plugins directory using the following terminal commands on the server site:

cd WordPress/wp-content
mv plugins plugin_tmp

Next I tried to enter the WordPress Network Admin area again using my browser. It turned out now there was no HTTP 500 Error. Therefore is must be concluded that one of the plugins was causing the problem. Next I renamed the plugins directory to its original name and started looking for the specific plugin that was causing the problem. This was done by  renaming one of the plugin sub-directories to deactivate a specific plugin. This way I could determine which plugin(s) were causing the problem and which not. I removed the problem causing plugins using the terminal commands:

cd WordPress/wp-content/plugins
rm -R plugin_name

where “plugin_name” was the directory name of the plugin to be removed. This procedure has solved my  HTTP 500 Internal Server Error on entering the WordPress Network Admin area.

SeaMonkey on Ubuntu 14.04

Date
Posted by
Comments0

This is not an expert article.
The goal of this article is to share my experiences related to problems and challenges I have had on my computer environment. I hope it can help people who are struggling with the same issues.

In the past I had some experience with SeaMonkey as a “What You See is What You Get” (WYSIWYG) HTML editor. SeaMonkey made it quite easy for me to set up a webpage and to make little html changes to fine tune the page in the way that I liked.

Currently I’m working with a Ubuntu 14.04 system and wanted to use SeaMonkey on this system. SeaMonkey is not included in the Ubuntu Software enter, so it must be installed in another way.

From  the SeaMonkey Website the Ubuntu version can be downloaded and the instructions for unpacking are described. However, after installation I tried to start SeaMonkey from terminal using the command ./seamonkey. This resulted in the following error message:

XPCOMGlueLoad error for file /home/ole/bin/seamonkey2/seamonkey/libxul.so:
libdbus-glib-1.so.2: cannot open shared object file: No such file or directory
Couldn't load XPCOM.

Apparently additional libraries had to be installed, which I did not known how to do. Therefore I decided to abort this installation and to search for alternative ways for installation. I found the following link:

http://linuxg.net/how-to-install-seamonkey-2-25-on-ubuntu-14-0413-1012-1012-04-linux-mint-161413-and-elementary-os-0-2/

This page describes how to install SeaMonkey 2.25 on Ubuntu 14.04 from terminal. For installation the following commands have to performed from terminal:

 $ echo -e "deb http://downloads.sourceforge.net/project/ubuntuzilla/mozilla/apt all main" | sudo tee -a /etc/apt/sources.list > /dev/null
$ sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com C1289A29
$ sudo apt-get update
$ sudo apt-get install seamonkey-mozilla-build

This resulted in a complete installation of SeaMonkey.