Jump to content
thirty bees forum
  • 0

Migration from 1.6 failed


nickon

Question

Hi all,

At last I am migrading a site of a client of mine to thirtybees. But when I run the migration module I ge Archives will come from https://api.thirtybees.com/migration/packs/thirtybees-v1.0.1.zip and https://api.thirtybees.com/migration/packs/thirtybees-extra-v1.0.1.zip md5 hashes for core and extra should be resp. 384da5ef55a0d11a74ac335a177b06b6 and ce3a43d9e7cafb46e62d4bba3583a039 Directory tests complete. Downloading from https://api.thirtybees.com/migration/packs/thirtybees-v1.0.1.zip and https://api.thirtybees.com/migration/packs/thirtybees-extra-v1.0.1.zip false Download directory has been cleared Download complete but the md5 sum of the core package does not match (a76e0f1233a1c2b98640d1d46fd5963e).

First question is why is it trying to download 1.0.1 and not 1.0.2 ? Second why is it failing. This is a lammp installation on a linux machine. I tried manually copieing the file to the download dir but it ignores it and redownloads it.

Any Ideas ? Kind Regards nick

Link to comment
Share on other sites

21 answers to this question

Recommended Posts

  • 0

OK. that went bad LOL. During upgrading I got some error messages (can post them if needed) But after that I get an error 500 both in the font and backoffice. Enableling debug shows this error: Fatal error: Cannot access protected property Shop::$idshop /httpdocs/testing/Adapter/AdapterEntityMapper.php on line 103

Link to comment
Share on other sites

  • 0

File marketing/2.9.0.zip (size: 36944881) has been skipped during backup. File marketing/vendor/lightsaml/lightsaml/resources/sample/EntitiesDescriptor/ukfederation-metadata.xml (size: 21805988) has been skipped during backup. File themes/shop-new.zip (size: 23379503) has been skipped during backup. SQL 2.0.0.1 1115 in CREATE TABLE ps_module_carrier ( id_module INT(10) UNSIGNED NOT NULL, id_shop INT(11) UNSIGNED NOT NULL DEFAULT '1', id_reference INT(11) NOT NULL ) ENGINE = InnoDB DEFAULT CHARSET = utf8mb4 COLLATE utf8mb4unicodeci: Unknown character set: 'utf8mb4' SQL 2.0.0.1 1115 in CREATE TABLE ps_redis_servers ( id_redis_server INT(11) UNSIGNED NOT NULL AUTOINCREMENT, ip VARCHAR(46) NOT NULL, port INT(11) UNSIGNED NOT NULL, auth TEXT, db INT(11) UNSIGNED NOT NULL, PRIMARY KEY (id_redis_server) ) ENGINE = InnoDB DEFAULT CHARSET = utf8mb4 COLLATE utf8mb4unicodeci: Unknown character set: 'utf8mb4' SQL 2.0.0.1 1115 in CREATE TABLE ps_currency_module ( id_currency INT(11) UNSIGNED NOT NULL, id_module INT(11) UNSIGNED ) ENGINE = InnoDB DEFAULT CHARSET = utf8mb4 COLLATE utf8mb4unicodeci: Unknown character set: 'utf8mb4' SQL 2.0.0.1 1115 in CREATE TABLE ps_page_cache ( id_page_cache INT(11) UNSIGNED AUTOINCREMENT, cache_hash VARCHAR(32) NOT NULL, id_currency INT(11) UNSIGNED, id_language INT(11) UNSIGNED, id_country INT(11) UNSIGNED, id_shop INT(11) UNSIGNED, cache TEXT NOT NULL, cache_size INT(10) UNSIGNED, entity_type VARCHAR(30) NOT NULL, id_entity INT(11) UNSIGNED, UNIQUE KEY cache_combo (cache_hash, id_currency, id_language, id_country, id_shop), PRIMARY KEY (id_page_cache), INDEX (cache_hash), INDEX (id_currency), INDEX (id_language), INDEX (id_country), INDEX (id_shop), INDEX (id_entity), INDEX (entity_type) ) ENGINE = InnoDB DEFAULT CHARSET=utf8mb4 COLLATE utf8mb4unicodeci: Unknown character set: 'utf8mb4' Warning detected during upgrade.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...