Skip to content Skip to sidebar

This thread is resolved. Here is a description of the problem and solution.

Problem:
If you're experiencing a 'Uncaught TypeError' when saving a page in the original language with ACFML version 2.1.0 or above, and you have true/false fields or Google location fields on it, you're not alone.
Solution:
We recommend trying the following steps:
1. Turn off the option 'Keep repeater and flexible sub-fields in the same order as the default language' and update the post.
2. If the error persists, edit the

\plugins\acfml\classes\Helper\HashCalculator.php

file. On line 25, replace:

return self::hashArray( $value );

with:

return self::hashArray( (array) $value );

Please ensure you backup your database before making any changes. This should resolve the error.

Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please don't hesitate to open a new support ticket in the WPML support forum.

0% of people find this useful.

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 15 replies, has 3 voices.

Last updated by Andrey 1 year, 9 months ago.

Assisted by: Andrey.

Author Posts
May 6, 2024 at 7:25 pm #15599101

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+02:00)

@danielH-88, if you are experiencing an issue that appears to be different from what we have already tried to fix, please create a separate support ticket and provide detailed information. This will ensure we do not miss the issue, and we can report it further if necessary.


@basF, I would like to confirm that the fix will be introduced in a future release. Unfortunately, I cannot provide an estimated date at this time, but I believe it will be shortly.