thomastolkien
Forum Replies Created
-
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?!
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?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_postswithpost_type = 'feedback'andpost_status = 'publish' - All expected meta fields are present (
_jetpack_feedback_form_id, etc.) - REST API endpoint
/wp-json/wp/v2/feedbackreturns 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
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}}
Previous message edited. Downgrading plugin to previous version did not resolve the issue.
- This reply was modified 10 months, 4 weeks ago by thomastolkien.
Forum: Fixing WordPress
In reply to: Editing options no visiableWe’re seeing the same thing. The visual editor is broken after upgrading to 6.8.
Rolling back to 6.7.2 resolves the issue.
Please stop marking this issue as resolved. It has NOT been resolved.
- This reply was modified 1 year, 4 months ago by thomastolkien.
We do not and have never used Varnish cache.
We are still seeing this issue.
This issue has not been resolved.
Console errors:
backend.min.js:1 ReferenceError: swcfpc_ajax_url is not defined
at swcfpc_purge_whole_cache (backend.min.js:1:4522)
at HTMLAnchorElement. (backend.min.js:1:14526)
2
backend.min.js:1 Uncaught ReferenceError: swcfpc_cache_enabled is not defined
at swcfpc_update_toolbar_cache_status (backend.min.js:1:12453)
22
backend.min.js:1 Uncaught ReferenceError: swcfpc_cache_enabled is not defined
at swcfpc_update_toolbar_cache_status (backend.min.js:1:12453)
swcfpc_update_toolbar_cache_status @ backend.min.js:1Last call for an update on this?
Otherwise, do you have any objections if we fork version 4 of your plugin?
Yes this still happens on the latest version.
This happens on all admin backend pages, including the dashboard, when an admin presses the “purge whole cache” menu link. It also happens on all front end pages when logged in when a logged in admin presses the “purge whole cache” menu link.
We’ve not been able to find any instances of pressing the “purge whole cache” menu link which do not produce the error as described.
The last working version of the plugin – which we’ve downgraded our sites to – is 5.0.1
@soitre01 We don’t have or use LiteSpeed or it’s plugin on the sites we’re observing this error on, so I don’t think that’s the root cause unfortunately.
Is there any update on this?
@desigstate are you sure you want that function to run on the front end?