Skip to content Skip to sidebar

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: 

This topic contains 4 replies, has 2 voices.

Last updated by Christopher Amirian 1 year, 3 months ago.

Assisted by: Christopher Amirian.

Author Posts
April 3, 2024 at 12:25 pm

Joonas Nuutinen

Hi, I’m using ACFML. When I go to ACF -> Field Groups -> Sync Available, I’m seeing the following error: "There has been a critical error on this website. Please check your site admin email inbox for instructions."

The email includes the following error log:

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.4.3
Active theme: KTT (version 0.2.4)
Current plugin: WPML Multilingual CMS (version 4.6.9)
PHP version 8.2.14

Error Details
=============
An error of type E_ERROR was caused in line 26 of the file /nas/content/live/kuvataidetalo/wp-content/plugins/sitepress-multilingual-cms/menu/post-menus/wpml-posts-listing-page.class.php. Error message: Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, null given in /nas/content/live/kuvataidetalo/wp-content/plugins/sitepress-multilingual-cms/menu/post-menus/wpml-posts-listing-page.class.php:26
Stack trace:
#0 /nas/content/live/kuvataidetalo/wp-includes/class-wp-hook.php(324): WPML_Posts_Listing_Page->pre_populate_caches(Object(WP))
#1 /nas/content/live/kuvataidetalo/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#2 /nas/content/live/kuvataidetalo/wp-includes/plugin.php(565): WP_Hook->do_action(Array)
#3 /nas/content/live/kuvataidetalo/wp-includes/class-wp.php(830): do_action_ref_array('wp', Array)
#4 /nas/content/live/kuvataidetalo/wp-includes/functions.php(1336): WP->main(Array)
#5 /nas/content/live/kuvataidetalo/wp-admin/includes/post.php(1291): wp(Array)
#6 /nas/content/live/kuvataidetalo/wp-admin/includes/class-wp-posts-list-table.php(165): wp_edit_posts_query()
#7 /nas/content/live/kuvataidetalo/wp-admin/edit.php(235): WP_Posts_List_Table->prepare_items()
#8 {main}
thrown

April 3, 2024 at 12:56 pm
April 4, 2024 at 8:42 am #15481656

Christopher Amirian
WPML Supporter since 07/2020

Languages: English (English )

Timezone: Asia/Yerevan (GMT+04:00)

Hi there,

The error is reported to the second-tier support.

For the time being we recommend you keep PHP 7.4 till further notice.

I will update you here if there is a release with a fix or there is a need for further investigation.

Thank you.

April 7, 2024 at 10:21 am #15491486

Christopher Amirian
WPML Supporter since 07/2020

Languages: English (English )

Timezone: Asia/Yerevan (GMT+04:00)

Hi there,

Would you please provide us with the staging version of the website with PHP 8.2.4 to check on your server and set the next reply as private to give the login info?

We checked with PHP 8.2.4 in our local installations and we could not replicate the same issue and everything worked ok.

Thank you.

April 10, 2024 at 9:12 am #15503268

Joonas Nuutinen

Hi, I created the staging environment but wasn't able to reproduce the error anymore. Furthermore, when I upgraded the production site back to 8.2, I don't see the fatal error anymore. Now when I try to access the ACF -> Field Groups page, I see the following error banner: "Error. Something went wrong, please try again." However, this doesn't prevent me from doing my stuff.

My database state was different when the error occurred. Whatever I did while on 7.3 must have changed the database state enough to not cause the error anymore on 8.2. So I guess this would be quite difficult to fix because even I'm not able to reproduce it anymore.

I'll still keep your credentials active for a while in case you want to inspect the error banner on the production environment. Otherwise, I think things are fine now. Thanks for the help!

April 13, 2024 at 11:43 am #15514762

Christopher Amirian
WPML Supporter since 07/2020

Languages: English (English )

Timezone: Asia/Yerevan (GMT+04:00)

Hi there,

Thank you, as the original issue is fixed already and the other one does not prevent you from doing your normal work I think we can close here.

But if the second issue starts to creeping on something that is a show stopper please open up a separate ticket and we will investigate.

Thanks.

April 15, 2024 at 3:46 am #15516959

Joonas Nuutinen

Thanks, sounds like a plan!