I'm having a few strange things happening in WPML:
- I have been unable to connect to WPML.org from this website for quite a while. I see no errors in communication log. In installation log I see a succesful connection.
- Checking for WPML updates does not work. It just hangs.
- Re-registering the site with WPML does work.
I have manually updated all WPML plugins to be sure everything is up-to-date. That results in the following:
- the issue described above remains.
- WordPress crashes on a fatal error when I activate WPML String translation v3.2.8.
- when I revert back to v3.2.7, the fatal error is gone. But the issues described above remains.
Can you help me get this sorted?
Thanks very much!
You are currently using the latest WPML Multilingual CMS with an outdated WPML String Translation plugin, which is incorrect. But you have mentioned that WPML String Translation 3.2.8 gives an error. We need to find out what it is about.
The first thing is to download a fresh copies of WPML, just in case: https://wpml.org/account/downloads/. If there is still a problem, the first step is to enable debug.log. You can do this by adding a few lines to the site’s wp-config.php file. With the error log enabled, you will see what the actual problem is.
To enable it, open your wp-config.php file and look for define(‘WP_DEBUG’, false);. Change it to:
define('WP_DEBUG', true);
In order to enable the error logging to a file on the server you need to add yet one more similar line:
define( 'WP_DEBUG_LOG', true );
In this case, the errors will be saved to a debug.log log file inside the /wp-content/directory.
Hi Andrey,
I already downloaded the latest versions of WPML + addons and replaced the old installations with that - before I created this ticket.
For now: I've activated debug and replaced string translation addon v3.2.7 with 3.2.8. I did not activate it as the site will crash. If you need to activate it to test, go ahead.
It seems like you've followed the necessary steps correctly. To proceed further, please enable WPML String Translation and share with me the crash report. You should be able to locate the debug.log in the /wp-content/directory/debug.log directory. Kindly copy and paste its contents here so that we can identify the actual error.
To return your site back, using FTP you can go to /wp-content/plugins/wpml-string-translation and rename wpml-string-translation plugin folder.
Hi Andrey,
I did what you asked. Here is the debug.log content:
[03-Nov-2023 17:32:56 UTC] Connection refused
[03-Nov-2023 17:32:58 UTC] PHP Warning: include_once(/var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/wpml-string-translation/plugin.php): Failed to open stream: No such file or directory in /var/www/vhosts/bijladvies.eu/httpdocs/wp-settings.php on line 462
[03-Nov-2023 17:32:58 UTC] PHP Warning: include_once(): Failed opening '/var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/wpml-string-translation/plugin.php' for inclusion (include_path='.:/opt/plesk/php/8.1/share/pear') in /var/www/vhosts/bijladvies.eu/httpdocs/wp-settings.php on line 462
[03-Nov-2023 17:32:59 UTC] PHP Warning: require_once(wpml-string-translationclass-wc-connect-api-client.php): Failed to open stream: No such file or directory in /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/woocommerce-services/classes/class-wc-connect-api-client-live.php on line 13
[03-Nov-2023 17:32:59 UTC] PHP Fatal error: Uncaught Error: Failed opening required 'wpml-string-translationclass-wc-connect-api-client.php' (include_path='.:/opt/plesk/php/8.1/share/pear') in /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/woocommerce-services/classes/class-wc-connect-api-client-live.php:13
Stack trace:
#0 /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/woocommerce-services/woocommerce-services.php(713): require_once()
#1 /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/woocommerce-services/woocommerce-services.php(552): WC_Connect_Loader->load_dependencies()
#2 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/class-wp-hook.php(310): WC_Connect_Loader->pre_wc_init()
#3 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters()
#4 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action()
#5 /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/woocommerce/includes/class-woocommerce.php(684): do_action()
#6 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/class-wp-hook.php(310): WooCommerce->init()
#7 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters()
#8 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action()
#9 /var/www/vhosts/bijladvies.eu/httpdocs/wp-settings.php(632): do_action()
#10 /var/www/vhosts/bijladvies.eu/httpdocs/wp-config.php(111): require_once('...')
#11 /var/www/vhosts/bijladvies.eu/httpdocs/wp-load.php(50): require_once('...')
#12 /var/www/vhosts/bijladvies.eu/httpdocs/wp-admin/admin-ajax.php(22): require_once('...')
#13 {main}
thrown in /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/woocommerce-services/classes/class-wc-connect-api-client-live.php on line 13
[03-Nov-2023 17:33:02 UTC] Connection refused
[03-Nov-2023 17:33:03 UTC] PHP Warning: include(/var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/wpml-string-translation/vendor/composer/../../classes/translation-memory/class-wpml-st-translation-memory.php): Failed to open stream: No such file or directory in /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/ClassLoader.php on line 571
[03-Nov-2023 17:33:03 UTC] PHP Warning: include(): Failed opening '/var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/wpml-string-translation/vendor/composer/../../classes/translation-memory/class-wpml-st-translation-memory.php' for inclusion (include_path='.:/opt/plesk/php/8.1/share/pear') in /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/ClassLoader.php on line 571
[03-Nov-2023 17:33:03 UTC] PHP Warning: class_implements(): Class WPML_ST_Translation_Memory does not exist and could not be loaded in /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/sitepress-multilingual-cms/classes/action-filter-loader/class-wpml-action-type.php on line 53
[03-Nov-2023 17:33:03 UTC] PHP Fatal error: Uncaught TypeError: array_intersect(): Argument #1 ($array) must be of type array, bool given in /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/sitepress-multilingual-cms/classes/action-filter-loader/class-wpml-action-type.php:72
Stack trace:
#0 /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/sitepress-multilingual-cms/classes/action-filter-loader/class-wpml-action-type.php(72): array_intersect()
#1 /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/sitepress-multilingual-cms/classes/action-filter-loader/class-wpml-action-type.php(63): WPML\Action\Type->has_implementation()
#2 /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/sitepress-multilingual-cms/classes/action-filter-loader/class-wpml-action-filter-loader.php(37): WPML\Action\Type->is()
#3 /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/wpml-string-translation/plugin.php(62): WPML_Action_Filter_Loader->load()
#4 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/class-wp-hook.php(310): wpml_st_core_loaded()
#5 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters()
#6 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action()
#7 /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php(523): do_action()
#8 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/class-wp-hook.php(310): SitePress->init()
#9 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters()
#10 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action()
#11 /var/www/vhosts/bijladvies.eu/httpdocs/wp-settings.php(495): do_action()
#12 /var/www/vhosts/bijladvies.eu/httpdocs/wp-config.php(111): require_once('...')
#13 /var/www/vhosts/bijladvies.eu/httpdocs/wp-load.php(50): require_once('...')
#14 /var/www/vhosts/bijladvies.eu/httpdocs/wp-admin/admin.php(34): require_once('...')
#15 /var/www/vhosts/bijladvies.eu/httpdocs/wp-admin/plugins.php(10): require_once('...')
#16 {main}
thrown in /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/sitepress-multilingual-cms/classes/action-filter-loader/class-wpml-action-type.php on line 72
[03-Nov-2023 17:33:03 UTC] PHP Notice: Functie is_embed werd verkeerd aangeroepen. Voorwaardelijke query-tags werken niet voordat de query is uitgevoerd. Daarvoor geeft deze altijd 'false' terug. Lees Foutopsporing in WordPress voor meer informatie. (Dit bericht is toegevoegd in versie 3.1.0.) in /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/functions.php on line 5905
[03-Nov-2023 17:33:03 UTC] PHP Notice: Functie is_search werd verkeerd aangeroepen. Voorwaardelijke query-tags werken niet voordat de query is uitgevoerd. Daarvoor geeft deze altijd 'false' terug. Lees Foutopsporing in WordPress voor meer informatie. (Dit bericht is toegevoegd in versie 3.1.0.) in /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/functions.php on line 5905
[03-Nov-2023 17:33:03 UTC] PHP Notice: Functie is_page werd verkeerd aangeroepen. Voorwaardelijke query-tags werken niet voordat de query is uitgevoerd. Daarvoor geeft deze altijd 'false' terug. Lees Foutopsporing in WordPress voor meer informatie. (Dit bericht is toegevoegd in versie 3.1.0.) in /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/functions.php on line 5905
[03-Nov-2023 17:33:03 UTC] PHP Notice: Functie is_page werd verkeerd aangeroepen. Voorwaardelijke query-tags werken niet voordat de query is uitgevoerd. Daarvoor geeft deze altijd 'false' terug. Lees Foutopsporing in WordPress voor meer informatie. (Dit bericht is toegevoegd in versie 3.1.0.) in /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/functions.php on line 5905
[03-Nov-2023 17:33:03 UTC] PHP Notice: Functie is_page werd verkeerd aangeroepen. Voorwaardelijke query-tags werken niet voordat de query is uitgevoerd. Daarvoor geeft deze altijd 'false' terug. Lees Foutopsporing in WordPress voor meer informatie. (Dit bericht is toegevoegd in versie 3.1.0.) in /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/functions.php on line 5905
[03-Nov-2023 17:33:03 UTC] PHP Notice: Functie is_search werd verkeerd aangeroepen. Voorwaardelijke query-tags werken niet voordat de query is uitgevoerd. Daarvoor geeft deze altijd 'false' terug. Lees Foutopsporing in WordPress voor meer informatie. (Dit bericht is toegevoegd in versie 3.1.0.) in /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/functions.php on line 5905
[03-Nov-2023 17:33:18 UTC] Connection refused
[03-Nov-2023 17:33:19 UTC] Connection refused
[03-Nov-2023 17:33:35 UTC] Connection refused
[03-Nov-2023 17:33:35 UTC] Connection refused
[03-Nov-2023 17:33:03 UTC] PHP Fatal error: Uncaught TypeError: array_intersect(): Argument #1 ($array) must be of type array, bool given in /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/sitepress-multilingual-cms/classes/action-filter-loader/class-wpml-action-type.php:72
Stack trace:
#0 /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/sitepress-multilingual-cms/classes/action-filter-loader/class-wpml-action-type.php(72): array_intersect()
#1 /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/sitepress-multilingual-cms/classes/action-filter-loader/class-wpml-action-type.php(63): WPML\Action\Type->has_implementation()
#2 /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/sitepress-multilingual-cms/classes/action-filter-loader/class-wpml-action-filter-loader.php(37): WPML\Action\Type->is()
#3 /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/wpml-string-translation/plugin.php(62): WPML_Action_Filter_Loader->load()
#4 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/class-wp-hook.php(310): wpml_st_core_loaded()
#5 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters()
#6 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action()
#7 /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php(523): do_action()
#8 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/class-wp-hook.php(310): SitePress->init()
#9 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters()
#10 /var/www/vhosts/bijladvies.eu/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action()
#11 /var/www/vhosts/bijladvies.eu/httpdocs/wp-settings.php(495): do_action()
#12 /var/www/vhosts/bijladvies.eu/httpdocs/wp-config.php(111): require_once('...')
#13 /var/www/vhosts/bijladvies.eu/httpdocs/wp-load.php(50): require_once('...')
#14 /var/www/vhosts/bijladvies.eu/httpdocs/wp-admin/admin.php(34): require_once('...')
#15 /var/www/vhosts/bijladvies.eu/httpdocs/wp-admin/plugins.php(10): require_once('...')
#16 {main}
thrown in /var/www/vhosts/bijladvies.eu/httpdocs/wp-content/plugins/sitepress-multilingual-cms/classes/action-filter-loader/class-wpml-action-type.php on line 72
I'm not certain which one comes up first. Would you be able to temporarily disable the woocommerce-services plugin (which is likely WooCommerce Shipping & Tax) and observe the results? I recommend clearing the debug.log beforehand, and if the issue still occurs, please provide a new error message here.
It seems that there may be an issue with the server configuration. Could you please try disabling all plugins except for WPML and switch to a default theme?
If there is still the issue, I need to request temporary access (wp-admin and FTP) to your site – preferably to a test site where the problem has been replicated if possible – in order to be of better help. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Hi Andrey,
I disabled all plugins except WPML, Page builder and Woo. Then activated the 2020 WP theme, then tested swapping string translation plugins 3.2.7 and 3.2.8.
The error immediately occurred again.
I also checked the firewall log in Plesk, and noticed some modsecurity errors. I added those two ID's to the firewall exception list, and after that, replacing 3.2.7 with 3.2.8 worked. But the site still cannot connect to wpml.org, so the connection issue remains.
New threads created by Andrey and linked to this one are listed below:
Thank you for letting me know about the update. I am glad to hear that it is now working. If you do not mind, I opened a new ticket for this question. This will also help other users with similar problems find solutions when searching the forum.
I will respond to you in the new ticket, which can be found athttps://wpml.org/forums/topic/split-wpml-plugin-cannot-connect-to-wpmlorg/
