Getting these errors on latest Dev release (dated 5/8/12):
Recoverable fatal error: Object of class stdClass could not be converted to string in DatabaseStatementBase->execute() (line 2136 of /var/www/html/drupal_test/includes/database/database.inc).
Recoverable fatal error: Object of class stdClass could not be converted to string in DrupalDefaultEntityController->cacheGet() (line 368 of /var/www/html/drupal_test/includes/entity.inc).
I'm wondering if I've understood this right:
Was this happening during upgrade or just install?
Were you enabling the module or just replacing the previous version?
For me, I replaced a previous dev version of 7.x and this started happening. I upgraded my site several months ago, so for me, I don't think it has anything to do with upgrading.
After replacing the old 7.x dev, I ran update.php but there were no DB updates. I cleared cache and that didn't help. I disabled FAQ Ask and the errors went away. I re-enabled the module and the errors didn't return until several hours later.
Very strange.
I think I might have had this problem on the previous dev version, but I was screwing with the module code a bit so I'm not really sure. =p
Have this coming up but bizarrely only in Chrome browser. In Firefox no issues. Not sure why. The message is
Recoverable fatal error: Object of class stdClass could not be converted to string in DatabaseStatementBase->execute() (line 2171 of /home/.../public_html/includes/database/database.inc).
Site runs in Drupal 7.38. Have about 46 modules - no custom-built modules. All modules were updated to latest version.
In Chrome sometimes if we refresh it goes away but comes up again on next click. Other times it doesn't go away even if refreshed. At the same time if I open the site in Firefox it opens up correctly. Never faced the issue in Firefox.
Since I Firefox is my default browser, not sure when this issue actually started. It happens on all URLs of the site.
Comments
Comment #1
bfroehle commentedComment #2
GStegemann commentedWhen I disable the FAQ_Ask module (current development snapshot) the error is not thrown.
What function, interface or hook is responsible for this?
Comment #3
berdirMoving to FAQ_Ask Module.
The issue is likely in an update function of that module. It is passing an object instead of a string as a query placeholder value.
Comment #4
stenjo commentedIs this still an issue?
A lot have been happening with the D7 version lately. This might have been overcome by now.
Comment #5
stenjo commentedComment #6
jlea9378 commentedGetting these errors on latest Dev release (dated 5/8/12):
Recoverable fatal error: Object of class stdClass could not be converted to string in DatabaseStatementBase->execute() (line 2136 of /var/www/html/drupal_test/includes/database/database.inc).
Recoverable fatal error: Object of class stdClass could not be converted to string in DrupalDefaultEntityController->cacheGet() (line 368 of /var/www/html/drupal_test/includes/entity.inc).
Disabling FAQ Ask makes them go away.
Comment #7
jlea9378 commentedOddly when I re-enabled FAQ Ask, the errors didn't return. Strange...
Comment #8
stenjo commentedCan I ask you to try the upgrade again, but now with the Devel module enabled?
That might give us some more clues to what is going on...
Comment #9
jlea9378 commentedOk now the errors are back again. I didn't do anything... just refreshed the page a couple hours later.
I tried clearing all caches from the AdminMenu but that didn't help.
Comment #10
stenjo commentedI'm wondering if I've understood this right:
Was this happening during upgrade or just install?
Were you enabling the module or just replacing the previous version?
Comment #11
jlea9378 commentedFor me, I replaced a previous dev version of 7.x and this started happening. I upgraded my site several months ago, so for me, I don't think it has anything to do with upgrading.
After replacing the old 7.x dev, I ran update.php but there were no DB updates. I cleared cache and that didn't help. I disabled FAQ Ask and the errors went away. I re-enabled the module and the errors didn't return until several hours later.
Very strange.
I think I might have had this problem on the previous dev version, but I was screwing with the module code a bit so I'm not really sure. =p
Comment #12
jlea9378 commentedSo far I haven't seen these errors appear again after switching to the 5/9 dev release.
Comment #13
stenjo commentedI suggest we mark this as fixed for now. If it reoccurs this issue can be reopened.
Comment #15
viggie commentedHave this coming up but bizarrely only in Chrome browser. In Firefox no issues. Not sure why. The message is
Site runs in Drupal 7.38. Have about 46 modules - no custom-built modules. All modules were updated to latest version.
In Chrome sometimes if we refresh it goes away but comes up again on next click. Other times it doesn't go away even if refreshed. At the same time if I open the site in Firefox it opens up correctly. Never faced the issue in Firefox.
Since I Firefox is my default browser, not sure when this issue actually started. It happens on all URLs of the site.
Comment #16
HJulien commenteddelete