URL key in hierarchy not updated after URL key update in CMS page

[Etje]

Preconditions and environment

Magento 2.4.4 Enterprise Edition

Steps to reproduce

• Make a CMS page.
• Add the page to Hierarchy (Content -> Elements -> Hierarchy)
• Go back to the CMS page and change URL key
• Go back to hierarchy, and you will see that the URL key has not changed

Expected result

Expected result is an updated URL key in the hierarchy

Actual result

Actual result is the the URL key in hierarchy is not updated

Additional information

No response

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 @Etje. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Lima. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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-Lima]

@magento give me 2.4-develop instance with edition ee

[magento-deployment-service]

Hi @engcom-Lima. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Lima, here is your Magento Instance: https://ad63673c29d04ebe569993df546407a2.instances.magento-community.engineering
Admin access: https://ad63673c29d04ebe569993df546407a2.instances.magento-community.engineering/admin_6d9a
Login: 94adf993
Password: 6bf8cfc1dbdc

[engcom-Lima]

Hi @Etje ,

I have tried to reproduce the issue in clean Magento 2.4-develop with EE edition but unable to reproduce it.
Kindly refer my video if anything I am missing kindly provide me more information.
Also try to test in latest Magento 2.4-develop & let us know if you are facing any issue.

Thanks

[Etje]

I saw your video. unfortunately the Magento instance provided by @engcom-Lima does not work anymore, so I can not verify it. That said, I am oké with closing the issue, because it's not relevant anymore

[engcom-Lima]

Hi @Etje ,

As per your last comment marking this issue as fixed. Hence, closing this issue.

Thanks

[nouchka]

I still have the issue. In magento 2.4.3 in my case.

Hi @engcom-Lima , I watched the video and you added the page to the root node. I tried on my local setup and I don't have the issue when it's the root node.
so "Steps to reproduce" should be:
Add the page to Hierarchy (Content -> Elements -> Hierarchy) on a sub-node, not the root one

best regards

[reense]

I've created a similar issue, and I think it's the same problem. It's still not fixed: #39482