Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
After installing 7.x-1.3 update.php got stuck and all site pages show White Screen Of Death. Only removing the views and ctools modules remove WSOD. Updating to core 7.22 did not help.
This is a multi-site installation with mysql.
Comment | File | Size | Author |
---|---|---|---|
#9 | Screenshot-1.png | 77.15 KB | mac1973 |
Comments
Comment #1
rhoerbe CreditAttribution: rhoerbe commentedforget to mention that the recommended error reporting settings do not show any information on the screen, and the error log is empty as well:
error_reporting(E_ALL);
ini_set('display_errors', TRUE);
ini_set('display_startup_errors', TRUE);
Comment #2
Gerben Zaagsma CreditAttribution: Gerben Zaagsma commentedSimilar issue here using Drupal Commons 7.x-3.2. The website works but when I try to access a panels page I now get a WSOD.
Comment #3
merlinofchaos CreditAttribution: merlinofchaos commentedWhen you get a WSOD, please look in the apache or php error log and see what is reported there. Without the error reported by the server, it is nearly impossible to tell what might be causing the problem.
Comment #4
ABaier CreditAttribution: ABaier commentedI have the same problem. After the update to 1.3 my page manager type (node_view) for node
pages "/node/%node" is not editable or viewable anymore (WSOD). I had many variants in there,
quite complex relationships and so on. The type for the front page is still working.
No errors or reports in the php or apache or drupal logs.
Comment #5
Gerben Zaagsma CreditAttribution: Gerben Zaagsma commentedI have to check tomorrow with our server maintenance person for apache/php logs but the drupal error logs gives me this erro (of type php):
Notice: Array to string conversion in filter_xss() (line 1434 of /data/drupal/community/includes/common.inc).
Comment #6
IreneKraus CreditAttribution: IreneKraus commentedThe error the site is giving me after the upgrade is this, if its any help:
Call to undefined function ctools_include() in (path)/sites/all/modules/context/context.module on line 481
My sites are all installed separately from each other. Have yet to try upgrading the other as I hit this one on the first.
Sorry, can't seem to find anything in server logs as it is only showing me the most recent 300 lines, and that seems filled with scripted attacks. (My one site that I have yet to update was shut down by my hosting company as it was consuming too much CPU time, even though that one is a rather low traffic site. I should say it was a low traffic site back when things were running normally. Part of what I'm doing here is a database rollback for that site.)
Comment #7
IreneKraus CreditAttribution: IreneKraus commentedIn upgrading my second site, I thought maybe I could avoid the problem by not installing the update for CTools. Nope, getting the same sort of error although this one says the problem is with the Superfish library (I think):
Fatal error: Call to undefined function libraries_get_path() in (path)/sites/all/modules/superfish/superfish.module on line 700
I did try deleting the superfish library files and re-upload to see if that would help. No improvement.
Comment #8
ABaier CreditAttribution: ABaier commentedIn my case the problem depended on some selection rules with taxonomy references (tid),
which were not save correctly, due to a bug that was fixed with the new version (#1630820 & #1601062).
To solve the WSOD I had to delete all the above mentioned selection rules first, do the
update to 7.x-1.3 and re-apply the rules. Now everything is fine!
Maybe the upgrade process could look for those fields and rewrite them to work with the new scripts?!
Thanks,
Anton
Comment #9
mac1973 CreditAttribution: mac1973 commentedSimilar problem here. After ctools upgrade - Drupal stopped rendering/displaying mini-panel (with logo block and superfish menu). Checking config for this mini-panel - it was not displaying layout (in Content section) but error message. Once mini-panel removed and recreated - seems to be working but with the error message on Mini-panel > Content page:
Warning: strlen() expects parameter 1 to be string, array given in drupal_validate_utf8() (line 1573 of /var/www/m1/includes/bootstrap.inc).
Notice: Array to string conversion in filter_xss() (line 1434 of /var/www/m1/includes/common.inc).
Warning: strlen() expects parameter 1 to be string, array given in drupal_validate_utf8() (line 1573 of /var/www/m1/includes/bootstrap.inc).
Notice: Array to string conversion in filter_xss() (line 1434 of /var/www/m1/includes/common.inc).
Pls see screenshot.
Comment #10
gausarts CreditAttribution: gausarts commentedI had the same issue. In case a help with those similar root cause:
1. Corrupt archive. I found out the extracted archive was corrupt, when I was trying to revert back to previous version. So I redownloaded it.
2. registry_rebuild to fix and find out the rest of registry issue.
So far so good now.
Comment #11
IreneKraus CreditAttribution: IreneKraus commentedThinking my problems could be traced back to a corrupted archive, I decided to re-download CTools and Views. All of my sites are now running as they should be, so that was my problem as well! Sorry that I can't confirm which one, but that was the fix for my end.
Comment #12
szt CreditAttribution: szt commentedSame problem. Trying the above methods...
Comment #13
carsonblack CreditAttribution: carsonblack commentedDid as suggested in #10 and things are back to normal. Thanks gausarts!
Comment #14
rhoerbe CreditAttribution: rhoerbe commentedI removed all modules, downloaded ctools and views, uploaded the to sites/mysite instead of sites/all, run registry_rebuild, enables them, and it worked again.
The only thing that I could not fix is to display errors when there is a WSOD although I enabled error reporting in index.php.
Comment #15
RaulMuroc CreditAttribution: RaulMuroc commentedRelated error:
#1003188: Warning: strlen() expects parameter 1 to be string in drupal_validate_utf8(), line 1503 /includes/bootstrap.inc