When updating coreshop from version 2.2 to version 3

[claudesimo1990]

The classes table has been modified. The Products no longer have the reference number 17 but rather cs_product so new tables are created with the extension cs_product instead of 17. with this change my data (Products) is no longer displayed on the site. because the requests are made on the new table with the extension (cs_product). is there a solution? i would like not to do this manually, as it involves a lot of sensitive data.

[dpfaffenbauer]

@claudesimo1990 please check your original class definitions id values and compare them to what they are after the update. if they changed, please revert the line to what it was before.

[claudesimo1990]

@dpfaffenbauer

After Coreshop Update
the definition_CoreShopProduct.php looks like:
protected $o_classId = "cs_product"; protected $o_className = "CoreShopProduct";

Before Update
protected $o_classId = "17"; protected $o_className = "CoreShopProduct";

After the update, we will receive a new empty table for the products with the classID cs_product, in addition to the old table. However, our products will still be located in the old table (object_localized_query_17_de_DE).

[dpfaffenbauer]

@claudesimo1990 not sure how you did update the class-definitions, but change the id back to 17 (in the file var/classes/CoreShopProduct_definition.php).

Please also check all other CoreShop Definition files.

Once you checked them, run ´bin/console pimcore:build:classes` and you should have your data back

[claudesimo1990]

@dpfaffenbauer thank you very much now it works :)

But we must update the class-definitions so that the migrations could pass through or is there another solution for the migration (in the vendor)?

We also have the problem that the controllers in the document_page table are not adjusted during the migrations. In the new Coreshop version (3), the controllers only work if there is no '@' in the DB.

[dpfaffenbauer]

But we must update the class-definitions so that the migrations could pass through or is there another solution for the migration (in the vendor)?

I did several updates of CoreShop and I never had the Problem that the CoreShop Migrations changed the class-ids....

We also have the problem that the controllers in the document_page table are not adjusted during the migrations. In the new Coreshop version (3), the controllers only work if there is no '@' in the DB.

you have to run bin/console migration:controller-reference on Pimcore 6.9 before updating to Pimcore X. The Command does NOT exist in Pimcore X, so you have to do it on Pimcore 6.9.

[claudesimo1990]

@dpfaffenbauer

you have to run bin/console migration:controller-reference on Pimcore 6.9 before updating to Pimcore X. The Command does NOT exist in Pimcore X, so you have to do it on Pimcore 6.9.

Thanks for the hint :)

I did several updates of CoreShop and I never had the Problem that the CoreShop Migrations changed the class-ids....

if I run bin/console doctrine:migrations:migrate Command I get this problem. They have problem with the class-id in the class-definitions

[dpfaffenbauer]

@claudesimo1990 ok, now it is getting to specific, I don't know what you did before and how the setup and what has been adapted.

[M4X1L]

Hi @dpfaffenbauer ,
I am currently facing an issue regarding the management of different themes for Coreshop. I have multiple shops and depending on which store they should render different templates.

In Coreshop 2, I have solved this by creating a separate theme directory for each shop, which contains the overridden templates. This allows me to customize the templates for each individual shop.

config.yaml

twig:
    paths:
        '%kernel.project_dir%/templates/themes/common': 'CORESHOP_COMMON'

services.yaml

    app.coreshop.store.context.request.document_based:
        class: AppBundle\CoreShop\Store\Context\DocumentBasedRequestRequestResolver
        arguments:
            - '@coreshop.repository.store'
        tags:
            - { name: coreshop.context.store.request_based.resolver, priority: 300 }

How does it work in Coreshop 3?

[dpfaffenbauer]

basically the same... CoreShop 3 uses Sylius Theme Bundle for theming. You can use theme inheritance to have a common theme.

[claudesimo1990]

@dpfaffenbauer

Good day, I have another problem with rebuilding the classes. when I run the command bin/console pimcore:build:classes and bin/console pimcore:deployment:classes-rebuild -c -n I don't get any errors displayed but on the page I see the error with the return type. is there another command to rebuild the classes with the return type of the individual methods in the classes?

[dpfaffenbauer]

CoreShop added return-types with CoreShop 3, please enable that in your class-definitions by setting 'generateTypeDeclarations' to true in all CoreShop definition files in var/classes/definition_CoreShop*.php

[claudesimo1990]

@dpfaffenbauer

I found this migration guide online, please I want to know how can I do this without adjusting the vendor directories ?

coreshop/CoreShop#2161