Hot answers tagged

10

This and many more issues occurs in SP2010 when using IE10. This is because ASP.NET Framework 2.0 / 3.5 does not recognize IE10 as a valid browser and will handle it as an anonymous/disfunctional browser and disable javascript, silverlight etc. By installing KB2600100 on your hosting servers this issue should disappear. You can get it here: ...


10

Delete all the console.log lines from your script. It errors out until the console is open, which is why it suddenly works when you open the console


7

I've fixed it, or at least worked around it in a way that seems to solve all of our issues. When I added PDF icon support to our server, I used the following XML in the C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\XML\DOCICON.XML file, as suggested in the linked KB article: <Mapping Key="pdf" Value="pdficon.gif" /> ...


7

After long investigation I found solution. It is both SharePoint and IE 8 specific problem. IE 8 loads styles in different order, than IE 10. In IE 8, after my custom css, class .ms-core-needIEFilter was loaded. The class has gradient inside. I added to my custom CSS following code: .ms-core-needIEFilter #suiteBarLeft { background-color:transparent; ...


5

This seems to be a problem with the SharePoint client-side code, possibly as a result of changes to support branding. I have also seen it when trying to save a page I have edited. Your choices are: 1) Set your browser to use IE8 standards - you can do this by using F12 to get the IE developer tools panel and setting Document Mode to IE8 standards in the ...


5

I think the problem may be the console.log() line. With IE, (I believe) console is only available when the debugger is opened, thus an error is thrown if it is not. Replace console.log(Status) with alert(Status) and you hopefully will see it.


4

A good description on the browser support is here. Basically SP 2010 supports IE 7+ with 32 Bit and limited support on 64 bit. Also another things is that default SharePoint master page sets the document mode to IE 8 Compatible. So even you upgrade the browser, it will work on IE 8 Compatible document mode. It can be set with following code. <meta ...


4

Sorry, looks like the answer is no. No, this is a hard limit in SharePoint. Studying the schema of the content database reveals the limit originates from the primary key columns DirName and LeafName in the AllDocs table. The only way is to work around it by creating shorter names. They do offer a link to a tool to help (see source), but not sure if ...


4

This is caused by the installation of KB977724 when Office 2007 applications are also installed on the machine. There are further details about this problem on the Office Sustained Engineering site. A hotfix to this hotfix can be downloaded from Microsoft Download Center.


3

This fixed my problem.... 1) From Internet Explorer select Tools -> Internet Options -> Security tab 2) Select Local internet -> Sites -> Advanced -> 3) Under Add this website to the zone: type https://*.microsoftonline.com -> Add


3

A Couple of things you can try: In internet explorer, uncheck the "Enable Integrated Windows Authentication" box in the security options page. This doesn't actually disable it, it just forces NTLM. When the checkbox is clicked it will try to use Kerberos first, than it is supposed to fall back to NTLM (IE7+). I would also suggest loading up fiddler and ...


3

Try using "\\" before the username when you login to the sharepoint website from client machines.


3

There are some known issues with IE9 and SharePoint 2007's JavaScript, etc. You might set the IE Compatibility Mode meta tag in the master page so that it forces IE 9 to render in IE 7 or 8 mode: i.e: < meta http-equiv="X-UA-Compatible" content="IE=7" / > http://msdn.microsoft.com/en-us/library/cc288325(v=VS.85).aspx


3

Check this thread and answer for that: View PDFs in web browser Also consider the pros/cons for the approach (comments in the answer)


3

First off, you can use $().SPServices.SPGetQueryString rather than rolling your own Query String parser. Secondly, you should be able to just set the simple select and not worry about the hidden complex select. The $().SPServices.SPComplexToSimpleDropdown function takes care of updating the complex select under the covers. Finally, you shouldn't need any ...


3

IE will automatically log you in as the current Windows user if the site is in the Intranet zone in IE either by explicit reference in the Internet options|Security|Local Intranet|Sites|Advanced list of URL or by "Automatically Detect Intranet Network". You can change this by either removing the site from the intranet zone or by disabling automatic login in ...


3

Actually, you can set it up so that you can use the Rich Text in IE9 (some people believe you have to disable it completely)! You just have to override 3 functions in form.js (I created a file called form.ie9fix.js) and make sure it loads AFTER the "normal" form.js (or form.debug.js, whichever). The functions in question: RTE_DD_GetMenuFrame() ...


3

This is a notorious and well-known issue in SharePoint. Background Let me explain why it happens: SharePoint is a Microsoft product, as is Internet Explorer, and it's quite a customary thing when some features work in IE but don't work in other browsers. Other browsers always were and still are "partially supported" by SharePoint. This is what happens ...


3

The new page added in layouts folder "inplview.aspx". When paging, sorting or filtering happens there is an AJAX call to the inplview.aspx and it returns a JSON based result set. That is the rows of the defined list view webpart. The "inplview.aspx" generates the "inplviewhash" tag and appends it with "#" in url.


2

We are testing the same thing in our farm as well. we decide to turn on the Enterprise mode(EMIE). there are many things which are not working with IE 11 in native mode. datasheet view will not work with IE 11 trying to edit the page but it fails certain webpart properties can not modified. Workflow having the issue I would also recommend you to upgrade ...


2

SP2 provided support for IE10. Since you're rolling out IE11, rather than placing the site in Compatibility View, try IE11's Enterprise Mode: http://blogs.msdn.com/b/ie/archive/2014/04/02/stay-up-to-date-with-enterprise-mode-for-internet-explorer-11.aspx


2

This has nothing to do with any restriction of the internet explorer. This works by design of html. Your src="http://search/Pages/default.aspx" simply doesn't know that it has been loaded in an iframe. In order to get this work you need to add some javascript or modify the master page of your search center and add the following html tag in the header. ...


2

IE 11 will support all of the same features as IE 10, however IE 11 is only supported with SharePoint when the SharePoint site(s) is added to Compatibility View. There should be very little to no reason to explicitly test IE 11 functionality with SharePoint 2013.


2

I've also had trouble linking to shared drives in older SharePoint versions. It tends to flip all of my backslashes (\) to forward slashes (/), thus turning the file path into a URL. Sometimes this occurred while editing, sometimes after saving. To determine if this is the issue, hover over the link after saving or publishing to confirm all of your slashes ...


2

I decided to give one more search for the solution before I really ask for help ticket. Luckily I found something here that exactly match with my scenario. After reading through it I also realized that my I.E. crashes as soon as I hover through a User Online Presence Control. I did have Office 2013 installed on my computer. As the blog suggests I repaired ...


2

I can't tell you what part of SP decides when you should browse by navigating between pages, or when the start.aspx is used, but once start.aspx is used it uses the hash to store the location of where you are, in case you copy it and link a colleague. You can find some information in this blog post: ...


2

@DJ Monzyk this is a follow up javascript file as reference in previous answer function RTE_DD_GetMenuFrame() { var ifmMenu=null; var elemMenu=RTE_DD_GetMenuElement(); if (null !=elemMenu) { if (document.frames.length > 0) { ifmMenu=document.frames[g_strRTETextEditorPullDownMenuID]; } else ...


2

Try this: SP.UI.ModalDialog.RefreshPage(SP.UI.DialogResult.OK); Call this instead of location.reload(true);


2

Are you sure that you have registered the dialogReturnValueCallback, when you open the dialog? function openModalDialog(targetUrl) { var options = { url: targetUrl, title: 'Your Dialog', allowMaximize: true, showClose: true, width: 800, height: 600, dialogReturnValueCallback: onCloseCallback }; ...



Only top voted, non community-wiki answers of a minimum length are eligible