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
- - 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00
- - - - - - -

Supporter timezone: America/Lima (GMT-05:00)

This topic contains 8 replies, has 0 voices.

Last updated by Andreas W. 5 days, 11 hours ago.

Assisted by: Andreas W..

Author Posts
January 2, 2026 at 4:51 pm #17700795

Marie-Aude

The slugs of custom postypes have been defined in the settings, nevertheless, they are not applied when trying to display an archive page in an other language.
Examples :
hidden link in French is in English hidden link instead of hidden link

Or :
hidden link in French is in English hidden link instead of hidden link (and the English version misses a part of the CSS).

(Ticket Re-opend because you closed it without giving me time to answer)

January 2, 2026 at 6:07 pm #17700889

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

It seems the minimum server requirements are not met:
https://wpml.org/de/startseite/mindestanforderungen/

Could you please increase the WordPress memory limit (WP Memory Limit) to at least 256 MB? WPML requires at least 128 MB.

Your current values ​​are:

PHP Memory Limit 512 MB
WP Memory Limit 64 MB

To do this, you need to connect to your website's server and open the wp-config.php file in a text editor. The file is located in the WordPress root directory.

Add this code to the wp-config.php file to increase WordPress's memory:

define ('WP_MEMORY_LIMIT', '256M');

Add this just before this comment:

// That's all, stop editing! Happy blogging.

The current values ​​can be viewed under WPML > Support > WordPress.

These settings can be restricted directly by your hosting provider. Therefore, I recommend contacting them and asking them to change them directly if the changes are not applied automatically.

After adjusting the limit, please go to WPML > Settings > Post Types Translation and edit the fields for your slug translations, then save these settings again.

If this does not solve the issue or you need assistance with adjusting the WP MEMORY LIMIT, please let me know.

Best regards
Andreas

January 7, 2026 at 9:26 am #17708755

Marie-Aude

WP Memory limit is now 512 M, PHP limit 768M

I resaved the fields for slug translations. It does not solve the problem.

January 7, 2026 at 4:44 pm #17710284

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

I'd be happy to take a closer look at this and request temporary access (wp-admin and FTP) to the website to investigate the issue further.

You'll find the necessary fields below the comment section if you log in to leave the next reply. The information you provide will be private, meaning only you and I will be able to see and access it.

IMPORTANT
Please be sure to create a backup of the website and database before granting us access.

If you don't see the "wp-admin / FTP" fields, your login credentials for the post and website will be set to "PUBLIC." Do NOT publish the information unless you see the required wp-admin / FTP fields.

I may need to install a plugin called "All In One WP Migration" to create a copy of the website on which I can investigate the problem more thoroughly.

I would also be very grateful if you could provide a staging site on your server for this purpose.

If you have any questions about creating such a staging site, please contact your hosting provider. Please ensure that WPML is also registered on this staging site at https://wpml.org/de/account/websites/.

If you are unable to provide such a copy of the website for testing, please let me know on this ticket.

The private reply form looks like this:
hidden link

When replying again, click "I still need assistance".

Video:
hidden link

Please note that we are required to request this information individually on each ticket. We are not permitted to access any login information that was not specifically provided in the private reply form for this ticket.

Best regards,
Andreas

January 9, 2026 at 12:35 pm #17715994

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Your translated CPTs are using the correct slugs:
hidden link

The issue is about the slug of the page "L'equipe", and the page slugs are set to "Translate" inside WPML. Inside the WPML Translation Editor, the slugs are translated on all jobs for this page.

If you revise the example, the English page "The Team" on the WordPress Editor, you can see that WPML translated the permalink correctly, and the page is accessible
hidden link

The odd thing is, we seem to reach a different page, with a different layout.

It seems like you are trying to use the same slug "equipe" in different ways, like once for a page and then again for a CPT for "member" and this creates a conflict:

Source:
hidden link
hidden link

January 14, 2026 at 2:49 pm #17729825

Marie-Aude

Hi, thanks but that does not solve my issue.

I'm speaking of the archive page of the CPT.
So I changed the slug of the page to "notre-equipe" and I took care of translating it in all languages.

Nevertheless, when we go to hidden link you see that the links in the language switcher are all with "notre-equipe".

And hidden link is now a 404

hidden link exists and is accessible, but is not the link in the lanquage switcher in French. But if you look at the links in the language switcher on this english page, they are correct.

January 14, 2026 at 3:36 pm #17730085

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

I am sorry to hear that my suggested workaround did not solve this issue. To investigate this issue further, I am going to take a local copy of the site.

Once I have finished the tests, I will reach out again.

January 14, 2026 at 7:48 pm #17731086

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

My apologies, but the first migration attempt failed due to issues with the database migration.

I will give it a second try and then reach out again.

January 14, 2026 at 9:18 pm #17731289

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Still, the problem is that hidden link is recognized as CPT archive and not as a page.

This problem is visible even if you disable WPML.

1) Activate the plugin "Debug Bar"
2) Go to hidden link and check the admin bar for "Debug" on the top right and click on request.

You will see:
notre-equipe

Query String:
post_type=member

The issue is not the translation, as the conflict already exists in the original content.

You can see the same issue even when testing the site only with the Porto Theme and the Porto Theme - Functionality plugin.

If you revise the member post type in Porto, I can confirm that the slug for this post type and the slug of your team page are not identical. Anyhow, WordPress is not recognizing the page as such.

This is why I suggest you consult the Porto Support Team about this issue.