|Applies To||This issue only affects clients running 5.4 SP1 (5.4.1.0000.1164). It does not affect clients running any other version. |
The issue has been resolved in 188.8.131.52 which is scheduled to be released at the end of November. If you have not upgraded to 5.4 SP1 yet, please make sure you make the change to your web.config file after upgrading/installing or wait until 184.108.40.206 is released to upgrade.
We will also have a tool available to identify any content records where encoding may have been inserted and will update the data to remove the encoding. This tool is coming shortly. Please contact Archer Support for assistance.
|Issue||Keyword searching on a text string that contains a space does not return any results|
Keying off of a text field or text area field that contains a space through Data Import or Data Feed does not find a match
Statistic Reports grouping on a text field or text area field are inaccurate
|Cause||We added a new component to our web.config file in 5.4 SP1 that is encoding the spaces in the database. The text will look correct in the UI, but it will display encoded in the database. Please see the chart below for an example.|
|Resolution||There are two ways to resolve the issue in 5.4 SP1|
1.Open the web.config file
2. Search for ?HttpRuntime?
2. 3. Update the existing key as shown below. The text in red is what needs to be removed from the web.config file.
<httpRuntime maxRequestLength="2097151" requestValidationType="ArcherTech.Web.UI.ArcherRequestValidator, ArcherTech.Web" enableVersionHeader="false" encoderType="System.Web.Security.AntiXss.AntiXssEncoder,System.Web, Version=220.127.116.11, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
<httpRuntime maxRequestLength="2097151" requestValidationType="ArcherTech.Web.UI.ArcherRequestValidator, ArcherTech.Web" enableVersionHeader="false" />
We have also updated the web.config file for the different authentication methods (SSO, SSL, BASIC) so if you want to just replace your web.config file for the ones we wrote, you can do that as well. Please contact Archer Support for the updated web.config file.
|Legacy Article ID||a63073|