Hashtags not allowed with wp-login.php?redirect_to

[artifexmedia]

Hi,

With wp-login.php it is not possible to use an url with an hashtag in it, referring to what possibly would be an HTML section or an anchor tag.

For example:
Referral url: ​https://domain.com/dashboard/filemanager/#folder_1

Gets transformed into:
​https://domain.com/dashboard/

But all other urls, such as:
​https://domain.com/category/item/page/1

Etc., will be kept clean and have no problems at all.

The problem with this might be that you cannot write a function to redirect afterwards, as the ?redirect_to parameter gets writting directly into the hidden redirect_to <input> and will be used with the login_redirect hook.

From there, the url is already misformed.

Solution-wise, I've taken almost all Google now and all solutions have been provided but they are all solutions to redirect or change the URL after it has already been misformed because it is already being misformed while placed into the <input>, so I am out of solutions and I am pretty sure it is in fact a bug?

I do understand this might not be taken as a bug but rather as an enhancement, but I think for user accesibility - it is a bug.

[henry.wright]

A # character in a URL has special meaning. It precedes the fragment component of the URL. If you want to use a # character in a URL and remove the special meaning, you should encode it. For example, # becomes %23

[johnbillion]

@artifexmedia I've tested this with a URL such as wp-login.php?redirect_to=%2Fwp-admin%2Foptions-general.php%23start_of_week (using %23 for the hash as Henry mentions) and the redirect works as expected. If you're using a PHP function to generate the redirect URL you need to use urlencode() as it's a URL query parameter.