Upgrade from 18.10.11 to 22.7.1
Forum rules
Always add your TYPO3, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
Spam and unrelated posts will be removed immediately!
Always add your TYPO3, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
Spam and unrelated posts will be removed immediately!
Re: Upgrade from 18.10.11 to 22.7.1
Think, we've found the error. Can you please try this pre-release?
https://aimeos.org/fileadmin/download/a ... 3-pre1.zip
https://aimeos.org/fileadmin/download/a ... 3-pre1.zip
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, give us a star
If you like Aimeos, give us a star
Re: Upgrade from 18.10.11 to 22.7.1
Thank you very much!
In a fresh Typo3 environment the installation is successfully now.
But on the system of our clients I get the following error when installing.
The value in mshop_order.relatedid of every record is NULL.
In a fresh Typo3 environment the installation is successfully now.
But on the system of our clients I get the following error when installing.
The value in mshop_order.relatedid of every record is NULL.
Ubuntu 22.04.01
PHP 7.4.30
Typo3 v11.5.21 LTS
Aimeos web shop 22.10.4-pre3
PHP 7.4.30
Typo3 v11.5.21 LTS
Aimeos web shop 22.10.4-pre3
Re: Upgrade from 18.10.11 to 22.7.1
Why does the mshop_order.relatedid column use DATETIME instead of VARCHAR?
At least it seems to do so according to the error output.
At least it seems to do so according to the error output.
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, give us a star
If you like Aimeos, give us a star
Re: Upgrade from 18.10.11 to 22.7.1
Good question, I hope you can give me the answer
Maybe in the migration the SQL parameter is bind as datetime or something like that?
Maybe in the migration the SQL parameter is bind as datetime or something like that?
Ubuntu 22.04.01
PHP 7.4.30
Typo3 v11.5.21 LTS
Aimeos web shop 22.10.4-pre3
PHP 7.4.30
Typo3 v11.5.21 LTS
Aimeos web shop 22.10.4-pre3
Re: Upgrade from 18.10.11 to 22.7.1
What's the output of "SHOW CREATE TABLE mshop_order" at that database?
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, give us a star
If you like Aimeos, give us a star
Re: Upgrade from 18.10.11 to 22.7.1
This is the output of the statement on the production system (v18.10.11) our clients, on which we try the upgrade.
Ubuntu 22.04.01
PHP 7.4.30
Typo3 v11.5.21 LTS
Aimeos web shop 22.10.4-pre3
PHP 7.4.30
Typo3 v11.5.21 LTS
Aimeos web shop 22.10.4-pre3
Re: Upgrade from 18.10.11 to 22.7.1
Seems like an error due to the setup task order. Can you try this pre-release package?
https://aimeos.org/fileadmin/download/a ... 3-pre2.zip
https://aimeos.org/fileadmin/download/a ... 3-pre2.zip
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, give us a star
If you like Aimeos, give us a star
Re: Upgrade from 18.10.11 to 22.7.1
Thank you very much!
Now the migration on our clients system was successfully.
I appreciate your awesome support.
Now the migration on our clients system was successfully.
I appreciate your awesome support.
Ubuntu 22.04.01
PHP 7.4.30
Typo3 v11.5.21 LTS
Aimeos web shop 22.10.4-pre3
PHP 7.4.30
Typo3 v11.5.21 LTS
Aimeos web shop 22.10.4-pre3
Re: Upgrade from 18.10.11 to 22.7.1
With aimeos_22.10.3-pre2 I still get the error we discussed by PM which is similar to this one from Moritz:
The Upgrade Wizard finishes successfully with no errors and the columns are present in the database. They already have been migrated from 18 > 20 > 22 but the error occurs here.
Backend runs fine.
We are using ai-customergroups, could that interfere?
My error:
Code: Select all
(1/1) Aimeos\Base\DB\Exception
SQLSTATE[42S22]: Column not found: 1054 Unknown column 't3feu.cnum' in 'field list': SELECT t3feu."cnum", t3feu."shipping_conditions", t3feu."shipping_info", t3feu."fca_threshold", t3feu."payment_terms", t3feu."payment_type", t3feu."department", mcus."uid" AS "customer.id", mcus."siteid" AS "customer.siteid", mcus."name" AS "customer.label", mcus."gender" AS "customer.salutation", mcus."username" AS "customer.code", mcus."title" AS "customer.title", mcus."company" AS "customer.company", mcus."vatid" AS "customer.vatid", mcus."first_name" AS "customer.firstname", mcus."last_name" AS "customer.lastname", mcus."address" AS "customer.address1", mcus."zip" AS "customer.postal", mcus."city" AS "customer.city", mcus."zone" AS "customer.state", mcus."static_info_country" AS "customer.countryid", mcus."language" AS "customer.languageid", mcus."telephone" AS "customer.telephone", mcus."email" AS "customer.email", mcus."fax" AS "customer.telefax", mcus."www" AS "customer.website", mcus."longitude" AS "customer.longitude", mcus."latitude" AS "customer.latitude", mcus."password" AS "customer.password", mcus."date_of_birth" AS "customer.birthday", mcus."usergroup" as "customer.groups", mcus."pid" AS "typo3.pageid", mcus."disable" AS "customer.status", mcus."crdate" AS "customer.ctime", mcus."tstamp" AS "customer.mtime" FROM "fe_users" as mcus WHERE ( ( mcus."siteid" IN ('','1.') ) AND ( ( mcus."uid" IS NULL ) AND ( mcus."disable" = 0 ) ) ) AND mcus."deleted" = 0 GROUP BY mcus."uid", mcus."uid", mcus."static_info_country" ORDER BY mcus."uid" ASC LIMIT 100 OFFSET 0
Backend runs fine.
We are using ai-customergroups, could that interfere?
Re: Upgrade from 18.10.11 to 22.7.1
Your SQL statement uses two different table aliases, "t3feu" and "mcus" while only "mcus" is defined.
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, give us a star
If you like Aimeos, give us a star