Notice about "no parsers / processors defined for this content type" on content types with FeedAPI disabled

I'm not sure if this will be taken care of by the patch for #348780, but here is the problem:

After enabling FeedAPI, when saving changes to a content type, the feedapi_settings_$contenttype variable is saved. When no parser and/or processor is enabled for the content type it displays the error about one needing to be enabled for the content type. This error should only be displayed if the content type actually has FeedAPI enabled for it.

I have a patch coming to fix displaying the error when FeedAPI isn't enabled for the content type.