Quantcast
Channel: ventigrate Wiki Rss Feed
Viewing all 51 articles
Browse latest View live

Updated Wiki: Permissive X-FRAME-OPTIONS Header

$
0
0

Permissive X-FRAME-OPTIONS Header

A SharePoint 2010 module that will allow Excel Services or Office Web Apps to be rendered inside cross-domain iframes.

Updated Wiki: Permissive XFrame Header

$
0
0

Permissive XFrame Header

A SharePoint 2010 module that will allow Excel Services or Office Web Apps to be rendered inside cross-domain iframes.

Updated Wiki: Home

$
0
0
Project Description
This is the public repository for Ventigrate, a Belgian IT service provider active in SharePoint Solutions, Web Applications, Rich Internet Applications and Integrated Solutions. This repository contains solutions and techniques that were developed by employees of Ventigrate and that are shared for the benefit of the community.


Projects and Samples:

* Advanced Computed Field (26 May 2011)
* Taxonomy Uploader (1 Jun 2011)
* Room and Equipment Reservations (planned)
* User Profile Exclusion Filters (20 Jul 2011)
* External User Management (30 Sep 2011)
* MUI Search Refinement Panel (13 Dec 2011)
* Sanboxed Logging (26 Dec 2011)
* Permissive XFrame Header (3 Jan 2012)

Updated Wiki: Permissive XFrame Header

$
0
0

Permissive XFrame Header

A SharePoint 2010 module that will allow Excel Services or Office Web Apps to be rendered inside cross-domain iframes.

 

Consider a scenario where you want to display a with Excel Services rendered workbook inside a cross-domain iframe:

But because Excel Services and Office Web Apps render a HTTP response header X-FRAME-OPTIONS: SAMEORIGIN this won’t work and you get “This content cannot be displayed in a frame”

The content cannot be displayed in a frame

Not used to seeing such a straight-forward error :)

I did a bit of investigating but couldn’t find an easy way to configure this through UI or Powershell, so I was left with the following options:

  • Strip the header in a reverse proxy (between client and SharePoint server) like Apache or ForeFront
  • Remove the header with development of a HttpModule

PermissiveXFrameHeader

I wrote up a quick HttpModule that can be activated by Web Application Feature and will remove the X-FRAME-OPTIONS header no questions asked.

You might want to adapt the code for additional checks on referrer, querystring, client, or similar for conditional removal of the header (see final note below).

Installation and activation

Download from here (Ventigrate Codeplex Repository)

Deploy the WSP (farm solution) to the SharePoint Farm

STSADM -o addsolution -filename Ventigrate.Shared.PermissiveXFrameHeader.wsp
STSADM -o deploysolution -name Ventigrate.Shared.PermissiveXFrameHeader.wsp -allowgacdeployment -immediate

Activate the Web Application Feature to the Web Application referred to in the iframe

Manage Web Application Features

Final note

The header was designed to protect against clickjacking. If you intend to use the above solution keep this in mind and plan for it accordingly.

Original blog

http://www.moss2007.be/blogs/vandest/archive/2012/01/03/sharepoint-2010-office-web-apps-and-iframes.aspx

Updated Wiki: Anonymous Version History

$
0
0

Anonymous Version History

This SharePoint 2007 allows anonymous users to access Version History if their permission level allows for it. Adds a link to the page in the ECB menu and Toolbar for Document Libraries and Lists.

Updated Wiki: Anonymous Version History

$
0
0

Anonymous Version History

This SharePoint 2007 solution allows anonymous users to access Version History if their permission level allows for it.

Updated Wiki: Home

$
0
0
Project Description
This is the public repository for Ventigrate, a Belgian IT service provider active in SharePoint Solutions, Web Applications, Rich Internet Applications and Integrated Solutions. This repository contains solutions and techniques that were developed by employees of Ventigrate and that are shared for the benefit of the community.


Projects and Samples:

