Solutions to common WordPress blog errors

Solutions to common WordPress blog errors

WordPress is a mainstream Blog building platform. WordPress is the world's most advanced weblog program. Currently, most of the programs developed are based on it. It can better grasp the search engine. After you use WordPress and master several plug-ins, you don't have to worry too much about optimization. It will think more.

If you are a WordPress user who prefers to compile a piece of code, or if you are a user who prefers to install plug-ins and change themes, you will understand that there is no way to avoid errors. You will also understand how desperate you are when you get involved in an unpredictable error and fail to find a solution. In fact, most WordPress errors can be solved. So when you encounter a mistake, don't worry, because it is very likely that someone else has encountered this problem and there is a solution.

In today's article, let's take a look at the most common WordPress errors and share with you the solution, so that you don't have to worry about it after reading the post and can write your blog more happily.

1. the email retrieval function does not work when the user password is lost.

Problem description:

You lost your WordPress administrator password and tried to click "forgot password" to enter your username and Email address. However, no password reset email is received.

Here are two simple methods to reset your WordPress administrator password:

[Page_break]

　　Method 1: phpMyAdmin

1. If you are a cPanel user, log on to cPanel and click phpMyAdmin under Database

2. Select Your WordPress database. For example, Username_wrdp1

3. Find wp_users and Click Browse.

4. Find your username and click Edit.

5. Reset your password by writing a new value in user_pass. Remember, it is case sensitive.

6. After completing the preceding step, click the Function drop-down menu and select MD5 from the options.

7. Click Go at the bottom of the page.

