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.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: America/Los_Angeles (GMT-07:00)

This topic contains 2 replies, has 0 voices.

Last updated by Bobby 1 month, 2 weeks ago.

Assisted by: Bobby.

Author Posts
April 14, 2025 at 10:54 am #16928543

mohabM-4

Background of the issue:
I recently installed the WPML plugin on my website ctab.tn, which is originally in French. I added Arabic and English as additional languages and configured custom directories for each language: hidden link (base language), hidden link, hidden link. I expected my web pages to be correctly translated and accessible through these links, with smooth navigation between languages via the language selector in the footer.

Symptoms:
I encounter a critical error in the wp-background-process.php file whenever I try to switch to another language, making the site inaccessible and preventing me from viewing my translations. Additionally, I was charged immediately for automatic translations despite the system indicating 'use now, pay later.'

Questions:
How can I regain access to my site dashboard to identify the cause of the problem?
How can I view my already published translations when switching between languages?
How can I resolve the compatibility issues between WPML and Elementor?

April 17, 2025 at 12:06 am #16941446

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Hi there,

I have reviewed this fatal error and I am not able to locate a known issue at the moment.

To further debug, if possible, please provide us with your debug information.
You can find the steps on how to do this here:
https://wpml.org/faq/provide-debug-information-faster-support/#:~:text=Your%20debug%20information%20is%20located,supporter%20assigned%20to%20your%20ticket.

If you are not able to access your site due to the fatal error, go to your file manager and navigate to /wp-content/plugins/sitepress-multilingual-cms and add ".deactivate" at the end of the folder name and this will manually deactivate the plugin.

April 17, 2025 at 5:32 pm #16945511

mohabM-4

Hello,

Thank you for your quick response regarding the fatal error on my website.

As per your request for debugging information, I'm providing direct access to my site and server so you can examine the issue more effectively:

[removed due to privacy]

I have also found log files that might be relevant to resolving this issue and have attached them to this message.

I would like to emphasize that this situation is extremely urgent for my site, as I currently cannot access the translated versions, which significantly impacts the user experience and visibility of my content.

If you need additional information or if you encounter any difficulties accessing the site or server, please don't hesitate to contact me immediately.

Thank you in advance for your prompt assistance in resolving this critical issue.

Best regards,

April 18, 2025 at 4:48 pm #16947857

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Thank you for sharing this information with me!

If possible please add the access drtails in our private reply thread as sensitive information is removed due to the forum threads being public.

I would like to request temporary access (wp-admin and FTP) to your site to test the issue.
(preferably to a test site where the problem has been replicated if possible)

**Before we proceed It is necessary to take FULL BACKUP of your database and your website. Providing us with access, you agree that a backup has been taken **

I often use the Duplicator plugin for this purpose: http://wordpress.org/plugins/duplicator/
You will find the needed fields for this below the comment area when you log in to leave your next reply.
The information you enter is private which means only you and I have access to it.

NOTE: If access to the live site is not possible and the staging site does not exist please provide me with a duplicator package created with the duplicator plugin.

Thank you,
Bobby

April 22, 2025 at 6:42 am #16953160

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Thank you for the access details!

i was able to successfully access the site, however, each time I attempt to navigate to Dashboard -> Plugins I am receiving an error 500 that seems hosting related.

Screenshot 2025-04-21 at 11.40.44 PM.png
April 22, 2025 at 9:49 am #16954150

mohabM-4

First, access the site through this link: hidden link.

Once you’ve done that, please close and reopen the link: hidden link. This will allow you to access the plugin on my website.

April 22, 2025 at 6:57 pm #16957113

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

I follow these steps:

1. Go to hidden link; loads and then I close it
2. Got to hidden link. --> loads and i am in the backend OK
3. Try to view the front end of hidden link and it either works or it gives me an error 504 and then that leads to err 500 or just a blank page, and that happens both in the front end and backend.

Unfortunately this is not allowing me to test this issue properly.

