Upgrade from D5 ends with disabled nodewords module, but enabled submodules
hass - October 27, 2009 - 22:58
| Project: | Nodewords |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
See attached. Nodewords was disabled when running update.php. The problem could be Update #6136, that needs to verify if nodewords is already enabled before it enabled the submodules programmatically.
You can see in the screenshot that nodewords checkbox is disabled... Hopefully there is no data lost.
| Attachment | Size |
|---|---|
| nodewords_upgrade_from_D5.png | 13.25 KB |
#1
I think the submodules need to be kept disabled if the main module is disabled...
#2
The bad is that the checkbox for Nodewords has been disabled from Drupal core code, which notices there are modules that require nodewords.module. It would be better that the checkbox should be disabled only when it is checked.
I fixed the code, which now checks if the module is enabled; this needs to be done because the update functions are invoked even when the relative module is disabled.
#3
Note: The module wasn't disabled by core, it was disabled by me for the reason that the core documentation suggest to disable all modules prior to a major version upgrade. Your fix should solve this! thx.
#4
I was referring to the checkbox under , which for Nodewords is not selectable; that means you cannot enable the module, which remains disabled.
I notice that there are two columns of checkboxes; which module do you have enabled? It could be of use for my site too.
#5
throttle
#6
Automatically closed -- issue fixed for 2 weeks with no activity.