Upon update we to new version we now have all of these warnings at top of screen. Never had an issues with previous build. Cleared all cache etc and update browscap, no fix. Please help.
Notice: Object of class stdClass could not be converted to int in /home/mysite/html/sites/all/modules/browscap/browscap.module on line 165
Warning: Cannot modify header information - headers already sent by (output started at /home/mysite/html/sites/all/modules/browscap/browscap.module:165) in /home/mysite/html/includes/bootstrap.inc on line 729
Warning: Cannot modify header information - headers already sent by (output started at /home/mysite/html/sites/all/modules/browscap/browscap.module:165) in /home/mysite/html/includes/bootstrap.inc on line 730
Warning: Cannot modify header information - headers already sent by (output started at /home/mysite/html/sites/all/modules/browscap/browscap.module:165) in /home/mysite/html/includes/bootstrap.inc on line 731
Warning: Cannot modify header information - headers already sent by (output started at /home/mysite/html/sites/all/modules/browscap/browscap.module:165) in /home/mysite/html/includes/bootstrap.inc on line 732
Comment | File | Size | Author |
---|---|---|---|
#9 | error.jpg | 139.56 KB | ashraful |
#5 | restore-old-cache-check-condition-1445654-5.patch | 504 bytes | Devin Carlson |
#3 | restore-old-cache-check-condition-1445654-3.patch | 488 bytes | Devin Carlson |
Comments
Comment #1
jzornig CreditAttribution: jzornig commentedI'm also getting the Object of class stdClass could not be converted to int in /sites/all/modules/browscap/browscap.module on line 165 error.
Comment #2
venusrising CreditAttribution: venusrising commentedThis update has issue with mobile tools alos and caused a WSOD. We had to roll back but have an update stuck in the system, table.
Comment #3
Devin Carlson CreditAttribution: Devin Carlson commentedThe attached patch restores the old cache check condition.
Comment #4
Devin Carlson CreditAttribution: Devin Carlson commentedCommitted to 6.x-1.x.
Comment #5
Devin Carlson CreditAttribution: Devin Carlson commentedForwardport of #4.
Comment #6
Devin Carlson CreditAttribution: Devin Carlson commentedCommitted to 7.x-1.x.
Comment #7
venusrising CreditAttribution: venusrising commentedWe are running Drupal 6. Not sure how 7 Dev was selected on this help request. We had a big issue on update and had to roll back for two sites. Do you think applying this patch and re applying update will fix this issue for 6.x-1.2 or is this only for DEV?
Thanks for your help.
Comment #9
ashraful CreditAttribution: ashraful commentedI getting this error. how to solve this error. Please anybody help me.(error screenshot has attached)
Comment #10
ldekay CreditAttribution: ldekay commentedTurns out for our site that a database table had crashed. We have GoDaddy hosting and a call to them resulted in them correcting the table within 20 seconds. Not a total GoDaddy fan but this was worth the other aggravations.