Answered

Error switching language on power page when query string is present

(0) Share

Report

Posted on by PDL

I've set up a power pages site from the blank template and done no customisation other than adding two additional languages.

I have a scenario where a query string parameter needs to be appended to the site/page address.

This all works fine except that when switching from one language to another using the switcher drop down on the site, it will url encode the query string, including the ? mark, which then results in an ASP.NET error. I disabled custom errors on the site to show the full exception message.

Categories:

General topics

I have the same question (0)

All responses (4)

Answers (1)

Sort by

oliver.rodrigues 9,482 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!
did you create the localized Web Page for the additional languages?

is this working without the additional parameter?

does the URL look right when you just hover over the additional language?

Was this reply helpful? Yes No
PDL 21 on at

Like
a
(0)

Report
Copy link

Link copied!

Yep it's all working without the additional query parameter.

When hovering on the link, you can see its encoded there. The rendered link in devtools shown

Feels like I may have to hack it with some javascript until this gets fixed.

Was this reply helpful? Yes No
LucasRoss232 6 on at

Like
a
(2)

Report
Copy link

Link copied!
This seems to be a recently introduced issue with the language.url_substitution liquid object. I've been able to fix it in a hacky way using the language.code and request.url liquid objects (removing the domain from request.url):

href="/{{ language.code }}{{ request.url | remove: "domain/en-US" | remove: "domain/fr-FR" }}

This seems to return the correct URL for language switching.

Correction: This didn't actually work. Had to go with some Javascript function to change the href.

Was this reply helpful? Yes No
Verified answer

PDL 21 on at

Like
a
(1)

Report
Copy link

Link copied!

I raised a ticket with MS and they confirmed a recent change has resulted in this default behavior.

The good news is that it can be switched off with a portal site setting called Site/EnableLanguageDropUrlEncoding.

Set to false to switch off the encoding.

Was this reply helpful? Yes No