* Advanced Computed Field (26 May 2011)
* Taxonomy Uploader (1 Jun 2011)
* Room and Equipment Reservations (planned)
* User Profile Exclusion Filters (20 Jul 2011)
* External User Management (30 Sep 2011)
* MUI Search Refinement Panel (13 Dec 2011)
* Sanboxed Logging (26 Dec 2011)
* Permissive XFrame Header (3 Jan 2012)
* Anonymous Version History (3 Jan 2012)

Updated Wiki: Anonymous Version History

$
0
0

Anonymous Version History

This SharePoint 2007 solution allows anonymous users to access Version History if their permission level allows for it.

 

You can configure the permission level of anonymous users to allow for viewing versions of documents and items, but no matter what you do, they get prompted for credentials.

The Version History page has the property “AllowAnonymousAccess” set to false. It is a virtual property in theMicrosoft.SharePoint.ApplicationPages.UnsecuredLayoutsPageBase class that needs to be overridden in those layout pages that should be visible for anonymous users.

SharePoint 2007

The solution is an identical copy of the original Version History page of SharePoint 2007 but with the aforementioned property set totrue.

The farm solution contains the page and a Site Collection Feature for activation which will add links to the page in the Toolbar and ECB menu for Document Libraries and Lists. You could hide or replace the link to the original page, but that isn’t straight-forward using CustomAction elements.

ECB Menu

Toolbar

Version History

Installation and activation

Download from here (Ventigrate Codeplex Repository)

Deploy the WSP (farm solution) to the SharePoint Farm

STSADM -o addsolution -filename Ventigrate.Shared.AnonymousVersionHistory.wsp
STSADM -o deploysolution -name Ventigrate.Shared.AnonymousVersionHistory.wsp -allowgacdeployment -immediate

Activate the Site Collection Feature where you want this functionality

Site Collection Features[10]

SharePoint 2010

SharePoint 2010 suffers from the same issue. You need to adapt the above solution to make it work for SharePoint 2010

  • Copy the markup of the SharePoint 2010 Version History page (and add the property override)
  • Adapt the CustomAction elements to add links to UI elements for SharePoint 2010 (and optional Dialog UI)

Original blog

http://www.moss2007.be/blogs/vandest/archive/2012/01/03/sharepoint-2007-anonymous-version-history.aspx


Updated Wiki: Home

$
0
0
Project Description
This is the public repository for Ventigrate, a Belgian IT service provider active in SharePoint Solutions, Web Applications, Rich Internet Applications and Integrated Solutions. This repository contains solutions and techniques that were developed by employees of Ventigrate and that are shared for the benefit of the community.


Projects and Samples:

* Advanced Computed Field (26 May 2011)
* Taxonomy Uploader (1 Jun 2011)
* Room and Equipment Reservations (planned)
* User Profile Exclusion Filters (20 Jul 2011)
* External User Management (30 Sep 2011)
* MUI Search Refinement Panel (13 Dec 2011)
* Sanboxed Logging (26 Dec 2011)
* Permissive XFrame Header (3 Jan 2012)
* Anonymous Version History (3 Jan 2012)
* Delete All Items Ribbon Button (8 Feb 2012)

Updated Wiki: Delete All Items Ribbon Button

Updated Wiki: Delete All Items Ribbon Button

$
0
0

Delete All Items Ribbon Button

A SharePoint 2010 Sandboxed Solution that adds a Ribbon Button that recycles all items in a Document Library with a single mouse click.

I' have created this miniproject more as an academic exercise in creating a Ribbon Button than for real business value. It can come in handy for development environments sometimes.

 

Installation and activation

Download from here (Ventigrate Codeplex Repository)

Upload the WSP (sandbox solution) to the Site Collection Solution Gallery and activate it

Solution Gallery

 

 

 

 

 

 

 

 

 

 

Activate the Site Collection Feature

Site Collection Features

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Final note

Some lessons learned and things worth noting:

  • Use a Module to deploy resource files to a folder or library like the Style Library (Sandbox cannot access the Layouts folder)
  • The Module will overwrite the existing resource files with a newer version, but will not delete them
  • Working with ECMAScript seems to have no effect on resource or resource quota
  • Use InPrivate Browsing for testing Ribbon development, this avoids caching of Ribbon resources
  • CustomAction.ScriptSrc points to the Layouts folder when using relative URLs. Use ~SiteCollection if you want to reference a resource in the Site Collection

 

