Using Milkbox with SharePoint

By -
Recently we needed to integrate Milkbox (Lightbox that supports Flash and other things) to our SharePoint-based Intranet Site.



In order to do this you need to do the following to your master page.




  1. Download the Milkbox Code. Depending on how you plan to implement this solution you can store the files in a number of places, either in a doc library or on the file system in the 12 hive. In this example I created an STSDEV solution and added the downloaded files into the solution so they would deploy to the TEMPLATE/LAYOUTS directory in the 12 hive. If you choose to save it to another location, be sure to update your references from the '_layouts/...' references I gave to the .js and .css files.
     

  2. Ensure the following DOCTYPE declaration is at the top of your masterpage:


    <!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01 Transitional//EN”>

  3. Ensure the following assembly registration is in the top of your master page:

    <%@ Register Tagprefix="PublishingWebControls" Namespace="Microsoft.SharePoint.Publishing.WebControls" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

  4. In the <head> section of your master page add the following (Also, pay attention that the version numbers match up with the most current version you've downloaded):

    <PublishingWebControls:EditModePanel PageDisplayMode="Display" runat=server id="MilkboxPanel">
    <!--Lightbox -->
    <script type="text/javascript" src="/_layouts/Lightbox/milkbox-2.3.2/js/mootools-1.2.3-core-yc.js"></script>\>
    <script type="text/javascript" src="/_layouts/Lightbox/milkbox-2.3.2/js/mootools-1.2.3.1-assets.js"></script>
    <script type="text/javascript" src="/_layouts/Lightbox/milkbox-2.3.2/js/milkbox.js"></script>
    <style type="text/css">
    @import url(/_layouts/Lightbox/milkbox-2.3.2/css/milkbox/milkbox.css);
    </style>
    <!--End Lightbox-->
    </PublishingWebControls:EditModePanel>

    *Notice the Edit Mode panel wrapping the <style> and <script> tags. This is to prevent a javascript error that appears when the page is in edit mode and you try to edit a text field. This fix was proposed by Steve Mann of RDA, thanks for the help!

  5. In your page content area, ensure that your links include the milkbox 'rel' attribute:

    <a href="img/01b.jpg" rel="milkbox" title="Caption goes here...">image #1</a>

After this setup, you should be able to use Milkbox as it is documented on the page

Comments

Post a Comment

Popular posts from this blog

Programmatically Update Page Layouts

By -
I updated my page layouts that I deployed as a feature, but found that I could not overwrite the Layout File. The solution was to add a new page layout and then you would have to associate the new layout with every page on your site that used it. Obviously with a site of any size you'd have a lot of manual work to get this done, so doing it programmatically makes for a much better (and thorough) approach. After you've got your new page layouts, you could do something like this (in your event receiver class): public override void FeatureActivated(SPFeatureReceiverProperties properties) { //replace current page layouts with new page layouts on all pages SPWeb web = SPContext.Current.Web; SwapPageLayout(web, "FullWidthContentWithTitleV1.aspx", "FullWidthContentWithTitleV2.aspx"); } private void SwapPageLayout(SPWeb web, string oldPageLayoutName, string newPageLayoutName) { PublishingWeb pubWeb = PublishingWeb.GetPu...
Read more

Microsoft Virtualilzation Headaches

By -
As a SharePoint consultant, I am constantly moving from client to client and the best way to develop and test the code, designs and configurations for each client while maintaining complete separation is to virtualize. Since I work for a Microsoft partner, we try to use Microsoft tools and technologies as much as possible, which can be quite frustrating, as you will find out below. I recently started working for a large client with a global presence whose IT policies are well-established, difficult to change and not always up-to-date. In that vein, enter the corporate VPN: it's a web-based signin with a host checker that doesn't support any x64 OS. This prompted me, running Win 7 x64, to try to get a co-worker's Hyper-V Win2k3 x86 MOSS VM and run it in Windows Virtual PC . Seems like a logical thing to do, right? I mean, a Microsoft VHD should work, and be able to be imported by other Microsoft tools, right? Wrong. After spending quite a bit of time trying to attach the VHD...
Read more

ERROR: Failed to create feature receiver...

By -
I was working on a STSDev project which deployed a feature with a feature receiver. I had the feature working without the FeatureReceiver but as soon as I added the FeatureReceiver related attributes to my <Feature> element I got the following error: Failed to create feature receiver object from assembly "Org.Project.Solution, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c632353d405b3209", type "Org.Project.Solution.MyFeature.FeatureReceiver" for feature 6a9b2358-ea4e-486d-a4e4-4f813c52ce88: System.ArgumentNullException: Value cannot be null. Parameter name: type at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() After much digging around I discovered that STSDEV's Solution config file refers to a namespace as well as the dll. My FeatureReceiver's namespace was not prefixed with the right namespace So just...
Read more