Title: Plugin changes PHP version after restoring
Last modified: August 22, 2019
---
# Plugin changes PHP version after restoring
* Resolved [blackeye0013](https://wordpress.org/support/users/blackeye0013/)
* (@blackeye0013)
* [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-changes-php-version-after-restoring/)
* Hi,
* I’ve faced a really strange behaviour: I wanted to migrate a site from localhost
to online dev site. After clicking restore button process started, but stopped
just before finishing the task. The last line was stating loading (or opening)
file XXXX__backup_core.zip (or something like this). After a while, I openned
a frontend of the web in a new window and got this message “Your server is running
PHP version 5.3.29 but WordPress 5.2.2 requires at least 5.6.20.”
* The web is hosted on HostGator and in cPanel I can select different PHP version
for different (sub)domains. For legacy reasons the default PHP version is set
to PHP 5.4. Of course the dev subdomain I have worked with was set to 7.1 (othervice
it would’t be even possible to run the last version of WP there).
* But during the restore process your plugin set the version back to default! I
had to go to cPanel and change the PHP to 7.1 again (yes, it was really changed
there). Immediately after changing the PHP version the process started again
and I was told the restoring was succesfuly finished (I had both windows opened
side by side).
* I found this behaviour very strange, so I decided to repeat it 2 more times.
2nd attempt was on the same subdomain and went exactly the same. 3rd attempt
I did on another subdomain (of the same site) and again – exactly the same.
* This is my first try with your plugin. Unfortunately not very successful. On
the same domain I have used All In One WP Migration too and it worked without
any problems.
* Any ideas?
* Thanks
Viewing 6 replies - 1 through 6 (of 6 total)
* Plugin Support [nicholas2019](https://wordpress.org/support/users/nicholas2019/)
* (@nicholas2019)
* [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-changes-php-version-after-restoring/#post-11859171)
* Thanks for your feedback. Generally, WPvivid backup plugin creates backups for
wp core files. We guess the configuration for changing PHP version in wp core
may be restored in restore process. So php version is changed becauses of this.
We will try to fix it in future release.
* Thread Starter [blackeye0013](https://wordpress.org/support/users/blackeye0013/)
* (@blackeye0013)
* [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-changes-php-version-after-restoring/#post-11859179)
* Thanks for your reply. I’m 100% positive, the original version wasn’t on the
lower PHP either. I can send you the backup file if you’d like to investigate
it.
* Plugin Support [nicholas2019](https://wordpress.org/support/users/nicholas2019/)
* (@nicholas2019)
* [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-changes-php-version-after-restoring/#post-11859187)
* We would appreciate it if you could send the backup file to us. Please send it
to our support email (support@wpvivid.com). Thanks in advance.
* Plugin Support [nicholas2019](https://wordpress.org/support/users/nicholas2019/)
* (@nicholas2019)
* [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-changes-php-version-after-restoring/#post-11859243)
* Alternatively, you could provide us with a download link of your backup file
by email. After that, we try to reproduce the issue you encountered and fix it.
Thanks in advance.
- This reply was modified 6 years, 7 months ago by [nicholas2019](https://wordpress.org/support/users/nicholas2019/).
* Thread Starter [blackeye0013](https://wordpress.org/support/users/blackeye0013/)
* (@blackeye0013)
* [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-changes-php-version-after-restoring/#post-11892147)
* Sorry for the delay, I was quite busy last week.
* In the meantime I’ve discovered that the problem could be code in `.htaccess`,
which is responsible for setting up the non-default PHP version.
* Here is the code in `.htaccess` of initial ‘blank’ install (to where I’ve tried
to move the devel version):
* ```
# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress
# Use PHP71 as default
AddHandler application/x-httpd-php71 .php
suPHP_ConfigPath /opt/php71/lib
```
* I haven’t checked it up yet, but I would bet, that during the migration process
targer `.htaccess` is rewritten by the source version, where the last part is
missing (it’s from local environment). In the moment, when the .htaccess is rewritten,
PHP is back to default 5.2 and WP dies.
* Do you find this scenario possible?
* I havent sent you the backup link yet, but I suppose this info would explain
this issue better.
* Plugin Support [nicholas2019](https://wordpress.org/support/users/nicholas2019/)
* (@nicholas2019)
* [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-changes-php-version-after-restoring/#post-11892484)
* Thanks for your reply. This makes sense. We will try to be compatible with this
situation in next version.
Viewing 6 replies - 1 through 6 (of 6 total)
The topic ‘Plugin changes PHP version after restoring’ is closed to new replies.
* 
* [WPvivid — Backup, Migration & Staging](https://wordpress.org/plugins/wpvivid-backuprestore/)
* [Frequently Asked Questions](https://wordpress.org/plugins/wpvivid-backuprestore/#faq)
* [Support Threads](https://wordpress.org/support/plugin/wpvivid-backuprestore/)
* [Active Topics](https://wordpress.org/support/plugin/wpvivid-backuprestore/active/)
* [Unresolved Topics](https://wordpress.org/support/plugin/wpvivid-backuprestore/unresolved/)
* [Reviews](https://wordpress.org/support/plugin/wpvivid-backuprestore/reviews/)
* 6 replies
* 2 participants
* Last reply from: [nicholas2019](https://wordpress.org/support/users/nicholas2019/)
* Last activity: [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-changes-php-version-after-restoring/#post-11892484)
* Status: resolved