This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|
12:00 – 20:00 | 12:00 – 20:00 | 12:00 – 20:00 | 12:00 – 20:00 | 12:00 – 20:00 | - | - |
- | - | - | - | - | - | - |
Supporter timezone: Asia/Karachi (GMT+05:00)
Tagged: Exception
This topic contains 7 replies, has 0 voices.
Last updated by Noman 10 hours, 27 minutes ago.
Assisted by: Noman.
Author | Posts |
---|---|
December 14, 2024 at 6:15 pm #16513798 | |
alexandreR-30 |
Background of the issue: Symptoms: Questions: |
December 15, 2024 at 9:11 am #16514548 | |
Noman Supporter
Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
Hi, Thank you for contacting WPML Support. I can see the issue on your site, and I’ll do my best to assist you with it. Could you please follow the steps below and let me know the results? 1. The current WP Memory Limit on your site is 40MB. The WP memory limit needs to be increased, it's different from PHP memory. PHP memory is fine but WordPress uses 40MB as default in your site. The minimum requirements for WPML are 128MB: https://wpml.org/home/minimum-requirements/ Please add this line to your wp-config.php file to increase WP memory, wp-config.php file is located in the root of your WP install: /* WP Memory Limit */ define('WP_MEMORY_LIMIT', '256M'); You can add it anywhere in your file. I recommend placing it right before the following line: /* That's all, stop editing! Happy blogging. */ 2. Please delete all sorts of caches on your site/server cache if any / plugin cache / CDN cache, clear the browser cache, and then see if it resolves the issue afterward. 3. If the issue persists, please enable error reporting on your site as I need to see the details of the latest error log to understand the cause of the issue better. To enable it, open your ‘wp-config.php’ file and look for ‘define(‘WP_DEBUG’, false);’. Change it to: // Enable WP_DEBUG mode define( 'WP_DEBUG', true ); // Enable Debug logging to the /wp-content/debug.log file define( 'WP_DEBUG_LOG', true ); // Disable display of errors and warnings define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 0 ); define( 'SCRIPT_DEBUG', true ); After adding the above code, please try activating the WPML String Translation plugin and visiting this page: hidden link again, and if this process creates a debug.log file in your site's wp-content directory. Please send us its contents. Here is a doc for more details: Thank you |
December 15, 2024 at 10:21 am #16514654 | |
alexandreR-30 |
Hi, I followed the steps but the issue is still present. Here is the content of the debug.log [15-Dec-2024 10:17:56 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the complianz-gdpr domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/flwpptmy/public_html/wp-includes/functions.php on line 6114 interactive-geo-maps domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/flwpptmy/public_html/wp-includes/functions.php on line 6114 complianz-gdpr domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/flwpptmy/public_html/wp-includes/functions.php on line 6114 interactive-geo-maps domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/flwpptmy/public_html/wp-includes/functions.php on line 6114 complianz-gdpr domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/flwpptmy/public_html/wp-includes/functions.php on line 6114 interactive-geo-maps domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/flwpptmy/public_html/wp-includes/functions.php on line 6114 complianz-gdpr domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/flwpptmy/public_html/wp-includes/functions.php on line 6114 interactive-geo-maps domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/flwpptmy/public_html/wp-includes/functions.php on line 6114 complianz-gdpr domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/flwpptmy/public_html/wp-includes/functions.php on line 6114 interactive-geo-maps domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/flwpptmy/public_html/wp-includes/functions.php on line 6114 complianz-gdpr domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/flwpptmy/public_html/wp-includes/functions.php on line 6114 interactive-geo-maps domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/flwpptmy/public_html/wp-includes/functions.php on line 6114 complianz-gdpr domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/flwpptmy/public_html/wp-includes/functions.php on line 6114 interactive-geo-maps domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/flwpptmy/public_html/wp-includes/functions.php on line 6114 |
December 15, 2024 at 12:41 pm #16514846 | |
Noman Supporter
Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
Thanks for sharing the error details. I can see the Fatal error which causing this issue: [15-Dec-2024 10:18:01 UTC] PHP Fatal error: Uncaught Error: Call to a member function get_class_name() on null in This usually arises when some invalid content is stored in a database somehow or some elementor template is not saved properly. To fix this issue, can you please try to follow the below procedure for those elementor template which are being used on this page: 1. Open the default language page/template in Edit mode. 7. If the above steps don’t help, please provide temporary access (WP-Admin and FTP Login info) to your site (preferably staging site), so that I can look into your setup and debug the issue. Your next answer will be private, meaning only you and I can access it. === Please backup your database and website === ✙ I would additionally need your permission to deactivate and reactivate Plugins and the Theme and to change configurations on the site. This is also a reason the backup is essential. Thank you |
December 15, 2024 at 1:06 pm #16514898 | |
alexandreR-30 |
Hi, The steps you mentioned are working and when followed they do reactivate the post. The only problem is that there are 375 articles on my site. It is not possible to do them one by one. Plus, how to prevent this from happening in the future? Regards |
December 15, 2024 at 3:09 pm #16514992 | |
Noman Supporter
Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
Thank you for the update. If all 375 articles have the same issue, I recommend checking if there’s a common Elementor template/popup/section used across those articles. If so, please try applying the suggested steps to that specific template instead of doing it individually for each article. Since this error is originating from the Elementor Pro plugin, it’s worth reaching out to their support team. They might be able to provide insight into the root cause and steps to prevent such issues in the future. Let me know if you need further assistance or have any updates. Thank you for your cooperation |
December 15, 2024 at 3:54 pm #16515036 | |
alexandreR-30 |
What's troublesome is that this issue is not over all articles. Just "randomly" across some of them. The manual solutions is either to turn off WPML, or to open one by one all the articles to find which one are affected and update them. However, none of this solve the issue and guarantee that it will not happen anymore. Plus, it is extremely time consuming. |
December 16, 2024 at 7:57 am #16516096 | |
Noman Supporter
Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
Thank you for clarifying. Since the issue occurs randomly and not across all articles, it may indicate an inconsistency in the database or specific templates. Resolving this manually for all affected articles is indeed time consuming and might not be a long-term solution. To address this more efficiently, I recommend: 1. Identify if specific templates are linked to the affected articles and apply the earlier suggested steps to those templates. 2. Since the error originates from the Elementor Pro plugin, their support team might provide a better resolution or tools to identify and fix affected pages systematically. If you’d like, I can also assist further by debugging directly in a staging environment to better understand the scope of the issue. Let me know how you’d like to proceed. Thank you for your cooperation and patience |
December 19, 2024 at 2:54 pm #16530678 | |
Noman Supporter
Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
It seems you’ve marked the ticket as closed, but if the issue still persists, I’d be happy to assist further. To investigate this thoroughly without affecting your live site, we can migrate your website to a test server(cloudways) for deeper debugging. I’m going to share the migration details in my next private reply. Thank you, and I apologize for any inconvenience caused so far. I’m here to help resolve this issue. |