New answers tagged

0

You will have to add a column to your list view, then choose Type as Date and Time and put the default value as Today's Date. You create a new column under views in Library settings.


0

Create One Calculated type column and set data return formula type to Number and apply this formula: ="<img src='/_layouts/images/blank.gif' onload=""{"&" var day=new Date();"&" this.parentNode.innerHTML= day ;"&"}"">" You will current date and time.


0

You create the column as you'd like, and set the default value to Todays Date.


1

As @Aveenav is suggesting, it may be that your custom master page is missing the "ms-dialogHidden" CSS class on the navigation controls that is design to hide these elements in a modal dialog. From a sample master not the css class: <div class="ms-dialogHidden"> <SharePoint:AjaxDelta ID="DeltaTopNavigation" BlockElement="true" ...


0

Add 'ms-dialogHidden' class to nav and breadcrumb div or section.


0

I didn't found the solution but for dark reasons, it's working now. Howevever, I can tell that one of the procedures (or the combination of them), described in the body of my question, solved my issue. I think it's the part with the alternate access mapppings. In the "alternate access mappings collection" drowpdown list in the page with the same name, I ...


0

This happens because the order of items in the package influences the way the wsp/publishing process compiles the assemblies. Often you cannot get around that by adding assemblies to the "advanced" section. You need to unload the project and reorder the items in the Package.package xml file. Make sure the order of the references to items in different ...


1

I normally debug by attaching w3wp process. If you try running solution from visual studio it tries to deploy solution on virtual IIS and load it from there. In case of SharePoint that will not work.


0

No. there won't be any impact on your SP infrastructure. VS 2012 ULTIMATE/PROFESSIONAL is just a tool/IDE to enable a smooth SharePoint development experience. Using VS Versions, you would be developing SP solutions as packages [.wsp files], and using PowerShell or stsadm command line tools you would deploy on the SharePoint farm.Without VS, you wont be ...



Top 50 recent answers are included