-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'jetpack-help-center plugin has encountered an error' preventing page/post edit #98126
Comments
Another customer report here: 9259071-zd-a8c |
Support References This comment is automatically generated. Please do not edit it.
|
Closing it as it's resolved. See p1736419910869009/1734445748.634449-slack-C06E7TFSFK2. |
Another user report here: 9297048-zd-a8c |
Another user report here: 9362128-zd-a8c |
Thanks for reporting! I checked the last two reports, and those customers are experiencing this issue on the WordPress Desktop App on Windows 11. 📌 REPRODUCTION RESULTS 📌 ACTIONS |
Raised in Slack: p1738726964251459-slack-C029GN3KD @emilijamu, welcome! Just a quick note to say if you're commenting on a closed issue with a new user report, please be sure to select "Reopen with comment" so it gets flagged. Even better, you can create a new bug report and add a link to the closed one to create a trail of context! 🙏 |
I just tested this on a Windows 11 machine and WordPress desktop app 8.0.4 and I couldn't replicate the issue. I'm afraid we're going to need more details on how to replicate this. I wonder if it's a mix of settings or perhaps having CoBlocks installed? |
cc @arthur791004 if you know more about this than us. |
Another user reported it here: 9375713-zd-a8c |
At least some of the users experiencing this can only reproduce this in the WordPress.com app and they checked and couldn't reproduce it via the web. |
I can repro too, if I login to the desktop app on a non-a12 account. In the dev tools I get some errors:
See the zendesk url here: 36e64-pb/ and the second
|
I was able to reproduce this as well, but I needed to click on the "Help" icon from the top-right to initialize the help center: CleanShot.2025-02-06.at.16.08.35.mp4I'm marking this issue as triaged and adding to Vertex board. |
This should be fixed now, but we are keeping this issue open for improvements. See p1738940763017159/1738726964.251459-slack-C029GN3KD |
Was fixed with: #99422 |
Quick summary
We're receiving reports that some users are affected by a bug where an error message 'jetpack-help-center' plugin has encountered an error and cannot be rendered' shows on top of their post/page editor. I cannot replicate this on a simple site, as the error appears to be account-specific. I was able to reproduce it on my atomic test site, when unproxied.
9245219-zd-a8c
9239446-zd-a8c
Steps to reproduce
What you expected to happen
The error should not be there, and it should allow the user to edit
What actually happened
The error shows and it's preventing me to edit
Impact
Some (< 50%)
Available workarounds?
No and the platform is unusable
If the above answer is "Yes...", outline the workaround.
No response
Platform (Simple and/or Atomic)
No response
Logs or notes
Failed to load resource: net::ERR_PROXY_CONNECTION_FAILEDUnderstand this errorAI
pixel.wp.com/boom.gif?v=0.9&u=https://public-api.wordpress.com/pinghub&json={%22beacons%22:[%22pinghub.conn_close_code.1006.chrome:3092|ms%22]}:1
8registry.js:220 Store "jetpack-modules" is already registered.
i @ registry.js:220Understand this errorAI
react-dom.min.js?ver=18:1 Error: useLocation must be used within a RouterProvider
at useLocation (router.tsx:88:9)
at o (help-center-gutenberg.min.js?ver=dd3a763558783f476aa4:49:10670)
at y (help-center-gutenberg.min.js?ver=dd3a763558783f476aa4:70:223234)
at gt (react-dom.min.js?ver=18:1:45667)
at js (react-dom.min.js?ver=18:1:120123)
at Sl (react-dom.min.js?ver=18:1:88331)
at kl (react-dom.min.js?ver=18:1:88259)
at bl (react-dom.min.js?ver=18:1:88122)
at sl (react-dom.min.js?ver=18:1:84974)
at dl (react-dom.min.js?ver=18:1:85354)
The text was updated successfully, but these errors were encountered: