โซลูชั่นที่มีอยู่

Problem:
The client reported an issue with the language switcher on a paginated taxonomy page. When switching from English to Chinese on page 4, the URL constructed loses the page suffix and language parameter, causing the page to revert to the default English page instead of the intended Chinese page 4.
Solution:
We identified that the issue was due to the incorrect order of URL parameters in the custom language-switcher filter. The solution involves modifying the filter to correctly assemble the page segment and the language parameter in the URL. Here is the corrected code:

add_filter( 'wpml_ls_language_url', function( $url, $lang_data ) {<br />    if ( is_singular() ) {<br />        return $url;<br />    }<br />    $paged = absint( get_query_var( 'paged' ) );<br />    if ( $paged < 2 ) {<br />        return $url;<br />    }<br />    if ( get_option( 'permalink_structure' ) ) {<br />        $url_parts = wp_parse_url( $url );<br />        if ( empty( $url_parts['scheme'] ) || empty( $url_parts['host'] ) ) {<br />            return $url;<br />        }<br />        $path = isset( $url_parts['path'] ) ? $url_parts['path'] : '/';<br />        $path = trailingslashit( untrailingslashit( $path ) ) . 'page/' . $paged . '/';<br />        $url = $url_parts['scheme'] . '://' . $url_parts['host'];<br />        if ( isset( $url_parts['port'] ) ) {<br />            $url += ':' + $url_parts['port'];<br />        }<br />        $url += $path;<br />        if ( ! empty( $url_parts['query'] ) ) {<br />            $url += '?' + $url_parts['query'];<br />        }<br />        if ( ! empty( $url_parts['fragment'] ) ) {<br />            $url += '#' + $url_parts['fragment'];<br />        }<br />    } else {<br />        $url = add_query_arg( 'paged', $paged, $url );<br />    }<br />    return $url;<br />}, 10, 2 );

This code ensures that the pagination segment is correctly placed in the URL, maintaining the intended language switch functionality. If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum.

Problem:
After installing the WPML Media Translation plugin, the client encounters a persistent message stating, "The WPML Media Translation setup is almost complete. Click here to finish the setup." However, clicking the link leads to a loop without completing the setup.
Solution:
We have identified this message as a false warning. Our developers are aware and currently working to resolve it. You can safely ignore this message and continue using the plugin as normal without any issues.

If this solution does not apply to your situation, or if it becomes outdated, we recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please open a new support ticket.

Problem:
The client was experiencing an error when switching from the Latvian (LV) to Lithuanian (LT) language on certain custom post type (CPT) product URLs after editing or removing the LV CPT URL slug. The issue was specifically tied to a user-created Avada template.

Solution:
1. We recommended refreshing the permalink structure by navigating to Settings -> Permalinks and clicking Save Changes without altering any settings.
2. We verified that the CPT translation settings were set to Translatable with translated slugs enabled.
3. We checked that Avada Builder and Avada templates were configured as translatable in WPML.
4. We suggested ensuring that the Lithuanian and Latvian versions of the affected items were linked as translations of one another.
5. If these steps did not resolve the issue, we advised the client to provide access for further investigation and possibly contact the support teams for the caching and security plugins, as the issue seemed related to outdated cached data or plugin configuration.

Please note that this solution might be outdated or not applicable to your specific 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 the problem persists, please open a new support ticket for personalized assistance.

Problem:
The client reported an issue where a menu created in Portuguese and translated into Spanish using WPML became duplicated in the default language. Additionally, the Spanish translation became unavailable, and the pencil icon to access the translation did not show the expected content.
Solution:
We acknowledged that this behavior is unexpected and suggested that something might have affected the menu or its translation relationship. We recommended checking the errata page for known issues related to menu translations at https://wpml.org/errata/menu-translations-losing-connection-and-displaying-as-duplicates-intermittently/.
To further investigate and resolve the issue, we requested temporary access (WP Admin and FTP) to the client's site, preferably to a staging/test site where the problem has been reproduced. We informed the client that the connection would be made from Ukraine.

Please note that the solution provided might be outdated or not applicable to your specific 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 the issue persists, please open a new support ticket at WPML support forum.

Problem:
On the Malay homepage, clicking on the GX2002 product (both the image and the title) redirects to the Indonesian version of the product page instead of staying in Malay.
Solution:
If you're experiencing this issue, we recommend you try the following steps:
1. Edit the homepage in the original language.
2. Make a small change to the page title, for example, and update the page. Then, revert the change and update the page again. This may be necessary to trigger a new translation job, as the translation is currently marked as completed.
3. Open the Malay translation and update the GX2002 product link to the correct URL:

https://site.com/ms/produk/inklinometer-digital-gx2002/

4. Complete the translation and save the changes.
After completing these steps, the GX2002 link on the Malay homepage should correctly point to the Malay product URL.

Please note that this solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum.

Problem:
The "Browse" button on the second slide of the homepage banner redirects to the English version of the page in all other languages (German, Spanish, Hungarian, etc.), instead of staying in the current language.
Solution:
If you're experiencing this issue, we recommend you try the following steps:
1. Edit the homepage in the original language.
2. Make a small change to the page title, for example, and update the page. Then, revert the change and update the page again. This may be necessary to trigger a new translation job, as the translation status is currently marked as completed.
3. Open each translation and add the correct link to the BROWSE button.
4. Complete the translation and save the changes.

This solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum.