[Resolved] Plugin conflict issue

Please enable the WordPress debug log. This will allow us to see if any PHP errors are being produced.

1. Edit wp-config.php and insert the following lines (just before /* That's all, stop editing! Happy publishing. */ part)

define( 'WP_DEBUG', true);
define( 'WP_DEBUG_LOG', true);
define( 'WP_DEBUG_DISPLAY', false);

2. Reproduce the issue.

3. Locate the debug log in: /wp-content/debug.log

4. Paste the latest lines here. No need to paste the entire log file, just 20 lines or so will do. Please censor any sensitive information.

https://codex.wordpress.org/Debugging_in_WordPress

Thank you for the update! No worries, I’ll keep the ticket open and wait for your reply.

The warning messages shown in the image aren't necessarily specific to WPML, but they are related to translation loading, which could involve WPML or any plugin handling translations, including:

- ld-multilingual (likely related to WPML and LearnDash)
- learndash-certificate-builder
- learndash-memberpress

The key message is that these plugins or code are calling translation functions like _load_textdomain_just_in_time too early in the WordPress lifecycle. This is not strictly a WPML issue but a timing issue with how translation domains are being loaded, and WPML could be involved if it's managing translations for those domains.

You could perhaps try this:

add_action('init', 'my_plugin_load_textdomain');

function my_plugin_load_textdomain() {
    load_plugin_textdomain(
        'my-plugin-slug', 
        false, 
        dirname(plugin_basename(__FILE__)) . '/languages'
    );
}

This should ensure you're loading the plugin's translation files inside a function hooked to init. Replace 'my-plugin-slug' with your actual text domain and ensure the .mo/.po files are in the /languages subdirectory.

The warnings you're seeing are not necessarily caused by WPML directly, but WPML could be involved if it's managing translations for the affected text domains (`ld-multilingual`, `learndash-certificate-builder`, `learndash-memberpress`).

The actual issue is that some code is trying to load translation files too early in the WordPress lifecycle. This is more of a timing or code placement issue, not a direct fault of WPML itself.

The code I shared is just an example of the correct way to load translation files using the `init` action. It's not required unless you're working on custom plugin or theme code and want to ensure translations are being loaded at the right time.

If you're using third-party plugins (like LearnDash or MemberPress), they should already handle this correctly—if not, it would be something to report to their support.