Since there are no warnings on the content type edit page regarding changing the machine name, feeds should react to this change by updating relevant feeds so they don't break.

Obviously this is minor, but I couldn't find any posts about it and someone may get stuck. My solution was to change the machine name back to the original name and refresh the feed edit page.

CommentFileSizeAuthor
#1 1764542-handle-missing-content-type.patch1.49 KBdgtlmoon
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dgtlmoon’s picture

dgtlmoon CreditAttribution: dgtlmoon commented
Priority: Minor » Normal
Status: Active » Needs review
FileSize
1764542-handle-missing-content-type.patch1.49 KB

yeah nice one, i see "Notice: Trying to get property of non-object in FeedsNodeProcessor->getMappingTargets() (line 284 of /var/www/feeds/drupal-7.16/sites/all/modules/feeds/plugins/FeedsNodeProcessor.inc)."

See supplied patch, alerts user if content type is missing

MegaChriz’s picture

MegaChriz CreditAttribution: MegaChriz at WebCoo commented
Issue summary: View changes
Status: Needs review » Closed (duplicate)

This has been fixed as part of #1166100: Notices and warnings on mapping page, when no content type is selected for NodeProcessor. See also the commit.