I've installed 7.x-3.19 into a site that was running quite happily with 3.18. But when I (try to) run update.php, I get thrown to my site's home page. There are no entries in the site log (admin/reports/dblog) or the apache log, and no drupal_set_message-type messages. I've tried changing the site's theme to Bartik while doing update.php, but with no effect.

Any advice? I'm comfortable with hacking around in module and site source, so if I can do anything to track down the problem at this end, please let me know.

Comments

jim_at_miramontes created an issue. See original summary.

jim_at_miramontes’s picture

jim_at_miramontes CreditAttribution: jim_at_miramontes as a volunteer commented
Issue summary: View changes
jim_at_miramontes’s picture

jim_at_miramontes CreditAttribution: jim_at_miramontes as a volunteer commented
Issue summary: View changes
jim_at_miramontes’s picture

jim_at_miramontes CreditAttribution: jim_at_miramontes as a volunteer commented

Sorry for the versioning confusion. Upshot: my site is working fine with 3.17 and 3.18, but can't update to 3.19 (when trying to update from 3.18).

A bit of crude debugging indicates that it properly (successfully, anyway) makes its way through the update.php code, but when it goes off to theme up the update_page, something goes sideways in the theme_update code and it decides to throw to my home page.

markhalliwell’s picture

markhalliwell
Primary language English
CreditAttribution: markhalliwell at Tag1 Consulting commented
Category: Bug report » Support request
Status: Active » Closed (cannot reproduce)

I've tried changing the site's theme to Bartik while doing update.php, but with no effect.

Then this alone should tell you it's not a theme problem, nor an issue with this project.

jim_at_miramontes’s picture

jim_at_miramontes CreditAttribution: jim_at_miramontes as a volunteer commented
Category: Support request » Bug report
Status: Closed (cannot reproduce) » Active

Hmm. Sadly, I see the point. If I come up with any relevant insights, I'll re-post. Thx.

markhalliwell’s picture

markhalliwell
Primary language English
CreditAttribution: markhalliwell at Tag1 Consulting commented
Category: Bug report » Support request
Status: Active » Closed (cannot reproduce)
jim_at_miramontes’s picture

jim_at_miramontes CreditAttribution: jim_at_miramontes as a volunteer commented

I figured this out, sort of. My problem was that my theme includes a page--front.tpl.php file, which gets invoked by theme(), down inside the module update process to create the page. If I disable page--front during the update process, everything works normally. So, my immediate problem is solved; I don't know enough about the theming system at this level to say whether anything needs to be done on the module's side or not. I'll leave that to others...

jim_at_miramontes’s picture

jim_at_miramontes CreditAttribution: jim_at_miramontes as a volunteer commented

(I guess I should note that I haven't had this problem while updating other parts of my site, whether core or modules.)

Correction: Now that I have 7.x-3.21 installed, I *am* getting the problem when updating other parts of the site. As before, temporarily deactivating page--front.tpl.php gets me around it.