[Page_breakMethod 2: use FTP

1. log on to your FTP account.

2. Find the ../wp-content/themes/(your theme file)/directory, and then download the functions. php file.

3. Open functions. php and

Wp_set_password ('yourpassword', 1 );

Replace YourNewPassword with your desired password. In this Code, 1 represents the user ID of the wp_users table.

4. Upload the modified functions. php file to FTP again.

5. When you can log on to WordPress, delete the line of code.

　　2. WordPress Control Panel (Dashboard) cannot be properly displayed

Problem description:

The CSS in the WordPress control panel is not displayed, and the links on the page are messy.

Solution 1: Port and Firewall

Check whether your network connection is through the port and firewall. Some ports and firewalls are filtered out by CSS, so CSS is abnormal. Try to clear the cookies and caches on the port and firewall, and then Ctrl + F5 re-load the page.

Solution 2: Upgrade Your WordPress plug-in

If you have some plug-ins that are used to replace the default Control Panel, such as Admin Drop Down Menu and Lighter Menus, upgrade these plug-ins. If they still do not work, disable them.

　　3. Warning: Cannot modify header information-headers already sent

Problem description:

After you upgrade WordPress to a new version or install it completely, you may encounter the following error in your browser: Warning: cannot modify header information-headers already sent by (output started at/path/blog/wp-config.php: 34)

Solution: Remove unnecessary spaces, blank lines, and other useless information in the wp-config.php.

1. Download wp-config.php files through FTP

2. Open wp-cinfig.php

3. Remove

4. Make sure that the first field is

5. Remove?> All spaces.

6. Make sure the last character is?>, Put it in the last line to ensure that there is no space in the middle.

This error can occur in other files. Read the error message carefully, and record the location of the error file.

[Page_break4. Blank WordPress blog page and Control Panel

Problem description:

This error usually occurs when a new theme is installed or the version is upgraded. Opening a blog is a blank page. In the control panel, there will also be such a situation, so there is no way to enter the control panel.

Solution 1: Rename the currently installed topic through FTP.

If you rename the currently installed theme folder, it will force WordPress to automatically select the default theme and load it normally.

1. Find the wp-contents/themes folder through FTP.

2. reactivate the currently installed theme folder. For example, name twentytwenty twenty-temp.

3. log on to your WordPress background.

4. Check whether your topic is compatible with the WordPress currently running.

5. Check whether your topic contains code that cannot be executed.

Solution 2: reset the plug-in folder through FTP

1. Find the wp-contents folder through FTP.

2. Rename the plugins folder as plugins-temp

3. Create a new folder named plugins under the same directory.

4. log on to the WordPress control panel again.

5. Move your plug-in from plugins-temp to plugin, and then reactivate them one by one.

6. check whether any plug-in is incompatible with the current WordPress.

[Page_brea5. Fatal error: Allowed memory size of 33554432 bytes exhausted

Problem description:

When uploading a photo, you encounter the Fatal error: Allowed memory size of 33554432 bytes exhausted error message. To solve this problem, we should try to increase the memory allocated to PHP. You can set the limit to 32 MB, 64 MB, 128 MB, or 256 MB, depending on whether your host provider supports it.

Solution 1: Edit php. ini

If you can edit the php. ini file, you can directly modify the value of memory_limit on it.

Memory_limit = 64 M; Maximum amount of memory a script may consume (64 MB)

If the default value is 64 MB, try 128 MB.

Solution 2:. htaccess File

Add the following line of code to the. htaccess file.

Php_value memory_limit 64 M

Solution 3: edit the wp-config.php File

Add the following code to the wp-config.php file.

Increasing memory allocated to PHP

Define ('wp _ MEMORY_LIMIT ', '64m ');

Solution 4: Create a php. ini file in the wp-admin folder.

1. Open notepad.

2. Insert the following code:

Memory_limit = 64 M;

3. Save it as php. ini.

4. Upload the file to the wp-admin directory.

　　6. You are not authorized to browse this page (error 403)

Problem description:

When You enter the user name and password on the background logon page, You receive the following error: You are not authorized to view this page. (403 error)

Solution: Enable index. php

If your blog is installed on Windows Server, this error occurs because IIS does not set the default homepage to indexx. php.

1. Open the control panel.

2. Open IIS management.

3. Find the default homepage.

4. Add index. php.

　　7. Fatal error: Fatal error undefined function is_network_admin ()

Problem description:

When you upgrade WordPress, the Fatal error undefined function is_network_admin () is Fatal when you try to log on.

Solution: manual upgrade

This error is caused by a failed WordPress upgrade. Try to upgrade manually.

1. Download and decompress the latest WordPress package.

2. Back up your current WordPress.

3. Rename the wp-nodes and wp-admin directories as wp-includes.bak and wp-admin.bak.

4. Upload the wp-uplodes and wp-admin directories to the server via FTP.

5. Upload the content in the new wp-content directory to the corresponding location on the server.

6. upload other files to the WordPress root directory.

7. Delete the. maintenance File through FTP.

8. log on to WordPress again and you will see a link like http: // your domain name/wordpress/wp-admin/upgrade. php. Follow the instructions.

9. Clear the cache and check whether it takes effect.

For more details about manual upgrade, see: Updating WordPress

[Page_break]8. WordPress logon page 404

Problem description:

You cannot log on to the WordPress background and the Error 404 is displayed.

Solution 1: update the URL on the database.

If you can access phpMyAdmin, try to update the URL in the database.

1. log on to cPanel and click phpMyAdmin in Databases.

2. Select Your WordPress database, for example, Username_wrdp1.

3. Go to wp_options and Click Browse.

4. Search siterul under the option_name field.

5. Click Edit Field.

6. Change the URL in the option_value option.

7. Click OK at the bottom.

Solution 2: Change the folder properties.

1. Enter the/wp-admin directory under FTP.

2. Right-click the wp-admin directory and click folder properties.

3. Change the attribute value to 755 and then check whether the directory has the corresponding options.

4. Click OK.

5. Perform steps 1-4 in the wp-content and wp-uplodes folders.

6. Open your browser and try to log on to WordPress. Then press Ctrl + F5 to clear the cache.

[Page_break9. The Briefly unavailable for scheduled maintenance error is displayed after the automatic upgrade is completed.

Problem description:

If the Briefly unavailable for scheduled maintenance error message is displayed after your site is upgraded.

Solution: Delete the. maintenance File.

During the upgrade, you will generate a file named. maintenance to remind visitors that the website is being maintained. If the upgrade fails, the file will be retained in the folder.

Delete. maintenance.

1. log on to the root directory of your blog through FTP.

2. Find the. maintenance File.

3. Delete the. maintenance file from the root directory.

Once you solve this problem, you can perform another automatic upgrade operation.

　　10. Unable to delete the plug-in

Problem description:

You cannot delete a plug-in from the WordPress control panel. After you delete the plug-in folder via FTP, you still cannot delete the folder on the control panel.

Solution: Use SSH to delete the plug-in.

Your plug-in may have uploaded some hidden files to directories that are invisible under FTP.

If your blog can log on via SSH:

1. log on to your blog through SSH.

2. Run the SSH command to find the Directory: wp-content/plugins/

3. Run the ls-al command to display the entire folder.

4. Run the rm directory name command to delete the plug-in.

Due to the extensiveness of WordPress, you can only list solutions to these common problems for the moment. I hope to help you ~