Tag Info

New answers tagged

2

If all these pages are on the same site you could look at using the sites property bag. Read in Property Bag values var ctx = new SP.ClientContext.get_current(); var site = ctx.get_site(); var web = site.get_rootWeb(); var webProp = web.get_allProperties(); ctx.load(web); ctx.load(this.props); ctx.executeQueryAsync(); To set the property ...


3

You can access the Site's Property Bag using the JavaScript Client Object Model. Here's a walkthrough: http://www.jeremythake.com/2013/10/using-the-sharepoint-csom-api-to-get-a-property-bag-value/


2

A few options: Write the value to a list on the site (it may only have a couple of columns and a single row if it's just storing one value) and read that. Create a single frame in the window and use JavaScript to navigate through the pages. You can either read from this frame's JavaScript or by tacking a query string onto the links on the page and reading ...


0

If you are using SharePoint 2010, SharePoint does special formatting to content editor web-parts. You have two options Use an HTML Form Webpart. SharePoint will not modify the contents of this webpart and it will work like a content editor webpart working in SharePoint 2007 and prior. Use a .txt file which you store your content in and link to it with ...


0

If they are audiences and not AD groups or Sharepoint groups, then it is probably an underlying GUID mismatch and it can't be resolved. While named the same, they have unique GUIDs under the hood on the Devs machine and the QA/Prod environment. This is most likely where the problem is. At a previous employer, they had news which was heavily reliant on ...


3

As Pradip has already told the reason for this behaviour I won't repeat it here again. But there are a couple of things you can try. Have a look at this article, Inconvenient Content Query Web Part and server-relative URLs, which suggests - Another way to get around this issue is to use a Feature Receiver. After activating the Feature that provisions ...


2

If you enter a URL into the Content Editor Web Part as a relative link, the link converts to an absolute URL when the entry is saved. This automatic conversion can be an issue if you are deploying content from a staging environment to production, where absolute URLs reference the original server's name. To address this automatic conversion issue, You ...


2

Since in SharePoint 2013 CSOM API was introduced SP.Publishing.Navigation namespace, the following example demonstrates how to create a publishing page. How to create a publishing page via SharePoint 2013 JSOM function createPublishingPage(pageName,pageLayout) { var ctx = SP.ClientContext.get_current(); var pubWeb = ...


0

It seems like a limitation of embed tag. You can use an iframe instead <iframe id="ExampleEmbed" src="somfile" height="850" width="850"></iframe> <script> function ChangeSrc(qsValue) { document.getElementById("ExampleEmbed").src=qsValue; } </script> Update <div id="embedDiv"> <object> <embed ...


0

You can do this through javascript. If you pass the querystring in the URL, you can fetch it with javascript and update the embed element. How to get querystring. Code from answer, below: function getParameterByName(name) { name = name.replace(/[\[]/, "\\[").replace(/[\]]/, "\\]"); var regex = new RegExp("[\\?&]" + name + "=([^&#]*)"), ...



Top 50 recent answers are included