Tag Info

New answers tagged

0

One possibility is that JavaScript could be adding the spans. Are you using any extra frameworks? i.e. Telerik, jQuery etc... I would remove everything except the essentials, check if this fixes it and slowly add back in everything until you see the spans again. Failing that create a simple aspx page separately and see if you are getting the same ...


0

You can add RichText Editor using following way also and it will make Embed Code action enable in ribbon. Designer <%@ Register TagPrefix="SharePointPublishing" Namespace="Microsoft.SharePoint.Publishing.WebControls" Assembly="Microsoft.SharePoint.Publishing, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> ...


0

A bit of trickery is to prepend the filenames with spaces and sort alphabetically


1

You could add a number column to the list, call it, say, "Sort Order", and then create a view that sorts on the values of your "Sort Order" column.


0

I have seen this before, my solution is that if your WebPart has any validator, you should fill some data to pass this/these validator(s) for saving your page. It often happens in SharePoint. Hope to help you.


0

/// <summary> /// Method to update users for a selected group for a given subsite (. /// </summary> /// <param name="userID"></param> /// <param name="updatetype"></param> private void UpdateUserInSharePointGroup(string userID, string updatetype) { ...


0

/// Method to update users for a selected group and subsite. /// </summary> /// <param name="userID"></param> /// <param name="updatetype"></param> private void UpdateUserInSharePointGroup(string userID, string updatetype) { SPSecurity.RunWithElevatedPrivileges(delegate() { using (SPSite ...


1

/// <summary> /// Method to add user to subsite /// </summary> /// <param name="userID" userID="domain\username"></param> protected void AddUserToSubsite(string userID) { try { SPUserToken sysToken = SPContext.Current.Site.SystemAccount.UserToken; SPSecurity.RunWithElevatedPrivileges(delegate { ...


0

This seems like library version is on. So the page you edit will only reflect to admin user. Unless and until you check in the page other users can't see changes.


0

Here's the final function I ended up using to add the web part: function addWebPart(webUrl, pageUrl,webPartXml,zoneId,zoneIndex, Success,Error){ var context = new SP.ClientContext(webUrl); var web = context.get_web(); var file = web.getFileByServerRelativeUrl(webUrl + pageUrl); var webPartMngr = ...


0

I found out that out-of-the-box if you set the chrome to none and minimize the webpart (via its own menu) it looks like it is not there. Workaround if you do not want to use coding.


0

I think it's a bug, but opening the site on IE compatibility mode resolves the problem.


0

It looks like SharePoint 2010 has some issues with IE 11, and in your case, web part properties cannot be modified and you get a weird looking web part property menu. To get around this, you'll need to run your site in compatibility mode. Here are some articles that have more info abut SharePoint 2010 and IE 11 problems and compatibility mode: SharePoint ...


0

Because you are using IE11, you will encounter these types of difficulties. You can open the site in compatibility mode in IE11, or use a different browser (Chrome, Firefox, etc) and it should work fine. We experienced this same issue when testing IE11 deployments in our organization, and ended up having to update everyone's settings to add our Intranet ...


0

x=$(".block .title h2 span#title").text(); If you have multiple spans then var arrSpanTitles = []; $(".block .title h2 span").each(function(){ arrSpanTitles.push($(this).text()); }); arrSpanTitle will contain all span titles


0

This isn't actually an attempt to answer (I just don't have the rep to simply post a comment to your question). Can you replace the link that you posted above with a screen shot of what the error looked like or maybe use the snipping tool. The link provided doesn't show the error just a huge log of information.


0

What PDF Viewer Web Part are you using? I have been working on a SharePoint 2013 site at work and don't have one called that specifically so I use the Content Editor Web Part instead. This may or may not work for the issue but I'll explain it either way. Go to edit mode on the desired page. Go to Insert, Web Part, scroll to Media and Content, select ...


0

First, you have to set the scope of you View element. FilesOnly will get you only the files within the selected folder. Default will get you the files of the selected folder and the subfolders. Then to specify the folder, add a parameter in SelectParameters for the XsltListViewWebPart element. <SelectParameters> <asp:Parameter ...


0

