The current node_export_features integration aborts creation of the node options list if more than 20 nodes do not have UUIDs. This behaviour is undesirable on some sites. The UUID module has a feature which allows only certain content types to receive UUIDs (I'm not sure why, but they do..). When this functionality is enabled, in UUID, it is possible that all Page nodes get a UUID but all Blog nodes do NOT get a UUID, and this is totally correct behaviour.
This patch removes the auto UUID creation functionality and instead directs the user to go fix the settings in their UUID configuration in the case where a node is missing a UUID.
Patch to be attached shortly..
Comments
Comment #1
James Andres commentedThe patch.
Comment #2
James Andres commentedForgot to mention, Daniel I know you're busy, if you think this looks OK I'll go ahead and commit it. Would be good to have someone verify this.
Comment #3
danielb commentedYeah that was a weird thing I did, but only really works if you have a few nodes. While you have your head in this, can we do something similar in Drupal 7? Not sure if the same method is used there.
Also I'd prefer to do something like this with the formatting of the message
It still looks awkward, it's just that I'm worried the whitespaces within the string could show in translation interfaces - though I really have no idea if they would. I know the escaping backslashes will, so I changed that.
Comment #4
danielb commentedI've committed the patch and changed the message like in #3.
http://drupalcode.org/project/node_export.git/commit/7364f21
Still need to look at D7 though.
Comment #5
danielb commented7.x done
I'm also going to remove the $msg_printed variable from both versions. drupal_set_message() has a parameter that prevents duplicate messages being printed.
Comment #6
danielb commentedI guess that's it. If you want to revisit it, go ahead and reopen.
Comment #7
James Andres commentedThanks Daniel. Sorry for going dark there, I was on holiday last week. Much appreciated.
Comment #9
fxarte commentedHi there,
This may only affect in my case, which is, using drush features component command and selecting any particular components class, it produces this message for all the nodes without UUID, a really long list, which is really undesirable.
As some times you just need to export a very small subset of nodes, I added an extra check for a variable: node_export_features_generate_messages which we could set/unset whenever we need this messages to show up or not.
I just wanted to run the idea in this thread as there may be a better solution for this situation:
Comment #10
joelpittetThis looks like it would be the trick but needs to be ported back to 6.x.
Comment #11
joelpittetHmm maybe I'm wrong, I just see all nodes spitting that warning message and thought this was the cure but it may have been the cause.
Some nodes aren't generating UUID (on purpose) and I think it's still throwing errors for them, thousands of them!
Comment #12
rogerbI think this issue is being over-thought. As Joel says above, some nodes have UUIDs and other don't. Only nodes with UUIDS are candidates for export, so only those nodes should be listed.
Comment #13
danielb commented