This is probably related to #310873: D6 Upgrade path broken when CCK modules are disabled.

I'm trying to upgrade from Drupal 5.10 CCK 1.9 to Drupal 6.4 CCK 2.x dev.

  • Drupal Core upgrade: OK
  • CCK Content upgrade: OK
  • CCK Fieldset upgrade: OK
  • CCK Number upgrade: OK
  • CCK Text upgrade: OK
  • CCK Option Widgets upgrade: Fails

After enabling CCK Option Widgets I go to update.php as per usual. The upgrade script runs and throws no error.

  1. From the upgrade page I try to return to /?q=admin, get a Page not found.
  2. At /?q=admin/build/modules I get the modules list, but none of my enabled modules are checked.
  3. The sidebars on the modules page are missing. (Elsewhere on the site I still have them.)
  4. The Admin Menu module no longer loads.
  5. The whole site is excruciatingly slow.
  6. No errors or warnings in the logs.

Disabling the Option Widgets module in itself does not solve the problem. I get my modules page back only when I disable Content as well.

I've run the upgrade 3 times: twice with RC8 and once with 2.x.dev, with the same sad results.

Comments

Anonymous’s picture

Title: Malfunctioning modules page after Option Widgets upgrade from 1.9 to 2.x.dev » Malfunctioning modules page on Windows XP after upgrade from 1.9 to 2.x.dev

Today I tried every non-broken release candidate as well as 2.0 beta - all produce the same symptoms. I'd been working on Windows XP all along.

Then I exported the D5 site, ran the upgrade on Ubuntu Linux and everything went smoothly.

When I reimported the upgraded database under Windows, I got my CCK fields working properly, but the same problem again with the modules page, missing sidebars, etc. Disabling CCK completely solves these issues. D6 works perfectly by itself.

My Windows installation:

  • Windows XP SP2
  • Apache 2
  • PHP 5.2.6
  • MySQL 5.0.5

I'll upgrade my PHP/MySQL tomorrow to see which element of my setup has the bug.

Anonymous’s picture

I've updated my system to the latest stable versions:

  • Apache 2.2.9
  • PHP 5.2.6
  • MySQL 5.0.67

The problem persists. I'm reluctant to upgrade this ticket to critical until someone else confirms the issue, please test if you have access to a Windows machine.

KarenS’s picture

Status: Active » Postponed (maintainer needs more info)

What other CCK modules are in your modules folder besides the core modules? If you have other modules in that folder and they are broken they can screw up your update even if you don't have them enabled.

You'll note that I've updated the update instructions on the project page to recommend that you do your D6 upgrade without any contrib modules in your modules folder and get that much working, then add only the core CCK files to the folder, enable them, and run update. And only after that add other CCK modules to the folder. This process will help prevent broken modules from interfering with the CCK update and should also make it easier to see exactly which module is creating a problem if there is a problem.

Updating optionwidgets by itself is not creating problems for anyone, at least no one has reported it, so I think it's likely that some other module is the real source of the problem. I've run updates in Windows and have not seen this at all.

Another possibility is that this is actually a theme problem -- what theme are you using for your administration theme? Try resetting that option to use Garland as the admin theme.

Anonymous’s picture

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

Thanks for your reply. Actually I've moved away from the upgrade idea and now I suspect this has something to do with Windows/PHP. I followed your instructions during the upgrade and anyways, the same site (same file system, same database content) is working perfectly on Linux.

Someone on drupal.hu reported having a working RC8 on Windows XP and PHP 5.2.4. I've downgraded my PHP and still get the malformed modules page, so probably something's wrong with my installation. (Interestingly, on the same install the Drupal 5 version of the site works without problem.)

I'm closing this issue now as there's nothing that you can do to help me at this point. Thanks again.