Page Visibility Path Validation

Created on 5 December 2022, about 2 years ago
Updated 16 May 2023, over 1 year ago

Problem/Motivation

Client accidentally entered a fully qualified url into the field for Page Visibility and was confused when the functionality did not work as they expected and state wasn't saved as they expected.

Steps to reproduce

1. Create an alert. Under the Page Visibility group, select Limit by Page and enter a fully qualified url such as:
https://www.example.org/test instead of a relative path such as /test
2. Save
3. The user doesn't get any feedback saying that this is the incorrect format for paths to be entered and so expects this to work but it doesn't.
3. User edits the alert and sees that the Limit by Page button state has not been saved and thinks that's the issue.

Proposed resolution

Recommend providing minimum form validation letting the user know that the path must be relative and start with a slash.

✨ Feature request
Status

Fixed

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States sassafrass

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024