Category Url Rewrite not correctly generated when updating url_key through API

[SteffenCH]

Preconditions and environment

• Magento version: 2.4.* ( Tested on 2.4.6)

When updating an url_key in backend/admin, url rewrites are created from old-url to new-url, and new-url to category/view/id/{id} as expected.

Updating through REST API "V1/categories" (POST) results in only new-url to category/view/id/{id} being generated, essentially losing the connection between old-url to new-url and thus losing valuable SEO potential.

Steps to reproduce

• Ensure "Create Permanent Redirect for URLs if URL Key Changed" is enabled in:
  Stores > Configuration > Catalog > Catalog > Search Engine Optimization

• Update url_key through REST API "V1/categories" (POST)

• Observe

Expected result

Url rewrites should be created from old-url to new-url, and new-url to category/view/id/{id} when updating url_key through API

Actual result

Only new-url to category/view/id/{id} urls is genereated when updating url_key through API, thus losing connection between old url and new url.

Additional information

This is quite critical as it basically means that any shop managing its categories through the api with an external system can't reliably generate category urls without losing valuable SEO.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @SteffenCH. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @SteffenCH,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and we are not able to reproduce the issue.Kindly refer the screenshots.

Could you please provide us payload for the APi and also provide screenshots or screencast if possible to proceed further.

Thanks.

[SteffenCH]

@engcom-Bravo You've actually managed to reproduce the issue it seems.

When UPDATING a category URL through API, we expect oldUrl -> newUrl, and newUrl -> catalog/category/view/id{id} - This happens when done through backend, not when done through API however.

If your screenshot is from updating using API, you have successfully reproduced the error

[engcom-Bravo]

Hi @SteffenCH,

Thanks for your update.

We have tried to reproduce the issue in Latest 2.4-develop instance and we are not able to reproduce the issue.Kindly refer the screenshots.

This one when we are updating from Backend.

Could you please let us know if we are missing anything and elaborate the steps to reproduce.

Thanks.

[hostep]

@SteffenCH: can you try with providing the flag save_rewrites_history and set it to 1 in your api call?
I remember from a long time ago that this did the trick, but not 100% sure, so maybe you can give it a try?

Update: here you can find some more info about it: #29205

[engcom-Bravo]

@hostep Thanks for your Contribution!!.

Hi @SteffenCH,

Could you please refer this comment #39632 (comment) and please let us know if you are still facing any issue.

Thanks.

[SteffenCH]

Much appreciated. Will report back if it works or not - Will not be able to test it today sadly.

[SteffenCH]

We're still producing data and screenshots to provide as good details as possible - i do apologise the wait, but we have not forgotten about this :)