Noodleman

seems valid. One thing that can cause oddities is the session data not being stored correctly. check your web server error log and see if you have warnings about sessions in there. it may offer some clues.

snap aww, smilies are still broken

malicious. follow this guide:

weird. seems to have worked OK for me. it's a bit slow, you've got a bad reference to a CSS file, and also an image file. I'm testing in Chrome. FireFox also working correctly. Check your cookie domain is set correctly in store settings, review the error log and check if you have anything being reported.

unsure without seeing the error first hand. can you share a link?

probably a javascript issue. open your dev console (F12) and check for messages/errors when reproducing the issue.

there may be some other considerations. Why pay for SSL? you can (in most cases) use Lets Encrypt at no cost, however some hosting providers don't allow you to use this. If you are using any tracking codes / conversion codes they may need to be updated to reflect the domain change (google analytics etc) If you use any live chat software, chances are the domain needs to be updated in config Some commercial modules are domain locked by license, you may need to have these migrated in store settings, under SSL tab change the domain to reflect the new domain As Brian said, clear cache after the move, but also check your store permissions are correct after the migration as they typically get reset review your mail configuration, it may need to be changed (although, in your case probably not) Review MySQL configuration (although, in your case I doubt it will change) re-setup any cron jobs (If you have any)

Sounds expected. the upgrade from v4 will rename images to make them more URL friendly, so spaces are replaced with underscores etc. If you have any direct linked images in descriptions they will need to be revised. You may find that after the upgrade, going to the "File Manager" in the admin area shows a 500 error. if it does, keep refreshing until it goes away. it will take a while to build the image cache, and the error means it timed our doing a "batch" of images. should be a one time thing after upgrade unless you clear the image cache manually. CubeCart_image_index should be populated, if it is not, within file managed use the tab to re-scan the files after upgrade. Images should be moved to the /images/source/ directory by the upgrade, you may also still have an "uploads" directory.

status off will remove the item from the store front available for purchase off and status on, will keep the item visible on the store front, but not allow it to be purchased.

Before you make ANY change using a bulk utility, take a database backup. this is in case it goes wrong and you need to rollback the changes. I've seen it happen countless times.. please backup! You may not need the module I offer, it's there for a very specific purpose. I've not checked into this feature for you as I am pushed for time at the moment, just wanted to share a warning about the backup to potentially save you a headache later.

Do you have English UK installed? if not, try installing that. there is a dependency on it, even if your using other languages. if not, cross reference your store default language in store settings, and validate that actually exists. another possible glitch from an earlier version.

did you generate one yet? Store Admin -> Maintenance it will then be here: https://testvalleymodels.co.uk/sitemap.xml.gz

Perhaps this may be a problem that can be addressed with product filters? you can setup filters for colours/brands/shades etc, whatever you require and let customers filter to those items of interest, then have each single paint tin/product you keep on shelf as a product in the store, easier for inventory control. Not a cheap solution, but its a really powerful, mature filter system https://www.cubecart.com/extensions/plugins/product-filters-filter-categories-and-build-menus-dynamically-using-product-metadata

There isn't a limit, however consider the usability from a customer perspective, at some point it becomes painful to select the colours you want. if it were I, I would consider 1 item per colour, with the shades as options.

copy/paste into new directory (or, download via FTP, and upload to new location) set permissions update global file with new database details backup/restore database into new DB set new store URL in store settings done..