Hi, I have generated a valid (as determined by the w3c online validator) atom feed. Everything seems to import as expected and there are no errors/warnings.
(First, to debug I set the feeds_debug variable to TRUE in the settings.php, which I verified with drush:
~/Sites/d7$ drush vget feeds_debug
feeds_debug: TRUE
(I could not figure out how to set a boolean through drush -- always turned into a string) However, no debug output is being created. I do have devel installed and use dd() to write to drupal_debug.txt in the same tmp dir. The Feeds log under the admin Reports menu just provide the import count.)
I am able to successfully import all feed items using the standard/provided feed importer and a custom/new one setup similar to the feed importer. I see these items rendered properly (long list of all feed items and their content) when visiting the *Feed* content type instance's 'View Items' tab.
However, when I try to go to view or edit a *Feed Item* content type instance:
* I see the title, and it is editable
* I do not see the Description (field_feed_item_description) in either view or edit. In edit there is *no* Description (field_feed_item_description) field even displaying. However, when I go to the devel tab, I can drill into $object->field_feed_item_description['und'][0]['value'] and I can see the content (escaped so all tags are visible, not rendered in the browser). The Feed Item content type is set to display the Description with the 'Default' option selected.
Does there need to be a node--feed-item.tpl.php? It seems so, I created that file by copying node.tpl.php and added:
print $node->field_feed_item_description['und'][0]['value'];
to get the content to display. Is this what is be expected? In other words, why doesn't the content get dumped into a normal Body field or display at the feed item page?
I assume will have to override the edit view template for this so the content can be edited. Is that right?
Or what am I doing wrong?
Comments
Comment #1
RobKoberg commentedThis issue has something to do with Organic Groups' Organic groups field access module. When this module is enabled you cannot view or edit a node's body or other custom fields.
Comment #2
heathergaye commentedI'm having the same problem - looks like it's because the text format is not set for the description field when it's imported.
Comment #3
kash83 commentedI've got the same problem.
Its true, it seems that the text format will not be set (to FULL HTML for example).
Comment #4
megachrizI think this is no longer an issue. In the latest version of Feeds you can specify the text format to use either on the processor settings or on the target itself on the mappings page.