Tag Info

New answers tagged

1

To change the locale for a specific site, go to the Site Settings area and select Regional Settings from the Site Administration group of links. For more options you can check: http://blog.funknstyle.com/2012/08/working-with-date-formats-in-sharepoint-2010/


0

Check my answer here you can use WebRun, we are using the Pro version and works great...


1

What do you mean by InfoPath is going away? Microsoft will support InfoPath till 2023. Yes you always has the flexibility to create Visual WebParts and deploy them with SharePoint. Using the JSOM is also not bad. If the shifting means some additional learning to you as well, then go with client side development. Because SharePoint will try its best to be a ...


0

It would be better if you create Custom aspx forms for list forms. As it would be easier for you to develop and deploy the forms to the SharePoint site. For reference how to create the Custom forms in Sharepoint designer 2013, you can follow: http://social.technet.microsoft.com/wiki/contents/articles/23955.sharepoint-2013-building-custom-forms.aspx ...


0

Use this as your CSS file: /* reset styles */ html, body, div, span, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, abbr, address, cite, code, del, dfn, em, img, ins, kbd, q, samp, small, strong, sub, sup, var, b, i, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, ...


2

I like John-o's answer, but if the HTML is simple enough that it won't be modified by SP, then go ahead and add it to the page. But my preference would be to add it via a content editor part, simply do to the fact that it makes it easier for other developers to figure out how the page was changed later on. (Meaning, if I am responsible for editing a page ...


3

The 'Edit Source' dialog frequently modifies the source that you enter before saving it to the page. You'll often find that custom classes, styles, spacing, markup, etc. are changed/modified/added/removed by SharePoint as it attempts to avoid possible conflicts. Simple solution to your scenario (a single page where you want some minimal customization) is to ...


1

Add the following CSS and reference it from your masterpage: <style> #aspnetForm[action*="Home.aspx"] #pageContentTitle {display:none;} </style> where Home.aspx is the page you want to hide the title from.


1

you can edit the page directly using sharepoint designer, then add your snippet of code directly, it will break the page definition... but that normally isn't a big deal.


-1

You could edit the page in SharePoint Designer, and add the CSS to the page.


3

You can easily add a content editor webpart and add in your CSS in the HTML editor. Or you can add your CSS to a text file, then using a content editor webpart, you can reference that text file and it will include the css in that page.


0

You can use The Open Data Protocol or OData to retrieve data from your SharePoint. OData is a Web Protocol created on top of Web technologies incluiding XML,Atom,JSON. So you can retrieve the information from your SharePoint using OData in form of Atom entries. You can take a look at the following ling from msdn blog. ...


0

It seems you are getting the proper wiki page content but you are missing styles defined in SharePoint CSS files as you mentioned earlier. In SharePoint 2013 the specified styles are declared in file: /_layouts/15/1033/styles/corev15.css


1

Try including the inline CSS to the body of the email. Use the max-width property for images inside the body's div. For ex. if you blog post body's div has a class 'ms-BlogPost' add css as: <style type='text/css'> div.ms-BlogPost img {max-width: 600px; } </style>


0

You could insert a Content Editor Web Part (CEWP) into the page and then create and upload a css style sheet where you assign attributes to the classes/parts you want and use "!important" -parameter on the attributes if they don't work. Example below: .class-name { attribute: value !important; } Then just enter the CEWP toolbox/options menu and ...


3

in your page make sure there is no reference to core.css.... issue is due to masterpage which has that reference that the page your using could be referencing the masterpage. several methods: 1) if its referencing a masterpage than make a custom masterpage that is almost the same only that it doesnt contain the core.css reference. 2) within your css add ...


1

I have noticed really similar problems with images and I ended up solving it by changing the name of the new image. Somehow if I made modifications to the image or changed it and replaced the old one with it while keeping the same name, the old image was still shown around insted of the new one. Don't know why it's happening, but I suspect it might be ...



Top 50 recent answers are included