Latest Update – Critical Error
-
I’ve disabled the plugin until I can diagnose. Latest update causes a critical error on the site.
Disabling or rolling back corrects the issue.
The page I need help with: [log in to see the link]
-
Please provide more details. What’s the error you are getting exactly? Depending on your host settings you would see it displayed or saved to the PHP error file.
Also please confirm the embedding method that you are using.
I also got a critical error that took out our website. Rolling back fixed it. Here is the error:
Fatal error: Uncaught TypeError: str_contains(): Argument #1 ($haystack) must be of type string, array given in wp-includes/shortcodes.php:150 Stack trace: #0 wp-includes/shortcodes.php(150): str_contains() #1 wp-content/plugins/fresh-forms-for-gravity/class-fresh-forms-for-gravity.php(424): has_shortcode() #2 wp-content/plugins/fresh-forms-for-gravity/class-fresh-forms-for-gravity.php(503): Fresh_Forms_For_Gravity->find_gf_shortcode() #3 wp-content/plugins/fresh-forms-for-gravity/class-fresh-forms-for-gravity.php(406): Fresh_Forms_For_Gravity->find_gf_acf_field() #4 wp-content/plugins/fresh-forms-for-gravity/class-fresh-forms-for-gravity.php(621): Fresh_Forms_For_Gravity->check_gf() #5 wp-content/plugins/fresh-forms-for-gravity/class-fresh-forms-for-gravity.php(643): Fresh_Forms_For_Gravity->exclude_the_post() #6 wp-includes/class-wp-hook.php(324): Fresh_Forms_For_Gravity->fresh_content() #7 wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #8 wp-includes/plugin.php(517): WP_Hook->do_action() #9 wp-includes/template-loader.php(13): do_action() #10 wp-blog-header.php(19): require_once('/home/649545.cl...') #11 index.php(17): require('/home/649545.cl...') #12 {main} thrown in wp-includes/shortcodes.php on line 150
@lamordnt Thanks for the error message, I’m unable to replicate it in my test sites. I have been using the latest version for a few days before the release.
Can you please confirm the following details?
PHP version.
WordPress version.
Embedding method used to embed the form.We received the standard WP critical error message. I have since removed the plugin from the site until this can be resolved so I do not have the exact error message as Chris was able to provide.
It is 100% an issue related to the plugin update, but it may be some conflict with the update and an existing plugin?
We embed the forms using Elementor. Perhaps there is some conflict with Elementor?
Thank you for your quick response. ??
WP 6.4.3
Elementor v3.19.4
Elementor Pro v3.19.3
PHP 8.2
All plugins are updated to the latest version.- This reply was modified 7 months, 3 weeks ago by Brady Louveau.
- This reply was modified 7 months, 3 weeks ago by Brady Louveau.
@bradyjosephmills Are you adding the form shortcode directly into an Elementor widget or maybe using an ACF field for it? If so, please confirm which ACF field you use.
This is being added into our pages directly through the Elementor toolbar using Essential Addons for Elementor Pro Version 5.8.9
- This reply was modified 7 months, 3 weeks ago by Brady Louveau.
I don’t have access to the pro version of Essential Addons for Elementor, but I tried the Gravity Forms widget provided by the Lite version and there’s no issue.
It sounds to me like some kind of conflict because in the end the problem is that the post content that Fresh Forms is receiving to check if there’s a GF shortcode is an array when it should be a string. I’m unable to replicate this scenario, but in any case I have deployed a new version of Fresh Forms (1.4.16), that should prevent the fatal error in that scenario.
Thanks for your cooperation guys, I really appreciate it.
Thank you for looking into it, Samuel! ??
I’m experiencing a similar problem after the 1.4.15 update (resolved by disabling the plugin). I’m getting the same critical error message.
Before I upgrade to .16, can you verify the latest update addresses the problem I’m experiencing?
Specifically, here’s the message I got from my webhost who was helping me to diagnose the issue:
…your application is trying to allocate over 2GB of PHP memory for itself. The majority of this does appear to be due to a large amount of information that it is trying to prefetch, like :
[pid 16353] 1709471402.874020 (+ 0.000039) recvfrom(11, “l c\303\255rculo con m\303\272sica de fondo. Cuando se detenga la m\303\272sica, la persona con la pelota contar\303\241 una historia sobre su experiencia pasada o violencia enfrentada. El tercero, conlleva movimiento corporal y cada participante contar\303\241 una historia feliz o triste vivida durante el pasado a\303\261o.\”;i:17;s:31:\”4) Thursday / jueves (July 28)\”;i:7;s:10:\”Workshop 4\”;i:33;s:1:\”3\”;i:15;s:0:\”\”;s:3:\”1.2\”;s:0:\”\”;s:3:\”1.4\”;s:0:\”\”;s:3:\”1.8\”;s:0:\”\”;i:13;s:0:\”\”;i:14;s:0:\”\”;i:25;s:0:\”\”;s:4:\”26.1\”;s:0:\”\”;s:4:\”26.2\”;s:0:\”\”;i:28;s:0:\”\”;i:32;s:0:\”\”;s:4:\”30.2\”;s:0:\”\”;s:4:\”30.3\”;s:0:\”\”;s:4:\”30.4\”;s:0:\”\”;s:4:\”31.1\”;s:0:\”\”;s:4:\”31.2\”;s:0:\”\”;s:21:\”gv_revision_parent_id\”;b:0;s:16:\”gv_revision_date\”;b:0;s:20:\”gv_revision_date_gmt\”;b:0;s:19:\”gv_revision_user_id\”;b:0;s:19:\”gv_revision_changed\”;b:0;s:33:\”workflow_current_status_timestamp\”;b:0;s:26:\”gravityview_ratings_star_1\”;b:0;s:26:\”gravityview_ratings_star_2\”;b:0;s:26:\”gravityview_ratings_star_3\”;b:0;s:26:\”gravityview_ratings_star_4\”;b:0;s:26:\”gravityview_ratings_star_5\”;b:0;s:25:\”gravityview_ratings_stars\”;b:0;s:29:\”gravityview_ratings_vote_down\”;b:0;s:32:\”gravityview_ratings_vote_neutral\”;b:0;s:27:\”gravityview_ratings_vote_up\”;b:0;s:25:\”gravityview_ratings_votes\”;b:0;s:25:\”gravityview_ratings_total\”;b:0;}i:38;a:74:{s:2:\”id\”;s:2:\”89\”;s:7:\”form_id\”;s:1:\”2\”;s:7:\”post_id\”;N;s:12:\”date_created\”;s:19:\”2022-06-17 19:12:34\”;s:12:\”date_updated\”;s:19:\”2022-07-18 15:00:53\”;s:10:\”is_starred\”;s:1:\”0\”;s:7:\”is_read\”;s:1:\”1\”;s:2:\”ip\”;s:38:\”2806:2f0:7001:6031:9d31:fb90:be5f:518b\”;s:10:\”source_url\”;s:56:\”https://www.i-i-p-e.org/iipe_mexico/program-submissions/\”;s:10:\”user_agent\”;s:111:\”Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.0.0 Safari/537.36\”;s:8:\”currency\”;s:3:\”USD\”;s:14:\”payment_status\”;N;s:12:\”payment_date\”;N;s:14:\”payment_amount\”;N;s:14:\”payment_method\”;s:0:\”\”;s:14:\”transaction_id\”;N;s:12:\”is_fulfilled\”;N;s:10:\”created_by\”;s:1:\”1\”;s:16:\”transaction_type\”;N;s:6:\”status\”;s:6:\”active\”;s:3:\”1.3\”;s:11:\”Ana Azucena\”;s:3:\”1.6\”;s:20:\”Gutierrez Casta\303\261eda\”;i:2″…, 32768, MSG_DONTWAIT, NULL, NULL) = 32768
I know this to be data it is trying to fetch from a form.
My site is i-i-p-e.org
- This reply was modified 7 months, 3 weeks ago by pttony.
@pttony It is not the same problem that was reported by the previous users, but the main change from 1.4.12 to 1.4.15 was enabling ACF support by default. So the above should be some content that you added to an ACF field and Fresh Forms is scanning it looking for a form.
I see no reason for the above content to require 2GB of RAM, but in any case I have reverted ACF support back to disabled by default, as it was in 1.4.12. Just update to 1.4.17 and everything should be fine.
- The topic ‘Latest Update – Critical Error’ is closed to new replies.