ExpressionEngine® Answers is a question and answer site for administrators, end users, developers and designers for ExpressionEngine® CMS. It only takes a minute to sign up.
Sign up to join this community
I have a live site currently down with the message:
{!-- ra:00000000638f5ffd00000000469f18aa --} Fatal error: Cannot use object of type stdClass as array in /xxx/system/expressionengine/libraries/Functions.php(688) : eval()'d code on line 33
Added a channel entry yesterday and I know the site worked fine after that yesterday afternoon. This morning the site was down with that error so no obvious cause.
The admin section still works, running ExpressionEngine v2.9.2
This is a PHP parse error. It's exactly what Derek Hogue said. On line 33 you are trying to use a stdClass as an array in some functionality on a template that has PHP parsing turned on.
EE template:
Hello from {site_url}!
<?php
$stdclassvar = new stdClass;
echo gettype($stdclassvar);
// this outputs "object"
$arrayvar = array();
echo gettype($arrayvar);
// this outputs "array"
// ... down to line 33 on your template, you are confusing these two types
// here's an example that will give your error:
$stdclassvar['random_key'] = 'random_value';
// this kills the crab (PHP parser)
?>
Goodbye from {site_url}!
The function from Functions.php is part of EE's template evaluater. Please review your template and PHP code, or post it with your answer so we can fix it for you. I tested the exact code above and got your error:
{!-- ra:000000004a226f8000007f5841b7ebd8 --} Hello from {site_url}! objectarray
Fatal error: Cannot use object of type stdClass as array in /var/www/html/system/expressionengine/libraries/Functions.php(688) : eval()'d code on line 15
Thanks for pointing me in the right direction! It was indeed a php enabled template causing the issue. I was at a loss as I hadn't changed anything to cause the error from the site working which made me think it was another issue. The error was in a php script that uses the twitter api to show latest tweets on the site. It turned out my client had changed their twitter username without me knowing and that was causing the error in the script.