Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update category attribute isActive fails with REST, "URL key for specified store already exists." #3543

Closed
Widmayer opened this issue Feb 25, 2016 · 2 comments

Comments

@Widmayer
Copy link

I added a category with the following REST-call:

curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'Authorization: Bearer abcd' -d '{
"category": {
"parentId": 2,
"name": "TestCategory",
"isActive": false
}
}' 'http://0.0.0.0/index.php/rest/default/V1/categories'

When I try to update the attribute "isActive" to true with the same call I get an error:

{
"message": "Could not save category: %1",
"parameters": [
"URL key for specified store already exists."
]
}

When I try to use the PUT method with the following command:
curl -X PUT --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'Authorization: Bearer abcd' -d '{
"category": {
"name": "TestCategory",
"isActive": true
}
}' 'http://0.0.0.0/index.php/rest/default/V1/categories/76'
I get the error:
{
"message": "Could not save category: %1",
"parameters": [
"The value of attribute "is_active" must be set"
]
}

is_active is set, so I think this is a bug.
Any hints how to update a category attribute with REST?

Regards,
Tobias

@katmoon katmoon added the MX label Feb 25, 2016
@vkorotun vkorotun removed the MX label Aug 4, 2016
@veloraven
Copy link
Contributor

@Widmayer thank you for your report.
Please, provide the used Magento version.

@veloraven
Copy link
Contributor

According to contributor guide, tickets without response for two weeks should be closed.
If this issue still reproducible please feel free to create the new one: format new issue according to the Issue reporting guidelines: with steps to reproduce, actual result and expected result and specify Magento version.

magento-engcom-team pushed a commit that referenced this issue Dec 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants