Previous message edited. Downgrading plugin to previous version did not resolve the issue.
There’s a console error:
wp-json/wp/v2/feedback/298303?_locale=user
displays
{“code”:”rest_forbidden”,”message”:”Sorry, you are not allowed to do that.”,”data”:{“status”:401}}
Further:
Issue Description
Summary:
Jetpack Feedback entries are being correctly created in the database and email notifications are sent, but no feedback items display in the Jetpack Forms > Responses admin UI. The table is empty except for the <div class="dataviews-view-table__cell-content-wrapper"></div> markup per cell. The issue persists even though:
- Entries exist in
wp_posts with post_type = 'feedback' and post_status = 'publish'
- All expected meta fields are present (
_jetpack_feedback_form_id, etc.)
- REST API endpoint
/wp-json/wp/v2/feedback returns feedback entries correctly when accessed while logged in as admin
- No errors show in browser JS console on the admin Responses page
- No plugin or theme conflicts (tested with only Jetpack and default theme)
- No custom code or filters affecting the Feedback post type or REST API
- Jetpack was deactivated, deleted, reinstalled, and reconnected
- All caches (server, plugin, CDN) have been flushed or disabled
- The problem occurs for all admin users
Hi there, @thomastolkien,
Thanks for reporting it and for adding more additional details (and doing some more troubleshooting). I tried to replicate the issue on my test site, but I was able to display the form responses and delete them.
Before escalating this to our tech team, we’d like to run some more tests on your specific site. Could you please post your site URL here so that we can have a look? If you want it to remain private, you can also contact us via contact form. If you choose to reach out directly, please include a link to this thread.
Thanks!
Sorry – no can do.
We had to remove your plugin after our hosting provider said Jetpack form responses:
“Triggered 699 hits on the endpoint wp-json/wp/v2/feedback over the course of a few minutes.”
They added:
“We saw 57 requests per second, then 42 – all of these requests were to index.php WP core code, which resulted in the amount of PHP workers being spawned.”
Until this issue is fixed we’re not able or willing to reinstate the plugin.
We were able to replicate the issue on five other production sites and our hosting provider has since advised/demanded we remove your plugin.
I hope you manage to resolve this. I suspect you will be seeing a lot more instances of this. Perhaps rolling back to a working version of the code would be prudent?
Hello @thomastolkien,
Thank you so much for explaining this, we really appreciate the details. I completely understand why you’d want to hold off for now. Jetpack is usually very reliable and server-friendly, so we don’t often see this kind of spike; when it happens, we can normally address and fix it with the help of the hosting provider.
If you ever feel comfortable trying again in the future, we’d be glad to help make sure things run smoothly with your setup.
Thanks again for sharing this, and best wishes 🙂
TL;DR
- User reports a serious bug in good faith.
- WordPress plugin support not really interested.
No wonder developers are leaving this platform. Didn’t you guys used to be Happiness Engineers?!
Hi @thomastolkien,
In my previous reply, I asked whether you’d feel comfortable sharing a bit more information with us, as this would help us better understand the issue and pass it along to our developers if needed. We truly appreciate all the details you’ve already provided – they’ve been very helpful – but we may still need a bit more to complete a thorough bug report. Of course, we completely respect your decision if you prefer not to share additional information right now.
Rest assured that we do take users reports seriously, and we haven’t said we won’t report it – we simply want to make sure we have enough context to investigate it properly. For example, we need to confirm whether the issue might be specific to your hosting provider’s servers or settings, which is something we must assess before filing a bug report with our development team.
As said previously, we do hope you’ll consider giving Jetpack another try in the future, or share the info we requested (also privately) and if you’d ever like to revisit this, we’ll be here and ready to help.
