Warning: Invalid argument supplied for foreach() in LimesurveySyncInfosToken->schema_ls_fields_variables() (line 343 of limesurvey_sync/api/limesurvey_sync_token.class.inc).

In case it is part of the same problem, when trying to sync tokens from Limesurvey to Drupal I get this error messsage, as well:

EntityFieldQueryException: Unknown field: field_ls_token_994774 in EntityFieldQuery->addFieldCondition() (line 817 of /srv/bindings/f4fb368aebef4687999a8e4eaac56f2e/code/includes/entity.inc).

Thanks.

I think that part of the problem may be this:

protected function entity_property_info_ls_fields_known($field, $sid) {
    return FALSE;
  }

that is defined and then called in limesurvey_sync_api.class.inc

It looks as though it will always return false, although I'm not a developer and might be missing something.

Hi,

Any chance you could take a look at this?
thi
Although not a developer, I'm trying to get up to speed enough to understand your code but it's slow going.

How are you handling / planning to handle custom attributes added to limesurvey tokens? Would it make sense to use bundles and have the attributes as fields on the bundles?

I realize that you have other priorities, but is there any chance you could take a look at this?

Thanks.

I am no longer getting the original errors mentioned above. I think that they were caused by enabling tokens after adding the survey or because some of the survey parameters weren't set correctly. Since then, I have uninstalled and reinstalled the module.

However, I still get:
Warning: Invalid argument supplied for foreach() in LimesurveySyncInfosToken->schema_ls_fields_variables() (line 343 of /srv/bindings/f4fb368aebef4687999a8e4eaac56f2e/code/sites/all/modules/limesurvey_sync/api/limesurvey_sync_token.class.inc).

This seems to come from:

$attributedescriptions = $this_survey['attributedescriptions'];
    $fields = array();
    foreach ($attributedescriptions as $attribute_field => $datas) {
      $fields[$attribute_field] = $attribute;
      $fields[$attribute_field]['description'] = $datas['description'];
    }

    return (isset($fields[$field])) ? $fields[$field] : FALSE;

Any idea what is going wrong here?

Thanks.

Might the message, however, have something to do with whether token attributes in Limesurvey are available in Drupal?

Given the current state of version 2.x, might it make sense, when you have time to go back to it, to have a dependency on ECK and take advantage of the functionality it gives for exposing entities and using them in rules and views?