Path alias throws and error because source path needs to start with a slash

Created on 19 April 2019, almost 6 years ago
Updated 28 January 2025, 2 months ago

I used a search view with ajax enabled and facets. Had an error in console that source path needs to start with a slash in checkProtectedPage. The getAliasByPath was returning the absolute url. I changed that part of the code and the error was gone.

🐛 Bug report
Status

RTBC

Version

1.0

Component

Code

Created by

🇸🇮Slovenia deaom

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.

  • Was getting errors trying to apply 3049350-7.patch to protected_pages version 1.7.0 rerolled the patch.

  • 🇩🇪Germany droprocker

    When installing patch in #12, the validation for entered path aliases fails on /admin/config/system/protected_pages/add. Input field for paths only allows /node/123 format.

Production build 0.71.5 2024