- Install SureFeedback & Addons
- Update SureFeedback
- Translate SureFeedback
- WPML For Multilingual Sites
- Main Site Or Dedicated Installation?
- Automating SureFeedback Workflows With OttoKit
- Manage Licenses
- Caching & SureFeedback
- Litespeed Caching
- Chrome Incognito: Session Expired Notice
- Gridpane Compatibility
- Breeze Compatibility
- W3 Total Cache Compatibility
- Download Failed: Unauthorized
- Flywheel Cache Exclusion
- Generate Invoice
- WPRocket Compatiblity
- Swift Performance Caching
- Debugging
- Varnish Caching
- Website Comments Not working
- Flywheel Compatibility
- Emails Not Sending
- WPEngine Cache Exclusion
- Increasing WordPress Memory Limit
- Client & Colleague Accounts
- Permissions Cheatsheet
- Slack Integration
- Export Comments in PDF / CSV
- Provide Project Access
- Hosting
- Subscribed Projects Shortcode (Below 3.1.x)
- Activate SureFeedback License
- Dashboard Shortcode
- Cloudways Compatibility
- Known Issues
- SureFeedback On External Site
- Emails
- Project Shortcode
- Customization Settings
- Project Shortcode (Below 3.1.x)
Flywheel Compatibility
Note: This exclusion only needs to be done on the server where you have SureFeedback installed (your dashboard site). You don’t need to add these cache exclusions on your connected sites!
If you host your site on Flywheel, you may encounter some issues with the Client Site Plugin and Access Links. This is due to aggressive page caching (which is a good thing!), but it can be easily resolved by requesting that Flywheel set up special cache exceptions.
To do this, simply submit a support ticket to Flywheel via their support portal and ask them to exclude a few URL query variables from the cache.
Send them a link to this doc, so they can add these exclusions to your server configuration:
https://help.surefeedback.com/article/49-flywheel-compatibility
Legacy Servers Varnish Exclusions:
if (req.url ~ "(ph_apikey|access_token)") { return (pass); }
Cloud Sites NGINX configuration:
location / {
# Clear expires headers that the SureFeedback plugin sets on pages
more_clear_headers expires;
# Unset cookies for unspecified paths, with the option for exceptions
header_filter_by_lua_block {
if ngx.req.get_method() ~= "POST" and
-- Path exclusions, including query strings in the regex area
ngx.re.match(ngx.var.request_uri, "(add-to-cart|access_token|ph_apikey)", "io") == nil then
ngx.header['Set-Cookie'] = ""
else
ngx.header["cache-control"] = "private"
end
}
include internal-proxy.conf;
}
We don't respond to the article feedback, we use it to improve our support content.