SharePoint 2010 File Size Upload Limits – The Essential Mix

​Clearly there are a lot of articles & posts on net regarding increasing File Size Upload limits in SharePoint. Unfortunately I couldn’t find any one that was comprehensive enough to include ALL the tweaks you need to consider to accomplish the goal, on both the SharePoint and IIS level. So here’s mine:

Errors Encountered:
- “Page cannot be displayed” when uploading large files
- Error 0x800700DF: The file size exceeds the limit allowed and cannot be saved
- The specified file is larger than the maximum supported file size

1. Setting File Size Upload Limits on a Web Application

1. Login to Central Admin and navigate to Central Administration -> Application Management -> Manage Web Applications.
2. Once there highlight the web application that you want to change and then click on general settings:
clip_image001

3. Once in general settings scroll to the bottom of the list and you will see the maximum upload size the default setting is 50mb this can be can set to a maximum size of 2047mb (2GB). If you try to go beyond this it does flag up and tell you that you have exceeded the Maximum size.
clip_image002

2. Changing the Web.config file in the IIS Root Folder of Each Web Application

Independently of the SharePoint Web Application file size upload limit Central Admin steps described above, we need to also manually (backup with a copy first) open up the Web.config XML file located in the root folder of each web applications IIS Website.

1. Open the Internet Information Server (IIS) management console on the server desktop
2. Open the Websites tree node on the left 3. Select the website(s) one at a time and go to their root folder by clicking “Open in Explorer View”
3. Locate the web.config file in the folder and make a copy of it (generally acceptable to leave a copy with a name like “web_backup.config” in the root folder) in case it becomes corrupted while you’re editing it.
4. Open the web.config file with NotePad and change the value in the following node from the default of 50MB (expressed in KB):

<httpRuntime maxRequestLength=”51200″ />
..to a new value, e.g. 200 MB:
<httpRuntime maxRequestLength=”204800″ />

If you are not a math fan (like me), you can easily do the KB / MB / GB calculation (sorry, Bing doesn’t seem to want to help on this one!) by just typing in “200 MB in kilobytes” into Google.
5. IMPORTANT: Repeat the same settings configurations for each server in the SharePoint farm. Web.config’s are just plain XML files and when we are manually mucking about with them there is nothing to tell their sister .config files on the other SharePoint servers in the farm to reflect those changes. You want to avoid inconsistent settings between servers.

Notes on these steps:
- services will be briefly interrupted to SharePoint at the moment you click “Save” in Notepad as it will induce an application pool recycle
- make sure not to dilly dally when you have any particular web.config open in Notepad; it is possible that other processes could potentially may want to modify the config file while you’re using it. Get in and get out like that mission in Grenada.

3. Increase the IIS7 Machine-level Request Length Setting

1. Open an Administrative Command Prompt on each SharePoint server desktop
2. Enter the following command, entering the value in BYTES (not kilobytes this time) at the end:
%windir%\system32\inetsrv\appcmd set config -section:requestFiltering -requestLimits.maxAllowedContentLength:209715200

You will receive a confirmation message after applying the command. Please bear in mind that you will need to run the cmd.exe in administrator mode.
clip_image004

Notes on these steps:
- services will be briefly interrupted to SharePoint at the moment you click “Save” in Notepad as it will induce an application pool recycle

4. Increase the IIS7 Application Pool Idle Time-out Settings (Optional)

IIS7 sets application pools to “time-out” after 20 minutes of inactivity. So if you don’t have a visitor to your site within 20 minutes the application pool will shut down – freeing up those system resources. Then the next time a request comes into the site IIS7 will automatically restart the application pool and serve up the requested pages.

This is a great way to preserve resources since every running application pool does place a certain amount of overhead on the system. But, it also means that the first request – the one that causes the application pool to restart – is very slow. It is slow because the process literally needs to start, then load the required assemblies (like .NET) then load the requested pages. Depending on the size and complexity of your application, this might just be a couple of seconds or it might take 30+ seconds (during which time a user would likely give up and move on to a different site).

