Now that #1733658: Inject a comment body text area and input format selector into the node edit form is committed, there's already a place you can put the comment body and input format selection into $node so that it'll be used when generating the comment for a given revision, namely $node->nodechanges_comment_body['value'] and $node->nodechanges_comment_body['format']. Therefore, I'd like to propose we rip out the support for $node->nodechanges_body and $node->nodechanges_format and teach the migration code that's relying on that to use the better-namespaced ones, instead.
However, this isn't blocking launch, so I'm not even tagging for Drupal.org D7. Just wanted to capture this into an issue so it doesn't get lost when I close #1733658.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 1819944-1.nodechanges.patch | 1.2 KB | dww |
| #1 | 1819944-1.project_issue.patch | 757 bytes | dww |
Comments
Comment #1
dwwNow that I know where the migrate code lives, I wanted to post a proof-of-concept for what I'm talking about here.
Comment #2
drummThe nodechanges patch looks good, but no longer applies. At least in the Drupal.org codebase, there are no references to "nodechanges_body" other than this.
Comment #3
drummCommitted, http://drupalcode.org/project/nodechanges.git/commit/5c29590