Skip Navigation

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

Last updated by Mihai Apetrei 1 year, 2 months ago.

Assisted by: Mihai Apetrei.

Author Posts
August 23, 2023 at 8:00 am #14275367

Ole Kroer

I have tried change to standard theme dont help. all is functioning in main language danish but error when language is changed to english. The error come after latest wpml upgrade, can you help
regards
ole

yuu cann see the error just change language on the site

August 23, 2023 at 12:42 pm #14278499

Prosenjit Barman
Supporter

Languages: English (English )

Timezone: Asia/Dhaka (GMT+06:00)

Hello There,
Thanks for reaching out to WPML Support.

Before one of my colleagues takes over this thread, please follow the instructions I've provided below and update us on the progress. This will surely expedite the process of finding a solution.

If you can access the backend(wp-admin), would you please run a conflict test on your site and check if the issue persists or not?

- Prior to making any changes, take a full backup of the entire website to ensure data safety.
- Switch to a default theme such as "Twenty-twentyone" to determine if the issue persists in this configuration.
- If switching to the default theme resolves the issue, it indicates that there might be a problem with the current theme. In such a case, it is recommended to get in touch with the theme author to discuss and investigate the issue further.
- However, if the problem still persists even after switching to the default theme, please deactivate all plugins except for WPML and its addons.
- If the issue is resolved after deactivating the plugins, start activating the plugins and after activating each, check if the issue reappears or not.

In this way, you'll be able to pinpoint the one that causes the issue.

If the issue persists, please enable the WordPress debug log on your site and check if any errors are getting recorded in the log file. The documentation below will help to understand the process of enabling a debug log.

- https://wpml.org/documentation/support/debugging-wpml/

The errors will be saved to a debug.log log file inside the /wp-content/directory.

If you can paste your debug.log to pastebin.com and share the link it would be great! (This is the cleanest way because sometimes the logs are long and create a complete mess in discussion).

Let us know the update. We will be happy to help if you need further assistance in this matter.

Best Regards,
Prosenjit

August 23, 2023 at 2:11 pm #14278907

Ole Kroer

Here is the debug file link: https://pastebin.com/XPR4vdLZ

August 24, 2023 at 9:19 pm #14288287

Mihai Apetrei
Supporter

Languages: English (English )

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

Hi there.

Sorry for the delayed response - it has been a full queue for the past few days.

Also, thank you for adding the debug information.

From what I can see, there are only 2 lines that are important (fatal errors):


[23-Aug-2023 14:01:40 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 12288 bytes) in /var/www/vhosts/****.dk/httpdocs/wp-includes/pomo/streams.php on line 229
[23-Aug-2023 14:01:40 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 12288 bytes) in /var/www/vhosts/****.dk/httpdocs/wp-includes/pomo/streams.php on line 229

The "allowed memory exhausted" error is usually related to server/hosting settings so they (the hosting support) might be the only ones who can fix it.

However, there are a good amount of existing tickets related to this exact error with recommendations and solutions from our team.

I created this custom search URL below - can you please take a look at the tickets showing up and see if the solution that worked for the customers works for you, too?

Please let me know how that goes.

- hidden link

PS: Also, please make sure your server environment meets our minimum requirements as described here:
https://wpml.org/home/minimum-requirements/

Kind regards,
Mihai Apetrei

August 28, 2023 at 2:45 pm #14301645

Ole Kroer

Hi support
I have tested a lot of thing, and the the problem is connected to string translation plugin and the bambora checkout plugin, if I deactivate string translation all is fine (but all is not translated), and if I deactivate bambora checkout payment plugin and activate string translation all is fine. The 2 plugins also run fine together until i go from main language (danish) and choose english then the PHP fatal error come. Hope yor can help, I need both plugins!!
regards
ole

August 28, 2023 at 7:13 pm #14303055

Mihai Apetrei
Supporter

Languages: English (English )

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

Hi there.

The issue here might be resolved by updating WPML String Translation and the main WPML plugin to the beta versions, as explained here, in this other ticket:
https://wpml.org/forums/topic/critical-error-caused-by-string-translation-plugin/

Please let me know how that goes and if it resolves the issue.

Mihai