I am in the process of updating my site from 6x to 7x. The Upgrade Assistant module keeps hanging on the "Verify maintenance theme" section of the upgrade list. I have set the maintenance theme to every theme installed on my site. Has anyone else experienced this issue? Should I be doing more than just selecting the theme I want to use as a maintenance theme? I also selected the theme listed in the settings.php file which was minnelli and it still will not move to the next list item.

Comments

powery’s picture

powery commented

I have the same issue, any help for this?

doub1ejack’s picture

doub1ejack commented

Ditto.

jct’s picture

jct commented

I was able to get it to move on by temporarily removing non-core themes and saving settings on /admin/build/themes

ergophobe’s picture

ergophobe commented

I was stuck there in that it was verifying the maintenance theme, but not letting me move on. Why? I wasn't logged in as user 1, so I was failing the update.php access check. Doh!

dkane’s picture

dkane commented

I am still experiencing this issue. I am logged in as user 1 and have removed all non-core themes and saved the settings as suggested in #3. Any other thoughts?

dkane’s picture

dkane commented

Update - I was using Blue Marine as my standard theme and my maintenance theme. I tried (or so I had thought) all of the standard themes with no luck, but I guess I'd never used Garland. The moment I switched the maintenance theme to Garland it moved on. I have no idea why, but there it is, I hope this helps someone else!

thagenhofer’s picture

thagenhofer commented

I had the same problem. The reason was the fixed maintenance theme in settings.php at .../sites/default/.

Search for
'maintenance_theme' => 'xxx',
and change it to
'maintenance_theme' => 'garland',

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented
Issue summary: View changes
Status: Active » Closed (works as designed)

Triaging all Drupal 6 Upgrade Status issues. As Drupal 6 is no longer supported by this module and it appears people found ways to deal with this issue, closing this.