Skip to content

Update category name via API REST #14119

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

Closed
cpjeanpaul opened this issue Mar 15, 2018 · 5 comments
Closed

Update category name via API REST #14119

cpjeanpaul opened this issue Mar 15, 2018 · 5 comments
Assignees
Labels
Event: distributed-cd Distributed Contribution Day Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@cpjeanpaul
Copy link

Preconditions

  1. Magento 2.1.10

Steps to reproduce

  1. CREATE a Category via API REST
  2. UPDATE the name of the same category via API REST

Expected result

  1. show the new name of the category in the store menu
  2. show the new name of the category in category tree (backoffice)

Actual result

  1. The updated name is displayed by GET via API REST
  2. The updated name is displayed in the store menu
  3. THE UPDATED NAME IS NOT DISPLAYED in category tree (backoffice). It keeps old name.
@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Mar 15, 2018
@AaronKaa
Copy link

This could be related to #14080

@magento-engcom-team magento-engcom-team added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed labels Mar 16, 2018
@magento-engcom-team
Copy link
Contributor

@cpjeanpaul, thank you for your report.
We've acknowledged the issue and added to our backlog.

Steps to reproduce

  1. CREATE a Category via API REST POST /V1/categories

{
"category": {
"name": "CAT",
"is_active": true
}
}

  1. UPDATE the name of the same category via API REST PUT /V1/categories/3

{
"category": {
"name": "CATnew",
"is_active": true
}
}

@mrodespin
Copy link
Contributor

I think this is not an issue is just a documentation problem.

If you don't specify any store code the API will update the data in the same store that you are using in the API, in a regular magento installation, it means store code 1 or default.

This means that de admin store will keep the older information about the category. If you want to change the information in the admin too is necessary to use the following endpoint.

rest/all/V1/categories/:id/

The bold param is the store code.

  • All for update the category in all stores
  • Storecodeview for update the category only in that store view

It happens the same in product API update logic.

@mrodespin
Copy link
Contributor

#distributed-cd

@magento-engcom-team
Copy link
Contributor

@mrodespin thank you for joining. Please accept team invitation here and self-assign the issue.

@magento-engcom-team magento-engcom-team added the Event: distributed-cd Distributed Contribution Day label Mar 24, 2018
@osrecio osrecio closed this as completed Mar 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Event: distributed-cd Distributed Contribution Day Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests

5 participants