I cold not find any order in which to enable the workflow-ng modules that wouldn't break with an error that the cclinks_admin_menu was not found, until I disabled the logic at lines 10 and 12 of cclinks.module that conditionally load the admin ui, if workflow-ng admin ui is enabled. Is this a new problem or did I do something wrong?

Comments

stephthegeek’s picture

I had the same issue:

Fatal error: Call to undefined function: cclinks_admin_menu() in example.com/html/sites/default/modules/workflow_ng/cclinks/cclinks.module on line 35

fago’s picture

Category: support » bug
Status: Active » Fixed

yep, I think on module activation the code failed. I've improved it. -> 5.x-dev

shawn conn’s picture

I don't think the latest development branch fixes this problem. As Steve initially mentioned, removing the conditional around the include on lines 10 & 12 fixes the problem.

<?php
//if (module_exists('workflow_ng_ui')) {
    include_once(...);
//}
?>

I had to do this to get our ubercart installer working with installing workflow-ng along with Ubercart. Is there a reason for implementing the check? It seems like the everything works even without the check.

fago’s picture

I've just tested again with the 1.1 release and it is working fine. Did you have problems with the new code?

If workflow-ng-ui isn't active the CCL admin menu doesn't make much sense alone. So if people decide to disable workflow-ng-ui to save the time, which is needed to parse the code each page load, the time for the CCL admin menu can also be saved. That's the motiviation: don't unnecessarily include php files.

fago’s picture

You are right, I managed to get the error again. I've committed a new fix to 5.x-dev. This time it should do it.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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