If you want to extend the length of the time-out setting, just change it from the default of 20 to however many minutes you want. You can also adjust the setting to 0 (zero) which effectively disables the timeout so that the application pool will never shut down due to being idle.

1. Open Server Manager & Expand the Roles node
2. Expand the Web Server (IIS) node. Then click on the Web Server (IIS) node
3. Expand the node with your local server name
4. and click on the Application Pools icon. You’ll then see a list of the application pools that are defined on your server. In the right-hand pane you’ll see an option for Advanced Settings – click that.
clip_image005

5. Once you see the Advanced Settings dialog box just look for the Idle Time-out (minutes) property; click where the default “20″ is, and change it to whatever value you prefer.

Notes on these steps:
- you need to monitor & plan resource consumption; the idle timeout mechanism is there for the health of the overall system so that idle applications don’t chew up memory needlessly. Setting a huge timeout may be great for allowing big uploads but you need to make sure it’s not throwing resource consumption patterns off kilter in other areas.

5. Increase the IIS7 Connection Timeout Length (Optional)

One more thing to keep in mind is the connection timeout settings: When you upload large files, depending on your connection speed it can happen that the connection times out. If you want, you can increase the connection timeout to a larger value. The standard is 120 seconds. This step is optional, but can become required if you have users with low speed internet connections.

1. Open IIS
2. Select the Web Application
3. Click on Advanced Settings
4. Expand Connection Limits
5. Set the new value for Connection Time-out (seconds)

clip_image008

6. Increase the Web Client File Size Limit

When you upload a large file (over 50Mb usually) to SharePoint 2010, you might get an “Error 0x800700DF: The file size exceeds the limit allowed and cannot be saved” message. Check your  current SharePoint file size upload quota and web.config settings. If the quota is not a problem, then the error is most likely caused by a local restriction set on Web Client service. By default, Web Client file size limit is set to 47Mb or so. To increase this limit:

1. Open Windows Registry using regedit command
2. BACKUP THE REGISTRY!
3. Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
4. Right click on the FileSizeLimitInBytes and click Modify
5. Click on Decimal, and type 4294967295 and click OK
6. Restart Web Client service by typing services.msc.

This will increase the Web Client file size limit to 4Gb, which is a maximum file size you can upload using WebDAV. Please note, that this will only address Web Client service restrictions, and will not increase your SharePoint quota .. you still need to address those points approriately as per the linked MSDN blog post above.

It is also of note that the SharePoint max, cannot raise, hardcoded file size limit is 2GB, period, so raising to 4Gb is essentially overkill. ;)

p.s Don’t forget, if you want to use WebDAV effectively in SharePoint, you will need to have the Desktop Experience feature turned on in Win2k8 – you’ll run into inexplicable intermittent transfer drops otherwise.
That’s it!

clip_image010

7. Increase the SQL Chunk Size for Large Files

The large-file-chunk-size property sets the amount of data that can be read from server running SQL Server at one time. If you have a file that is greater than your chunk size (such as 70 MB when the chunk size is set to 5 MB), the file would be read in 14 chunks (70 / 5).
The chunk size is not related to the maximum upload file size. The chunk size simply specifies the amount of data that can be read from a file at one time. By default, the large-file-chunk-size property is set to 5 MB. If you notice performance or scale problems on the client or server, then you may need to tune this setting to get the performance you are targeting.

1.The large?file?chunk?size property must be set from the command line. This property is configured for a server or server farm, and cannot be configured for an individual virtual server. To set this property, use the following syntax:

Stsadm.exe ?o setproperty ?pn large?file?chunk?size ?pv <size in bytes>

2. After making a change to this property, you must restart IIS. You can restart IIS by typing iisreset on the command line.

Notes on this section
-if you raise the chunk size too high, the files might use up too much front-end memory and you may need to lower this setting.

Notes & Caveats

