Home / Wordpress / Error In WordPress And The Right Solution

Error In WordPress And The Right Solution

Error In WordPress And The Right Solution

Although WordPress is very easy to use, there is some common errors and panic for novice users. Fortunately, errors in WordPress that you experience may have been reported and addressed by others before you.

Error in WordPress and the Solution

Here we have summarized the tutorial on how to fix a number of popular errors in WordPress.Before troubleshooting an error in WordPress, make sure you have a complete WordPress backup.

If you still can not solve the error that occurred with the steps mentioned in this article, you can contact WordPress hosting company.

Let’s look further how to solve common problems on WordPress one by one.

How to Solve Error on Internal Server

Perhaps the most confusing error in WordPress for beginners is “Internal Server Error”, or sometimes “500 Internal Server Error.” This error usually appears when something goes wrong but the server can not identify where the problem is. Because error messages do not indicate where you need to look for the problem, it’s up to you how to figure it out.

You may see HTTP 500 Internal Server Error several times when it has been surfing the web for more than a year. Internal Server Error is a common error in WordPress that can make novice users panic. Unfortunately, panic is not the solution to this problem. Take a deep breath and understand if others before you also experience similar problems. With a little patience, this problem can be overcome.

Here are some possible solutions.

Check the corrupted .htaccess file

The first thing you need to do when troubleshooting an internal server error in WordPress is checking for a corrupted .htaccess file. You can do this by renaming the .htaccess file with a name like .htaccess_lama. To name the .htaccess file you need to login to the site using FTP. Once logged in, the .htaccess file will be in the same directory as the folders like wp-content, wp-admin, and wp-includes.

After naming the .htaccess file, try opening the site to see if the issue has been fixed. Before doing anything else, make sure you go to Settings ┬╗Permalinks and click the save button. This step will generate a new .htaccess file with rewrite rules to ensure the post page does not return to 404.

When checking a corrupted .htaccess file does not work, then you need to move on to the next step.

Increase the limit for PHP Memory

Sometimes an internal server error can occur when PHP memory limit is problematic. If you experience internal server errors only when logging into WordPress admin or when uploading images in wp-admin, then you need to increase memory limit with the following steps:

  • Create an empty text file called php.ini
  • Copy this code there: memory = 64MB
  • Save the file
  • Upload to wp-admin or folder using FTP

When upgrading the memory limit to a solution, you have solved this problem for a while. This is because there is certainly something that makes your memory limit problem, either because of coded plugin or inappropriate theme function. Try asking your hosting company so they can see the server logs to help find the right diagnosis.

Disable all plugins

If all of the above solutions do not work, then this error may be caused by a particular plugin or a combination of plugins that are out of sync with others. There is no way to know this, you must disable all plugins in WordPress.

Disable all plugins using FTP

With this method, you need to use an FTP client or file manager. First, you need to connect to the web site using FTP client and file manager in cPanel. Once connected, navigate to the / wp-content / folder.

In the wp-content folder, you’ll see a folder called plugins. This folder becomes the place WordPress keeps all plugins installed to your website. Right-click the plugins folder and select rename. Rename the plugins folder to whatever you like. After doing this, all plugins become inactive. Usually, this way is used when you can not access the admin area. If the problem is with your plugin, it allows you to login to the WordPress admin area.

After doing this step, go back to folder / wp-content / and return the name to plugins. Now you can re-enable plugins one by one. That way you’ll know exactly which plugin is causing the problem.

Disable all plugins using phpMyAdmin

The FTP method is easier, but you can disable all plugins using phpMyAdmin. First, you need to login to the web hosting dashboard.

Then click the phpMyAdmin icon under ‘Databases.’ A new browser window will appear, select the WordPress database, and a WordPress database table will appear.

Click the wp_options table. In the wp_option table, you can see the rows of options. Find the ‘active_plugins’ option and click ‘edit’. On the next screen change, the option_value option to a: 0: {} then click the Go button to save this change.

Now you can successfully disable the WordPress plugin using phpMyAdmin. If one of the plugins makes you unable to access the WordPress admin area, you should now be able to log in.

When disabling the plugin can resolve errors, it means one of the plugins that caused this problem. Simply re-enable the plugins one by one until you find the cause of the problem, remove the plugin, and report the error in the author plugin.

Re-upload the main file

If the plugin option does not resolve the internal server error, you will need to re-upload the wp-admin and wp-include folders. This will not remove any information, but it can be a solution when there is a corrupted file.

Check with your hosting provider

If all else fails, you need to contact the hosting provider. By looking at the server logs, they can detect problems that occur.

How to Overcome Error Sidebar Under Content on WordPress

Another common problem facing beginners is when the sidebar appears below the content when it should appear next to the content. This problem is mostly caused by the WordPress theme.

Sometimes when users add the snippet code to the site, they forget to close the HTML div tag which could cause damage to the theme layout. Another cause is the extent of disproportionate CSS.

Has this problem started happening recently? Only happens on a particular post or page? If the answer is yes, then the following steps can help you.

Find the section you recently changed. Do you add plugins? Making changes related to HTML? One of the best ways to resolve this error is by using W3 Validator.

When you create a custom theme and this problem occurs, there may be more than one problem. One of them has been solved by the above steps. Some other problems can be:

Incorrect area ratios. You have to make it all proportional. For example, content size is 600 px and a 300 px sidebar with a margin of 60 px.

Another problem could be a float property. You should make sure to add a float, left and right, right on the appropriate element. If you do not do it this way will not work.

How to Troubleshoot Image Upload in WordPress

