I've built a custom fetcher and parser (neither have configurable elements), created a new importer, and exported that to code.
Attempting to run the import (through the UI at /import/my_custom_importer) causes the error:
Fatal error on running import: "Unsupported operand types in /FeedsConfigurable.inc"
The import form creates a fieldset called "feeds" with #tree set to TRUE, then attempts to add in the importer's configuration. As there isn't any configuration, the values in the form submit handler include "tree" => NULLL. This results in invoking $source->addConfig(NULL), but config is always expected to be an array.
NB: there's a bunch of similar issues in the feeds queue which appear to be facing the same problem from different directions. I've found one approach to solve this, there may be an alternative, or more generic solution.
Similar issues:
- #625196: Fatal errors (Unsupported operand types) and warnings (Argument is not an array) in FeedsConfigurable
- #1013314: Cloning a feed is not possible due to Fatal error: Unsupported operand types in FeedsConfigurable.inc on line 116
- #1213472: " Fatal error: Unsupported operand types in /FeedsConfigurable.inc" when importing
- #1273622: Feeds error on node_save()
- #1406260: Fetchers without source configuration fails.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | feeds-1545264-fix_unsupported_operands.patch | 518 bytes | manarth |
Comments
Comment #1
manarth commentedPatch attached.
Comment #2
franzI think this logic should rather be implemented inside the addConfig() method.
Comment #3
rogarbe commentedThis patch work rightly for me.
Thank you manarth
Comment #4
joelpittetThis looks like it has been added already to the latest dev.
Comment #5
twistor commented