Import of a context export fails

I'm not getting an error message, but I am getting nothing imported. I've tried in 3.x-dev, beta4 and beta5

Here's a simple export that isn't working:

$context = new stdClass;
  $context->disabled = FALSE; /* Edit this to true to make a default context disabled initially */
  $context->api_version = 3;
  $context->name = 'admins_home';
  $context->description = '';
  $context->tag = 'Home';
  $context->conditions = array(
    'user' => array(
      'values' => array(
        'Chapter Admin' => 'Chapter Admin',
        'Super Admin' => 'Super Admin',
        'TRA Admin' => 'TRA Admin',
      ),
    ),
  );
  $context->reactions = array(
    'block' => array(
      'blocks' => array(
        'user-1' => array(
          'module' => 'user',
          'delta' => 1,
          'region' => 'sidebar_first',
          'weight' => 0,
        ),
      ),
    ),
  );
  $context->condition_mode = 0;

  $translatables['admins_home'] = array(
    t('Home'),
  );

What version of ctools are you using?

this was with 1.4

I'm having the same issue: multisite installation with 2 databases on the same core and modules, created a feature in the first with a context, tried to enable the feature on the second, and the context won't import. (Also says the feature is overridden, I try drush features-update on it and it removes the context.) Tried to import the context manually and got the errors described above.
CTools 6.x-1.4, Context 6.x-3.0-beta5 (Context and UI enabled, Context Layout not enabled), Features 6.x-3.0-beta4.

The common.inc errors are caused by a syntax error in context_ui.admin.inc, patch attached. It's trying to drupal_set_message "An error occurred while importing. Please check your context definition." but the syntax error with t() caused the intermediate message.
This doesn't solve the problem, just allows it to be accurately debugged.

The bug is in the import code. eval() creates each variable/object defined in the string, so $context in the eval string will become an object, but $context = eval($import); where $context is set inside $import means the outer $context will override the imported/eval'd one.
This patch fixed both the issue in the previous comment and the larger one, and contexts seem to be importing now.

The patch from #6 works for me in the regular context import. Reverting contexts from features still does not work, however, but perhaps this is a separate issue.

I would make sure you all are using the latest stable releases of each of these modules, re-create your contexts, and then update your feature.

I am and I have. Reverting contexts from features just seems to have no effect

> Reverting contexts from features just seems to have no effect

Just to clarify, did you recreate the context and update the feature first?

Yes, that's right. So, for example, this afternoon I created a new context, exported it in a feature, and then deployed (copied and enabled) the feature to another server. On enabling the feature, the context was not created and shows as 'overridden.' Attempting to revert the context from within features has no effect -- there is a success message saying it has been reverted, but it still shows as overridden and does not appear in the contexts admin UI.

Turns out it was indeed a Features issue. Patch here fixes it: http://drupal.org/node/814414

I’ve tried the latest dev version of Features that includes the patch from #814414: Exported contexts are overridden and removed, but it does not appear to solve this issue.

The patch from #6, however, does solve the problem.

Thanks, committed: http://drupal.org/cvs?commit=379734