Sometimes users find all images from their site lost. When a user tries to upload an image to a post using a media uploader, the result becomes an error.

All files in the media library will be corrupted. This error occurs due to improper file and permission directory of WordPress installation.

A number of factors can cause this problem and most often due to wrong file permissions. Upload directory must have proper file permissions, otherwise, WordPress will not be able to store files in it or sometimes not even display files from upload directory. To set up the correct file permissions for the upload directory, you need an FTP client, such as Filezilla.

My previous site works fine, then who changed its file permissions? This can happen for several reasons. Maybe your web hosting provider is upgrading and some are causing file permissions to change. It’s also possible that hackers made those changes when uploading a hacked backdoor. In shared hosting, it is likely that when a user installs a theme or plugin from an untrusted source, the script changes the file permissions for everyone.

When all goes well on your website, then you just need to change file permissions back to normal. When in doubt, ask your hosting provider for support.

You need to connect to the website by using FTP client then go to directory / wp-content /. There you will see folder/uploads /. Right-click on the uploads directory and select the file permissions.

A new dialog box for file permissions will open. In the beginning, you need to set the file permissions to upload the directory and all sub-directories in it to 744. To do this, enter 744 in the numeric box, and then check the box next to it into Recurse into subdirectories. Finally, you click on the “Apply to directories only” button. Click OK to apply this change. Filezilla will now begin applying file permissions to directories.

If setting the directory permissions to 744 does not give a solution, you can try to be 755.

In the next step, set file permissions for all files uploaded directory. To do so, right-click on the upload directory and select the file permissions. In the file permissions, dialog box replaces numeric to 644. Check the Recurse into subdirectories box. Then click on the “Apply to files only.” Click the OK button to apply this change. Filezilla will begin to set file permissions for all files. Once done, you can go back to the WordPress admin area and start uploading the image again. Know what tools you can use to adjust the image size.

How to Troubleshoot Always Log Out on WordPress

Have you ever encountered a problem where WordPress is always logged out? The problem persists even if you’ve done normally troubleshoots like disabling plugins, clearing cache, clearing browser cookies and restricting WordPress from backups.

To find out why WordPress always logs out, you need to understand how to log into WordPress. WordPress set the cookies in your browser to authenticate login sessions. This cookie is set for the WordPress URL stored in the settings section. When you access from URLs that do not match the settings in WordPress, WordPress will not be able to authenticate your session.

Fixed login issues

A simple fix for this login issue is to make sure you have the same URL in your site address and WordPress address in your WordPress settings. This means you must choose the www or none www URL in both charts. Log in to the WordPress Dashboard and select Settings >> General.

If you can not access the admin area, you can update this field by editing wp-config.php file. Connect to the website using the FTP client, and place the wp-config.php file in the root directory of the site. You need to download the file to the desktop and open it in a text editor like Notepad. Add this code just above the firearm That’s all, stop editing! Happy blogging. Remember to replace example.com with your own domain name.

Why can this solution work? Technically, www is a subdomain. This means that URLs with www and without www are actually two different domains. Changing and updating URLs to the same address will solve this problem.

You also need to note the incorrect settings in the WordPress address and website address also caused too many redirect problems in WordPress.

How to Troubleshoot an Inappropriate Facebook Thumbnail on WordPress

There are many factors that prevent Facebook from guessing the right image thumbnail. One most common factor is the number of image settings in original: image tags where the image feature is smaller than other images.

Facebook uses open graph tags (original) and many WordPress plugins like WordPress SEO by Yoast that automatically add them to the site to prevent missing thumbnail issues.

Among other causes are caching plugins, CDN issues, open graph meta tags for missing thumbnail images, and so on. It is difficult to guess what caused this problem because there are no specific error messages that are displayed when using the debugging tool.

Here’s how to fix inappropriate Facebook thumbnail issues.

Upload thumbnail images manually

When you share an article on a Facebook page, and Facebook does not select the right thumbnail, you can click the upload link to upload the image you want to use.

The images you upload are stored in the photo section of your Facebook page. You can delete images on photos, Facebook will continue to show the images you upload as thumbnails for articles on your timeline.

But this solution does not affect other users. This means that when other users share your article, it still appears the wrong thumbnail. But the next step can handle it.

Tell Facebook to use thumbnails of your choice

When using WordPress SEO with the Yoast plugin, you can easily set up specific thumbnail images for Facebook.

When writing a post, scroll down to the Yoast SEO meta box under the post editor and click the social tab. There you will see the thumbnail image upload button for Facebook. Just add thumbnail images up there and this will solve the problem. But if you continue to appear thumbnail that is not appropriate, you need to reset the cache up.

Using the Facebook debug tool

Facebook debug tool becomes the easiest way to troubleshoot issues with a Facebook open graph on your WordPress site. Simply copy the URL in the WordPress post and paste it into the debugger tool.

What happens is Facebook uses their best guess method to select thumbnail images. When there is greater amber in the article, then Facebook will use the image. For reasons that can not be explained, pressing the debug button again in the same URL makes this error resolved.

Hopefully, the guides that we provide help overcome the error in WordPress that you experience.

About Nazrul Islam

From NE India, The Founder & Admin Of Infomint.net I Likes To Write On Any Topic Related To Blogging, Such, As Tech, Wordpress, Make Money Online, Android, Online Tutorials, And, How to, Computer, Lives in Barpeta Road Assam, India.

Check Also

Update WordPress 4.8 Add Some Great New Features

Update WordPress 4.8 Add Some Great New Features

WordPress Update to the latest version; WordPress 4.8 and has added some great new features. …

Leave a Reply

Your email address will not be published. Required fields are marked *