When I try to look at any my forms I get the attached page and an email from WP say in caged a fatal error.
I don't know what to do with this.
Thanks for any and all help.
the last image is not clear, does it show the error details ? can you paste that here or make the image bigger ?
I coped and pasted the information below:
--------------
When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.5.3
Active theme: Clean Magazine Pro (version 2.7.1)
Current plugin: Chronoforms (version 7.0.9)
PHP version 8.2.18
Error Details=============
An error of type E_ERROR was caused in line 25 of the file /home2/midsouth/public_html/wp-content/plugins/chronoforms/chronog3/libs/lang.php.
Error message: Uncaught TypeError: vsprintf(): Argument #2 ($values) must be of type array, string given in /home2/midsouth/public_html/wp-content/plugins/chronoforms/chronog3/libs/lang.php:25
Stack trace:
0 /home2/midsouth/public_html/wp-content/plugins/chronoforms/chronog3/libs/lang.php(25): vsprintf('Select image of...', '%s')
1 /home2/midsouth/public_html/wp-content/plugins/chronoforms/chronog3/gcloader.php(50): G3\L\Lang::_('Select image of...', '%s', false)
2 /home2/midsouth/public_html/wp-content/plugins/chronoforms/admin/chronoforms/views/field_secicon/field_secicon.php(16): rl3('Select image of...', '%s')
3 /home2/midsouth/public_html/wp-content/plugins/chronoforms/admin/chronoforms/themes/default/views/connections/draggables2.php(18): require('/home2/midsouth...')
4 /home2/midsouth/public_html/wp-content/plugins/chronoforms/chronog3/libs/view.php(261): include('/home2/midsouth...')
5 /home2/midsouth/public_html/wp-content/plugins/chronoforms/chronog3/libs/view.php(333): G3\L\View->_contents('/home2/midsouth...', Array)
6 /home2/midsouth/public_html/wp-content/plugins/chronoforms/admin/chronoforms/themes/default/views/connections/dragndrop_forms.php(68): G3\L\View->view('/home2/midsouth...')
7 /home2/midsouth/public_html/wp-content/plugins/chronoforms/chronog3/libs/view.php(261): include('/home2/midsouth...')
8 /home2/midsouth/public_html/wp-content/plugins/chronoforms/chronog3/libs/view.php(333): G3\L\View->_contents('/home2/midsouth...', Array)
9 /home2/midsouth/public_html/wp-content/plugins/chronoforms/admin/chronoforms/themes/default/views/connections/edit.php(115): G3\L\View->view('/home2/midsouth...')
10 /home2/midsouth/public_html/wp-content/plugins/chronoforms/chronog3/libs/view.php(261): include('/home2/midsouth...')
11 /home2/midsouth/public_html/wp-content/plugins/chronoforms/chronog3/libs/view.php(217): G3\L\View->_contents('/home2/midsouth...')
12 /home2/midsouth/public_html/wp-content/plugins/chronoforms/chronog3/libs/app.php(248): G3\L\View->renderView('edit')
13 /home2/midsouth/public_html/wp-content/plugins/chronoforms/chronog3/libs/app.php(78): G3\L\App->dispatch(true)
14 /home2/midsouth/public_html/wp-content/plugins/chronoforms/chronog3/libs/app_loader.php(61): G3\L\App::call('admin', 'chronoforms', 'connections', 'edit', Array)
15 /home2/midsouth/public_html/wp-content/plugins/chronoforms/chronoforms.php(200): G3\L\AppLoader->__construct(Array)
16 /home2/midsouth/public_html/wp-includes/class-wp-hook.php(324): Chronoforms->cf7_admin('')
17 /home2/midsouth/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
18 /home2/midsouth/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
19 /home2/midsouth/public_html/wp-admin/admin.php(175): do_action('admin_init')#20 /home2/midsouth/public_html/wp-admin/index.php(10): require_once('/home2/midsouth...')#21 {main} thrown
We (I assist jhager62 with the above site) are on CF 7.0.9 which is the latest version available for Wordpress - is that PHP8 compatible? There is no update that I see to the latest CF7 version and it appears WP shut it down last year due to a security issue. Do we have any recourse other than start over again with CF8?
I think the PHP version is the reason, v7 for WP supports PHP 7.2 only, and v8 is not yet released for WP and you would have to remake the form
but the error you posted is not a fatal error, so it should not return the broken page, I think another error is causing this
