The term "alias" generally refers to an alternative name or label that points to a file, command, address, or other item, allowing it to be located or accessed more easily.
In Cloudimage / DMO and DAM you can create 2 types of aliases:
- Standard aliases - Primarily used to hide parts of the original URL. You can also associate specific global headers with an alias. For configuration:
- Storage aliases - Optimized for connecting to private storage buckets, blobs, and HTTP-based S3 buckets. For configuration:
Troubleshooting: Reasons you may not be able to save a new alias
-
Prefix requirement
All aliases must be prefixed with at least single underscores (_).
Example:
| Alias | Allowed? |
| __hideurl__ | Yes, highly recommended |
| __hideurl | Yes |
| _hideurl_ | Yes |
| hideurl__ | No |
| hideurl_ | No |
| hideurl | No |
-
Unique aliases
All alias values must be unique. An alias defined in the Standard Alias section cannot be reused in the Storage Alias section, and vice versa.
If you encounter the error:
"Alias conflict! Alias must not be a subkey of another alias and must start with _", and you have confirmed the underscores are correct, check both the Standard and Storage Alias sections for overlapping values.
-
Subkey restrictions
An alias must not be a subkey of another alias. Aliases should not be part of any other URL aliases or Storage aliases.
Example: If you define the alias __hideurl_, you cannot use __hideurl_storage_ or __storage__hideurl_.
Additional resources
For more details, visit:
- https://scaleflex.zendesk.com/hc/en-gb/articles/4405756280850-How-to-use-alias-to-shorten-your-website-URL-s-in-Cloudimage-
- https://scaleflex.zendesk.com/hc/en-gb/articles/360018711260-How-can-I-shorten-my-Cloudimage-URLs-
If you have any questions or issues, please feel free to contact our Software Support team and mention the following details:
- Token
- Short description of the issue (including URLs, screenshot, short video if available)
- Steps to reproduce the issue.
Comments
Please sign in to leave a comment.