features Work Item Rss Feed

Commented Issue: UniqueColumnPolicy - not working with Lookup fields (including users) [8838]

mcalicea — Thu, 18 Nov 2010 13:45:35 GMT

The UniqueColumnPolicy doesn't work with looup fields (including users) although these fields are listed in UniqueColumnSettings.ascx.
THis is because the CAML query created in Validation.cs only returns the ID as the value.
There is a simple way to avoid this: detecting if the field type is "User" or "Lookup" and if so, add the following attribute to the FieldRef node LookupId="TRUE".

You will find attachedd the updated Validation.cs (modifications are from line 101 to line 116)
Comments: ** Comment from web user: mcalicea **

How can I add this Validation.cs file to solution? I am new to features and was wondering if I have to replace the file and then load it to my Sharepoint collection or can I do it after its already deployed?

Commented Issue: UniqueColumnPolicy - not working with Lookup fields (including users) [8838]

sfurbacher — Fri, 08 Oct 2010 14:44:03 GMT

Impact should be raised.

Created Issue: Content Type Hierarchy [14352]

bobbyangers — Thu, 30 Sep 2010 18:10:53 GMT

The hyperlink generated in the Tree always point to the root of web application. This is fine if your site collection is at the root of the web application, but what if your site collection is a sub web...

http://sharepoint/collection1

where collection1 is my rootweb of a site collection.

Commented Issue: 3.5 Config & Ajax.Config httpHandlers added in the wrong order [6623]

Mr_T — Fri, 30 Jul 2010 13:17:47 GMT

<remove verb="*" path="*.asmx" /> gets added after <add verb="GET,HEAD" path="ScriptResource.axd" <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

This Means the .asmx pages do not work on the sharepoint application affter adding the feature. This also prevent you edit the site using sharepoint designer because /_vti_bin/usergroup.asmx will give a 401.

Before features

<httpHandlers>
<remove verb="GET,HEAD,POST" path="*" />
<add verb="GET,HEAD,POST" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
<add verb="OPTIONS,PROPFIND,PUT,LOCK,UNLOCK,MOVE,COPY,GETLIB,PROPPATCH,MKCOL,DELETE,(GETSOURCE),(HEADSOURCE),(POSTSOURCE)" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
<add verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
<add verb="*" path="Telerik.RadUploadProgressHandler.ashx" type="Telerik.Web.UI.RadUploadProgressHandler, Telerik.Web.UI, Version=2008.1.515.35, Culture=neutral, PublicKeyToken=121fae78165ba3d4" />
<add verb="*" path="Telerik.Web.UI.WebResource.axd" type="Telerik.Web.UI.WebResource, Telerik.Web.UI, Version=2008.1.515.35, Culture=neutral, PublicKeyToken=121fae78165ba3d4" validate="false" />
</httpHandlers>

After features

<httpHandlers>
<remove verb="GET,HEAD,POST" path="*" />
<add verb="GET,HEAD,POST" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
<add verb="OPTIONS,PROPFIND,PUT,LOCK,UNLOCK,MOVE,COPY,GETLIB,PROPPATCH,MKCOL,DELETE,(GETSOURCE),(HEADSOURCE),(POSTSOURCE)" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
<add verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
<add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
<add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
<add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" validate="false" />
<add verb="*" path="Telerik.RadUploadProgressHandler.ashx" type="Telerik.Web.UI.RadUploadProgressHandler, Telerik.Web.UI, Version=2008.1.515.35, Culture=neutral, PublicKeyToken=121fae78165ba3d4" />
<add verb="*" path="Telerik.Web.UI.WebResource.axd" type="Telerik.Web.UI.WebResource, Telerik.Web.UI, Version=2008.1.515.35, Culture=neutral, PublicKeyToken=121fae78165ba3d4" validate="false" />
<remove verb="*" path="*.asmx" /> </httpHandlers>
Comments: ** Comment from web user: Mr_T **

I tried the fix from bbattah0...didn't work

Commented Issue: Error deploying toolbar manager [13516]

beavermjr — Fri, 11 Jun 2010 12:49:38 GMT

I've installed the toolbar manager on my company's sharepoint 2007 site and have been using it for a few months now. Functionality is as expected.

We began having some issues with the server which caused us to notice the following error message within central admin

Name: toolbarmanager.wsp
type: Core Solution
Contains Web Application Resources: Yes
Contains Global assembly: Yes
Contains Code Access Security Policy: No
Deployment Server Type: Front-end Web Server
Deployment Status: Error
Deployed To: None
Last opperation Result: Some of the files failed to copy during deployment of the solution
Last opperation Details: RCDA-PORTAL: Http://rcda-portal/ : sharepoint - 37171 : Error: the web config is invalid on this IIS Web Site:
C:\inetpub\wwwroot\wss\virtualDirectories\37171\web.config

The weird thing is that we never had a site 37171. Why was the solution trying to deploy to that site rather than the default IIS Server? The solution deployed correctly on our staging server.
Comments: ** Comment from web user: beavermjr **

I removed the solution and tried deploying it again. I am still getting the same error.

Created Issue: Error deploying toolbar manager [13516]

beavermjr — Thu, 10 Jun 2010 18:05:49 GMT

Created Issue: Toolbar manager has no effect [13432]

Poynter — Thu, 03 Jun 2010 10:00:08 GMT

Running SharePoint Server 2007 x64.

Installed and activated the webpart; added to a list page, set to hide menu items. Restarted IIS and menu items still appearing. Tried on several different lists and has no effect on any of them.

Any ideas?

Commented Issue: Could not load file or assembly 'Microsoft.Office.Policy, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the fi

iOnline247 — Mon, 03 May 2010 15:06:06 GMT

