datepicker problem in side the master page

Question

0.00/5 (No votes)

See more:

hello .net and jquery experts . i need one help
Sir i am using three tier architecture. and one master page .
and come contents pages .
my project is working but my problem is that once i create datepicker on the master page so it is not working .
if i create a simple page a part of three tier architecture and write the same codes on the source code so it works but it does not work on three tier architecture.
why is it happening please reply

Posted 6-Aug-15 1:43am

faizyab 2009

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

F-ES Sitecore · Answer 1 · 2015-08-06T01:59:00

99% of problems with master pages are down to three things 1) you don't appreciate that javascript runs on the *client*, it works of the html your server code renders so you need to view the source of the page to work out why things aren't working, what is in your aspx markup files is irrelevant 2) the master page executes in the context of the *child* page, not its location in the solution tree so any relative paths in the markeup won't work 3) .net controls the IDs of your elements so they aren't what you think they are going to be (see point 1).