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.

Sun Mon Tue Wed Thu Fri Sat
- 12:00 – 16:00 10:00 – 14:00 10:00 – 14:00 9:00 – 13:00 9:00 – 13:00 -
- 17:00 – 21:00 15:00 – 19:00 15:00 – 19:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Europe/Bucharest (GMT+03:00)

Tagged: 

This topic contains 5 replies, has 2 voices.

Last updated by Mihai Apetrei 11 months, 3 weeks ago.

Assisted by: Mihai Apetrei.

Author Posts
July 31, 2024 at 10:10 am #16024051

stephanW-22

<b>Background of the issue: </b>
I need to update the site server from PHP 7.4 to 8.1. I have the same error as described in the documentation here: https://wpml.org/errata/wpml-string-translation-3-2-10-fatal-error-due-to-format-specifier/. However, I can't find the /missing/ folder on my server. When I deactivate the WPML plugin, the website works.

<b>Symptoms: </b>
Fatal error: Uncaught Error: Missing format specifier at end of string

<b>Questions: </b>
How can I resolve the fatal error related to the format specifier?
Why can't I find the /missing/ folder on my server?
Is there a specific step I need to follow to update the server to PHP 8.1 without encountering this error?

Screenshot 2024-07-31 at 12.03.13.png
July 31, 2024 at 9:29 pm #16026988

Mihai Apetrei
WPML Supporter since 03/2018

Languages: English (English )

Timezone: Europe/Bucharest (GMT+03:00)

Hi there.

There might be a chance that you are not using the latest WPML and WooCommerce versions.

From what this error tells me, it seems that some information is missing from the WooCommerce plugin files (this plugin is separate from WPML so I don't think it is related to WPML).

Can you please paste your WPML Debug information in the Debug information field I activated below?

- http://wpml.org/faq/provide-debug-information-faster-support/

August 1, 2024 at 11:56 am #16029312

stephanW-22

Thanks, for replay.

Well maybe you are right, but it works everything fine with PHP 7.4. But when I update the PHP to 8.1 this error is happens and then I deactivate the WPML with PHP 8.1 then page works again. So thats why I think is something with WPML, or any setting in WPML. Because the site works on both PHP version without WPML.

This is a dev site and pass. protected, if you need anything else let me know.

Additionally, both plugins are latest versions and in file class-wc-post-types.php is not done any change. If you need I can share a login informations or FTP/SFTP !

Thanks,

August 1, 2024 at 8:42 pm #16031341

Mihai Apetrei
WPML Supporter since 03/2018

Languages: English (English )

Timezone: Europe/Bucharest (GMT+03:00)

Welcome back and thank you for the updates!

Can you please first make sure that you download and try to use the very latest version of the WPML String Translation add-on from here:
https://wpml.org/download/wpml-string-translation/?section=changelog

If nothing changes after activating that latest version, can you also try to manually create a folder under "wp-content/languages/wpml" called "missing" but leave it empty, and see if that resolves the issue?

Please let me know how things go.

August 2, 2024 at 9:08 am #16032338

stephanW-22

Well here what I did,
Switched back to PHP 7.4 where everything works.

Downloaded the WPML String Translation add-on from your link, installed/activated, everything was fine working. Then switched back to PHP 8.1 the same error.

Then back to 7.4 added the "missing" folder at "wp-content/languages/wpml", and back to 8.1 and again the same error. Actually nothing helped.

Screenshot 2024-08-02 at 11.07.48.png
Screenshot 2024-08-02 at 10.25.58.png
August 3, 2024 at 9:34 pm #16035937

Mihai Apetrei
WPML Supporter since 03/2018

Languages: English (English )

Timezone: Europe/Bucharest (GMT+03:00)

Hi there.

Thank you for the update.

I would like to request temporary access (wp-admin and FTP) to your site so I can better examine the issue. The needed fields are below the comment area. When you log in to leave your next reply, the information you enter is private, meaning only you and I can see and access it.

Our Debugging Procedures

I will check various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to back up the site before providing us access. In the event that we do need to debug the site further, I will duplicate it and work in a separate, local development environment to avoid affecting the live site.

Privacy and Security Policy

We have strict policies regarding privacy and access to your information. Please see:
https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/

**IMPORTANT**

- Please back up the site files and database before providing us access.

If you do not see the wp-admin/FTP fields, your post and website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box.

The private box looks like this: hidden link

I will be waiting for your response.

The topic ‘[Closed] Fatal error: Uncaught Error: Missing format specifier at end of string in’ is closed to new replies.