Hi there,
Sorry you’re having trouble. Can you please provide more detail about the error message you are seeing? The error message should include the file name and line number for the error.
Thread Starter
Mesasix
(@jervenmatthew)
Hi,
Here is the full log:
PHP Fatal error: Uncaught Error: [] operator not supported for strings in /nas/content/live/earstexas/wp-content/plugins/formidable/classes/models/FrmEntryFormat.php:468\nStack trace:\n#0 /nas/content/live/earstexas/wp-content/plugins/formidable/pro/classes/models/FrmProEntryFormat.php(153): FrmEntryFormat::html_field_row(Array, ”)\n#1 [internal function]: FrmProEntryFormat::single_html_row(”, Array)\n#2 /nas/content/live/earstexas/wp-includes/class-wp-hook.php(286): call_user_func_array(‘FrmProEntryForm…’, Array)\n#3 /nas/content/live/earstexas/wp-includes/plugin.php(208): WP_Hook->apply_filters(Array, Array)\n#4 /nas/content/live/earstexas/wp-content/plugins/formidable/classes/models/FrmEntryFormat.php(463): apply_filters(‘frm_entry_html_…’, Array, Array)\n#5 /nas/content/live/earstexas/wp-content/plugins/formidable/classes/models/FrmEntryFormat.php(397): FrmEntryFormat::single_html_row(Array, Array)\n#6 /nas/content/live/earstexas/wp-content/plugins/formidable/classes/models/FrmEntryFormat.php(375): FrmEntryFormat::html_cont in /nas/content/live/earstexas/wp-content/plugins/formidable/classes/models/FrmEntryFormat.php on line 468
Thanks. It looks like you are running an outdated version of Formidable, as well as the Pro version. Can you please update to the latest version and open a ticket in our helpdesk if you still have questions?
Thread Starter
Mesasix
(@jervenmatthew)
Hi,
I am running the latest I believe: Version 2.03.01
Is this correct?
Thanks
Hi there,
The current release is 3.06.02, so your version is about 2 years old now…
Thread Starter
Mesasix
(@jervenmatthew)
Oh weird. The dashboard doesn’t say I need updates.
I think I’m gonna have to update via cli.
Thread Starter
Mesasix
(@jervenmatthew)
I just updated to 3.06.02.
And now the whole site is 502.
WPEngine cant even figure out what caused the error lol.
Thread Starter
Mesasix
(@jervenmatthew)
its now fixed. i had to deac all plugins and reinstall everything. ty