Tag Info

Hot answers tagged

9

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: ...


6

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" /> ...


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 ...


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.


4

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; ...


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

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

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

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

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

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 ...


2

IE6 is not supported as an authoring browser in SP2010. Read more on the support levels for browsers on TechNet http://technet.microsoft.com/en-us/library/cc263526(office.14).aspx Just saw Randy Drisgill did a nice post on this subject as well: http://blog.drisgill.com/2009/11/sp2010-branding-tip-5-handling.html


2

Publishing sites in display mode should work in IE6. The problem is with the editing controls, ribbon, etc. which won't work properly. If you are still seeing problems with specific controls not looking quite right, you could use Control Adapters to target IE6 and modify the rendered HTML to work around any IE quirks. Generally, for publishing sites, you ...


2

I saw two good posts about this earlier in the year: http://blogs.msdn.com/b/maximeb/archive/2010/04/01/what-sharepoint-2010-looks-like-with-internet-explorer-6.aspx http://blogs.msdn.com/b/maximeb/archive/2010/07/30/what-can-work-with-internet-explorer-6-and-sharepoint-2010.aspx Tags will work, but there is so much other stufff that doesn't that it makes ...


2

In my case, the step that was missing was to add the website to my list of trusted sites in Internet Explorer. That takes the list of pre-requisites to: Enable the WebClient service in Windows (if you're using a Windows Server environment, you need to enable the Desktop Experience feature of Windows Server) Add the website to the Trusted Sites list in ...


2

Perhaps you've already solved this and moved on, but since I ended up here when searching for a solution and didn't find it, I better add my solution: A customer had exactly the same problem and the reason for it was that the customer is using a Language Pack (Swedish) on the site. Solution: Go to the user menu (upper right corner) and switch to English. ...


2

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 ...


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

I can confirm that it does it in my lab environment with using IE8... Vanilla 2013 install with default 2013 master. I'm guessing it's an IE8 limitation of not being able to process the gradient filter under zoomed condition. I'd probably write a custom CSS class to push a background color separately and see if that takes in scenarios where the gradient ...


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

Try using the following css code .yourcssclass{ background: url(fundraiser.jpg) no-repeat, -moz-linear-gradient(top, #ff3b68 0%, #0029d3 100%); /* FF3.6+ */ background: url(fundraiser.jpg) no-repeat, -webkit-gradient(linear, left top, left bottom, color-stop(0%,#ff3b68), color-stop(100%,#0029d3)); /* Chrome,Safari4+ */ background: ...


1

Currently, IE 10 (release preview) is not supported in SP 2010. In the meantime, try this. Press F12, to bring up the developer tools. In the Script tab, debug ewamoss.js file to see why you are getting a null reference. Supported browsers


1

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 }; ...


1

SharePoint does this by default. You can, however, override the page title with jQuery: http://www.sharepointjohn.com/sharepoint-2007-jquery-to-fix-ugly-page-titles/ You could use this solution to create a custom page head control that includes your JavaScript to override the page title: ...


1

You don't have async: false, on the first SPServices call to get the sites, so IE is probably just behaving as expected and continues to make the new requests without anything entered into subSites. I don't know why FF fails to run the request async, but that just shows you shouldn't use that if you want right behaviour


1

Well... its your custom branding. Both of these buttons rely on onclick events executing javascript so its likely something is causing a javascript error on the page. It could be that this error is happening before the click actually happens (i.e. page/modal load) so don't just look at the javascript that happens after the click. Use IE developer toolbar ...


1

If fonts aren't increasing in size, then you'll need to redefine the CSS for your site to use em as units for font size, rather than explicit pixel/point font sizes. Here's a post about the different font size units in use today: http://kyleschaeffer.com/best-practices/css-font-size-em-vs-px-vs-pt-vs/


1

The code you use looks ok... Does your browser allow you to save cookies? (Since cookies are stored client-side) If you need to be sure that every user uses this, you'll need a server-side solution like viewstate, session, database,... since not every user allows cookies! Cookies in Internet Explorer Cookies in Firefox Cookies in Opera Cookies in Netscape ...



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