1

On a live, multilingual (fr/en) client site, I've just update Drupal 7 to its latest version (along with a few modules). Everything went fine, except that, even though the maintenance mode has been disabled, the maintenance page still shows up on ONE specific URL of the public site.

www.domain.com/ -> OK
www.domain.com/fr -> !!! maintenance page
www.domain.com/fr/ -> OK
www.domain.com/en -> OK
www.domain.com/en/ -> OK

(All the other pages are OK, as far as I can tell.)

I've tried clearing all caches multiple times, and I tried running update.php again, with no effect.
Following other answers, I've also checked the database (cache_bootstrap and variables), but as far as I can tell, everything is normal there too.

What's wrong?

UPDATE
Problem solved, although I haven't done anything in particular. Maybe it was caused by some third-party caching mechanism (e.g. from the hosting provider). Will look into that if the problem occurs again.

closed as off-topic by kiamlaluno Feb 4 at 8:08

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This question was caused by a problem that can no longer be reproduced, was solved by a cache clear, or was a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers." – kiamlaluno
If this question can be reworded to fit the rules in the help center, please edit the question.

  • 2
    Are you using varnish, boost, or another external cache? – mpdonadio Nov 26 '14 at 19:50
  • I don't know the meaning of those words, so I guess no. ^^ But you raise a good point: maybe the hosting provider does? I should look into that. – s427 Nov 27 '14 at 9:01
  • Actually the problem appears to have "fixed itself", so I guess it was indeed some kind of caching mechanism... – s427 Nov 27 '14 at 9:04
0

I came across this scenario a few days back. In my case, the site was displaying maintenance page only on registration related pages in dev server.

After several hours of struggle, it was identified to be a huge secondary database (from PROD) which was connected only on enrollment related pages. I emptied the huge tables and the pages started loading seamlessly.

Hope this might help someone.

Not the answer you're looking for? Browse other questions tagged or ask your own question.