Feature hyperlink with ampersand incorrectly encoded
In our parcel data, we have a field that contains a hyperlink to a county assessor site. We've created a feature hyperlink using the syntax {Hyperlink} in the "Create/Edit Feature Hyperlink" dialog, "URI" textbox where Hyperlink is the name of the field in the data table. This works great until the URL contains an ampersand in the query string. When the URL contains an ampersand, any ampersands in the URL sent to the browser are incorrectly encoded in the form & So, for example, a URL like www.xyz.com?p=q&a=b is sent to the browser like www.xyz.com?p=q&a=b. This happens regardless of the "Encode Field Values" setting the "Create/Edit Feature Hyperlink" dialog. We are using Essentials 4.5.1 and viewer 2.6.1. Is this a bug? Are we missing something?
0
-
I'm now running into the same issue. I've tried all 3 encoding options with no different result.
We are using 4.6.2 Essentials and 2.7.1 GVH0 -
I appreciate that info since we were considering a move to 4.6.2 and 2.7.1 to improve the situation. Now we know it won't so thank you for saving us the time. 0 -
I normally launch our sites in Chrome and I see this behavior there, I switched over to IE and I don't have the same issue. Looks like Chrome is automatically encoding the URL in certain circumstances. I still get the URL to display correctly if I am clicking on the URL from the Results Table in both IE and Chrome. 0 -
I tested in both Chrome and IE and duplicated the issue in both. The problem is when identifying a feature, whatever code that runs underneath to present all the exposed attributes was grabbing the url and somehow html encoding the ampersand prior to dumping it into the "Hyperlinks" portion of the form. We've gotten around this by pre-encoding the url in database and it works. The behavior that happens with the hyperlink from a feature identify does not happen when bringing the same url into a workflow as a hyperlink...the hyperlink form control does not html encode the ampersand and the link works correctly. 0 -
Nope...we were wrong...pre encoding the ampersand in the database does not fix a layer feature hyperlink. We've ensured we've selected no encoding when creating the feature hyperlink, but it's not honored. Is the auto html encode of ampersands in feature hyperlinks a bug that needs to be fixed? We are pulling the complete url from our database and it works from the identify attribute list, but not as a feature hyperlink. 0 -
Hi guys,
I've checked with the viewer team and this is a bug (GVH-10416) in the current HTML5 viewer. It will be fixed in version 2.8.0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
6 kommentarer