Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Add feedback Subscribe
Product Configured Commerce
Categories Technical
Created by Guest
Created on Oct 2, 2024

RELATED FEEDBACK

Allow a way to see server side rendering on Sandbox

As someone responsible for site availability/uptime AND SEO, there should be a way for QA testers (not just developers on their local instance) to trigger SSR in Spire on Sandbox in order to do basic QA on the site. Currently, on Sandbox any "bot" user agents (Googlebot) cause a block at the Cloudflare level.

There are some React packages (i.e. sessionStorage) that when referenced/used in code will work fine in a browser but cause a 500 error when server side rendering. This makes testing by QA folks basically impossible.

A suggestion for this would be a SSR toggle asked for previously in the content admin. That might be difficult for QA to test as CMS permissions would need to be granted to QA staff.

Another that's perhaps easier to implement would be a setting in the main admin console to add 0-N user agents that trigger server side renderings - disconnected from the Cloudflare protections. So, I could add 0 agents and the default behavior would be maintained, or add my own additional bot user agents that do not get blocked by Cloudflare (like "my-testing-bot") but do trigger SSR, and have QA staff set user agent to that to test SSR scenarios.

  • Post comment