OS: Mac OS X 10.4.8
Upgraded from Drupal 5.0 to Drupal 5.1

Configuration file Protected
Cron maintenance tasks Last run 6 days 17 hours ago
You can run cron manually.
Database schema Up to date
File system Writable (public download method)
GD library bundled (2.0.28 compatible)
MySQL database 5.0.27
PHP 5.2.0
Unicode library PHP Mbstring Extension
Web server Apache/1.3.33 (Darwin) PHP/5.2.0

After upgrading from 5.0 to 5.1 - the contrib modules I downloaded (and the ones I am maintaining : ldapauth, ldapgroups ) did not appear in the "Site Configuration". They were enabled in the "Site Building" module listing section.

All it took was a disable and enabling of those modules for them to start showing up in Site Configuration.

What could cause this behavior ? As a module developer, what precautions should I be taking so that as we upgrades, these things don't happen ? I am pretty sure I am doing something wrong in my module (but so are a bunch of others !)

kreaper

Comments

kaerast’s picture

kaerast CreditAttribution: kaerast commented
Status: Active » Postponed (maintainer needs more info)

How exactly did you upgrade? Specifically, did you move the directory you are running Drupal from? Did you change the database name?

I know that moving the installation directory whilst upgrading has in the past caused theme issues, it may be to blame here.

kreaper’s picture

kreaper CreditAttribution: kreaper commented

this is what I did.

a) untarred drupal5.1 into a new directory
b) created sites/all/modules/
c) copied my contrib modules to this dir
d) copied the settings.php

ScoutBaker’s picture

ScoutBaker CreditAttribution: ScoutBaker commented

After one year, today, is this still an issue that needs to be open? Did it reoccur with any subsequent installs/upgrades?

Thanks.

ScoutBaker’s picture

ScoutBaker CreditAttribution: ScoutBaker commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Please change the status if there is still work to do on this issue. Thanks.