Original blog

Updated Wiki: Delete All Items Ribbon Button

$
0
0

Delete All Items Ribbon Button

A SharePoint 2010 Sandboxed Solution that adds a Ribbon Button that recycles all items in a Document Library with a single mouse click.

I' have created this miniproject more as an academic exercise in creating a Ribbon Button than for real business value. It can come in handy for development environments sometimes.

Installation and activation

Download from here (Ventigrate Codeplex Repository)

Upload the WSP (sandbox solution) to the Site Collection Solution Gallery and activate it

Solution Gallery

Activate the Site Collection Feature

Site Collection Features

Final note

Some lessons learned and things worth noting:

  • Use a Module to deploy resource files to a folder or library like the Style Library (Sandbox cannot access the Layouts folder)
  • The Module will overwrite the existing resource files with a newer version, but will not delete them
  • Working with ECMAScript seems to have no effect on resource or resource quota
  • Use InPrivate Browsing for testing Ribbon development, this avoids caching of Ribbon resources
  • CustomAction.ScriptSrc points to the Layouts folder when using relative URLs. Use ~SiteCollection if you want to reference a resource in the Site Collection

 

Original blog

Updated Wiki: Delete All Items Ribbon Button

$
0
0

Delete All Items Ribbon Button

A SharePoint 2010 Sandboxed Solution that adds a Ribbon Button that recycles all items in a Document Library with a single mouse click.

I' have created this miniproject more as an academic exercise in creating a Ribbon Button than for real business value. It can come in handy for development environments sometimes.

Installation and activation

Download from here (Ventigrate Codeplex Repository)

Upload the WSP (sandbox solution) to the Site Collection Solution Gallery and activate it

Solution Gallery

Activate the Site Collection Feature

Site Collection Features

 

Final note

Some lessons learned and things worth noting:

  • Use a Module to deploy resource files to a folder or library like the Style Library (Sandbox cannot access the Layouts folder)
  • The Module will overwrite the existing resource files with a newer version, but will not delete them
  • Working with ECMAScript seems to have no effect on resource or resource quota
  • Use InPrivate Browsing for testing Ribbon development, this avoids caching of Ribbon resources
  • CustomAction.ScriptSrc points to the Layouts folder when using relative URLs. Use ~SiteCollection if you want to reference a resource in the Site Collection

Original blog

Updated Wiki: Delete All Items Ribbon Button

$
0
0

Delete All Items Ribbon Button

A SharePoint 2010 Sandboxed Solution that adds a Ribbon Button that recycles all items in a Document Library with a single mouse click.

I' have created this miniproject more as an academic exercise in creating a Ribbon Button than for real business value. It can come in handy for development environments sometimes.

Installation and activation

Download from here (Ventigrate Codeplex Repository)

Upload the WSP (sandbox solution) to the Site Collection Solution Gallery and activate it

Solution Gallery

 

Activate the Site Collection Feature

Site Collection Features

 

Final note

Some lessons learned and things worth noting:

  • Use a Module to deploy resource files to a folder or library like the Style Library (Sandbox cannot access the Layouts folder)
  • The Module will overwrite the existing resource files with a newer version, but will not delete them
  • Working with ECMAScript seems to have no effect on resource or resource quota
  • Use InPrivate Browsing for testing Ribbon development, this avoids caching of Ribbon resources
  • CustomAction.ScriptSrc points to the Layouts folder when using relative URLs. Use ~SiteCollection if you want to reference a resource in the Site Collection

Original blog

Updated Wiki: Delete All Items Ribbon Button

$
0
0

Delete All Items Ribbon Button

A SharePoint 2010 Sandboxed Solution that adds a Ribbon Button that recycles all items in a Document Library with a single mouse click.

I' have created this miniproject more as an academic exercise in creating a Ribbon Button than for real business value. It can come in handy for development environments sometimes.

Ribbon

Installation and activation

Download from here (Ventigrate Codeplex Repository)

