Re: [Proto-Scripty] "Unterminated string constant" whens tring contains a trailing dot

[Walter Lee Davis]

On Apr 20, 2013, at 6:19 AM, Cardinal wrote:

> Hi all,
> when i'm including prototype into a JSP, IE throws the error "Unterminated string constant" when i open a popup window which contains strings with a trailing dot.
>
> Basically, it's a list of usernames in the format
>
> user1.data
> user2.data
>
> As soon as this list contains a value like
>
> users2.data.system.
>
> I will get the unterminated string contant error. This error only appears when im including prototype (1.6.1 or 1.7.1), even if i don't need it for this particular popu-window (but for other elemts of the site).
> That means the popup is working without errors when im not using prototype.
>
> I assume that there is some type of escape functiality or so which collidates with my popup.

Could you please show some code around this error, or a live example? It's hard to imagine what the issue might be without something to trace through.

Walter

>
> Any help would be appreciated.
> Unfortunately i cant give you a link to reproduce that as im running the web server on a local virtual machine.
>
> Thank you and sorry for my bad english :-)
>
>
> --
> You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to prototype-scripta...@googlegroups.com.
> To post to this group, send email to prototype-s...@googlegroups.com.
> Visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Walter Lee Davis]

Just read this part. Please try to make a cut-down example in a static page that duplicates the error. Often this exercise will either bring dependencies/alternate causes to light, or it will force you to think through the problem in a new way.

Walter

[Walter Lee Davis]

On Apr 22, 2013, at 3:04 AM, Cardinal wrote:

> Unfortunately i can't provide a live demo as i am talking about a plugin for Novell / NetIQs iManager.
>
> Attached please find the SelectEntity.jsp file and some of its includes.
>


Try this: get into the browser where you see the problem on a live server, and view source (actual source, not the DOM). Copy that entire source view. Paste it into the validator at http://validator.w3.org and see if there are any errors. Remember, browsers are endlessly forgiving by design. JavaScript is easily confused. Sometimes the entire problem can be fixed by making the HTML valid.

Next, paste that source into a new text file.html. View that in a new browser window, make sure it is working up to the point of failing (so no missing resources or any bad paths). Satisfy all missing paths with local copies. Cut the page down to only show the problem, and post it somewhere public so we can look at it in our browsers. If the error requires an Ajax call to demonstrate, then stub that out with a static endpoint and dummy test data. Be sure to duplicate the same reply that is borking your page if that is the moment that it fails.

I don't have a JSP container running here, haven't used one since the '90s. Without a live example, all we can do is wave our moist fingers in the air and try to guess which way the wind is blowing. The other benefit of this exercise is that very often (high 80% of the time) you will find the problem in the process of duplicating it in a static file.

Walter

>
>
> --
> You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to prototype-scripta...@googlegroups.com.
> To post to this group, send email to prototype-s...@googlegroups.com.
> Visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

> <SelectEntity.jsp><mandator.js><OS_inc.jsp><OSFooter_inc.jsp><cvFooter.inc.jsp>

[Cardinal]

First of all, thank you for the response Walter!

I tested a bit around with the W3C validator and i have noticed that my plugin page throws almost the same warnings / errors as any other (default) plugin page (or rather the entity selection site). So i have included prototye into one of the default plugins, and that resulted in the same error message when clicking on the object history button.

So i'm now pretty sure that anything of the core architecture of Novell iManager collidates with any functionality of the prototype framework, and the behaviour seems to not depending on the individual functionalities of my plugin.

Regarding the source code - i'm not sure if i was able to get the relevant contents of the page as the error only appear when clicking on a button (which opens a popup window, and the error only appear when this windows contains an object with trailing dot, and only when prototype is included...). IE don't allow me to extract the source code of a popup window.

I will now try to customize the prototye script as it seems to contain much more functionalitys as i need for my plugin..