Empty module list
tom120934 - March 16, 2006 - 14:16
Hi,
I just discovered Drupal and installed it.
I have an empty modules list. I've seen the entry about it in the Troubleshooting FAQ, but it didn't work to change PHP memory limit (neither in php.ini nor in .htaccess nor in settings.php). Didn't found any trick to fix it in the forum, so I ask for help here.
I've given a try to it using both 4.6.6 and 4.7.0-beta6. None worked (fresh install, no other problems than that). In addition, I've tried to insert a record in the system table in database, and it worked : I can activate module this way (example : blog), but it still doesn't appear on the module list.
Any idea ? Thanks by advance :)
Cheers,
Tom
Exactly the the same problem
Exactly the the same problem accoured suddenly at one of my D5 sites (Drupal 5.15).
The memory limit im php.ini before was set to 80M; I increased it in steps to 128M and am running currently 256M without any change - this is not a memory problem.
Currently available modules:
* Content management
** Content
** Content types
** Post settings
** RSS publishing
* Site building
** Blocks
** Modules
** Themes
* User management
** Access control
** Access rules
** Roles
** Users
** User settings
* Logs
** Recent log entries
** Top 'access denied' errors
** Top 'page not found' errors
** Status report
* Site configuration
** Administration theme
** Clean URLs
** Date and time
** Error reporting
** File system
** Image toolkit
** Input formats
** Performance
** Site information
** Site maintenance
All other modules are listed to "Uninstall" at /admin/build/modules/uninstall, even if none of them was disabled.
No need to say that the site is completely broken.
Any ideas or suggestions?
Greetings, -asb
--
Drupal playgrounds: www.kefk.org | www.cinedat.org | www.fotonexus.org | www.encycan.de | www.encymus.de
=-=
If the page is completely blank you have an apache error of some sort and without knowing what that error is it's hard to help. Check your apache error logs for an error being thrown when you visit that screen
it may help to check drupal's error logs as well.
What you link to above is the admin screen and doesn't necessarily suggest what modules are uninstalled or removed, thus that information doesn't help much.
The page isn't "completely
The page isn't "completely blank" (= no WSOD), it simply doesn't list all modules installed at /var/www/drupal/sites/all/modules at my server.
I'm not using Apache but Lighttpdy; it is configured to create an error.log, but it doesn't log any errors for this site. Also, the same daemon is runing several other Drupal sites (D5 & D6) on the same machine which do work fine so far (*knock on wood*). The other sites do run from a differentcodebase, but are configured similarily. This most probably isn't a webserver issue.
Drupal error logs? If you mean watchdog at /admin/logs/watchdog: It doesn't log anything but tons of "page not found". No wonder, since most of the crucial modules are not "available" anymore.
Greetings, -asb
--
Drupal playgrounds: www.kefk.org | www.cinedat.org | www.fotonexus.org | www.encycan.de | www.encymus.de
=-=
paging through the page not founds to the last time the site worked correctly could lead to some helpful information.
There's not much else logged
There's not much else logged in the recent hours; once per hour cron is running, the rest is "page not found". BTW, a Mediawiki installation installed in parallel to Drupal (running from /wiki/ wubdirectory still runs fine; so the webserver, php, and mysql should be fine).
Before I first noticed the problem, I did an update_status repeatedly (via drush pm refresh ; drush pm update ; and update status in the web interface, which is gone now).
Around this thime, several PHP errors are logged (nothing unusual in Drupal):
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'IS NOT '0') ) ORDER BY node_comment_statistics_last_comment_timestamp DESC LI' at line 1 query: SELECT DISTINCT(node.nid), node.type AS node_type, node.title AS node_title, node.changed AS node_changed, users.name AS users_name, users.uid AS users_uid, node_comment_statistics.comment_count AS node_comment_statistics_comment_count, node_comment_statistics.last_comment_timestamp AS node_comment_statistics_last_comment_timestamp, flag_ops_produktdaten.ops AS flag_ops_produktdaten_ops FROM node node INNER JOIN users users ON node.uid = users.uid LEFT JOIN node_comment_statistics node_comment_statistics ON node.nid = node_comment_statistics.nid INNER JOIN node_access na ON na.nid = node.nid WHERE (na.grant_view >= 1 AND ((na.gid = 0 AND na.realm = 'all'))) AND ( (node.status = '1') AND (.uid IS NOT '0') ) ORDER BY node_comment_statistics_last_comment_timestamp DESC LIMIT 0, 25 in /var/www/drupal/includes/database.mysql.inc on line 174.That might already be caused by the vanished modules.
Nothing else relevant seems to be logged in watchdog; before that, the log lists the usual notices and warnings. In this case, my memory serves better the logfiles.
Last steps before losing the site:
* Updated modules list from the shell (drush pm refresh)
* Checked for updated module versions from the shell (drush pm update)
* installed the modules themesettingsapi and themesettings from the shell (drush pm install themesettings ...)
* Disabled the "Read more tweak" module from the admin interface
* Activated the "Themesettingsapi" and "Themesettings" modules from the admin interface, and configured both modules
I already tried to move both new modules out of sites/all/modules - the only change in configuration I made -, but that had no effect. Also, on my other sites, those modules did not cause similar problems.
Noteworthy might be that /admin/logs/status logs errors since yesterday; from one of my other sites running Drupal 5.15:
Module update status: Unsupported releaseThe installed version of at least one of your modules or themes is no longer supported. Upgrading or disabling is strongly recommended! Please see the project homepage for more details. See the available updates page for more information.
According to /admin/logs/updates, the following modules are "Not supported" anymore (last checked 8 hours ago, rechecked just now):
* Atom 5.x-1.1, http://drupal.org/project/atom
* Similar Entries 5.x-2.0, http://drupal.org/project/similar
Indeed, both modules don't list any release "Recommended for 5.x" anymore. That is new, but I doubt that it causes one D5 site to break and does no harm to four other D5 sites, runnin the same modules.
Since "Similar Entries" is embedded in my customized "Slash" theme, I'm getting errors like the following, even when accessing pages or stories:
Fatal error: Call to undefined function content_format() in /var/www/drupal/sites/all/themes/slash/node-seite.tpl.php on line 9I changed my theme the the default "Garland" which gives me back those content types (with unformatted content, since the PEAR Wiki filter is gone with the rest of the modules).
But now I'm getting somewhere: /admin/build/modules is populated with disabled modules!
(clicking...)
OK, now I'm getting the site back online (with "Garland"). Switching back to "Slash" seems to work, but the modules list at /admin/build/modules is empty again.
Very strange...
Greetings, -asb
--
Drupal playgrounds: www.kefk.org | www.cinedat.org | www.fotonexus.org | www.encycan.de | www.encymus.de