Upload the WSP (sandbox solution) to the Site Collection Solution Gallery and activate it

Solution Gallery

 

Activate the Site Collection Feature

Site Collection Features

 

Final note

Some lessons learned and things worth noting:

  • Use a Module to deploy resource files to a folder or library like the Style Library (Sandbox cannot access the Layouts folder)
  • The Module will overwrite the existing resource files with a newer version, but will not delete them
  • Working with ECMAScript seems to have no effect on resource or resource quota
  • Use InPrivate Browsing for testing Ribbon development, this avoids caching of Ribbon resources
  • CustomAction.ScriptSrc points to the Layouts folder when using relative URLs. Use ~SiteCollection if you want to reference a resource in the Site Collection

Original blog

http://www.moss2007.be/blogs/vandest/archive/2012/02/08/delete-all-items-ribbon-button.aspx


Updated Wiki: Home

$
0
0
Project Description
This is the public repository for Ventigrate, a Belgian IT service provider active in SharePoint Solutions, Web Applications, Rich Internet Applications and Integrated Solutions. This repository contains solutions and techniques that were developed by employees of Ventigrate and that are shared for the benefit of the community.


Projects and Samples:

* Advanced Computed Field (1 March 2012)
* Taxonomy Uploader (1 Jun 2011)
* Room and Equipment Reservations (planned)
* User Profile Exclusion Filters (20 Jul 2011)
* External User Management (30 Sep 2011)
* MUI Search Refinement Panel (13 Dec 2011)
* Sanboxed Logging (26 Dec 2011)
* Permissive XFrame Header (3 Jan 2012)
* Anonymous Version History (3 Jan 2012)
* Delete All Items Ribbon Button (8 Feb 2012)

Updated Wiki: Advanced Computed Field

$
0
0

Advanced Computed Field

The Advanced Computed Field is a Custom Field Type for SharePoint 2010 that allows powerful and rich visualisation of other metadata fields on a document or list item. It has two configuration options: one is to specify which field values you want it to include, the other one allows defining the HTML markup combined with the specified field values.

This field was originally created for SharePoint 2007 and can still be downloaded here: http://www.moss2007.be/blogs/vandest/archive/2009/03/31/advanced-computed-field.aspx


Use it for:

  • Rich Text Formatting, Highlighting, ... of field values
  • Constructing parameterized URLs or mailto-links
  • Rendering of form controls (like a button) with javascript logic
  • Advanced javascript processing (create ellipsis of the 'Body' of an item)
  • ...

Other practical examples of use:

Installation

Add and deploy the SharePoint Solution Package (.wsp) using STSADM or PowerShell:

STSADM -o addsolution -filename VNTG.CustomFieldTypes.AdvancedComputedField.wsp 
STSADM -o deploysolution -name VNTG.CustomFieldTypes.AdvancedComputedField.wsp -allowgacdeployment -immediate -allcontenturls

Upgrading ?

Q. Will the Advanced Computed Field still work if I migrate from SharePoint 2007 to SharePoint 2010 ?
A. Definitely, but you'll need to upgrade the SharePoint 2007 solution package to the SharePoint 2010 version. Either retract and delete the SharePoint 2007 package prior to deploying the SharePoint 2010 package, or do an upgrade to the new solution. Make sure to IISRESET afterwards !

Changelog

  • 1 March 2012: Added XSL template to fix an issue with Connected Web Parts not showing value for the Advanced Computed Fields

Updated Wiki: Advanced Computed Field

$
0
0

Advanced Computed Field

The Advanced Computed Field is a Custom Field Type for SharePoint 2010 that allows powerful and rich visualisation of other metadata fields on a document or list item. It has two configuration options: one is to specify which field values you want it to include, the other one allows defining the HTML markup combined with the specified field values.

This field was originally created for SharePoint 2007 and can still be downloaded here: http://www.moss2007.be/blogs/vandest/archive/2009/03/31/advanced-computed-field.aspx


Use it for:

  • Rich Text Formatting, Highlighting, ... of field values
  • Constructing parameterized URLs or mailto-links
  • Rendering of form controls (like a button) with javascript logic
  • Advanced javascript processing (create ellipsis of the 'Body' of an item)
  • ...

