Update on version 2024.10
Forum rules
Always add your Laravel, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
Spam and unrelated posts will be removed immediately!
Always add your Laravel, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
Spam and unrelated posts will be removed immediately!
- AleksandarJovanovic
- Posts: 52
- Joined: 01 Jun 2022, 21:26
Update on version 2024.10
Php 8.2
Linux
Version 2024.07.
I am trying to update from version 2024.7 to the latest 2024.10.
As far as I understand, the command "composer up" should be sufficient.
However, after the update, I am still on the old version. Am I doing something wrong?
Thank you in advance.
Linux
Version 2024.07.
I am trying to update from version 2024.7 to the latest 2024.10.
As far as I understand, the command "composer up" should be sufficient.
However, after the update, I am still on the old version. Am I doing something wrong?
Thank you in advance.
Re: Update on version 2024.10
You have to change the version in the composer.json file to "~2024.10" and then run "composer up" (maybe "composer -W up" is required to update all dependencies too).
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
- AleksandarJovanovic
- Posts: 52
- Joined: 01 Jun 2022, 21:26
Re: Update on version 2024.10
Thank you, I successfully updated it. I have an issue with users who have edit or admin access. After I add and verify them, when I go to the admin panel, I get the following error:
"Not allowed to access JQAdm 'dashboard' client."
"Not allowed to access JQAdm 'dashboard' client."
Re: Update on version 2024.10
Did you change any settings for limiting access to the backend panels?
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
- AleksandarJovanovic
- Posts: 52
- Joined: 01 Jun 2022, 21:26
Re: Update on version 2024.10
No i didnt, i have another instalation and the same result. I will check all again.
- AleksandarJovanovic
- Posts: 52
- Joined: 01 Jun 2022, 21:26
Re: Update on version 2024.10
I have installed a completely new installation without any modifications. Standard configuration.
I added a customer and assigned them the "editor" permission. I verified them today. When I try to access /admin with this account, I get the error "Not allowed to access JQAdm 'dashboard' client".
Previously, I did the same, and everything worked fine.
Alex
I added a customer and assigned them the "editor" permission. I verified them today. When I try to access /admin with this account, I get the error "Not allowed to access JQAdm 'dashboard' client".
Previously, I did the same, and everything worked fine.
Alex
Re: Update on version 2024.10
Thanks for the hint! A last minute change caused some trouble and a new version of the aimeos/aimeos-laravel package with the fix has been tagged. Please use "composer up" to update your installation.
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
- AleksandarJovanovic
- Posts: 52
- Joined: 01 Jun 2022, 21:26
Re: Update on version 2024.10
Thank you very much for your help; that part is now working. I hope you don't mind if I send any bugs I notice in the new version.
The problem now is that when I search on the frontend as an unregistered user, if the search finds products, the search in the left sidebar encounters an error. When the user is logged in, it shows the following error:
SQLSTATE[23000]: Integrity constraint violation: 1052 Column 'id' in order clause is ambiguous: SELECT "product.status", max("val") AS "value" FROM ( SELECT mpro."status" AS "product.status", mindpr."value" AS "val" FROM "mshop_product" mpro LEFT JOIN "mshop_index_catalog" AS mindca USE INDEX ("idx_msindca_s_ca_lt_po", "unq_msindca_p_s_cid_lt_po") ON mindca."prodid" = mpro."id" LEFT JOIN "mshop_index_price" AS mindpr USE INDEX ("unq_msindpr_pid_sid_cid", "idx_msindpr_sid_cid_val") ON mindpr."prodid" = mpro."id" LEFT JOIN "mshop_index_text" AS mindte ON mindte."prodid" = mpro."id" WHERE ( ( mpro."siteid" IN ('','1.') ) AND ( ( mpro."status" IS NOT NULL AND mindpr."value" IS NOT NULL ) AND ( ( mindca."catid" IS NOT NULL AND ( mindte."siteid" IN ('','1.') AND mindte."langid" = 'en' AND MATCH( mindte."content" ) AGAINST( '\'dark* \"dark\"\'' IN BOOLEAN MODE ) > 0 OR mpro."code" LIKE 'dark%' ESCAPE '#' ) AND mindca."catid" IN ('14') AND mindca."siteid" IN ('','1.') AND mindca."catid" IN ( '14' ) AND mindca."listtype" = 'default' AND mindca."pos" >= 0 AND mindpr."siteid" IN ('','1.') AND mindpr."currencyid" = 'USD' AND mindpr."value" IS NOT NULL ) AND ( ( mpro."status" = 1 ) AND ( mpro."start" <= '2024-10-10 21:04:10' OR mpro."start" IS NULL OR mpro."type" = 'event' ) AND ( mpro."end" >= '2024-10-10 21:04:10' OR mpro."end" IS NULL ) ) ) ) ) GROUP BY mpro."status", mindpr."value", mpro."id" ORDER BY id ASC LIMIT 100 OFFSET 0 ) AS list GROUP BY "product.status"
These are all errors on a completely new installation without any modifications.
Alex
The problem now is that when I search on the frontend as an unregistered user, if the search finds products, the search in the left sidebar encounters an error. When the user is logged in, it shows the following error:
SQLSTATE[23000]: Integrity constraint violation: 1052 Column 'id' in order clause is ambiguous: SELECT "product.status", max("val") AS "value" FROM ( SELECT mpro."status" AS "product.status", mindpr."value" AS "val" FROM "mshop_product" mpro LEFT JOIN "mshop_index_catalog" AS mindca USE INDEX ("idx_msindca_s_ca_lt_po", "unq_msindca_p_s_cid_lt_po") ON mindca."prodid" = mpro."id" LEFT JOIN "mshop_index_price" AS mindpr USE INDEX ("unq_msindpr_pid_sid_cid", "idx_msindpr_sid_cid_val") ON mindpr."prodid" = mpro."id" LEFT JOIN "mshop_index_text" AS mindte ON mindte."prodid" = mpro."id" WHERE ( ( mpro."siteid" IN ('','1.') ) AND ( ( mpro."status" IS NOT NULL AND mindpr."value" IS NOT NULL ) AND ( ( mindca."catid" IS NOT NULL AND ( mindte."siteid" IN ('','1.') AND mindte."langid" = 'en' AND MATCH( mindte."content" ) AGAINST( '\'dark* \"dark\"\'' IN BOOLEAN MODE ) > 0 OR mpro."code" LIKE 'dark%' ESCAPE '#' ) AND mindca."catid" IN ('14') AND mindca."siteid" IN ('','1.') AND mindca."catid" IN ( '14' ) AND mindca."listtype" = 'default' AND mindca."pos" >= 0 AND mindpr."siteid" IN ('','1.') AND mindpr."currencyid" = 'USD' AND mindpr."value" IS NOT NULL ) AND ( ( mpro."status" = 1 ) AND ( mpro."start" <= '2024-10-10 21:04:10' OR mpro."start" IS NULL OR mpro."type" = 'event' ) AND ( mpro."end" >= '2024-10-10 21:04:10' OR mpro."end" IS NULL ) ) ) ) ) GROUP BY mpro."status", mindpr."value", mpro."id" ORDER BY id ASC LIMIT 100 OFFSET 0 ) AS list GROUP BY "product.status"
These are all errors on a completely new installation without any modifications.
Alex
Re: Update on version 2024.10
Yes, please report all bugs so we can iron out that issues!
The problem is fixed in aimeos/aimeos-core:2024.10.x-dev and will be part of the next tagged release. Can you confirm that it works using this version?
The problem is fixed in aimeos/aimeos-core:2024.10.x-dev and will be part of the next tagged release. Can you confirm that it works using this version?
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
- AleksandarJovanovic
- Posts: 52
- Joined: 01 Jun 2022, 21:26
Re: Update on version 2024.10
Thank you, my current version is "~2024.10", the installation was done yesterday, and I can confirm that the error is still present.