Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I'm having problems with the DatePicker in SP2013. The control shows fine, but the calendar popup is broken because of a missing stylesheet (the complete sprite sheet image is visible etc.).

The css missing is corev15app.css. It should have been returned by the _layouts/15/defaultcss.ashx handler called in the calendar iframe source, however this fails. Here is the related log output:

defaultcss.ashx: resource specified null
defaultcss.ashx: attempting to get web.MasterCssUrl
defaultcss.ashx: using elevated codepath to get css file or other resource because the non-elevated code path failed to get it. (...)
defaultcss.ashx: attempting to get web.MasterCssUrl
Application error when access /_layouts/15/defaultcss.ashx, Error=The object specified does not belong to a list.

Additional info: I upgraded a SharePoint 2010 solution, set up new layout pages and used the new seattle master page from SP2013. Just about everything works as it should. However the DatePicker and the "Add an app" page (addanapp.aspx) fails. The app page just stops with the loading animation.

share|improve this question
add comment

1 Answer 1

up vote 1 down vote accepted

It seems that the problem arise when your master pages are not located in the Master Page Gallery. The problem went away when I added the master page to the master page gallery and referenced it from there (i.e. _catalog/masterpage/mymasterpage.master) instead of the _layouts folder. The actual server deployment location of the master page is still in the layouts folder (could also be the feature directory itself).

I added a new module that adds the master pages to the site collection gallery, updated code that sets default master page and that fixed the tedious datepicker calendar problem.

I speculate that this might be related to new security measures regarding iframes (the datepicker control pops up an iframed calendar).

share|improve this answer
    
doing this did not solve my problem - same issue but my master page is already in the _catalogs folder. –  Matt Nov 8 '13 at 21:44
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.