Dreamweaver vs. WordPress

This post has the potential to be a monster. Instead, I thought I would just touch on this subject. Dreamweaver vs. WordPress. Even though I started out with Dreamweaver and notepad, I prefer WordPress, these days. I say “these days”, because the way we build websites have changed quite a bit in the last 10 years. I started using Dreamweaver in the late 90’s. WordPress wasn’t around until 2003. When WordPress was released I decided to hop on board. Back then WordPress was not much of a website builder, it was a “Blog” builder. Many of us did not take WordPress serious as a “website” builder because of that. It wasn’t until 2010, I felt WordPress really began to take shape as a website builder and not just a “Blogging” platform. In 2019 WordPress has blossomed into one of the most popular website platforms among professional web designers and marketing professionals.

In 1997, Macromedia came out with Dreamweaver, then it was acquired by Adobe in 2005. To this day (4/2/17), I continue to use Dreamweaver for my much smaller projects and some sand-boxing. I find WordPress is easier for large scale dynamic functionality. Don’t get me wrong, for the right website project, Dreamweaver might be better. When it comes to building websites, everyone has their flavor. With there being so many tools out there to build websites in 2017, I say start out on the easiest platform WordPress. As of 2017, it’s your best bet.

Note: It doesn’t matter which tools you decided to use for your next website project, just as long as you know how to be creative with those tools.

WordPress White Page of Death

Most Common Troubleshooting Techniques: (without getting into too much detail)

#1. Rename your plugins folder – If a plugin is the problem, renaming the folder where WordPress looks, will cause WordPress to not load any plugins inside that folder.
#2. Changing your custom theme to a default WordPress theme.
#3. Check for caching configuration issues. (cashing plugins)
#4. Troubleshoot any possible database issues.

If you had no success, try updating or even going back a version of PHP running on your web host. One thing we must remember, not all versions of PHP are guaranteed to play nice. Just because you upgrade to the latest and greatest doesn’t mean it will perform any better. In fact, it may perform worse, or in my case temporarily take down all 20 of my sites. cause a white screen of death, on not just 1 website, but 17. Scary stuff. I was fortunate to get my sites back up within an hour. This isn’t always the case.

WordPress Internal Server Error

At one time or another every WordPress web developer has experienced the WordPress Internal Server Error. When it happens it can be scary. In this post I will go through the most common reasons why the WordPress Internal Server Error occurs.

A few things to try

Check your .htaccess file

Rename your .htaccess to .htaccess-old and try to re-connect to the site in question. If that fixed it, log into your WordPress site, go to settings / permalinks and click save. That will re-write your .htaccess file.

Check your WordPress memory limits

Create a php.ini file and add this line to it —> memory=64mb. Upload it to the wp-admin folder. If this corrects the issue, you will need to figure out which plugin is causing the memory limits to be reached. You may need to contact your web host for assistance.

Check your plugins

You can deactivate all your plugins at once by renaming your plugins folder to something else. If you are able to access your website after doing this, then one of your plugins is the issue.

Check your wp-admin and wp-includes directories

Download a fresh copy of WordPress and upload the wp-admin and wp-includes folders in place of the one’s on your server.

Check your file permissions

These setting are default and will work.

644 -rw-r–r– /home/user/wp-config.php
644 -rw-r–r– /home/user/cgi-bin/.htaccess
644 -rw-r–r– /home/user/cgi-bin/php.ini
755 -rwxr-xr-x /home/user/cgi-bin/php.cgi
755 -rwxr-xr-x /home/user/cgi-bin/php5.cgi

My web host recommends 644. 644 is usually the default for most web hosts.
When all else fails contact your web host for assistance with this issue or hire a guy like me. I can be reached from my contact page or 954-895-2555.

WordPress RSS Feed To Open New Page

If you plan on using the RSS Feed widget that comes with WordPress, go for it, it’s actually a solid plugin. The thing I’d like to tell you about it is how I prefer to get my RSS feeds using this plugin.

If you would prefer the RSS Feed links to open a new page. I will tell you how tovisitors won’t get pulled away from your site, just follow these instructions.

You’ll need access to your web host’s file manager or FTP access. Once logged into either, navigate to your website’s home directory, then go into wp-includes and look for widgets.php. Once that file is open hit ctrl + f on your keyboard and search for href=’$link’ and replace it with href=’$link’ target=’_blank’. You should see 2 instances, replace them both and save. Now your WordPress RSS Feed widget links will open a new tab or page.