-2047MB is the limit you can use for uploading files. RBS does not get around this either. If you upload the 2GB file and watch you w3wp.exe worker process it will consume this extra memory so it’s not a good idea to do huge uploads it will stop other request to the server (IIS web site at least).
- the IIS7 worker process w3wp.exe has a 4GB limit therefore as the upload would need all the memory to perform an upload. 2GB is a safety limit enforced by SharePoint.

Incoming search terms:

Hide / Remove Quick Launch, Main Menu, Ribbon Bar SharePoint 2010

SharePoint 2010 introduced some more context-aware UI treats.

In case you need to write a new ASPX which you want to display as popup, or you just need it stripped down with less bells and whistles, just add a query string value to the URL references.

Same default.master, just that SP 2010 allows you to hide left navigation (quick launch), main menu, social widgets, welcome menu and top bar just by adding the Querystring parameter ?IsDlg=1 to the URL. Of course if there is already a base ?parameter on the URL you need to minimize, just add &IsDlg=1 to the end of the URL instead.

i.e. http://intranet.contoso.com/_layouts/create.aspx?IsDlg=1

or

http://intranet.contoso.com/_layouts/create.aspx?SomeExistingParameter=foo&IsDlg=1

Incoming search terms:

Get Check-in Comments with Nintex

NOTE: I’ve posted a revised version of this type of method for getting version history. The SQL in this post is not to be trusted! (but the rest is still good so I’ll leave the post as-is for posterity).

I needed to grab the document check-in comment insides of a Nintex 2010 / SharePoint 2010 list workflow. I couldn’t seem to locate the field anywhere Was told by Nintex support the following:

“It is not possible to reference the version history of a document within a workflow similar to how you can reference standard SharePoint fields. Even the web service method GetVersionCollection: http://msdn.microsoft.com/en-us/library/lists.lists.getversioncollection(v=office.12).aspx only returns the version history for a specific field. There may be another web service Microsoft exposes to enable this however this would be a question directly for MS.”

Oh well, right? Never say die! Use the Execute SQL Query widget in Nintex and let’s do some data mining:

1. Add an Execute SQL Query action to wherever in your Nintex workflow you need to access the Check-in comment.

2. Create a variable to store the check-in comment, in this case I call it vCheckInComment.

3. Add your SQL connection string. Considering that using Windows Authentication is probably what you’re going to be dealing with when using SharePoint, you will need the DB service account credentials.

4. Create your SQL query. For getting the check-in comments it is simple : In your SharePoint Content database there will be a table called AllDocs which contains two columns of interest: LeafName and CheckInComment.  You Can also grab the ListID GUID in there if needed – in this example I am already inside a Query List / For Each loop which has filtered the records based on the current list I am working with. The LeafName column stores the document e.g. MyDocument.doc. The CheckInComment column stores the comment for that file. In this example the {WorkflowVariable:vDocumentName} Nintex variable is my document name variable:

And that’s that – the check-in comment query associated with that documents record goes in the vCheckInComment column.

