[CLOSED] Token parsing issues on control serialization (eg. ${, #{ ,.... )

  1. #1

    [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:
    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
  2. #2
    Hello Adriano!

    The problem you are facing makes it a good example on preferring to use App.Store1 instead of #{Store1} in page codes. It ends up translated into the former in the end so I guess that would be the best way to refer to components.

    But it seems changing this approach is going to break a rather deep design constraint in your project so I believe the approach you took with ObjectHolder would be best. Other than that, I can't think on anything that wouldn't involve escaping the trigger patterns in text fields in either direction (server > client; client > server).
    Fabrício Murta
    Developer & Support Expert
  3. #3
    Hello again Adriano!

    Been some time since we replied to your inquiry here and still no feedback from you. Did the above help you or do you still need assistance with this thread?

    We may mark this thread as closed in 7 business days from now at least but this won't mean that you may not post follow ups here from then on so, take your time.

    Hope to hear back from you soon!
    Fabrício Murta
    Developer & Support Expert

Similar Threads

  1. image control cache issues
    By qtec in forum 2.x Help
    Replies: 1
    Last Post: Feb 18, 2016, 9:24 PM
  2. [CLOSED] Disable curly brace token parsing per control
    By jchau in forum 2.x Legacy Premium Help
    Replies: 1
    Last Post: Oct 28, 2015, 12:31 PM
  3. BADRESPONSE: Unexpected token { on calendar control
    By Felixkirathe in forum 2.x Help
    Replies: 1
    Last Post: Apr 17, 2012, 4:07 PM
  4. Replies: 3
    Last Post: Apr 16, 2012, 1:56 PM
  5. [CLOSED] Issues in Tab Control
    By Etisbew in forum 1.x Legacy Premium Help
    Replies: 1
    Last Post: Jun 10, 2009, 4:38 AM

Posting Permissions