By ShutterFreak on

Apparently Drupal 6.3 features a new way of retrieving module information. As a result, some contributed modules seem to break loading the admin/build/modules page (you are served a blank page).

I manually disabled ALL contributed modules via database access. Fortunately I install non-core modules in sites/all/modules hence the following query did the job:

UPDATE `system` SET `status` = '0' WHERE `filename` LIKE 'sites/all/%';

After this I manually reenabled modules one by one. So far I succeeded in accessing admin/build/modules after enabling the following contributed modules:

  • Advanced help (6.x-1.0)
  • Diff (6.x-2.0)
  • Google Analytics (6.x-1.2)
  • IMCE (6.x-1.0)
  • Mollom (6.x-1.2)
  • Poormanscron (6.x-1.0)
  • Views, Views exporter, Views UI (6.x-2.0-rc1)

However if I try to enable one of the following modules I am presented a blank page whenever I try to access admin/build/modules:

  • FCKeditor (6.x-1.3-beta)
  • Taxonomy Browser (6.x-1.3)
  • Taxonomy CSV import (6.x-1.5)
  • Taxonomy Manager (6.x-1.x-dev)
  • Term Relation Types (6.x-1.x-dev)
  • TinyMCE (6.x-1.1-dev)

Are there others that can confirm these findings? If so, should I file a bug report for each of the contributed modules in the 2nd bullet list posted above?

Regards,
Olivier

⋅ Categories: Drupal 6.x

Comments

ShutterFreak’s picture

ShutterFreak commented

I enabled PHP error output, and as a result I now see the reason why I could not load "admin/build/modules" once one of these modules is enabled: I have insufficient memory for PHP. Unfortunately I have to live with the 16MB boundary offered by my ISP.

The only thing I can do is manually enabling/disabling modules via a database query. Unfortunately this does not work when I have to upgrade a module to a newer version.

It would be great if an admin interface "for memory challenged sites" were available.

if and a’s picture

if and a commented

Hi,
I have the same problem. Requesting /admin/build/modules get an memory leak error. It appears after upgrade to v6.4. Maybe there are many modules but how can I fix it when I can not access modules page?

Is it a bug? 32mb memory would by enough but it wouldn't

mattyoung’s picture

mattyoung commented

I ran into this problem and had no idea what was wrong. Then I discover this page and learn this is a well known problem:

http://drupal.org/node/158043, visit this page to read up all about why the problem occur and how to fix them.

My problem came about because of inter-module incompatibility (calendar, cck, date and views all depend on each other having exactly the right versions and three days ago, they must all be dev). Luckily I saved my db before. The lesson I learned is be very careful when installing any new module or theme. Backing up db is a must.

BTW, how do you enable PHP logging and where to view the output?