PHP 7 offers one of the biggest jumps in performance we’ve seen so far from this particular software. If your web server is still running a previous version, you may be holding your site back from working as well as it could. The only problem is that learning how to upgrade WordPress to PHP 7 can be a little tricky.Despite that, upgrading your site to the latest version of PHP is a smart move, and one that will benefit you in a number of ways.
The wpoptions will be different if you have changed the default WordPress database prefix. This seemed to fix the issue for him and few others that commented on his post as well. Sachinum suggested that he was able to connect the database with testconnection.php, so he changed the wp-config.php user to the root user. WordPress started to work. Yes that is why I am confused as I have checked over and over and all of the info is correct. I'll even set up a new database and create a new user and still get the same errors. In the wp-config.php file I've even put djevscm before the name of the database and MySQL username and still get the same errors.
Plus, the process isn’t actually that difficult as long as you go about it safely, to ensure that the update won’t break any of your site’s elements. That way, you won’t have to rush around fixing things afterward.In this article, we’re going to talk about what is and why you should make the switch. Then we’ll teach you how to upgrade WordPress to PHP 7 safely, in just four steps. Let’s get to it! How PHP 7 can benefit your siteIn a lot of cases, people put off upgrading to the latest versions of the software they use because they don’t know a new version is available, or they don’t realize how much of an improvement it is. That’s why so many users still aren’t running PHP 7, despite its tangible benefits.PHP 7 offers some massive upgrades for end users.
For example:. You should see about a 50% performance increase after making the switch. PHP 7 offers that’s well worth the upgrade. It supports 64-bit Windows systems. Most people use Linux for their servers, but if you’re a Windows user, you’ll appreciate the new support for.Plus, PHP 7 is now the official.If your primary concern is that installing PHP 7 will break your site in some way, then we’ve got your back. There’s always some risk involved in an upgrade like this, but there are also ways to carry out the process safely.
How to safely upgrade WordPress to PHP 7 (in four steps)Before we go any further, let’s talk about how the upgrading process works. If you have full privileges on your server, you can upgrade WordPress to PHP 7. On the other hand, if you’re on shared or, you’ll probably have to ask your provider’s support team to upgrade your site manually.In either case, the actual process is straightforward. The problem is that if you don’t take any precautionary measures, you run the risk of breaking elements of your site that don’t play nicely with PHP 7.
That’s why we’re partial to a different approach that enables you to eliminate most of the risk involved. Step #1: Back up your websiteregularly is something you probably already do. However, you’ll want to have a backup of your site that’s as recent as possible.You’ll be using this backup to create a copy of your site, where you can test how everything works with PHP 7 without causing any damage to your live site. If a plugin ceases to work, for example, you’ll know you have to look for an alternative before you upgrade your real WordPress site to PHP 7.For this step, we recommend using the plugin, since it’s one of the most straightforward backup solutions available. It now, and then go to the Settings → UpdraftPlus Backups tab:Once you’re in, click on the Backup Now button, and choose to include both your database and files in your backup:Give the plugin a couple of minutes to back up your site, or possibly more (depending on how large your site is). When it’s done, you’ll find your new backup files under the Existing Backups tab:Now, you’ll want to click on the following four buttons in turn: Database, Plugins, Themes, and Uploads.
This will give you the option to download copies of each file to your computer:When you’re done, you should have four files containing your entire website. Now you’re ready for the next step. Step #2: Create a local staging copy of your siteThere are plenty of ways to create a staging copy of your website, but we’re partial to because it’s easy to set up.
Plus, you don’t need to be a customer to get the app. Just go to the website, fill out a short form, and download the tool.After installing Local by Flywheel, you’ll be able to add new local websites to your roster by clicking on the plus sign in the lower left-hand corner of the application:Do so now, and you’ll be prompted to choose a name and an environment for your staging site. When you get to the environment part, select the Custom option:This will give you the choice of using PHP 7 for your staging website instead of 5, which is the default setting. Make sure you choose the right version, and then create an admin name and password for your site. After that, sit back while the app sets everything up.Once your new staging website is ready, look for it under the list of local sites on Local by Flywheel’s main screen.
Then click on the Admin button that will show up next to its description, to access your dashboard:(Note; if you need some hands-on guidance on how to use Local by Flywheel, we’ve got a whole tutorial on that.)The first thing you’ll want to do here is install the UpdraftPlus plugin once more. When it’s running on your staging site, return to the Settings → UpdraftPlus Backups tab and look for the option that reads Upload backup files:Now, drop the four backup files you downloaded earlier into the designated area. When the upload is complete, you’ll see your backup appear on the list. Click the Restore button next to it, and you’re in business. Step #3: Test your staging siteWhat you’ve just done is created a staging website that’s a perfect copy of your original site in every way, except for the fact that this one is running PHP 7.Now comes the part where you look for errors on your staging site. What you’re looking for and what issues you might find will vary widely depending on your unique setup.
However, here’s how we recommend you go about conducting your test:. Make your way through every page on your website, looking for any elements that have suddenly stopped working. Check to see if your plugins are behaving as they should, one by one. Test any features that your active theme includes, to ensure that they’re still functioning.This might take a little time, depending on how large your website is. If you run into any broken plugins or themes, it’s worth looking for replacements, since PHP 7’s benefits are well worth making a few changes. Step #4: Upgrade your live site to PHP 7If you didn’t find any errors on your staging website (or after you’ve identified the source of any problems that do appear), all that’s left is to upgrade your live site to PHP 7. As we mentioned earlier, this process is rather simple.
There are two ways to approach it, depending on your host:. If you use a Virtual Private Server (VPS) or any other hosting option that gives you full control, you can upgrade WordPress to PHP 7. If your host doesn’t give you this level of access, you can ask them to upgrade you to the latest version through their support system.When you’re done, be sure to test your site’s performance again (just to be safe). Then you can start enjoying the improvements PHP 7 provides! ConclusionPHP 7 has been around for a while now, yet adoption rates are nowhere near where they should be. This new version offers a marked increase in performance, and most reputable web hosts will give you the option to upgrade WordPress to PHP 7.
If yours doesn’t, then it’s probably time to.
If you are a WordPress user who likes to get your hands dirty with the codes, or one who just loves installing plug-ins and changing themes, you’ll understand that encountering an error is an inevitable occurrence. WordPress users (like us) know how frustrating it is to stumble into an unexpected error and not be able to find a solution for it. Most WordPress problems are solvable; If you hit an error, don’t fret because chances are, some other WordPress user had the same problem and had already gotten it solved.In today’s post, we take a look at some of the most common WordPress errors users have encountered, and share with you the solutions to fix those problems or make them go away. We hope this will comes in handy for you – happy WordPressing!You might also like:.1. Lost Admin Password & Email Retrieval Is Not FunctioningThe problem:You lost your WordPress admin password, and have tried to enter your username or email address in the 'Lost your password?' Page but failed to receive any link to create a new password via email.Here are 2 simple solutions to reset your WordPress admin password. Solution 1: phpMyAdmin.
Login cPanel, click on phpMyAdmin under Databases. Select your WordPress database. For example: Usernamewrdp1.
Go to wpusers, click on Browse. Look for your Username and click Edit. Reset your password by inserting a new value into userpass. Remember, it is case-sensitive. Once you completed this, click the dropdown menu under Function, and choose MD5 from the menu. At the bottom of the page, click the Go button.Solution 2: Via FTP.
Login your FTP account. Go to './wp-content/themes/(your active theme)/', download the functions.php file. Open functions.php and add the code below right after the first.
Make sure the last characters are?, placed at the last line with no space in between.This error could happen on other files too. Read the error message carefully as it states the specific file name where the error occurred. WordPress blog and admin Is showing blank pageThe problem:This error normally happens right after a new installation or WordPress upgrade. The entire blog is showing a blank page; so is the WordPress admin login page. There’s no way to access the dashboard.Solution 1: Rename current installed theme folder via FTPRenaming the currently installed theme folder via FTP can force WordPress to choose the default theme to be put into service and you’re able to access WordPress wp-admin after that. Navigate to the wp-contents/themes directory via FTP. Rename current installed theme folder.
For example: 'twentytwenty' to 'twentytwenty-temp'. Login to your WordPress wp-admin. Check if your theme is compatible with your version of WordPress. Check if your theme contains coding which can’t be executed.Solution 2: Reset plugin folder via FTP.
Navigate to the wp-contents directory via FTP. Rename plugins folder to 'plugins-temp'. Create a new folder called 'plugins' at wp-contents. Try to login to your WordPress wp-admin. Move your plugin from 'plugins-temp' to 'plugin' and activate them one by one. Check if any plugin is not compatible with your version of WordPress.5.
Fatal error: Allowed memory size of 33554432 bytes exhaustedThe problem:Receive ' Fatal error: Allowed memory size of 33554432 bytes exhausted' when try to upload an image with medium file size. To solve this error, try to increase the memory allocated to PHP. You can set the limit to 32MB, 64MB, 128MB or 256MB. It depends on your host.
Solution 1: Edit PHP.iniIf you’re still allowed to edit your PHP.inifile, update your memorylimit in PHP.ini by modifying the below linememorylimit = 64M; Maximum amount of memory a script may consume (64MB)If the line is showing 64M in default, try 128M. Solution 2: Edit.htaccess fileAdd the script below to your.htaccess file.phpvalue memorylimit 64M Solution 3: Edit wp-config.php fileAdd the script below to your wp-config.php fileIncreasing memory allocated to PHPdefine('WPMEMORYLIMIT', '64M'); Solution 4: Create a PHP.ini file to wp-admin folder. Open Notepad. Insert the following code into Notepad. Memorylimit = 64M;.
Save as 'PHP.ini'. Upload this file to 'wp-admin' directory.6. You are not authorized to view this page (403 error)The problem:You receive an error message ' You are not authorized to view this page. (403 error)' after inserting the username and password in the WordPress admin login page.Solution: Enable Index.phpIf your blog is hosted on a Windows server, this could be an error with Directory Indexes.
Login to the Control Panel. Click on Web Options. Go to Directory Indexes section. Add index.php to the Directory Indexes.7. Fatal error undefined function isnetworkadminThe problem:You receive ' Fatal error undefined function isnetworkadmin' when you login to WordPress admin after updating WordPress.
Solution: Manual UpdateThis error is caused by a fail WordPress version upgrade. Try a manual update. Download the zip file and unzip it. Back up your WordPress. Rename wp-includes and wp-admin directories to wp-includes.bak and wp-admin.bak. Upload the wp-includesand wp-admin directories from unzipped folder to your web host via FTP. Upload files from new wp-content to your existing wp-content folder.
Replace and overwrite existing files. Upload the new version of the rest of files from the root directory to your existing WordPress root directory. Remove.maintenance at your WordPress directory via FTP. Login to WordPress admin and you will be given a link to URL like 'Follow the link and instructions. Clear your cache to see the changes if you have caching enabled.For more details about WordPress manual update, read. WordPress Admin Login 404 IssueThe problem:You’re not able to login to WordPress admin.
You receive a 404 error page instead. Solution 1: Update the URL in databaseIf you’re able to access phpMyAdmin, try to update the URL in the database. Login cPanel, click on phpMyAdmin under Databases. Select your WordPress database. For example: Usernamewrdp1. Go to wpoptions, click on Browse.
Search for siteurl under the field optionname. Click on Edit Field. Change the URL in the input box of optionvalue. At the bottom of page, click the Go button.Solution 2: Update Folder Attributes. Go to '/wp-admin' directory via FTP. Right click on wp-admin directory and click on File Attributes.
Update the value to 755 and check Recurse into subdirectories if there’s an option. Click OK. Repeat step 1 to step 4 for /wp-content and wp-includes. Open your web browser and try to login to WordPress admin. Press Ctrl + F5 to clear cache.9.
'Briefly unavailable for scheduled maintenance' message remainins after an automatic upgradeThe problem:Your WordPress site is showing 'Briefly unavailable for scheduled maintenance' after an automatic upgrade has completed.Solution: Remove.maintenance fileA file named.maintenance is placed by WordPress during an automatic upgrade to notify visitors that the site in under a short maintenance. If an upgrade fails or is corrupted, the file will remain in the WordPress folder and won’t get deleted.To remove.maintenance file,. Access your blog root directory via FTP. Locate the file.maintenance. Remove the.maintenance file from the blog root directory.Once you solve this problem, you may want to run the WordPress automatic upgrade again.
Can’t delete a pluginThe problem:You’re not able to delete a plugin in WordPress admin. It still appears even after you have deleted the directory via FTP. Solution: Delete plugin via Secure Shell (SSH)Your plugin might had uploaded some hidden/nested files inside the plugin directory which didn’t appear in FTP.If you have SSH access to your blog,. Login your site via SSH. Use SSH commands to nagivate './wp-content/plugins/'. Use ls -al to see the full list of folders. Delete the particular plugin folder with rm (Folder Name).Have comments you want to share abou the errors and solutions above?
Share them below.