Please try the following:

1. Increase the WP MEMORY LIMIT to 256M or higher --> currently at 40M
2. Enable REST API
3. If you go to WPML->languages->Language URL Format and switch to use the parameters format, what are your results?

April 26, 2025 at 1:26 pm #16970923

mohabM-4

I hope this message finds you well.

I am still experiencing server issues, with many pages not being accessible. I have copied the backup created to a temporary domain server where I can manage the WP MEMORY LIMIT to 256M, as the actual server doesn't allow changing this limit.

Many pages remain inaccessible, making it difficult to diagnose the errors correctly linked to the WPML plugin. I have provided you with a direct link to the temporary domain (please note that it does not have an SSL certificate, so you will see a warning stating 'Your connection is not private'). Please skip this warning and access the site; you will be able to see everything there and diagnose the problems. You also have the FTP credentials.

What I need from you:

Please help me remove all errors on the translated pages related to WPML.
Address any compatibility issues between WPML and my theme/plugins.
If any modifications are necessary on existing custom code to resolve errors, feel free to make those changes. Just provide me with a summary of what you did at the end.
Thank you for your assistance. I want to ensure my website is fully functional in multiple languages.

Here is the link: hidden link

Best regards,

April 28, 2025 at 6:33 pm #16976533

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Thank you, this environment is working better.

1. it's important to have a good amount of WP MEMORY LIMIT.

Please contact the hosting environment and ask them to increase it -- 128M is required per our minimum requirements to run WPML, 40M is below that.

https://wpml.org/home/minimum-requirements/

Typically 256M is just better and highly recommend for most sites even without WPML.

2. Query Monitor -- this plugin can stress the performance of your server and should only be activated when debugging a performance related issue.

3. The issue ONLY happens on the AR version.

This is the FATAL Error related to the issue:

Fatal error: Uncaught ValueError: Unknown format specifier "�" in /home/mobo2332/temp.ctab.mobo2332.odns.fr/wp-content/plugins/elementor-pro/modules/custom-code/custom-code-metabox.php:69

---> Deactivating Elementor PRO resolves the issue.

Possibly some custom code? I'd advise reviewing the area mentioned in the code above and having that adjusted, you will want to make sure only English characters are used in the custom code.

The following plugins had to be deactivated.

Elementor PRO
ElementsKit Pro
Ultimate Addons for Elementor Pro
Forminator

If you are using custom code please review and verify that all characters used are in English and no special characters are used such as apostrophes, etc.

Let us know your results.

April 28, 2025 at 6:46 pm #16976545

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Thank you, this environment is working better.

1. it's important to have a good amount of WP MEMORY LIMIT.

Please contact the hosting environment and ask them to increase it -- 128M is required per our minimum requirements to run WPML, 40M is below that.

https://wpml.org/home/minimum-requirements/

Typically 256M is just better and highly recommend for most sites even without WPML.

2. Query Monitor -- this plugin can stress the performance of your server and should only be activated when debugging a performance related issue.

3. The issue ONLY happens on the AR version.

This is the FATAL Error related to the issue:

Fatal error: Uncaught ValueError: Unknown format specifier "�" in /home/mobo2332/temp.ctab.mobo2332.odns.fr/wp-content/plugins/elementor-pro/modules/custom-code/custom-code-metabox.php:69

---> Deactivating Elementor PRO resolves the issue.

Possibly some custom code? I'd advise reviewing the area mentioned in the code above and having that adjusted, you will want to make sure only English characters are used in the custom code.

The following plugins had to be deactivated.

Elementor PRO
ElementsKit Pro
Ultimate Addons for Elementor Pro
Forminator

If you are using custom code please review and verify that all characters used are in English and no special characters are used such as apostrophes, etc.

Let us know your results.

The topic ‘[Closed] Critical Error After WPML Setup – Unable to Access Arabic/English Translations & Compatibility Issue…’ is closed to new replies.