Hi @tinpeas
Thanks for reporting this error. Our development team is investigating the issue and will keep you updated as soon as possible.
Hi @tinpeas
Could you please check and confirm whether you had any older version of the Yoast SEO Premium plugin (wordpress-seo-premium) installed on the website?
Nope, definitely no premium version installed.
Just has the same issue on a different domain using different PHP version on different hosting. I am updating anyway due to the security fix.
This site also seems fine by the way and again no Yoast Premium.
I should say both sites are WooCommerce sites if that helps.
Thanks for the details @tinpeas
Could you please check whether there are multiple occurrences of the fatal error in the logs, or if it was just a one-time event?
Also, does the error log mention any other plugin files or functions? If you can share the error log mentioning the error fully it would be helpful for us.
From our tests the fatal error occurred when the WooCommerce plugin is active and when we have updated from the Yoast SEO free plugin of version 27.1.1 manually installed on a website before to 27.2. Also the error only shown for once and its not showing again on any pages. Can you please confirm whether you have also noticed the same behaviour @tinpeas ?
Yep, that seems to be the case. I am seeing no obvious issues with the sites that generated the error and I updated 96 sites using WordPress Toolkit and didn’t get a single error, some of which are WooCommerce sites. So it does seem related to manual updates when WooCommerce is installed.
-
This reply was modified 2 months, 1 week ago by
tinpeas.
Good to hear that @tinpeas and thanks for replying! From our test, it only showed once and didn’t log the error again on the WooCommerce sites.
Some technical information from our development team’s analysis:
1) When you go to the plugin upload or update screen, WordPress loads some background data to prepare the page. During this process, WooCommerce also loads some data using the REST API.
2) At the same time, Yoast SEO is in the middle of being getting updated. Because of this, it may briefly try to use older files while loading the new ones, which can cause a temporary fatal error that you have noticed.
This usually happens only during the update process and does not affect your website otherwise.
Thanks for that Jose, it all seems to be working as expected so no issues this end.
Hey, i got the same fatal error! Ideas? What helps?
I’m still getting the fatal error on WooCommerce sites so am avoiding the update for now (the sites appear to be working though) – will there be a fix?
An error of type E_COMPILE_ERROR was caused in line 76 of the file /home/smalland/public_html/…/wp-content/plugins/wordpress-seo/src/task-list/application/tasks/complete-ftc.php. Error message: Declaration of Yoast\WP\SEO\Task_List\Application\Tasks\Complete_FTC::get_call_to_action(): ?Yoast\WP\SEO\Task_List\Domain\Components\Call_To_Action_Entry must be compatible with Yoast\WP\SEO\Task_List\Domain\Tasks\Task_Interface::get_call_to_action(): Yoast\WP\SEO\Task_List\Domain\Components\Call_To_Action_Entry
Hi @kaleu_87 and @angiefuz
As mentioned above, our test showed it only once and didn’t log the error again on the WooCommerce sites after the initial one.
Some technical information from our development team’s analysis:
1) When you go to the plugin upload or update screen, WordPress loads some background data to prepare the page. During this process, WooCommerce also loads some data using the REST API.
2) At the same time, Yoast SEO is in the middle of being getting updated. Because of this, it may briefly try to use older files while loading the new ones, which can cause a temporary fatal error that you have noticed.
This usually happens only during the update process and does not affect your website otherwise. So there won’t be any fix as this is not affecting the website loading or causing any issues. However, if you encounter the same issue again, kindly create a new thread with more details so we can replicate it.
