Contrib Toggle cannot handle module display names that include parentheses

More detail would be helpful. What version of Drupal are you running, and yes, list those contrib modules. What Admin theme are you using? Also your browser version, whether you have javascript turned on, etc. Given you say that you are not able to disable or enable any other modules in the list, what actually IS shown on the modules page? Are the checkboxes greyed out, or do they appear to be selecting but clicking on them does nothing, or does clicking on them change the tick but when you save the configuration it does nothing? Finally, you can disable the Contrib Toggle module by removing it from your sites/modules page. Does this fix the problems you are experiencing?

This could be most helpful. I'll try to replicate your setup and see if I can also replicate your bug.

I have a simular issue with the contrib module, but I'm not sure if it is related to this one.

In Firefox 3.5.7 the Contrib-module is working fine, but in Opera 10.10 the module does not work properly:
- There is a bug when I try to disable a module where other enabled modules depends on. There should a window appear where you can confirm to disable the depended as well, but this window is not appearing. I believe it appears outside the browser window, because I once saw the top of the window on the bottom of the module-page.

In both Firefox and Opera I also discover this problem on a Drupal-site with many modules enabled:
- When clicking on 'Disable Contrib' only the modules of the Administration-section are disabled (Administration Menu & Contrib Toggle). This should be a conflict with an other module, because this problem does not occur on an other Drupal site with less modules enabled. I'll check later with enabling and disabling modules which module might conflict.

same issue

Apologies for the insanely slow response on this. My current theory is that Contrib Toggle's code may be choking on any module names that contain parentheses in them—e.g. GetID3 which lists itself as GetID3()—and those which list dependencies on the same. Filefield Meta is dependent on GetID3(). Although you are not using Filefield Meta psmith it is installed as part of Filefield and so the GetID3() is being parsed in the dependencies. I think Contrib Toggle may be stopping building it's dependencies list at that point or missing some critical data etc and thus failing... sometimes rather nastily.

OK, having looked into this a bit further it appears that a number of current bug reports may all be pointing to the same issue—that Contrib Toggle cannot handle module display names that include parentheses, including if they are listed in the dependencies of inactive modules—e.g. FileField Meta's dependency on GetID3(). This can result in critical modules being disabled if you save the module configuration page, which results in a WSOD and the need to manually re-enable these modules in your database before your site will work correctly—pretty horrible.

Have marked the following issues as duplicates:
#508222: All contrib disabled on upgrade to 6.13 when Contrib Toggle installed but *not* actively used
#509046: Fatal error with imagefield module
#556924: Conflict with Filefield Meta (6.x-3.1) and Audio GetID3 (6.x-1.0-unstable4) modules
#732152: White Screen o' Death upon Disable Toggle

I will try and work on this. However, it highlights a pretty fundamental vulnerability in the underlying way in which Contrib Toggle works vs. Drupal's expectations about required modules, which is why if Contrib Toggle fails you can end up with modules disabled. It may not be possible to fix this in D6 due to the nature of the core codebase.

I've decided this is a bit bigger than just this issue. It highlights that the fundamental approach Contrib Toggle has taken is flawed in Drupal 6, as when Contrib Toggle fails to function correctly it leaves a Drupal installation open to the possibility of critical required modules then being deactivated when their dependencies are still activated.

This is unacceptable to me. I apologise for the major inconvenience this will have caused to users, and for the lack of foresight on my part to see the dangers inherent in the approach the module took. I have unpublished the current release of the module. Until these architectural issues can be addressed, I encourage all users of the module to disable it from their sites to avoid the issues outlined here.

I hope you'll be able to fix the issues soon, I really find the module helpfull.

MegaChriz: Perhaps there is a solution I have not hit upon, but at this stage I am not sure that it would be possible to resolve these issues in D6 (without hacking core) due to the way Drupal 6 manages modules with active dependencies... The parentheses issue merely highlighted the more fundamental flaw in how Contrib Toggle was working—which worked fine, most of the time, but if it didn't, it was pretty spectacularly bad. Thanks for your encouragement, however.

Maybe I can help you with Contrib Toggle in the future, I've bought a book for Drupal module development a few weeks ago, so I'm now studying how Drupal technical works. I have a good knowlegde of PHP and a average knowledge of javascript.

+1
Subscribe

Thank you very much for trying to resolve this issue an bringing this module back. I dread the day when I will have to update Drupal core without the help of the Contrib Toggle.
Thanks million for all your time.