Whenever I enable the three modules, I get following errors:

* The plugin definition of context cannot locate schema context.
* warning: Invalid argument supplied for foreach() in /home2/danstang/public_html/sites/all/modules/ctools/plugins/export_ui/ctools_export_ui.class.php on line 54.

The error regarding ctools is reported here: http://drupal.org/node/865738#comment-3459454

The modules seem to be enabled/ checked here '{domain}/admin/build/modules', but no new configuration forms nor menu items related to this module appear.

Running ctools-6.x-1.7. and jquery_ui-6.x-1.3.

Comments

not_Dries_Buytaert’s picture

not_Dries_Buytaert commented

After this error I can uninstall only the "Context" module (not the "Context layouts" nor "Context UI" module). Based on the file "context.install" I think that is by design, though.

sebastian.klinge’s picture

sebastian.klinge commented

I had the same problem, it went away when I installed the latest 6.x-dev versions of CTools and Context, though.

Anonymous’s picture

Anonymous (not verified) commented

I was able to fix this with out using the dev versions by disabling and uninstalling the ctools and contexts modules, then enabling ctools before enabling contexts. I got the error by checking contexts to enable it, and letting it automatically enable ctools.

not_Dries_Buytaert’s picture

not_Dries_Buytaert commented

I followed the suggestion in post #3 (and also enabled the submodules Context layouts and Context UI). The errors didn't occur then. :-) I couldn't find anything wrong with the 'context.info' file, but it is better if someone else would check this.
BTW: this (perhaps related?) issue does occur, though: http://drupal.org/node/921088

GodsBoss’s picture

GodsBoss commented

In addition to #3, this is what I did:

1. activated CTools 1.7
2. activated Context (but not UI or layouts)
3. activated Context UI, got the same error as above
4. deactivated Context UI
5. deactivated Context
6. activated Context
7. activated Context UI, no error and UI is accessible (didn't test functionality)

Some other modules, although very common, are installed and enabled as well: CCK, Views, Token, Pathauto.

No custom modules. Install is relatively fresh, without even content.

jamestombs’s picture

jamestombs commented

Had the same error come up with CTools-6.x-1.x-dev already enabled.

Checked all 3 Context modules together, got the error.

Disabled all 3 modules.

Enabled seperately, no error.

videographics’s picture

videographics commented

Suggestion #5 worked for me.

BlackCatWeb’s picture

BlackCatWeb commented

I got this error, too, but was able to solve it in even fewer steps:

1) disable Context UI, then "Save Configuration"
2) enable Context UI, then "Save Configuration"

This implies that things install out of order when both modules are enabled, which is weird, since Drupal recognizes the Context UI's dependency on Context.

Just curious- was anyone upgrading an existing module? I had upgraded Chaos (ctools) from the previous version (went from 6.x.1.7 -> 6.x.1.8) simultaneously as I installed Context and Context UI. That's not by "by the book", since you're supposed to run "update.php" after upgrading. In this case, though, update.php didn't have any updates to apply when I ran it after these steps. All odd.

As If’s picture

As If commented

You're right. It seems Context UI is depending on Context being fully installed *first*. That's all I needed to do to make the error message go away. And no, btw, I wasn't upgrading anything else.

echoz’s picture

echoz commented

subscribe

Rob_Feature’s picture

Rob_Feature commented

Had this problem also using an install profile. Even though context_ui is set to install after context (and after ctools) I still get this error when the install process is complete.

jim0203’s picture

jim0203 commented

Subscribe: my experience of enabling context.module and context_ui.module is as per #9

steven jones’s picture

steven jones commented
Status: Active » Postponed (maintainer needs more info)

Does this error persist after appearing, or does it go away with refreshing the page?

jamestombs’s picture

jamestombs commented

Goes away.

steven jones’s picture

steven jones commented
Version: 6.x-3.0 » 6.x-3.x-dev
Component: Code » Documentation
Category: bug » task
Priority: Critical » Normal
Status: Postponed (maintainer needs more info) » Active

I'm fairly sure then, that this is because Drupal 6 can't enable modules in the correct order of dependencies. If the issue doesn't actually cause anything other than an unfriendly message, then it's just an issue of documentation, so that people know to expect it.

leopinzon’s picture

leopinzon commented

Comment #8 Worked awesome and much simpler.

micnap’s picture

micnap commented

#8 worked for me too.

Thanks!
Mickey

akanik’s picture

akanik commented

Yeah, it seems that enabling things in the correct order will sometimes fix the error. Something good to keep in mind for other similar issues. Thanks guys!

kip stanning’s picture

kip stanning commented

followed advice in #5 in parts by just disabling context and context_ui and then enabling first context and in a separate step context_ui. after that context worked! thx @godsboss (whose boss?) --regards, karl