Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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',
Comments
Comment #1
Michael Hofmockel CreditAttribution: Michael Hofmockel commentedpatch moving location relatively up one directory
Comment #2
amanire CreditAttribution: amanire commentedLooks 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.
Comment #3
marcoscanoadding ../ to the class file name solves the problem for me also
Comment #4
amanire CreditAttribution: amanire commentedI'm going to go out on a limb since this is such a simple bug fix. This should really be committed.
Comment #5
devjrb CreditAttribution: devjrb commentedNot works for me. It's necessary to install Ctools? In the readme.txt it say "None" (requirements).
Comment #6
amanire CreditAttribution: amanire commentedThe README.txt is wrong. Ctools is a dependency in the .info file.
Comment #7
e0ipsoAFAIK 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.
Comment #8
amanire CreditAttribution: amanire commentedDoh, that makes perfect sense, e0ipso. Thanks!
Comment #10
sokrplare CreditAttribution: sokrplare commentedI'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.
Comment #11
dodozhang21 CreditAttribution: dodozhang21 as a volunteer and commentedAdded another patch due to the filename change.
Comment #12
dodozhang21 CreditAttribution: dodozhang21 as a volunteer and commentedFixed the path. Please disregard the previous file.