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.

We are pleased to announce that beginning on Tuesday, March 25th, we are launching a new feedback experience for our customers!

The new experience should transition over seamlessly, but please be aware that short interruptions to our feedback portal may occur on March 25th between 2:30-4:30pm EDT.


All the best, your Optimizely Product Team

Add feedback Subscribe
Product Content Marketing
Categories DAM/Library
Created by Guest
Created on Jul 29, 2024

RELATED FEEDBACK

File extensions for CMP image urls

Currently, the file extension implementation in the CMP seems inconsistently implemented.

  1. The urls generated by the CMP do not contain a file extension.
    https://images4.cmp.optimizely.com/assets/image001-12808-.png/Zz1jYzM4MmY1NjEzZDAxMWVmOTMzODZlM2ZmODAwZTZjYg==
    The .png does not function as a file extension for the browser.

  2. In the CMP, if I change the Title of an image, and leave the extension off, I get a warning, but it will let me do it. If I remove that extentsion, I end up with the url:
    https://images4.cmp.optimizely.com/assets/image001-12808-/Zz1jYzM4MmY1NjEzZDAxMWVmOTMzODZlM2ZmODAwZTZjYg==

In both cases above, the header contains the correct file type, regardless of the url.

Normally for a physical file, something that can be downloaded to your local machine, I would expect the url to contain a file extension so that the local machine knows what kind of file it is. In the examples above, when I try to download, it uses the hash as the file name, and I assume it gets the file type from the header because it can determine the file type regardless of the url.

A more consistent and logical method for handling file types would be better for the front end user. If the CMP is going to throw an error if I try and change the file type, then I would expect a more consistent file type experience.

  • Post comment