Jump to:
| Project: | Node export |
| Version: | 6.x-2.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
originally raised in http://drupal.org/node/383688
The idea is for this module to be verbose about the effects of it's current settings.
My first thought is that if this module is behaving unexpectedly then we should attempt to make it behave more expectedly.
My belief is that there are some parts of the node which you should expect will be lost, such as the node id, and the user id, any relations to other nodes, users, books, menus, etc.. this seems pretty obvious to me, but from the looks of some of the bug reports I get - people seem to think otherwise.
There is also the possibility of doing more work to support at least some of those specific features - in which case the status quo would change.
There is also a challenge in how to implement something like this - perhaps as the operation progresses it updates some kind of data log to inform it of what content types have been affected and how many, which is then used to create the messages.
Comments
#1
I've not done a bulk import,so I'm not sure what to advise for that method.
For the single node import that leads you to a node edit page, a drupal_set_message at the top of that page would be nice and simple and would do the job perfectly. A form_alter to add or prepend to each reset form item's description text would be snazzy, but maybe less noticeable?
#2
I've added a message to remind people about the settings during an import, the processing to figure out exactly which settings need to be mentioned is too complicated, so I didn't mention any. If you can come up with a patch to be more explicit I'll consider it, but I don't really know if it's worth it.
#3
Automatically closed -- issue fixed for 2 weeks with no activity.