matejK-16

Problem:
The client is unable to trigger translations when updating a default language post. They expected a translation prompt but received no response.
Solution:
We recommended verifying that the code for the WPML Non-Persistent Cache plugin is correctly saved and placed. The correct code should be in a file named

wpml-non-persistent-cache.php

and added to the

mu-plugins

subfolder inside

wp-content

. This plugin helps prevent persistent caching issues that might be blocking the translation triggers.

If this solution does not resolve the issue or seems outdated, 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 problems persist, please open a new support ticket at WPML support forum for further assistance.

Problem:
The client is having an issue with a redirect that has stopped working for a custom content type. The expected URL does not load and returns a 404 error.

Solution:
First, we confirm whether the code snippet provided above is still present in the current client theme. Then we suggest disabling all plugins except WPML to check if the issue still occurs.

If the issue persists, we provide an updated code snippet for the customer to try:

add_filter('parse_request', 'parse_test_fix');
function parse_test_fix($values)
{
     if (isset($values->query_vars["error"]) && $values->query_vars["error"] == "404") {
         $post_types = get_post_types( array(), 'objects' );
         $pattern = '/\.[a-zA-Z0-9]+$/'

         if ( ! preg_match( $pattern, $values->request ) ) {
             $slug = explode( '/', $values->request );
             foreach ( $post_types as $pt ) {
                 if ( isset( $pt->rewrite["slug"] ) && $pt->rewrite["slug"] === $slug['0'] ) {
                     $resolve = get_page_by_path( basename( untrailingslashit( $values->request ) ), OBJECT, $pt->name );
                     if ( $resolve ) {
                         unset ( $values->query_vars["error"] );
                         $values->query_vars["p"] = $resolve->ID;
                         break;
                     }
                 }
             }
         }
     }
     return $values;
}

We advise the customer that we cannot offer support for custom code and that if the code stops working in the future, we will not be able to fix it. However, we have created a support ticket in our internal system to improve this behavior in future versions.

If the solution provided is not relevant because it is outdated or does not apply to your case, we recommend opening a new support ticket. We also strongly recommend reviewing the known issues, checking the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.