Test Environment

Hi :)

How do we set up a test environment..?

Search the form. N it’s been answered many times. Keywords would be development site.

Hi :)

How do we set up a test environment..?

There is no need to buy extra license. Just make a copy of your store and close it for public

Okay thanks so much for your replies! We will continue looking into this :)

What is test environment? I don't heard it yet.Here you are not mention about its use and features.I would like to know more about it in detail.Thanks for sharing this.

It is a copy of your site and database for testing purposes.

If you are not doing development it is not necessary. If you are doing development then have your developer do it for you.

All I want is to upgrade my store to the newest version. I'd feel more safe if I could make a test copy and try out the upgrade on that as you recommend, but based on threads in this forum, making a test copy seems like an impossible task.
I plan to do the following in order to upgrade:
1. Close the existing store temporarily using the store admin settings general - Close Shop Frontpage option to temporarily avoid any customers placing an order.
2. Download a backup of both files and database using the cPanel's Backup utility.
3. Use the Install button inside the store admin Upgrade center. (4.2.4 -> 4.3.1)
4. Visually verify that everything went ok. ( I might have to reopen the store in order to do this )
5. If anything is wrong - use cPanel's Backup utility to restore both files and database from the backups.
6. Reopen the store using the store admin settings general - Close Shop Frontpage option
7. Repeat 1-6 this if there are any further upgrades.
Can I trust the backup to work, or is there risk of some issues when restoring from the backups?
Is a visual verification enough, or is there risk of hidden errors?

Almost all of that is done automatically for you by the upgrade process. I.e. close store, archive files/DB tables to be modified, etc. However, having a full backup of your store (files and DB) is always a good idea.

Error message "Kan ikke klargjøre restore.php filen. Filen "var/upgrade/restore.php" er lokalt endret/omdøpt/fjernet. Gjenopprett den lokale restore.php filen før oppgraderingen." = Could not "make ready" restore.php file - it is either changed / renamed or removed. Restore it"

Not changed by me. Must have been changed by the upgrade 4.3.1 - 4.3.2.

[~/public_html]# ls var/upgrade/ -al
total 12576
drwxr-xr-x 4 gasungsr gasungsr 4096 2016-11-27 13:20 ./
drwxr-xr-x 12 gasungsr gasungsr 4096 2016-11-27 13:18 ../
-rw-r--r-- 1 gasungsr gasungsr 6591 2016-11-27 13:28 core_log.txt
-rw-rw-rw- 1 gasungsr gasungsr 68 2016-11-27 13:20 .htaccess
-rw-rw-rw- 1 gasungsr gasungsr 192563 2016-11-27 13:09 installed_upgrades.php
drwxrwxrwx 3 gasungsr gasungsr 4096 2016-11-27 13:20 packages/
-rwxr-xr-x 1 gasungsr gasungsr 375290 2016-11-26 13:50 packages.xml*
-rw-rw-rw- 1 gasungsr gasungsr 29117 2016-11-27 13:28 restore.php
-rw-rw-rw- 1 gasungsr gasungsr 9787468 2016-11-27 13:04 uc.tgz
drwxr-xr-x 5 gasungsr gasungsr 4096 2016-11-27 13:09 upgrade_4.2.4_ultimate-4.3.1_ultimate.tgz/
-rw-r--r-- 1 gasungsr gasungsr 2451140 2016-11-27 13:07 upgrade.log

Having changed config.local.php with DEFAULT_FILE_PERMISSIONS 644 :

2016-11-27 13:47:07: Start installation of the "core" upgrade package
2016-11-27 13:47:07: ================================================
2016-11-27 13:47:07: Get all available validators
2016-11-27 13:47:07: Execute "Backups directory permissions" validator
2016-11-27 13:47:07: Execute "collisions" validator
2016-11-27 13:47:07: Execute "permissions" validator
2016-11-27 13:47:07: Execute "restore" validator
2016-11-27 13:47:07: Backup files and Database
2016-11-27 13:51:10:
2016-11-27 13:51:10: Start installation of the "core" upgrade package
2016-11-27 13:51:10: ================================================
2016-11-27 13:51:10: Get all available validators
2016-11-27 13:51:10: Execute "Backups directory permissions" validator
2016-11-27 13:51:10: Execute "collisions" validator
2016-11-27 13:51:10: Execute "permissions" validator
2016-11-27 13:51:10: Execute "restore" validator
2016-11-27 13:51:10: Backup files and Database
(stops and returns to install 4.3.2 -> 4.3.3 screen)
After changing DEFAULT_DIR_PERMISSIONS from 777 to 755:
2016-11-27 14:01:01:
2016-11-27 14:01:01: Start installation of the "core" upgrade package
2016-11-27 14:01:01: ================================================
2016-11-27 14:01:01: Get all available validators
2016-11-27 14:01:01: Execute "Backups directory permissions" validator
2016-11-27 14:01:01: Execute "collisions" validator
2016-11-27 14:01:01: Execute "permissions" validator
2016-11-27 14:01:01: Execute "restore" validator
2016-11-27 14:01:01: Backup files and Database
(hangs indefinitely on "compressing backup file")

Tried "experimental solution" from eComLabs, adding 'db_tables' => array(), to app\Tygh\UpgradeCenter\App.php.

Did not work - still returns with no error message to upgrade center with "upgrade from 4.3.2 to 4.3.3"

In that same file (instead of setting db_tables to array()), simply change the line that looks like:

'compress' => 'zip',

to

'compress' => '',

This will prevent compression of backps.

This worked for me. So I have successfully upgraded the store to v 4.4.2. Thanks for all the help.

I am still very interested in any guide to make a test copy on my local computer, exactly like the running store, with all the information from the existing store, so I can actually follow the recommendations in all the warnings.

I did set up a test environment with virtualbox and Ubuntu as instructed in the documentation, however the store did not work when I copied the public_html folder and database contents from the actual store.

This worked for me. So I have successfully upgraded the store to v 4.4.2. Thanks for all the help.

I am still very interested in any guide to make a test copy on my local computer, exactly like the running store, with all the information from the existing store, so I can actually follow the recommendations in all the warnings.

I did set up a test environment with virtualbox and Ubuntu as instructed in the documentation, however the store did not work when I copied the public_html folder and database contents from the actual store.

Did you configure config.local.php correctly? Are there any errors?

I did set up a test environment with virtualbox and Ubuntu as instructed in the documentation, however the store did not work when I copied the public_html folder and database contents from the actual store.

What do you mean by "store did not work"? Do you receive any error, blank screen, incorrect redirects or anything else?

All I want is to upgrade my store to the newest version. I'd feel more safe if I could make a test copy and try out the upgrade on that as you recommend, but based on threads in this forum, making a test copy seems like an impossible task.

I plan to do the following in order to upgrade:
1. Close the existing store temporarily using the store admin settings general - Close Shop Frontpage option to temporarily avoid any customers placing an order.
2. Download a backup of both files and database using the cPanel's Backup utility.
3. Use the Install button inside the store admin Upgrade center. (4.2.4 -> 4.3.1)
4. Visually verify that everything went ok. ( I might have to reopen the store in order to do this )
5. If anything is wrong - use cPanel's Backup utility to restore both files and database from the backups.
6. Reopen the store using the store admin settings general - Close Shop Frontpage option
7. Repeat 1-6 this if there are any further upgrades.

Can I trust the backup to work, or is there risk of some issues when restoring from the backups?
Is a visual verification enough, or is there risk of hidden errors?


Its not an impossible task its just a technical one. If you don't understand how to do it without posting on here then you should hire someone.

Concerning the backups have you ever restored from a backup before? Do you know what to do if an issue arises? Do you have an offsite backup? Do you know how to extract the relevant files from backup that cpanel makes?

If no then you should start exploring those things.

There are lots of problems in upgrade steps 4.2 or 4.3 to 4.4 I would go with store import. Much safer minimum down time…

There are plenty of threads in this forum on both topics. There are workarounds to the 4.2.x through 4.3.6 upgrade issues and how to address them. There are also many threads on how to create a clone of your store so you can test your procedure and results on a cloned environment before you upgrade your main store.

All you have to do is search. I would recommend using Google to search rather than the forum search unless you ware wanting to filter by the author of the post.