Import multilingual data from WPML into Polylang.
| Code | Message | Location | Category | |
|---|---|---|---|---|
| ERROR | PluginCheck.CodeAnalysis.DiscouragedFunctions.load_plugin_textdomainFound | load_plugin_textdomain() has been discouraged since WordPress version 4.6. When your plugin is hosted on WordPress.org, you no longer need to manually include this function call for translations under your plugin slug. WordPress will automatically load the translations for you as needed. | 59:3 | Plugin Repo |
| ERROR | outdated_tested_upto_header | Tested up to: 6.7 < 6.8. The "Tested up to" value in your plugin is not set to the current version of WordPress. This means your plugin will not show up in searches, as we require plugins to be compatible and documented as tested up to the most recent version of WordPress. | — | Plugin Repo |
| WARNING | trademarked_term | The plugin name includes a restricted term. Your plugin name - "WPML to Polylang" - contains the restricted term "wp" which can be used , as long as you don't change it to the full name. For example: You can use WP but not WordPress. | — | Plugin Repo |
| WARNING | plugin_header_nonexistent_domain_path | The "Domain Path" header in the plugin file must point to an existing folder. Found: "languages" | — | Plugin Repo |
| WARNING | trademarked_term | The plugin name includes a restricted term. Your plugin name - "WPML to Polylang" - contains the restricted term "wp" which can be used , as long as you don't change it to the full name. For example: You can use WP but not WordPress. | — | Plugin Repo |
| WARNING | trademarked_term | The plugin slug includes a restricted term. Your plugin slug - "wpml-to-polylang" - contains the restricted term "wp" which can be used within the plugin slug, as long as you don't use the full name in the plugin name. For example: You can use WP but not WordPress. | — | Plugin Repo |
| WARNING | WordPress.DB.DirectDatabaseQuery.DirectQuery | Use of a direct database call is discouraged. | 83:22 | Security |
| WARNING | WordPress.DB.DirectDatabaseQuery.NoCaching | Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete(). | 83:22 | Security |
| WARNING | WordPress.DB.DirectDatabaseQuery.DirectQuery | Use of a direct database call is discouraged. | 111:20 | Security |
| WARNING | WordPress.DB.DirectDatabaseQuery.NoCaching | Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete(). | 111:20 | Security |
| 11/14/2025, 2:16:48 AM | 9s | 87 | 2 | 44 |