Not sure what is the problem but if you rewrite your try and catch to use correctly the SPWeb and SPSite objects you might get some helpful error. In your example you are disposing objects before catch. String str; SPSite oSPSite = null; SPWeb oSPWeb = null; try { oSPSite = new SPSite("http://server"); oSPWeb = oSPSite.OpenWeb(..); str = ...


1

I'm afraid you miss-use the AAM. AAM are intended to set different absolute URL, but keeping all relative URL the same. SP uses two kinds od URLs in links, dynamic JavaScript code, etc: absolute URL (e.g. http://server/sites/site01) and relative URLs (e.g. /sites/site01). AAM are needed for SP for it to know two or more base addresses can be used with ...


0

Maybe I am missing something but why not add a list view web part for each view and use a simple JavaScript to hide or show only the views you are interested in seeing. If this sounds like a solution for you leave a comment and I will send you or post here a script I wrote that simulates tabs for the list view web parts on a page.


1

This would have worked with other types of webparts, e.g. $PLwebpart = New-Object Microsoft.SharePoint.WebPartPages.XsltListViewWebPart However, the TilesViewWebPart class is abstract, which means that you cannot instantiate it. You would have to do something like creating a class library to implement the webpart, and then use the .dll to add an instance ...


0

StartRow and RowLimit are supported, though I haven't looked to see if they are supported in the OOB Web parts.


0

Well I don't think you are going to be able to use the built in web part, as it references the lists on the blog subsite. What we did to solve this, was to use a content Query webpart with custom XSL to change the layout. Here are some links: Blog Post with good Explanation or just do a google search: ...


0

You can also try to use webpart connections (Filter by URL). To do it, Add the Context filter WebPart to Posts.aspx (URL) Edit it. In "Parameter Name" type ID Click Ok Click Edit webpart -> Connections - > Send Values to -> Posts On the popup, select Filter by (second option) Select ID. Click Finish. It should solve your problem even if you change the ...


0

You can use content query webpart ,where you can display list from the parent-site and add the columns as per your requirement.


2

This is what we are using currently in one of our projects to check if a page is in edit mode or not: // An accesser indicating whether or not the current page is in design mode. function inDesignMode () { var result = (window.MSOWebPartPageFormName != undefined) && ((document.forms[window.MSOWebPartPageFormName] && ...


2

Try the following: if (document.forms["aspnetForm"]["MSOLayout_InDesignMode"].value == 1) { //do your stuff } If you want to be sure-sure, you can double check with this property: document.forms["aspnetForm"]["MSOSPWebPartManager_DisplayModeName"].value which should have a value of "Design" if a page is in edit mode, or "Browse" if it's in display ...


0

The List View Web Part can be saved from the parent site as either a file or directly to the Web Part gallery. After that the web part can be added to the sub site. See http://sharepointontop.blogspot.com/2012/06/show-listview-webpart-from-parent-site.html for detailed instructions.


0

Not sure if it is useful for you, you may try something like this using jQuery: $('#s4-workspace').animate({ scrollTop: $("#divID").offset().top - 80 }, 0);


0

You can use WebPartPages:XsltListViewWebPart from <%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> with code: var view = web.TryGetView("listname"); var list = view.ParentList; var web = list.ParentWeb; ...


0

You should use the methode GetList(url) or Lists[GUID] instead of Lists["listName"]. var list = context.web.GetList("/mySite/Lists/sysCurrentUserInstance"); To quote Best Practices for SP OM: You can retrieve an SPList object from the SPWeb.Lists property by using the list's GUID or display name as an indexer. Using SPWeb.Lists[GUID] and ...


0

Your problem is that var list = context.web.Lists["sysCurrentUserInstance"] uses the title of the list. If this can vary, this is not a good method to use then. If the list url inside of the site will not change you can use string listUrl = "/sites/sitecollection/subsite/Lists/Announcements"; SPList list = web.GetList(listUrl); ...


0

Check your list internal name in both environment. or try another way var list = web.get_lists().getByTitle("ListInternalName");


0

Its a Posts web part available under Blog site template. For adding this webpart see the following steps here: http://stevemannspath.blogspot.com/2013/10/sharepoint-2013-adding-blog-to-existing.html


0

You're including a WebPartManager in your app part, and presumably there's already one on the page you're adding it to. These load various bits of JavaScript, and if I recall correctly having more than one per page causes problems. You might see JavaScript errors if you open your browser's developer tools. You could try removing the the WebPartManager from ...


1

Tinkering around to fix it in the database is not recommended or supported. The old stand by is to navigate to your web part page and add ?contents=1 to the end of the URL. Here you can delete the corrupt web part. Then go back to your web part page and add it back. You can always try exporting the web part from the site it is working in and importing it ...



Top 50 recent answers are included