WPIntell

Source evidence

Fatal Error in 2.21

WordPress.com Editing Toolkit · support · 2022-11-18T04:47:00+00:00

complaintsentiment
highseverity
1.0relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 35 rows with source links

14.3% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

30 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
justin-bigscoots unresolved
PHP Fatal error: Uncaught Error: Call to undefined function A8C\FSE\wpcom_get_site_purchases() in /home/user/public_html/wp-content/plugins/full-site-editing/help-center/class-help-center.php:126 Downgrading back to 2.20 fixes it. I had the same thing, once WordPress updated to version 6.1.1 I received the white screen of death. Once I rolled back to version 3.48304 it started working again. Any version after that gave me the same critical error. Totally just logged in to that today when I was going to actually get a blog post ready for tomorrow. I’ve currently rolled it back to the 3.48304 version but I’m waiting for my other admin to confirm we’re good before I exit recovery mode. I swear they don’t test ANY of these updates before they send them out into the world. @themaster2 i would re-reconsider using plugin which is NOT supposed to be used outside WordPress.com – it is clearly stated by authors See FAQ: Can I use this plugin in production? We’ll be making frequent updates to the plugin as we flesh out its feature set. You’re welcome to try it, just be aware that it is only designed to work on the WordPress.com environment and could break after an update. @medvidekpu , to politely tell you off, my blog is through wordpress.com I just own my URL. So your comment is 100% unnecessary and a very BOLD assumption.

Comments

4 shown
TypicalEDC 2022-11-19T08:35:00+00:00

I had the same thing, once WordPress updated to version 6.1.1 I received the white screen of death. Once I rolled back to version 3.48304 it started working again. Any version after that gave me the same critical error.

themaster2 2022-11-21T21:57:00+00:00

Totally just logged in to that today when I was going to actually get a blog post ready for tomorrow. I’ve currently rolled it back to the 3.48304 version but I’m waiting for my other admin to confirm we’re good before I exit recovery mode. I swear they don’t test ANY of these updates before they send them out into the world.

MedvidekPU 2022-11-22T06:20:00+00:00

@themaster2 i would re-reconsider using plugin which is NOT supposed to be used outside WordPress.com – it is clearly stated by authors See FAQ: Can I use this plugin in production? We’ll be making frequent updates to the plugin as we flesh out its feature set. You’re welcome to try it, just be aware that it is only designed to work on the WordPress.com environment and could break after an update.

themaster2 2022-11-22T15:56:00+00:00

@medvidekpu , to politely tell you off, my blog is through wordpress.com I just own my URL. So your comment is 100% unnecessary and a very BOLD assumption.