You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when creating a branded link in OneLink, the system does not accept hyphenated path segments in the URL ID (e.g., 'access-case'). The error message indicates that only a-z, A-Z, and 0-9 characters are allowed without spaces.
Suggested Enhancement
I propose an enhancement to allow hyphenated path segments in the URL ID.
Use Case
Many users create campaign links that are meant to be easily read and understood by end-users. Hyphens are commonly used in URLs to improve readability. For example, 'access-case' is more readable than 'accesscase' or 'accessCase'.
Expected Behavior
When entering a URL ID, users should be able to include hyphens in the path segment. The system should validate and accept the hyphenated path, allowing the creation of more descriptive and user-friendly URLs.
Additional Context
Thank you for considering this enhancement to improve the usability and functionality of OneLink.
The text was updated successfully, but these errors were encountered:
Issue Description
Currently, when creating a branded link in OneLink, the system does not accept hyphenated path segments in the URL ID (e.g., 'access-case'). The error message indicates that only a-z, A-Z, and 0-9 characters are allowed without spaces.
Suggested Enhancement
I propose an enhancement to allow hyphenated path segments in the URL ID.
Use Case
Many users create campaign links that are meant to be easily read and understood by end-users. Hyphens are commonly used in URLs to improve readability. For example, 'access-case' is more readable than 'accesscase' or 'accessCase'.
Expected Behavior
When entering a URL ID, users should be able to include hyphens in the path segment. The system should validate and accept the hyphenated path, allowing the creation of more descriptive and user-friendly URLs.
Additional Context
Thank you for considering this enhancement to improve the usability and functionality of OneLink.
The text was updated successfully, but these errors were encountered: