Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client encountered an issue when upgrading from WPML version 4.6.3 to 4.6.8. Specifically.

Solution:
We recommend the following steps:

  1. Ensure you have a backup of your site or perform these steps on a staging site. Also, enable the
    debug.log

    :
    Debugging WPML documentation
    .

  2. Disable all plugins and switch to a default theme like TwentyTwentyFour.
  3. If you have caching enabled via plugins, flush the cache then disable the plugin.
  4. If server caching is enabled, flush it or turn it off temporarily.
  5. Enable only WPML, starting with version 4.6.3, and update progressively to 4.6.5, then 4.6.7, and finally to 4.6.8, which can be downloaded here: WPML 4.6.8 Changelog.
  6. Delete all WPML add-ons and reinstall the latest versions from the Plugins > Add New > Commercial tab, or download them from WPML Downloads and upload them using the standard WordPress uploader.
  7. Re-enable the theme.
  8. Re-enable plugins in small batches to check for errors.

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 2 voices.

Last updated by Alejandro 1 year, 2 months ago.

Assisted by: Alejandro.

Author Posts
December 13, 2023 at 10:11 am #15052531

wernerT-3

We encountered a problem upgrading from WPML version 4.6.3. to 4.6.8

specifically - we have more than 20 languages, of which 2 global languages that are translations of each other /en/ and /fr/

after upgrading to 4.6.8 the /fr/ was no longer allowed anymore
It could only be solved by adding a trailing / to the permalink setting - which used to be (should be intended) for post-type post only. The /fr/ is a page.

So the /fr/ ended up redirecting back to /fr

that was not the expected behaviour in the past releases of WPML

Neither does this behaviour occur on any of our subsites (in case of multisite) in the latest release.

December 14, 2023 at 4:27 pm #15066617

Alejandro
Supporter

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+01:00)

Hello there!

There is something that Waqas mentioned but that i want to clarify. you can't have a page with slug "/fr" in the root and a directory fr (language). that will only create issues and it's just coincidence that it's not really creating issues right now.

i want to gather more information about this to make sure it's what i think it is.

you mentioned this "fr" page is a global page, so does that mean it's outside WordPress? does it mean that it's inside WordPress but setup in a particular way?

can you give me more info about this so i can better understand what we can do here?

Thanks in advance.

December 19, 2023 at 11:12 am #15091611

wernerT-3

Hi Alejandro
answering your questions: /fr is a language.
the homepage of france is called "accueil" in our slug. See attached screenshot.

see attached screenshot for more information explaining.

Note: after the downgrade to our previous WMPL version, we ran into a severe database loop causing a enormous load on our database and database backup replication process (causing to 15 GB per day) due to the incorrect WPML version being mentioned in the table icl_sitepress_version indicating 4.6.8 instead of our downgraded 4.6.3. This caused the upgrade process to always clear the icl_cache. That issue is now almost under control. after chancing the version number manually in the database ourselves.

Kind regards,
Ralph / Michel

fr-homepage-and-permalink-settings.png
December 19, 2023 at 2:34 pm #15093903

Alejandro
Supporter

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+01:00)

Hm, ok, well, then let's try a more cautious approach here.

0) Before you start, make sure you have a backup or if possible do this on a staging site. also make sure you have the debug.log enabled: https://wpml.org/documentation/support/debugging-wpml/

1) Disable every plugin on your site, and switch the theme to a default one like TwentyTwentyFour

2) If you have caching enabled via plugins, then first flush the cache, then disable the plugin

3) If you have cache enabled on your server, flush it or if possible turn it off temporarily

4) Now enable only WPML, in this case version 4.6.3 and update first to 4.6.5, then 4.6.7 and lastly 4.6.8 which you can download here: https://wpml.org/download/wpml-multilingual-cms/?section=changelog

5) Delete all the WPML add-ons and instead install the latest versions by going to plugins > Add New > Commercial and downloading them from that page. if you download them manually, make sure you do not upload them via FTP, but from the standard WordPress uploader ( https://wpml.org/account/downloads/ )

6) at this point, enable the theme

7) Enable the plugins in small batches.

if any error arises during these steps, please let me know in which one and send me the debug.log via any sharing platform (wetransfer, google drive, dropbox, etc)

Let me know how it goes.

December 20, 2023 at 11:07 am #15100797

wernerT-3

Hi
Thank you for detailed steps - we will be taking these into account next year when we return to work again. Ticket can be closed for now.
Kind regards,
Ralph.

December 20, 2023 at 6:42 pm #15105527

Alejandro
Supporter

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+01:00)

Alright!

i hope everything goes well, but if not, you know where to find us 😀

Regards.