Problem/Motivation

Custom entries will usually be related to e.g. views, custom controllers or other fixed routes but at the moment custom entries can't be exported.

Proposed resolution

It would be useful to provide custom entries as config so they become exportable.

Remaining tasks

Provide a config entity for custom entries.

User interface changes

API changes

Data model changes

Comments

daften created an issue. See original summary.

DarkstarTom’s picture

DarkstarTom CreditAttribution: DarkstarTom commented

I've been trying XML sitemap and I definitely think that custom links should be part of config. I would be very grateful if you could implement this.

G42’s picture

G42 CreditAttribution: G42 commented

Do you mean that when the site config is exported the xmlsitemap config should include all custom links that were added?

ShaunDychko’s picture

ShaunDychko CreditAttribution: ShaunDychko as a volunteer commented
Issue summary: View changes

@G42, yes, that's exactly what should happen.

Dave Reid’s picture

Dave Reid
he/him
Primary language English
Location Nebraska USA
CreditAttribution: Dave Reid as a volunteer and at Lullabot commented
Status: Active » Closed (won't fix)

As maintainer, my intent was never to support custom links as config. They are content, like menu links.

mpp’s picture

mpp CreditAttribution: mpp as a volunteer and at AmeXio for District09 commented
Title: Shouldn't custom xmlsitemap entries be config » [feature request] Make custom xmlsitemap entries exportable through config
Category: Bug report » Feature request
Issue summary: View changes
Status: Closed (won't fix) » Active

Hi Dave, perhaps we could re-label this one as a feature request? This way someone might still take a shot at implementing it.
We could do something like menu_link_config and make a submodule to make custom links exportable as config.

If not, I'd love to hear some arguments why it's designed as content.