This is the error I receive when trying to deploy the UniqueColumnPolicy.wsp. Has anyone else ran into this problem? I'm thinking it has something to do with the web.config file but I'm not that certain... Any guidance would be great!

Cheers,
Matt
Comments: ** Comment from web user: iOnline247 **

I ended up running this from the command line:

stsadm -o deploysolution -name UniqueColumnPolicy.wsp -force -immediate -allowGacDeployment

and it works now. Hope this helps someone else...

Cheers,
Matt

Created Issue: Could not load file or assembly 'Microsoft.Office.Policy, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file

iOnline247 — Fri, 30 Apr 2010 19:06:59 GMT

Created Issue: Ajax config feature - Failed to apply a web.config modification to file 'configuration/system.web/pages [12680]

rjn71 — Tue, 13 Apr 2010 19:08:51 GMT

The ajax config feature sometimes throws up exception "Failed to apply a web.config modification to file 'configuration/system.web/pages" and the fix http://features.codeplex.com/WorkItem/View.aspx?WorkItemId=8353 didn't work for me.

Though the feature fails to activate, it still creates all the config entries. Any fix for this?

Commented Issue: 3.5 Config - Reactivation issue, pages node. [7502]

Mr_T — Fri, 09 Apr 2010 06:06:28 GMT

The 3.5 Config feature on first activation activates OK, deactivation of the feature deactivates OK, BUT if then it is reactivated for a second time there is an error:

Failed to apply a web.config modification to file 'configuration/system.web/pages'. The specified node "C:\Inetpub\wwwroot\wss\VirtualDirectories\80\web.config" was not found in the web.config file.

The Pages node is completely removed from the web.config on deactivation. This is one issue but there is a further issue.

Original config

<pages enableSessionState="false" enableViewState="true" enableViewStateMac="true" validateRequest="false" pageParserFilterType="Microsoft.SharePoint.ApplicationRuntime.SPPageParserFilter, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" asyncTimeout="7">
<namespaces>
<remove namespace="System.Web.UI.WebControls.WebParts" />
</namespaces>
<tagMapping>
<add tagType="System.Web.UI.WebControls.SqlDataSource, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" mappedTagType="Microsoft.SharePoint.WebControls.SPSqlDataSource, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
</tagMapping>
</pages>

After first activation

<pages enableSessionState="false" enableViewState="true" enableViewStateMac="true" validateRequest="false" pageParserFilterType="Microsoft.SharePoint.ApplicationRuntime.SPPageParserFilter, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" asyncTimeout="7">
<namespaces>
<remove namespace="System.Web.UI.WebControls.WebParts" />
</namespaces>
<tagMapping>
<add tagType="System.Web.UI.WebControls.SqlDataSource, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" mappedTagType="Microsoft.SharePoint.WebControls.SPSqlDataSource, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
</tagMapping>
<controls>
<add tagPrefix="asp" namespace="System.Web.UI.WebControls" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
<add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
</controls>
</pages>

On deactivation the Pages node is removed. This means a second reactivation fails with the error above but a further issue is that the original nodes within the Pages node are now lost.
Comments: ** Comment from web user: Mr_T **

same prob here

Created Issue: Pages modification on AJAX Config [11682]

SanderSchutten — Tue, 02 Feb 2010 16:29:52 GMT

I noticed that you add the following modification "pages[@pageParserFilterType="Microsoft.SharePoint.ApplicationRuntime.SPPageParserFilter, Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"]". I think it's better to add an empty "<Pages />" node as EnsureSection. Because of this "pageParserFilterType" check, i now ended up with two <pages> nodes.

Created Issue: Placeholder Master Feature - Error Activating feature

Atworks — Fri, 26 Jun 2009 18:41:48 GMT

In order to successfully activate this feature, the placeholder.master to be local to the feature folder

Created Issue: Print List

chaosgenie — Tue, 21 Apr 2009 12:29:45 GMT

Hi,

it seems to me, that my Print-list-Button doesn't work correctly.
The {ListiD}-Variable is not filled.

false:
http://mysite/_layouts/PrintList/PrintList.aspx?list={ListId}

correct:
http://mysite/_layouts/PrintList/PrintList.aspx?list=%7b2047C360-D73A-41B7-BB1F-C703C55190E2%7d

Where is the error? What can I do?

Best regards,
Markus

Commented Issue: 3.5 Config - Reactivation issue, pages node.

danwoodard — Thu, 16 Apr 2009 02:56:54 GMT

This causes major problems in a multi-server farm it makes it impossible to add WFE's to the farm due to the corrupted web.config.

Commented Issue: 3.5 Config - Reactivation issue, pages node.

joshc — Wed, 08 Apr 2009 23:30:12 GMT

For me it seemed to be initiated when we had 2 WFE and the timer service wasn't running on one when the WSP package was installed and feature activated. I assumed something got out of sync but I feel your pain, I never came up with a solution and its still an outstanding issue right now.

Created Issue: Log Viewer Feature gets an error with empty log files.

esantonja — Wed, 11 Feb 2009 14:10:00 GMT

Hi, the Log viewer feture get an "Object reference not set to an instance of an object." trying to open an empty log file.

Commented Issue: 3.5 Config - Reactivation issue, pages node.

bikoenig — Fri, 30 Jan 2009 23:15:10 GMT

this is absolute bullshit. is there no way to fix a MOSS site once you've b0rked it?

Created Issue: UniqueColumnPolicy - not working with Lookup fields (including users)

FVK — Wed, 07 Jan 2009 17:29:54 GMT

Commented Issue: 3.5 Config - Reactivation issue, pages node.

tns — Mon, 22 Dec 2008 12:16:11 GMT

Anyone found a solution/workaround for this?