Other practical examples of use:

Installation

Add and deploy the SharePoint Solution Package (.wsp) using STSADM or PowerShell:

STSADM -o addsolution -filename VNTG.CustomFieldTypes.AdvancedComputedField.wsp 
STSADM -o deploysolution -name VNTG.CustomFieldTypes.AdvancedComputedField.wsp -allowgacdeployment -immediate -allcontenturls

Upgrading ?

Q. Will the Advanced Computed Field still work if I migrate from SharePoint 2007 to SharePoint 2010 ?
A. Definitely, but you'll need to upgrade the SharePoint 2007 solution package to the SharePoint 2010 version. Either retract and delete the SharePoint 2007 package prior to deploying the SharePoint 2010 package, or do an upgrade to the new solution. Make sure to IISRESET afterwards !

Changelog

  • 1 March 2012: Added XSL template to fix an issue with Connected Web Parts not showing value for the Advanced Computed Fields (thanks Federico Sanchez !)

Updated Wiki: Home

$
0
0
Project Description
This repository contains solutions and techniques that were developed by employees of Ventigrate and that are shared for the benefit of the community.


Projects and Samples:

* Advanced Computed Field (1 March 2012)
* Taxonomy Uploader (1 Jun 2011)
* Room and Equipment Reservations (planned)
* User Profile Exclusion Filters (20 Jul 2011)
* External User Management (SharePoint 2010 and SharePoint 2013) (22 February 2013)
* MUI Search Refinement Panel (13 Dec 2011)
* Sanboxed Logging (26 Dec 2011)
* Permissive XFrame Header (3 Jan 2012)
* Anonymous Version History (3 Jan 2012)
* Delete All Items Ribbon Button (8 Feb 2012)

Updated Wiki: External User Management

$
0
0

External User Management for SharePoint 2010 and SharePoint 2013

The External User Management solution allows for easy management of users and groups for a SharePoint 2010 or SharePoint 2013 environment configured for Forms Based Authentication (FBA), handled by Claims Based Authentication (CBA). It contains management pages for Site Collection Administrators to:

User Management tasks

  • Add users
  • Edit a user (edit details, password or role membership)
  • Unlock a user
  • Delete a user


Role Management tasks

  • Add a role
  • Delete a role



Prerequisites

Log4Net is a highly flexible and configurable logging mechanism and is used by this solution. It is included in the Deployment Package and can be installed as a SharePoint Solution Package (.wsp) using STSADM or PowerShell:

STSADM -o addsolution -filename Log4Net.v1.2.10.wsp
STSADM -o deploysolution -name Log4Net.v1.2.10.wsp -allowgacdeployment -immediate

 

Installation

Add and deploy the SharePoint Solution Package (.wsp) using STSADM or PowerShell:

STSADM -o addsolution -filename Ventigrate.Shared.ExternalMembership.wsp
STSADM -o deploysolution -name Ventigrate.Shared.ExternalMembership.wsp -allowgacdeployment -immediate



Add an internal Alternate Access Mapping "http://extranet" for the Zone on the WebApplication that has the Membership and Role Provider (Claims) configured in it's web.config. This is the key to getting the administration pages to connect to the correct provider.

Activate the Site Collection Feature to make a link to the management pages appear in Site Collection Administration.

FAQ

Q. Will this solution work on SharePoint 2007 ?
A. No, there are certain features that make it work only in SharePoint 2010 or SharePoint 2013. But there are similar projects for doing FBA User Management in SharePoint 2007 on CodePlex (CKShttp://cks.codeplex.com/).

Q. I don't use a Role Provider or my Membership Provider doesn't allow certain tasks such as Password Change. Can I use this ?
A. You should be fine. If you do run into a specific situation, feel free to provide improvements through the Discussion Boardshttp://ventigrate.codeplex.com/discussions.

Q. Other questions ?
A. No problem. Ask them in the Discussion Boards http://ventigrate.codeplex.com/discussions.

Viewing all 51 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>