Nov 25, 2016, 3:48 PM
[CLOSED] Token parsing issues on control serialization (eg. ${, #{ ,.... )
Hello,
we are experiencing similar issues as the ones explained here on v2:
http://forums.ext.net/showthread.php...org-in-MVC-app
The issue was related to the content of a JSON object we're streaming down to the client like this:
We tried other ways to workaround this issue because we can't prevent the user to insert these special keywords on text fields (sometimes imported from external systems too).
For instance, passing data through a <Bin> element using an
We know that there are some process-wide settings that can be set in order to avoid parsing tokens in some cases:
Thank you for some hints.
Adriano
we are experiencing similar issues as the ones explained here on v2:
http://forums.ext.net/showthread.php...org-in-MVC-app
The issue was related to the content of a JSON object we're streaming down to the client like this:
DetailCt.CustomConfig.Add(New ConfigItem("DetailContextConfig", System.Web.Helpers.Json.Encode(clientConfig), Ext.Net.ParameterMode.Raw))
It appears the system parses the token inside any text field, and both using "Raw" or "Value" rendering modes does not prevent this to happen.We tried other ways to workaround this issue because we can't prevent the user to insert these special keywords on text fields (sometimes imported from external systems too).
For instance, passing data through a <Bin> element using an
<ext:ObjectHolder />
... seems to address the issue, however we would like know if you can suggest a better approach.We know that there are some process-wide settings that can be set in order to avoid parsing tokens in some cases:
Ext.Net.TokenUtils.Settings.SelectParsingDisable = True
...but we are actually using this syntax in the application and we have no option on fixing this way.Thank you for some hints.
Adriano
Last edited by fabricio.murta; Jan 21, 2017 at 3:10 PM.
Reason: no user feedback for 7+ days