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.
I would like to be able to troubleshoot slot instances instead of contacting support for the log files. In the log stream you are only able to access the master slots and when appending -slot to the url it says that logging is not enabled for this site/slot.
We had an issue with a block type which had gone from a on page property to a contentarea and a change from string to XhtmlString on one of the blocks props. I thought it was solved when removing the single instance of the block but the on page property was still left causing a conversion error. With access to the logs one could solve it without the need to contact the support.