I'm importing nodes with two different feeds (from the standalone form) into two separate content types. One of the fields has HTML in it, was creating were encoding the HTML.

I looked around in the DB at the field_data_body table, and found the probable culprit: the body_format column value for the new, problem nodes was NULL (rather than filtered_html, full_html, etc.) Upon manually editing the node ONCE and saving the node, the problem went away, and sure enough the body_format field was then properly populated.

The problem is across two different feeds pointing at two different content types, and when I was using alpha5 this problem didn't exist (it started when I upgraded to alpha6).

I tried changing the input filter on the nodes (and the field), in the feed's Node Processor settings, etc. and repulling the nodes each time - no dice. The HTML is properly storing in the field_data_body table, and doesn't vary between alpha5 and alpha6 imported nodes (not encoded, etc.).

Note: I don't think this is directly related because this only happens with one of the two feeds, but there is also a notice appearing in the Drupal log with the 2nd feed: Notice: Undefined index: value in entity_metadata_field_property_get() (line 406 of /home/mine/domains/mydomain.com/public_html/sites/all/modules/entity/modules/callbacks.inc). Both content types have a Term Reference field. This also didn't occur with alpha5.

Comments

ErnestoJaboneta’s picture

Regarding the Undefined Index notice, I had the same notice coming up today for each feed item. I updated to the latest dev and the notice went away.

lyricnz’s picture

Status: Active » Closed (duplicate)
aubjr_drupal’s picture

Thanks for the update, and sorry about the dupe.

aubjr_drupal’s picture

Issue summary: View changes

Quick formatting change to HTML.