Disclaimer: there’s much more to the DB structure then just the document name and check-in comment. Versioning isn’t this simple. Also, running ad-hoc SQL queries on SharePoint is generally not best practice and you will get chewed out by MVP’s.  Reasons why ad-hoc SQL is bad news (see http://www.sharepoint4arabs.com/AymanElHattab/Lists/Posts/Post.aspx?ID=99 for a good summary)

  1. This is completely unsupported by the EULA you agreed to when you installed SharePoint.
  2. Your queries are not guaranteed to work after applying any patches or service packs to SharePoint since Microsoft could change the database schema anytime.
  3. Directly querying the database can place extra load on a server and hence performance issues.
  4. Direct SELECT statements against the database take shared read locks at the default transaction level so your custom queries might cause deadlocks and hence stability issues.
  5. Your custom queries might lead to incorrect data being retrieved.

Definitely run your SQL queries with NoLock on and keep it to simple, read-only queries if you’re going to pull stunts like running SQL queries from Nintex as described in this post. Also carefully consider versioning and data commit issues inherent from the SharePoint architecture side of things before counting on any of the results you pull out as gospel.

Incoming search terms:

User Profile Synch SharePoint 2010 – The Essential Mix

While I detailed my findings on initial pre-deploy Best Practices in my post Planning SharePoint 2010 User Profile Synchronization , I have since banged out a more organized reading list figured out through more hands-on. You may start UPS in SP 2010 as confident pro but but you’ll end with the thousand yard stare, UNLESS you follow the exact advice presented by the nice folks in the following list, in the order indicated:

1. Make sure you have the SharePoint 2010 August CU (build 14.0.5123.5000 ). Todd Klindt’s complete SharePoint 2010 build number list is here. I personally can’t vouch for newer CU’s as I haven’t tried yet but will post in the future when I learn more about the stablity of those CU’s.

2. Read Technet’s Configure profile synchronization (SharePoint Server 2010)   end-to-end. Do not do the worksheets component at the beginning yet – we will get to those when the basic synch service is up and running smoothly. Do not execute any of the config suggested in that article yet- just breeze through it, familliarize yourself with the config sections they are referring to, but just don’t set anything up yet.

3. Read and execute the steps described on Spencer Harbar’s guide at http://www.harbar.net/articles/sp2010ups.aspx . As he indicates in his follow-up troubleshooting guide at http://www.harbar.net/articles/sp2010ups2.aspx you need to follow the instructions exactly:

I must stress that the number one reason people have problems is that
they do not follow the procedure! No really, I can’t count the number of
times steps have been missed or I get a response like “oh, I didn’t
think I needed to do that”. If you follow the procedure you will be
successful unless you are hitting an environmental or other known issue.

.. but wait! Not everyone is a super MVP like Spencer so a lot of the little details he refers to will actually be more complex for those who have perhaps have dived straight into SharePoint without a lot of Windows SysAdmin experience. So if you find gaps in your understanding of Spencers instructions, refer to the following article by Microsoft Support Escalation Engineer Steve Chen in point 4. Heck, read it regardless.

If you are at any point not clear on user accounts and rights, refer to Sean Wallbridge’s guidance on SharePoint 2010 Server User Accounts

4.
Steve Chens User Profile Sync articleIn particular sections like detailing how to Grant Replicating Directory Permission in AD will help people who are new to the SysAdmin.

5. At this point you should have your two ForeFront Windows services up and started, and be able to access Central Administration > Synchronization Connections etc. normally. If not, or something else has blown out, do not pass go, do not collect $200 : return to Spencers troubleshooting article and be very sad because you very likely did not pay close enough attention to the steps involved.

6. Read Technet’s Plan for User Profile Synchronization

7. Grab theUser profile properties and profile synchronization planning worksheets for SharePoint Server 2010 , forget about being an environmentally friendly, paperless SharePoint zealot and print those suckers out. Post ‘em all over your cube, your bathroom, wherever. Make sure you run through them even if it’s not a mega enterprise deployment you are creating.

8. Deploy!

The preceding links are essential to avoid your first SharePoint 2010 User Profile Synchronization attempt turning into a headbanger where grown men stare anxiously at little service start status indicators.

 

Incoming search terms:

Save As Template for Publishing Site SharePoint 2010

If the publishing feature is enabled on a site in SP 2010, the Save As Template option becomes no longer available. This is because it’s not actually a Microsoft best practice to save Publishing Sites as Templates as there are a number of inherent issues with the process.

If you want to live on the wild side and get ‘er done anyways – get that publishing site saved as a template by appending the following to your base site URL:

/_layouts/SaveTmpl.aspx

..so https://go.site.com/sites/subsite/ becomes https://go.site.com/sites/subsite/_layouts/SaveTmpl.aspx, and you are officially on the side of the rebels.

Incoming search terms:

Synonyms not working in SharePoint Search

The custom thesaurus functionality of SharePoint search should be old hat to those of us experienced with MS Full Text Search, which is a mature technology that’s been around for years. What may trip you up in trying to get custom synonyms working with SharePoint’s implementation is the nuances of the file paths and deployment across multiple physical servers in a farm.

A basic example of the thesaurus format is as follows. This one would match instances of “it” to “information technology”

<XML ID="Microsoft Search Thesaurus">
    <thesaurus xmlns="x-schema:tsSchema.xml">
 <diacritics_sensitive>1</diacritics_sensitive>
        <expansion>
            <sub>it</sub>
            <sub>information technology</sub>
        </expansion>
    </thesaurus>
</XML>

First, does your thesaurus file validate as proper XML? Sometimes a forgotten –> closing tag etc. can be a showstopper.

Thesaurus files are stored in several locations on a SharePoint Server:

 \ Program Files \ Microsoft Office Servers \ 14.0 \ Data \ Config \ 

Updates to the thesaurus files here will ensure that any new Search Service Applications that you create will have the updated thesaurus definitions when they spin up.

 \ Program Files \ Microsoft Office Servers \ 14.0 \ Data \ Applications \ Config \ 

GUID is the guid of your Search Service Application, which you can get by using Get-SPServiceApplication. That powershell command will list your service applications and their corresponding GUID’s.

When you’ve verified your updated tsneu.xml files are in those locations, you’ll need to restart the search service with these commands:

net stop osearch
net start osearch

Once the service is restarted, go to your search center and plug in one of the newly added expansion/replacement terms to see your results.

If you’re running search on multiple servers, you will need to perform these steps on each server running search. If there are multiple search applications running, you have to copy your thesaurus files to each config directory under the GUID folder for each search service application.

You can run into the following situation when trying to get a custom thesaurus to kick in for the SharePoint search service:

1. You set up the thesaurus file(s), in our example we’ll use the basic tsneu.xml, which is the language-neutral default thesauraus.
2. You try putting the thesaurus XML file into

%ProgramFiles% \ Microsoft Office Servers \ 14.0 \ Data \ Applications \ Config \

and in

%ProgramFiles% \ Microsoft Office Servers \ 14.0 \ Data \ office servers \ applications \ data \ 

but with no luck – you don’t see the search results.
3. You try creating a folder on each query/crawl server with the GUID of the search application.
4. Restart the services.

Still no synonyms? It may be that you have partitioned the index, in which case the path changes, and it´s not the default one but the one you set up into the Central Administration > Manage search topology.

Chang the files there, restart the search service and voila!

Incoming search terms:

Firefox Friday #2 – SharePoint & Firefox

​Firefox does have issues when being used with SharePoint, let’s ID the known issues and workarounds:

Feature

Limitation

Connect to Outlook, Connect to Office, and Sync to
SharePoint Workspace

Works with an
ActiveX control, but requires a Firefox control adaptor. Microsoft Office
2010 does not provide a Firefox control adaptor for this control. The feature
also requires an application that is compatible with the stssync:// protocol,
such as Microsoft Outlook.

Datasheet view

Requires an
ActiveX control, such as the one that is delivered in Microsoft Office 2010,
and a Firefox control adaptor. Microsoft Office 2010 does not provide a
Firefox control adaptor for this control.

Drag and Drop Web Parts

Cannot be moved by
using drag and drop on Web Part pages. Users must click Edit on the Web Part, select Modify Web Part, and then select the zone
from the Layout section of the Web Part
properties page. Web Parts can be moved using drag and drop on Pages.

Edit in Microsoft Office application

Requires an
ActiveX control, such as the one that is delivered in SharePoint Server 2010,
and a Firefox control adaptor. For more information about Microsoft Office
2010 Firefox Plug-in, see FFWinPlugin Plug-in
(http://go.microsoft.com/fwlink/p/?LinkId=199867).
If you install and configure the Office Web Applications on the server, the
Edit functionality works and you can modify Office documents in your browser.
This functionality only works with Microsoft Office 2010 or an equivalent
product together with a Firefox plug-in.

Explorer view

Removed in
SharePoint Server 2010. Libraries that have been upgraded from earlier
versions of SharePoint Server 2010 may still have Explorer views, and these
may not work. Explorer view requires Internet Explorer.

Export to Excel

Downloads a file
with an .iqy extension to the Web browser. If Microsoft Excel is not
installed, and if no other application is configured to open this file, then
this feature will not work.

File upload and copy

Requires an
ActiveX control, such as the one that is delivered in Microsoft Office 2010,
and a Firefox control adaptor. Microsoft Office 2010 does not provide a
Firefox control adaptor for this control.

Microsoft InfoPath 2010 integration

Requires an
ActiveX control, such as the one that is delivered in Microsoft Office 2010,
and a Firefox control adaptor. Microsoft Office 2010 does not provide a
Firefox control adaptor for this control.

Microsoft PowerPoint 2010 Picture Library
integration

Requires an
ActiveX control, such as the one that is delivered in Microsoft Office 2010,
and a Firefox control adaptor. Microsoft Office 2010 does not provide a
Firefox control adaptor for this control. The user can use the following
workarounds when no control has been installed:

  • If a user wants to upload
    multiple pictures in a picture library, the user must upload one picture
    at a time by using Upload.aspx.
  • If a user wants to edit a
    picture in a picture library, the user must download the picture, edit
    it, and then upload the picture to the picture library.
  • If a user wants to download
    more than one picture from a picture library, the user must download one
    picture at a time by clicking on the picture link.

Microsoft Visio 2010 diagram creation

Requires an
ActiveX control, such as the one delivered in Microsoft Office 2010, and a
Firefox control adaptor. Microsoft Office 2010 does not provide a Firefox
control adaptor for this control.

New Document

Requires an
ActiveX control, such as the one delivered in Microsoft Office 2010, and a
Firefox control adaptor. For more information about Microsoft Office 2010
Firefox Plug-in, see FFWinPlugin
Plug-in
(http://go.microsoft.com/fwlink/p/?LinkId=199867).
Although the New Document command may
not work, you can use the Upload Document functionality. If you install and
configure Office Web Applications on the server, the New Document command works, and you can create an Office
document in your browser.

Rich Text Editor – Basic Toolbar

A user can update
the Rich Text Editor basic toolbar to a Full Rich Text Editor that includes
the ribbon by changing the field’s properties, as follows: On the
FldEdit.aspx, in the List Settings
menu, select Specific Field Settings.
Next, under Columns, click Description. In the Additional Columns Settings section, under Specify the type of text to allow, select Enhanced rich text (Rich text with pictures, tables,
and hyperlinks)
.

Send To

Can leverage an
ActiveX control, such as the one that is delivered in Microsoft Office 2010,
and a Firefox control adaptor. Microsoft Office 2010 does not provide a
Firefox control adaptor for this control. Without the control, files cannot
be sent from one SharePoint farm to another SharePoint farm. However, files
can still be sent from one site to another site.

Signing Forms (InfoPath Form Services)

Requires an
ActiveX control, such as the one that is delivered in Microsoft Office 2010,
and a Firefox control adaptor. Microsoft Office 2010 does not provide a
Firefox control adaptor for this control.

Spreadsheet and Database integration

Require ActiveX
controls, such as those that are delivered in Microsoft Office 2010, and
Firefox control adaptors. Microsoft Office 2010 does not provide a Firefox
control adaptor for this control. The user can use the following workarounds
when no control has been installed:

  • If a user wants to edit a
    document, the user must download the document, edit it, and then save it
    back to the server.
  • In a list that requires a
    document to be checked out for editing, a user must use the
    Edit menu to check out the
    document, edit it, and then check it in by using the
    Edit menu.
  • Export to spreadsheet.
    Users can export a SharePoint list as a spreadsheet by clicking
    Export to
    Spreadsheet
    on
    the
    List
    tab on the ribbon.

Web Part to Web Part Connections

May require
deactivation of browsers pop-up blockers for SharePoint sites.

Slide library and PowerPoint 2010 integration

Require ActiveX
controls, such as those that are delivered in Microsoft Office 2010, and
Firefox control adaptors. Microsoft Office 2010 does not provide a Firefox
control adaptor for this control. The user can use the following workarounds
when no control has been installed:

  • Delete a slide. Users can
    delete a slide by first clicking the slide, and then clicking
    Delete
    Slide
    . Repeat
    for each slide.

The following
features do not work on this platform:

  • Copy a slide to a
    presentation. This feature enables users to add a slide to a PowerPoint
    2010 presentation.
  • Publish a slide. This
    feature enables users to upload a single slide from a PowerPoint 2010
    presentation to a slide library. Microsoft Office must be installed on
    the client computer.

 


Incoming search terms:

Firefox Friday #1 – Useful Plugins for SharePoint Development

As SharePoint developers we are bound to IE but often fallback to other browsers for various reasons such as performance, HTML standards compliance, or in my case with Firefox – the plugins available.   The official Technet on what is and is not supported on various browsers (Chrome is notably not even in there): http://technet.microsoft.com/en-us/library/cc263526.aspx. I will follow up this post with a list of what specifically will not work with SharePoint when using Firefox (so you can’t say I didn’t warn you!)

While Google Chrome is definitely a solid choice, if you are using Firefox the following plugins will help you out:

FasterFox Plugin

Download: http://fasterfox.mozdev.org/
Description:
Various network tweaks that deliver a zippy experience. This will also speed up your SharePoint user experience greatly too.

  • Prefetch Links
    Dynamic speed increases can be obtained with Fasterfox’s unique
    prefetching mechanism, which recycles idle bandwidth by silently
    loading and caching all of the links on the page you are browsing.
  • Tweak Network
    Fasterfox allows you to tweak many network and rendering
    settings such as simultaneous connections, pipelining, cache,
    DNS cache, and initial paint delay.
  • Page Load Timer
    A millisecond accurate page load timer tests the effectiveness
    of your settings.
  • Block Popups
    A popup blocker for popups initiated by Flash plug-ins is also
    included.

Notes:
1. Remember, just because you’ve got a turbocharged browser doesn’t mean your colleagues or clients do.  This plugin is a double-edged sword because you can get lazy or indifferent about performance problems on web applications. If you are developing, testing, or QA’ing systems you should either use a different browser (COUGH IETester COUGH) or temporarily disable Fasterfox.

2. The out of the box setting in the Firefox > Add-Ons > FasterFox > Options menu is “Optimized“. Set that bad boy to “Turbo Charged” and to hell with playing nice with server resources – our time is worth more!


Windows Media Player Plugin for Firefox

Download: http://www.interoperabilitybridges.com/windows-media-player-firefox-plugin-download
Description: Lets you run Windows Media content in Firefox. In particular you will be able to stream WMV videos such as the ones we have in the newly minted it groove SharePoint center directly in your browser window.

Web Developer Toolbar

Download: https://addons.mozilla.org/en-US/firefox/addon/web-developer/
Description: Adds a toolbar with a slew of options essential for anything webby. CSS, Forms, Images, Cookies, Viewing Source – instantly get Xray vision into any web page.

iMacros for Firefox

Download: https://addons.mozilla.org/en-US/firefox/addon/imacros-for-firefox/?src=collection&collection_id=da0ecd99-2289-7ab0-7d57-e7c489c845c3
Description: Automate Firefox. Record and replay repetitious work. If you love the
Firefox web browser, but are tired of repetitive tasks like visiting the
same sites every days, filling out forms, and remembering passwords,
then iMacros for Firefox is the solution you’ve been dreaming of!
***Whatever you do with Firefox, iMacros can automate it.***

Colorzilla

Download: https://addons.mozilla.org/en-US/firefox/addon/colorzilla/
Description: With ColorZilla you can get a color reading from any point in your
browser, quickly adjust this color and paste it into another program.
You can Zoom the page you are viewing and measure distances between any
two points on the page. The built-in palette browser allows choosing
colors from pre-defined color sets and saving the most used colors in
custom palettes.

Basic end-user usage could be grabbing the color code for the blue from a clients logo and matching it up to another design element.

Firebug

Download: http://getfirebug.com/
Description: Firebug integrates with Firefox to put a wealth of web development tools
at your fingertips while you browse. You can edit, debug, and monitor
CSS, HTML, and JavaScript live in any web page.

Learning to use Firebug is a whole different topic but it is possible for non-developers to get working with it to quickly id and delegate issues due to Javascript or CSS issues, broken images, etc.

Firebug also is required for Yahoo YSlow and the Google Pagespeed Firefox Plugins

Incoming search terms:

Firefox Friday #3 – SharePoint Login Prompts on Firefox

​If you are using Firefox as your default browser, then either you get
an IE tab add-on to view SharePoint sites in Firefox, or type your user
name and password each time when you access to the SharePoint server.

There is a way thought to allow you to save your typed Windows
credentials in Firefox to prevent you from repeatly typing the Windows
user name and password.

  1. Enter “about:config” in the address bar of Firefox and hit [Enter]
  2. Do a search on "ntlm", at least three entries should appear
  3. Double click the entry titled
    "network.automatic-ntlm-auth.trusted-uris" and set its value to .yourdomain (do not
    forget the dot). You can have multiple domains by entering them as comma-separated.
  4. Restart your Firefox to get it to kick in.


  5. Woila! No more irritating login prompts. This only works with NTLM authentication and not Kerberos.

    Incoming search terms:

SharePoint 2010 Get Current Username / Logged in User

Have been exploring the SharePoint Client Object Model and in particular the Javascript Object Model

While there are methods to get the current user info, you can also simply borrow the logged in username from the top right of the screen:


<script type="text/javascript">// <![CDATA[
 var Username = document.getElementById("zz16_Menu").innerHTML ;
 var end = Username.indexOf("<");
 var nameOnly = Username.substring(8, end);
 document.write(nameOnly);

// ]]></script>

This technique is a little complex for my liking however, so here’s a snappier way to grab the current login name (using Jquery):


var Username = $("#zz16_Menu").text();
document.write(Username);

Note that the #zz16 identifier will vary based on your Master page. Use the Firefox Web Developer tools or Internet Explorer F12 tools to find out what the ID should be on your SharePoint site.

Using this type of technique is definitely more brittle than actually using a CAML query however in my mind would be more performant than actually doing a lookup in the DB. Would love to know if someone knows the scoop on that..

Update 05/12/2011

As my colleague Colin pointed out – the name that appears on the top right can really be anything and can change – for example if a user gets married and their name changes. A better approach would be to retireve the value programmatically using SPServices ( http://spservices.codeplex.com/wikipage?title=$%28%29.SPServices.SPGetCurrentUser ). As of version v0.6.1, you can also request the ID of the user by specifying fieldName: “ID”.  Much more stable to use in most scenarios:

$().SPServices.SPGetCurrentUser({
	fieldName: "ID",
	debug: false
});

Incoming search terms:

Recent Comments

  • Panoone

    I just hit this same issue with a web part I’d developed for 2013.

    Common sense dictated that that /_layouts would point to the current version. But the SharePoint dev team had other ideas. ;^)

Follow me on Twitter

Office 365 Service Health

  • Service: Exchange OnlineIncident Type: E-Mail and […]
    Sat, Jul 26, 2014
    Source: Office 365 Service Health Status
  • Service: Exchange OnlineIncident Type: Management […]
    Sat, Jul 26, 2014
    Source: Office 365 Service Health Status
  • Service: Exchange OnlineIncident Type: E-Mail and […]
    Fri, Jul 25, 2014
    Source: Office 365 Service Health Status
  • Service: Exchange OnlineIncident Type: Management […]
    Fri, Jul 25, 2014
    Source: Office 365 Service Health Status
  • Service: Office 365 PortalIncident Type: PortalSta […]
    Thu, Jul 24, 2014
    Source: Office 365 Service Health Status

SharePoint & Office Patches

VisualStudio.com Service Health