Let other modules alter the export of nodes [#1754428]

Comment	File	Size	Author
#1	1754428-allow-node-export-alter.patch	608 bytes	pirog

File	Size
1754428-allow-node-export-alter.patch	608 bytes

Comment #2

populist CreditAttribution: populist commented 21 September 2012 at 16:55

What kinds of use cases would this kind of alter hook be useful in solving?

Log in or register to post comments

Comment #3

pirog CreditAttribution: pirog commented 21 September 2012 at 20:25

i think there are a couple of tracks

1. if you wanted to provide a "content skeleton" that a site builder or end user could then modify and you didn't want these changes to make the feature show up as overridden.
2. if you have any sort of site specific ID reference, such as taxonomy terms on a node it would be good to exclude them from the export since they are likely not going to match up on different sites.

Log in or register to post comments

Comment #4

pirog CreditAttribution: pirog commented 21 September 2012 at 20:30

i look at #2 as something that eventually would be replaced with better support for handling referenced entities via UUID or something similar.

Log in or register to post comments

Comment #5

populist CreditAttribution: populist commented 29 October 2012 at 18:25

Here are some cleaner use cases:

1.) You want to modify your default content by adding information (i.e. taxonomy terms) as part of installation but you don't want those to be exported again

2.) You want to use the UUID module for your site, but don't want to export that out to your feature

3.) You want to automatically update the created/modified times each time the item is exported.

Log in or register to post comments

Comment #6

populist CreditAttribution: populist commented 29 October 2012 at 18:28

Status:

Needs review

» Reviewed & tested by the community

I also went ahead and tested this out and it works great. Shouldn't be a problem rolling it in since it only is used if someone explicitly invokes the alter hook.