serialized settings array ignored when building node edit form for some feedapi enabled nodes

When there are no processor-specific settings or no parser-specific settings for a feed-enabled node, all the other previously saved settings for an existing feedapi node are ignored when building the node form for editing that feed.

This forces the code to default to the values for the other settings from the serialized array to the defaults configured for the node's node-type at admin/content/node-types/[node-type]

In my case, I was saving a feedapi-enabled node to refresh as frequently as possible and to delete items after a year. I noticed that these settings would get properly saved to the database, but that the default values on the edit form for the created feed would be set to the default values for the node-type rather than the values already stored in the database for this particular node.

I simply deleted the lines in the hook_form_alter() where the settings are ignored if the settings array does not include 'processor' and 'parser' keys. I'm not quite sure if this will break anything else, but I know that it is possible for a feed not to have any processor-specific or parser-specific settings if the parser and processor have been implemented as such.

-Ankur

-Ankur

-Ankur