When Strongarm is enabled in addition to Features, it knows to automatically export variables that relate to a node type when a node type is exported. Of course, it only does that for core variables (such as node options, node preview, node submitted).

It would be nice if XML sitemap node did this for its own node type variable.

Patch coming.

CommentFileSizeAuthor
#4 2521574-strongarm-support.patch1.96 KBdave reid
#1 2521574.xmlsitemap.strongarm-features-support.patch682 bytesjoachim

Comments

joachim’s picture

joachim commented
Status: Active » Needs review
StatusFileSize
new 2521574.xmlsitemap.strongarm-features-support.patch682 bytes
elusivemind’s picture

elusivemind commented

I have tested this and confirm that it works.

elusivemind’s picture

elusivemind commented
Status: Needs review » Reviewed & tested by the community
dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Title: add support for automatically exporting node type variable to features » add support for automatically exporting node type / vocabulary / menu variable to features
Status: Reviewed & tested by the community » Needs review
StatusFileSize
new 2521574-strongarm-support.patch1.96 KB

Let's just expand this to all the submodules that should do this, not just node types.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Title: add support for automatically exporting node type / vocabulary / menu variable to features » When using Features and Strongarm, export XML sitemap variables along with node types, taxonomy vocabularies, and menus
Status: Needs review » Reviewed & tested by the community

I've tested this and confirmed it works.

  • Dave Reid committed 44a942b on 7.x-2.x 
    Issue #2521574 by joachim, Dave Reid: When using Features and Strongarm...
dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Reviewed & tested by the community » Fixed

I would suspect this needs to be ported to D8 but using a different issue: we should likely be storing these variables using third party settings on the node type / menu / vocabulary config entities. I'll file a different issue.

elusivemind’s picture

elusivemind commented

Did this make it into today's security update release?

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.