DivanteLtd / pimcore-magento2-bridge

Pimcore module for Magento 2 integration
36 stars 24 forks source link

REST doesn't return any of the inputfields #12

Closed ChatoDeVeirman closed 5 years ago

ChatoDeVeirman commented 5 years ago

Hello,

When I try to add a category it gives me

Error while syncing object: 12484 with instance: http://localhost for store view: 1. Message: An error occurred while insert/update category "12484": Notice: Undefined index: name in /var/www/html/app/code/Divante/PimcoreIntegration/Http/Response/Transformator/CategoryUpdateTransformator.php on line 67

After some more research and browsing the rest api, I found out that the elements data is empty.

Rest api get request:

http://localhost/webservice/rest/category?id=12484&status=SUCCESS&message=Test&instanceUrl=http://localhost&storeViewId=1&apikey=KEY

Response:

{
    "data": {
        "12484": {
            "path": "/",
            "creationDate": 1556956347,
            "modificationDate": 1556960424,
            "userModification": 19,
            "elements": {},
            "className": "integrationCategory",
            "id": 12484,
            "parentId": 12474,
            "key": "cat99",
            "published": true,
            "type": "object",
            "userOwner": 19,
            "properties": {
                "synchronize-status": {
                    "name": "synchronize-status",
                    "data": "ERROR",
                    "type": "text",
                    "inheritable": null,
                    "inherited": null
                }
            },
            "index": null,
            "isRoot": true
        }
    },
    "missing_objects": [],
    "success": true
}
mbolka commented 5 years ago

@PandaCrafter1 We have updated the version and solved multiple issues. As we were not able to reproduce your issue, could you please re-test and confirm if the issue still occurs?

mbolka commented 5 years ago

I’m closing this issue because it has been inactive for a few months. This probably means that it is not reproducible or it has been fixed in a newer version.

Please reopen if you still encounter this issue with the 1.2.0 and then please ireport issue. You can also contribute directly by providing a patch. Thank you!