When running 'Drush si', I get the following error.

Plugin environment_indicator_ctools_export_ui of plugin type ctools:export_ui points to nonexistent file [notice]
sites/all/modules/contrib/environment_indicator/plugins/export_ui/ctools_export_ui_environment_indicator.class.php for class handler handler.

Looks to me like the ctools plugin in environment_indicator_ctools_export_ui.inc is looking in the wrong place.

Is:

'handler' => array(
    'class' => 'ctools_export_ui_environment_indicator',

should be:

'handler' => array(
    'class' => '../ctools_export_ui_environment_indicator',
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Michael Hofmockel’s picture

Status: Active » Needs review
FileSize
471 bytes

patch moving location relatively up one directory

amanire’s picture

Version: 7.x-2.0 » 7.x-2.x-dev
FileSize
602 bytes

Looks good. I had an issue applying the patch though. Looks like it was done against two different file names. I rerolled the patch in #1 against the latest commit on 7.x-2.x-dev.

marcoscano’s picture

adding ../ to the class file name solves the problem for me also

amanire’s picture

Status: Needs review » Reviewed & tested by the community

I'm going to go out on a limb since this is such a simple bug fix. This should really be committed.

devjrb’s picture

Not works for me. It's necessary to install Ctools? In the readme.txt it say "None" (requirements).

amanire’s picture

The README.txt is wrong. Ctools is a dependency in the .info file.

e0ipso’s picture

Status: Reviewed & tested by the community » Fixed

AFAIK the 'class' key is a class name, not a path.

I fixed this with: http://drupalcode.org/project/environment_indicator.git/commit/c263b44

Thank you for your contribution!

Committed.

amanire’s picture

Doh, that makes perfect sense, e0ipso. Thanks!

Status: Fixed » Closed (fixed)

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

sokrplare’s picture

Issue summary: View changes

I've seen all four folks on our team consistently run into this about once every two weeks. Seems like a dependency loading error issue. The patch in #2 fixed things for me but this is hard to recreate so will try it again whenever it re-occurs.

dodozhang21’s picture

Added another patch due to the filename change.

dodozhang21’s picture

Fixed the path. Please disregard the previous file.