Problem with jquery ch 11

daveharney · February 23rd, 2012, 08:34 PM

If I remove { cssClass: 'Watermark' } from the $.updnWatermark.attachAll({ cssClass: 'Watermark' }); I get the same error in my UC page.

If I do the same thing in your sample, I don't get any error - just does not show the tool tip text in the text box.

Imar · February 23rd, 2012, 08:38 PM

HI there,

Looks indeed like the path to the JS file is incorrect. Try adding it as a script reference like the jQuery file. Alternatively, compare your code with the actual path, Something like:

Code:

 
<script src="/Scripts/jquery.updnWatermark.js" type="text/javascript"></script>

should work, provided you set the site's Virtual Path to / as explained earlier in the book, and provided that the JS file exists in the Scripts folder of course.

Cheers,

Imar

daveharney · February 23rd, 2012, 09:09 PM

I tried your suggestion and almost every other path combination I could think of. The first question is why did your sample work - as a single page - and mine as a UC does not? Did you try my sample?

The script is there because your sample works. Also, could you remind me again where to set the virtual Path?

I even tried putting the jquery.updnWatermark.js in the root and adjusting the path accordingly - same result. I've been at this for hours so really appreciate your help.

daveharney · February 23rd, 2012, 11:59 PM

Hi Imar,

I recalled how to set the path in the properties for the site. It was "/mysite"
and I changed it to "/". Now the script works in the UC.

I'm still puzzled how this made such a difference versus using the "~/" notation. I thought that the "~" resolved a lot of these issues.

Thanks for giving me the clue!

February 24th, 2012, 01:37 AM

The watermark script loaded above link to a file folder, and then to the Scripts folder and a folder from the current page Kodak 10. Yes, does it?

Imar · February 25th, 2012, 04:50 PM

Quote:

I thought that the "~" resolved a lot of these issues.

Yes, but only for server side resources, as the ~ is resolved at the server. If you have a plain client side HTML element such as a <script> element it won't work.

Cheers,

Imar

daveharney · February 25th, 2012, 10:49 PM

Hi Imar,

Thanks again, that explanation makes sense.