Undefined property: stdClass / line 775 of ctools/includes/export.inc

Hi--I updated to the Jul 12 dev version of ctools yesterday and got the same error. I went back to the previous version and still had it although it wasn't there before I updated. I did clear all the caches several times. I would be most happy to provide any information that would help resolve this.

It shows up on the system Node template in panels as well as the custom templates I have built. Thanks.

This might mean that a module updated its schema, but somehow the database isn't in sync with it. Be sure to hit update.php and clear caches? DOes that change anything?

I had run update.php but I went ahead and redid it. It said no pending updates. I cleared the cache a couple more times and now the error is gone. I guess I need to be a bit more patient before posting...thanks so much!

It is frustrating to me that the way caches get built, it can take multiple cache clears. I haven't been able to put myself into a situation where this is still needed, but many reports from the field indicate that it still is.

I was getting the same issue, but reporting for $options. It seems that in the loop in export.inc around line 775:

  foreach ($schema['fields'] as $field => $info) {
      $object->$field = empty($info['serialize']) ? $data->$field : unserialize($data->$field);
  }

That it's possible for the value of '$data->$field' to not be set, which yields an error: In this case, the field 'options' were not actually set.

I'm not sure if this is a correct solution, but it works as a hack, simply to check for the the field being set prior to the offending line 775 being executed. My adjusted code for export.inc now reads:

  foreach ($schema['fields'] as $field => $info) {
    if (isset($data->$field)) {
      $object->$field = empty($info['serialize']) ? $data->$field : unserialize($data->$field);
    }   
  }

Perhaps that's a bit too much of a shortcut hack, and means I've just stuck a plaster over some bigger problem that I don't understand....?

That hack fixes the notice, but it does not fix the schema/actual database being out of sync issue.

Active discussion on the issue happening over here #1209576: problems with ctools on update.php and login pages

When you are clearing your cache are you using Drush or are you using the Drupal admin>configuration>performance interface? I have been clearing cache like a mad man with both and I'm not getting the error to clear.