[Resolved] Critical error after translations

Please enable the WordPress debug log. This will allow us to see if any PHP errors are being produced.

1. Edit wp-config.php and insert the following lines (just before /* That's all, stop editing! Happy publishing. */ part)

define( 'WP_DEBUG', true);
define( 'WP_DEBUG_LOG', true);
define( 'WP_DEBUG_DISPLAY', false);

2. Reproduce the issue.

3. Locate the debug log in: /wp-content/debug.log

4. Paste the latest lines here. No need to paste the entire log file, just 20 lines or so will do. Please censor any sensitive information.

https://codex.wordpress.org/Debugging_in_WordPress

These notices would not tell us about the cause, however this points us into a possible cause of this:

[11-Dec-2025 09:33:45 UTC] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /home/host658063/domains/nusaspa.pl/public_html/wp-content/themes/nusaspa/templates/page-reservation.php:26 Stack trace: #0 /home/host658063/domains/nusaspa.pl/public_html/wp-includes/template-loader.php(125): include() #1 /home/host658063/domains/nusaspa.pl/public_html/wp-blog-header.php(19): require_once('/home/host65806...') #2 /home/host658063/domains/nusaspa.pl/public_html/index.php(17): require('/home/host65806...') #3 {main} thrown in /home/host658063/domains/nusaspa.pl/public_html/wp-content/themes/nusaspa/templates/page-reservation.php on line 26

This error means that on line 26 of page-reservation.php, the code expects an array but is receiving a string, so PHP cannot do $value['something'] on it.

WPML often triggers this when a field that is normally an array (ACF, theme options, repeater, etc.) is not translated or gets returned as a string in the translated version.

Would you be willing to provide me with WordPress and FTP credentials so I could investigate the issue directly?

https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/

I marked your next reply as private so that you can safely add credentials.

I would like to check the line 26 in page-reservation.php to see what exactly is there and why it fails.

I believe the issue is caused by ACF custom fields used in the template that are not correctly handled in translations.

The template expects the following ACF group fields to return arrays:

* section_details
* section_info
* section_map

In particular this:

        $salon_details = get_field('section_details');
        $salon_info = get_field('section_info');
        $salon_map = get_field('section_map');
        $map_link = $salon_details['map_link'];
        $address = $salon_info['address'];
        $coords = $salon_map['lat_lang'];

On translated pages, these fields appear to return a string or empty value instead, which leads to the PHP error. This usually happens when the fields are not properly registered for WPML or are defined in a different context, such as a custom post type or an options page.

Could you please confirm where these custom fields are defined?

* Are they attached to a specific page?
* A custom post type (for example locations or salons)?
* Or an ACF Options Page?

Thank you.

Can you check now?
hidden link

I've noticed that hidden link was empty in fact, no ACF fields were there at all so there was nothing to render in the frontend. It was because acf-field-group was set as "translate" on hidden link

Can you tell me where is that price list coming from? Maybe VOUCHER KWOTOWY? Because even when I removed that from hidden link, it still showed up on hidden link

It is this, correct?
hidden link

"Sekcja - Cennik dynamiczny"?

But if I switch to hidden link, it looks be empty, and these options are to be translated like this https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/translating-the-acf-options-page-custom-fields-with-wpml/#translating-options-page-custom-fields

You need to translate them like this:
https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/translating-the-acf-options-page-custom-fields-with-wpml/#translating-options-page-custom-fields

If you enter only few values as a test, do they show up hidden link?