Error: Problem Parsing Modifier | Community
Skip to main content
January 14, 2016
Solved

Error: Problem Parsing Modifier

  • January 14, 2016
  • 3 replies
  • 1601 views

We are using Scene7 URLs to display images in an XAML-based internal tool we are building and have run into an issue with the Scene7 Image urls. If the url contains curly brackets, the portion that contains the brackets is left off when the url is executed within the XAML. 

so for example:

http://s7d7.scene7.com/is/image/......&wid=1000&hei=1000&align=0,-1&src={ugc-file:800781074.tif?fmt=tif-alpha}))))

is sent as 

http://s7d7.scene7.com/is/image/......&wid=1000&hei=1000&align=0,-1&src=))))

which results in an error "Problem Parsing Modifier." 

The reason the brackets are left out is because in XAML, anything in curly brackets is a mark-up extension, usually used for data binding, and since no value is being provided, it is left off.  Generally, a value converter can be used to encode the string like so:

http://s7d7.scene7.com/is/image/......&wid=1000&hei=1000&align=0,-1&src%3D%7Bugc-file%3A800781074.tif%3Ffmt%3Dtif-alpha%7D))))

However, this is not also is not working. Has anyone ran into this issue? and if so, do you happened to know what kind of encoding could be used to replace the curly brackets? 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Kunal_Gaba_

Have you tried the following url with escape sequence ? - {}http://s7d7.scene7.com/is/image/......&wid=1000&hei=1000&align=0,-1&src={ugc-file:800781074.tif?fmt=tif-alpha}))))

Reference- http://www.abhisheksur.com/2010/05/how-to-escape-in-xaml.html

3 replies

Kunal_Gaba_
Kunal_Gaba_Accepted solution
January 14, 2016

Have you tried the following url with escape sequence ? - {}http://s7d7.scene7.com/is/image/......&wid=1000&hei=1000&align=0,-1&src={ugc-file:800781074.tif?fmt=tif-alpha}))))

Reference- http://www.abhisheksur.com/2010/05/how-to-escape-in-xaml.html

smt108Author
January 14, 2016

Yes in fact I did. I think i actually saw that same post when researching :) Still get the same result. Some of these URLs are very long and contain a lot of special characters so that might be throwing off the escape (the full url for the one in my example has around 2200 characters)

smt108Author
January 15, 2016

We have a rule set in place to check for expression {ugc-file:} and convert it.

This is why this works : http://s7d7.scene7.com/is/image/GTMSportswear/?layer=0&wid=500&hei=500&src={ugc-file:800781074.tif?fmt=tif-alpha}

and encoded do not work.

As a workaround use this : http://s7d7.scene7.com/is/image/GTMSportswear/?layer=0&wid=500&hei=500&src=(GTMSportswear/ugc/800781074.tif)