I have updated the following modules on my website:


After the upgrade whenever I log in, I am not able to access any page (not just the administration area).
Anonymous users have no problems.
Downloding the whole website and installing it locally with the backup before the update, everything works fine. I have enabled debug logs and all possibile error reporting options, but I have no error or warning of any kind.
I have increased the memory limit, clean every cache and run the registry rebuild via php.
I have no ssh access to the host, so I cannot run any remote debugging.
Can someone point me out to a possibile solution?

  • 1
    There must be an error message somewhere - have you checked the server logs?
    – Clive
    Feb 17 '14 at 13:00
  • Could you try to update locally the modules one-by-one to identify which one is kicking?
    – Wtower
    Feb 17 '14 at 13:04
  • I assure there is no error anywhere. I already asked the hosting provider to enable the deepest level of error report. I am waiting for their answer.
    – pasine
    Feb 17 '14 at 13:08
  • Locally everything works fine.
    – pasine
    Feb 17 '14 at 13:08
  • It's pretty much unheard of for Drupal to white screen without an error message being logged. If it works locally, but not on your hosted version, it simply has to be an issue with server config. Your web hosts would be the best people to help with that, as obviously we can't gain access to the server
    – Clive
    Feb 17 '14 at 13:09

go into you database, set the status to 0 on the rows for each of the modules you mentioned. Reinstall each module one by one to find the problem module.

you could also try adding this to the top of index.php (remember to remove it later)

  • This is the first thing I did, but the problem is that some of these module are required by many others (ctools, variables, libraries). Disable them would mean have to disable all the dependent ones.
    – pasine
    Feb 17 '14 at 12:55
  • I would start with the rel_to_abs and ds modules. And any that are the the dev version of the module.
    – 2pha
    Feb 17 '14 at 13:03

The problem ended up being Devel 7.x-1.4 dropped support for PHP 5.2.
A patch has been submitted to fix the issue and has been commited to the dev release.
See the issue report here.
Thanks for your support.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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