3 results found
-
Frontend and Backend Server Roles for Headless CMS / Graph driven websites
Seeking the ability to have frontend and backend server roles in the Optimizely DXP, similar to the way there is a special scheduler server role. Our website is currently set to use Affinity for backend purposes. we had Affinity off but it was turned on by the suggestion of Optimizely support. With the frontend and backend roles running on the same server the frontend customer facing website is forced to use affinity as well. This request is to create independent server roles for the frontend and backend so settings like Affinity could be managed independently. Would also like to be…
1 voteWe have a frontend hosting service already available that would accomplish this - your frontend is a separate project!
-
sync status
This request is to make the status of the Synchronize with Optimizely Graph more visible. Currently content editors only see the graph sync status when clicking into the dropdown menu on a content item in the content editing pane. Would like to see graph sync status visible on the content editing interface without having to click and additional item. Perhaps even elevating items which are not synced to have a visible indicator within the content navigation pane setting a view for whether an item or subitems have unsynced content. Currently we are having issues with our sync jobs and users…
1 voteWe’re happy to share that the Graph sync status is live for all users! Thank you for your feedback and patience - your input helped shape this release.
-
Missing autocomplete-attribute in Forms module
In the Forms module we are missing the possibility of setting the autocomplete-attribute, and therefore WCAG 1.3.5 is broken. Will this be fixed in a future update of Forms?
2 votesWe’re thrilled to share that this feature is now live for all users! 🎉
Thank you for your feedback and patience - your input helped shape this release. You can find more details in our latest release notes.
- Don't see your idea?