Bug

Problem:
You are trying to translate the contents in the Footnotes block on your pages using the Advanced Translation Editor (ATE), but the contents cannot be found for translation.
Solution:
1. Navigate to your WordPress Dashboard > WPML > Settings > Custom Fields Translation.
2. Search for "footnote" and set it to "Translate".
3. Click the blue save button.
4. Visit the page containing the footnote and make a change in the original language to trigger the need for a translation update.
5. Open the Advanced Translation Editor. You will find a search bar at the top. Search for the content of the Footnote, and you should be able to find it.
6. Ensure you copy the entire code as is, and only change the text inside. For example, for a code like this:

[{"content":"Christopher<br />Hello there!<br />General Kenobi!","id":"10def6f4-bf19-4e47-860e-aa9bfe4af89e"}]

Your translation should look like this:

[{"content":"Christopher translated<br />Hello there! translated<br />General Kenobi! translated","id":"10def6f4-bf19-4e47-860e-aa9bfe4af89e"}]

For more detailed instructions on how to search content inside Advanced Translation Editor, visit this link.

If this solution does not resolve your issue or seems outdated, we recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.

Problem:
You are experiencing a fatal error when using WP CLI commands with WPML and the Rollbar plugin due to a compatibility issue with the psr/log library. The error message indicates a declaration mismatch in

DebugFileLogger.php

.
Solution:
We recommend trying one of the following workarounds:
1) Disable the Rollbar plugin.
2) Modify the

DebugFileLogger.php

file in your WPML plugin directory. Replace its contents with the following code:>

<?php
 
namespace WPML\PHP\Logger;
 
use Psr\Log\AbstractLogger;
use Stringable;
 
class DebugFileLogger extends AbstractLogger {
 
  public function log($level, Stringable|string $message, array $context = []): void {
    if ( ! defined( 'WP_DEBUG' ) || ! WP_DEBUG ) {
      return;
    }
 
    $log = date( 'Y-m-d H:i:s' ) . ' [' . $level . '] ' . (string) $message . PHP_EOL;
    \error_log( $log );
  }
 
}

If these solutions do not resolve the issue or if they become outdated, please check for related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance.

Problem:

The client is unable to update the WPML Multilingual CMS plugin as the update link is not visible, and receives a message stating 'WPML String Translation is enabled but not effective, because WPML is outdated. Please update WPML first.'.

Solution:

If you're experiencing this issue, we recommend visiting Plugins>Add New>Commercial tab and clicking on the Check for updates button. This action will refresh the installer caches and should make the update link for the latest version of WPML visible. Please note that WPML releases updates in batches during the initial days of release, which might delay the visibility of the update link for some users.

If this solution does not resolve your issue or seems irrelevant due to it being outdated or not applicable to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.