Skip to content Skip to sidebar

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client was experiencing PHP warnings about attempting to read property "post_date" and "post_date_gmt" on null in the WPML plugin files when making changes in the backend.

Solution:
We recommended the following troubleshooting steps:
1. Back up the site's database.
2. Navigate to WPML -> Support -> Troubleshooting.
3. Press the following buttons one at a time, allowing each process to complete before proceeding:
- 'Disable cache for language switcher templates'
- 'Clear language information and repopulate languages' (if available)
- 'Synchronize posts taxonomies' for 'Products'
- 'Clear the cache in WPML'
- 'Remove ghost entries from the translation tables'
- 'Fix element_type collation'
- 'Fix WPML tables collation'
- 'Synchronize local job ids with ATE jobs'
- 'Synchronize translators and translation managers with ATE'
- 'Assign translation status to duplicated content'
- 'Set language information'
- 'Reset languages' (only if no custom language was added)
- 'Fix terms count'
- 'Fix post type assignment for translations'
- 'Cleanup and optimize string tables'
- 'Clear invalid strings'

It seems that the 'Synchronize local job ids with ATE jobs' step resolved the issue for the client.

Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If the issue persists, we encourage you to open a new support ticket. We also highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.

If further assistance is needed, please contact our support forum.

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.

Tagged: 

This topic contains 4 replies, has 3 voices.

Last updated by bjornE-6 1 year, 6 months ago.

Assisted by: Itamar.

Author Posts
April 9, 2024 at 9:34 am #15497955

bjornE-6

This is the error I get every few seconds on my website. Marked my website with XXXXXX
Debug informatie is added.

2024/04/08 11:01:38 [error] 100187#100187: *2248630 FastCGI sent in stderr: "PHP message: PHP Warning: Attempt to read property "post_date" on null in /www/XXXXXX_952/public/wp-content/plugins/sitepress-multilingual-cms/inc/translation-jobs/helpers/wpml-save-translation-data-action.class.php on line 179PHP message: PHP Warning: Attempt to read property "post_date_gmt" on null in /www/XXXXXX_952/public/wp-content/plugins/sitepress-multilingual-cms/inc/translation-jobs/helpers/wpml-save-translation-data-action.class.php on line 180" while reading response header from upstream, client: 31.149.239.163, server: hidden link, request: "POST /wp-json/wpml/tm/v1/ate/jobs/download HTTP/2.0", upstream: "hidden link:", host: "www.XXXXXX.nl:47906", referrer: "hidden link"

April 9, 2024 at 11:03 am #15498594

Bigul

Hello,

Welcome to the WPML support forum. We will do my best to help you to resolve the issue.

Please upgrade to the latest version of WordPress(6.5) and WPML(4.6.10) after a full site backup{mandatory} and make sure the issue exists or not.

We have a request. Please upgrade the following configurations for the better performance of the site.

1) Increase *WP Memory Limit* to *256*(the minimum required memory limit for WPML is *128*). Please check the following links for more details

https://wpml.org/home/minimum-requirements/

https://wordpress.org/support/article/editing-wp-config-php/#increasing-memory-allocated-to-php

2) Increase the *MaxInputVars* of PHP settings to *10000*. Please check the following article for more details or contact your system admin/hosting provider for this purpose.

hidden link

--
Thanks!

Bigul

April 15, 2024 at 11:42 am #15519733

bjornE-6

Hi, I updated to the latest version. Also the limits are also set rightu, but somehow it doesn't show up in the debug information.

I have some more information: the error occurs when we make changes in our backend.

The error:

FastCGI sent in stderr: "PHP message: PHP Warning: Attempt to read property "post_date" on null in /public/wp-content/plugins/sitepress-multilingual-cms/inc/translation-jobs/helpers/wpml-save-translation-data-action.class.php on line 179PHP message: PHP Warning: Attempt to read property "post_date_gmt" on null in /public/wp-content/plugins/sitepress-multilingual-cms/inc/translation-jobs/helpers/wpml-save-translation-data-action.class.php on line 180" while reading response header from upstream, client: 31.149.239.163, server: hidden link, request: "POST /wp-json/wpml/tm/v1/ate/jobs/download HTTP/2.0", upstream: "hidden link:", host: "www.-xxx-.nl:47906", referrer: "/wp-admin/update-core.php"

April 15, 2024 at 3:44 pm #15521241

Itamar
WPML Supporter since 02/2016

Languages: English (English )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

I'll continue to help you with this issue.

Please try WPML's troubleshooting section.

1. Take a backup of the DB of your site.

2. Go to WPML -> Support -> Troubleshooting (link)

3. Once on the troubleshooting screen, press the following buttons and check if it helps. Press each button at a time and wait for the process to complete.

- 'Disable cache for language switcher templates'

- 'Clear language information and repopulate languages' button (if it is showing)

- 'Synchronize posts taxonomies' for 'Products'

- 'Clear the cache in WPML'

- 'Remove ghost entries from the translation tables'

- 'Fix element_type collation'

- 'Fix WPML tables collation'

- 'Synchronize local job ids with ATE jobs'

- 'Synchronize translators and translation managers with ATE'

- 'Assign translation status to duplicated content'

- 'Set language information'

- 'Reset languages' Press this button only if you didn't add a custom language!

- 'Fix terms count'

- 'Fix post type assignment for translations'

- 'Cleanup and optimize string tables'

- 'Clear invalid strings'

*** Please backup your database before using this.***

Regards,
Itamar.

April 16, 2024 at 11:10 am #15524510

bjornE-6

Hi,
This works! Thank you very much!
I think in the end the 'Synchronize local job ids with ATE jobs' was the one that did the job.