I'd been attempting to use URL aliases to alias to VIews exposed filter destinations which contain query parameters. Such aliases always generate 404's, which is caused by menu_execute_active_handler rejecting the alias. I've been told on IRC that path.module shouldn't accept such aliases, and it was rather confusing that it did (as I assumed another module was causing the problem).

So, I see two solutions. The optimal one would be to make path.module allow for destinations to contain parameters. The sub-optimal one would be to block such submissions in the UI.

Thoughts?
--Andrew

Comments

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Title: Paths are accepted which contain query strings » Allows paths to contain query strings
Version: 5.3 » 7.x-dev
Category: bug » feature

I ran into this today. It's not logical as an end user why this doesn't work. I'd rather see us fix the problem, if possible.

deviantintegral’s picture

deviantintegral commented

It's understandable why we might want this to be in 7, but can 5 and 6 have their help text documentation update to note that use of query strings leads to undefined results?

--Andrew

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Marked #225177: Full Path URL Alias as a duplicate of this issue.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Version: 7.x-dev » 8.x-dev
dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Closed (duplicate)

Duplicate of #118072: Allow query strings in URL aliases