An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /batch?id=29&op=do StatusText: OK ResponseText: Fatal error: Cannot access empty property in /www/htdocs/a-drupal7-testspace/sites/all/modules/feeds/plugins/FeedsProcessor.inc on line 506

Seems to stay in connection with the following function in the FeedsProcessor.inc 

  public function setTargetElement(FeedsSource $source, $target_item, $target_element, $value) {
    switch ($target_element) {
      case 'url':
      case 'guid':
        $target_item->feeds_item->$target_element = $value;
        break;
      default:
        $target_item->$target_element = $value;
        break;
    }
  }

I've created a custom import with csv parser and the "use standalone form" and "file upload" options with mapping customfields (d7 fields, not CCK). I mapped wordpress post ID to Node ID and set it as unique. I left GUID without any mapping. Maybe this causes the issue, but it needs clearifying advices and maybe some more code to avoid it.

thanks for this great tool! hope it will work soon for me.

Comments

dqd’s picture

dqd
Location London | N.Y.C | Paris | Hamburg | Berlin
commented

Found the reason: It is one of the things never can be expected from the developers side before it happens. In certain cercumstances an unwanted browserrefresh can cause a set up of an undefinded field entry in the mapping queue. I only saw it by carefully looking on my mapping twice. There was a field defined like this: "Select a source" was the name of the source field and "choose a target" (or something) was the other one. Exactly like the selector below. Meaning that the description of the selector is shown in a new mapped entry. You can reproduce this by pressing "add" without selecting anything. After all, this is what causes the error and will interrupt the import.

Hope it helps. Best regards

bonjourmr’s picture

bonjourmr commented
Component: Code » Feeds Import

This fixed my issues, didn't even notice it. Thanks

dqd’s picture

dqd
Location London | N.Y.C | Paris | Hamburg | Berlin
commented
Status: Active » Fixed

you're welcome.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

flak’s picture

flak commented

Make sure you always have every field mapped on both sides (source/target) with real fields in your CSV/SQL and in your Content Type. Never leave "choose target" in a mapping. And, make sure that you pick a unique content type for one of the fields, go with GUID if you don't have one.