Having issue with navigation menu not updated

[zaheerahmad]

Problem:
for example my category name “soup, noodle & pasta” I add this category in my menu and after that will change my category name “pizza, pasta & noddles” it should automatically update in in menu too.

but unfortunately it's not working.

Think I already did I tried to disabled all plugin not happened I tried to change theme same result

Test case If you have category simple category name e.g "contact" it will work fine.

My issue is when I put special character like "," or "&" i face this issue

[achyuthajoy]

Hi @zaheerahmad!

I've tried the steps you've mentioned and couldn't reproduce the problem. I've also tried different combinations with special characters and the menu updated as expected.

Try switching your theme to Twenty Nineteen, turn of all plugins and see if you can reproduce the problem. If it appears on Twenty Nineteen, please share a screenshot / screen cast.

[zaheerahmad]

@achyuthajoy I test on fresh installed wordpress and yes theme is Twenty Nineteen and I deactivate all plugins I also create the video you can see in video

• ​https://vimeo.com/359226553

again I repeat my issue when I create one menu with categories after that when I update my category name, In menu category name not update automatically if i use any special character e.g ", or &" but if i change simple category name like hello it will be change automatically.

you can see all this thing in above video link

regards

[achyuthajoy]

Hey @zaheerahmad Thanks for the video. I was able to replicate the problem you've mentioned using the Navigation widget.

Found that when a category is created, the inputs are encoded (​https://developer.wordpress.org/reference/functions/_wp_specialchars/). However, when they're read from the db for using in the menu, it's not decoded making the Category Title act as a Custom label.

I've made a patch to fix it and will update the thread shortly.

[achyuthajoy]

Patch to fix problems with special characters & quotes on categories while adding them to menus

[achyuthajoy]

Here are the steps to re-produce the problem.

1. Add a Post Category with either quotes or special characters like &, > or <.
2. Create a new menu and add the category to it.
3. Create a footer navigation widget and choose the created menu.
4. Edit & Change the category name under Posts -> Categories to notice that the change didn't appear in the footer.
5. Try creating a new Category without any quotes or special characters and add it to the menu. Try changing the category name to something else to see that the changes are reflected in the footer.

P.S - This bug only when a category is created for the first time and it's name contains quotes or special characters. If an existing category is added to the menu and renamed to have quotes or special characters, doesn't cause this bug.

[desrosj]

Thanks for this ticket, @zaheerahmad, and thanks for investigating, @achyuthajoy!

I am able to reproduce the issue described with the steps that were outlined.

However, it seems that trac-48011.diff​ is not applying for me. Looking at src/wp-includes/nav-menu.php (source), I actually don't see the line being replaced in the patch, and the suggested change is already present. Can you take another look @zaheerahmad? Some unit tests showing the problem may also be helpful.

I am going to put this in the Future Release milestone. But, once a patch is ready and tested, this can be moved into a numbered milestone.

[achyuthajoy]

Thanks for taking a look @desrosj. It seems the diff file I added was incorrect. It changes should be in reverse. I'm adding a new patch file.

Thanks for this ticket, @zaheerahmad, and thanks for investigating, @achyuthajoy!

I am able to reproduce the issue described with the steps that were outlined.

However, it seems that trac-48011.diff​ is not applying for me. Looking at src/wp-includes/nav-menu.php (source), I actually don't see the line being replaced in the patch, and the suggested change is already present. Can you take another look @zaheerahmad? Some unit tests showing the problem may also be helpful.

I am going to put this in the Future Release milestone. But, once a patch is ready and tested, this can be moved into a numbered milestone.

[pento]

Patch looks good, could you add some unit tests?

tests/phpunit/tests/post/nav-menu.php would be a good place to add the tests.

[donmhico]

Included unit tests and use strict comparison.

[audrasjb]

Hi,

Thanks @donmhico for the unit tests. I tested the above patch and it looks good to me, the patch is fixing the issue as expected.
Let's milestone that for 5.4.

[birgire]

48011-3.diff​ refreshes 48011.2.diff​ that didn't apply clean on my install.

It further:

• Expands the test name string to 'Test Cat - \"Pre-Slashed\" Cat Name & >' to cover the pre-slashed case.
• Replaces array alias [] for array() in the test.
• Adjustments according to the coding standard.
• Adjusts the inline docs of the test.

[birgire]

48011-4.diff​ just removes my debug assignment relic and has a variation of the inline array comment in the test.

[kirasong]

Just a quick note that I tested 48011-4.diff​ and it looks to be working well + test passing.

[SergeyBiryukov]

Would like to give this a closer look, moving to 5.5 for now.

[audrasjb]

Patch refreshed for WP 5.5

[audrasjb]

Patch still works fine. I only took care of refreshing the current patch so it could hopefully ship with 5.5.

[achyuthajoy]

Replying to audrasjb:

Patch still works fine. I only took care of refreshing the current patch so it could hopefully ship with 5.5.

Thanks @audrasjb :+1

[whyisjake]

In 48416:

Menus: Ensure that category menus with special characters can be updated.

Slashes and HTML encoding could cause some menus not to be updated.

Fixes #48011.

Props zaheerahmad, achyuthajoy, desrosj, pento, SergeyBiryukov, donmhico, audrasjb, birgire, mikeschroder.

[SergeyBiryukov]

In 48439:

Menus: Simplify the test for wp_update_nav_menu_item() with special characters in category name.

The menu-item-title value is saved as a post_title property, so the resulting property can be checked directly, without a callback.

Follow-up to [48416].

See #48011.