I am including Custom Menu Link Entities: http://take.ms/7axvi
However, no menu links are showing up in the sitemap. Only content type entities are. When I look at the "Custom menu link" vertical tab of the settings, it is showing 53 indexed items but 0 visible. http://take.ms/kJdA0
I tried editing and saving several menu items (leaving XML sitemap settings to use the default), rebuilding through the UI, and clearing the cache. This did not fix it.
I tried editing and saving several menu items (changing XML sitemap settings from the default), rebuilding through the UI, and clearing the cache. This did not fix it.
There are no errors in the recent log messages.
Am I missing something? Or is this a bug?
Comment | File | Size | Author |
---|---|---|---|
#12 | 2852713-fix-menu-links.patch | 2.51 KB | Dave Reid |
#11 | 2852713-fix-menu-links.patch | 2.35 KB | Dave Reid |
|
Comments
Comment #2
cristian100Same problem, can't get Main menu items to show on xml sitemap.
Comment #3
anish.a CreditAttribution: anish.a commentedSame issue for me.
Comment #4
jorgegc CreditAttribution: jorgegc as a volunteer commentedThe issue is coming from checking whether anonymous users have access to view the menu item entity and not the page it is pointing to. I have created a patch that addresses this issue.
Comment #5
C-LogemannI can confirm this bug and patch #4 is fixing it.
+1 for RTBC
Comment #6
pifagorThis patch didn't passed the tests. You need to work on the patch
Comment #7
jorgegc CreditAttribution: jorgegc as a volunteer commented@pifagor, the patch didn't even trigger the tests because the branch hadn't passed tests in 4 weeks. I am manually triggering tests now.
Comment #8
pifagorThe patch must pass automatic tests
Comment #9
hanoiiIt works, although I noticed something odd on my use case.
I have a menu that has links for both internal nodes and also non-existant URLs, which is because this menu is fed to a frontend angular application. This non-existant URls end up with the URL from which the sitemap is regenerated.
I think it should use the same url configured as the rest.
Comment #10
Dave ReidComment #11
Dave ReidTook a look at this and I think we can do even better. Let's attempt to transform the URL to a relative one, and let's support when the user enters a manual base path like /something.
Comment #12
Dave ReidOkay I have tested this version with:
1. Normal routed menu links (entities, etc)
2.
<front>
links3.
<nolink>
links4. base:/path links
5. Not-same domain external links
Comment #14
Dave ReidComitted #12 to 8.x-1.x. Leaving open for tests.
Comment #15
pifagor