ECQWP Work Item Rss Feed

Commented Issue: Group items by [8891]

Pioute — Thu, 17 Sep 2009 09:21:56 GMT

Hi,

The group items by <site> doesn't seem to do what I would expect.
If I apply this grouping on task list or document library content types (both for a range of subsites beneath a certain path), and I choose in the Presentation to group the items by <site>, I get following result:

All sites are displayed as header where items reside, but the items itself aren't visualised beneath each header per site.

I would expect something like this:

Site 1
item 1 from site 1
item 2 from site 1
Site 2
item 1 from site 2
item 2 from site 2
and so forth

What I get is the following
Site 1
Site 2
item 1 from site 1
item 2 from site 1
item 1 from site 2
item 2 from site 2
Comments: ** Comment from web user: Pioute **

This issues is really annoying... One of the most important feature is the ability to aggregate contants from subsite... I think it's normal to be able to group.

Commented Issue: Potentially excessive number of SPRequest objects error

ishaisagi — Wed, 05 Aug 2009 02:11:34 GMT

I am getting this error when using the ECQWP. This did not occur in Development or Test but under load in Production we are seeing these errrors in the ULS logs.

I did find a possible similar issue around xsl style link [sheets|http://www.tech-archive.net/Archive/SharePoint/microsoft.public.sharepoint.windowsservices/2007-02/msg00073.html] but could not remove this error even with having inline XSL in the web part itself rather than an XSLLink like we currently have. The web part renders fine and just wanted to clean up the issue in the ULS logs as it could possibly be the reason our w3wp.exe process is consuming so much memory.

08/04/2009 14:28:57.95 w3wp.exe (0x0FF8) 0x0B70 Windows SharePoint Services General 0 Medium Potentially excessive number of SPRequest objects (9) currently unreleased on thread 29. Ensure that this object or its parent (such as an SPWeb or SPSite) is being properly disposed. Allocation Id for this object: {9410FF4D-9085-466B-AA39-19D272A2F412} Stack trace of current allocation: at Microsoft.SharePoint.SPRequestManager.Add(SPRequest request, Boolean shareable) at Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity(Boolean bNotGlobalAdminCode, String strUrl, Boolean bNotAddToContext, Byte[] UserToken, String userName, Boolean bIgnoreTokenTimeout, Boolean bAsAnonymous) at Microsoft.SharePoint.SPWeb.InitializeSPRequest() at Microsoft.SharePoint.SPWeb.EnsureSPRequest() at Microsoft.SharePoint.SPWeb.get_Request() at Microsoft.SharePoint.SPWeb.SetMondoPr...
08/04/2009 14:28:57.95* w3wp.exe (0x0FF8) 0x0B70 Windows SharePoint Services General 0 Medium ...ocHint(Int32 hint) at Microsoft.SharePoint.SPSite.OpenWeb(Guid gWebId, Int32 mondoHint) at Microsoft.SharePoint.SPSite.OpenWeb(Guid gWebId) at CKS.EnhancedContentQueryWebPart.Wrappers.ListItemWrap..ctor(DataRow dr, SPSite site) at CKS.EnhancedContentQueryWebPart.ContentQueryWithContextMenus.EditDataRow(DataRow row, Int32 itemIndex) at CKS.EnhancedContentQueryWebPart.ContentQueryWithContextMenus.ProcessItems(DataTable dt) at Microsoft.SharePoint.Publishing.WebControls.ContentByQueryWebPart.IssueQuery() at Microsoft.SharePoint.Publishing.WebControls.ContentByQueryWebPart.GetXPathNavigator(String viewPath) at Microsoft.SharePoint.WebPartPages.DataFormWebPart.PrepareAndPerformTransform() at Microsoft.SharePoint.WebPartPages.DataFormWebPart.PerformSelect() ...
08/04/2009 14:28:57.95* w3wp.exe (0x0FF8) 0x0B70 Windows SharePoint Services General 0 Medium ... at Microsoft.SharePoint.WebPartPages.DataFormWebPart.DataBind() at Microsoft.SharePoint.WebPartPages.DataFormWebPart.EnsureDataBound() at Microsoft.SharePoint.WebPartPages.DataFormWebPart.CreateChildControls() at CKS.EnhancedContentQueryWebPart.ContentQueryWithContextMenus.CreateChildControls() at System.Web.UI.Control.EnsureChildControls() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean...
08/04/2009 14:28:57.95* w3wp.exe (0x0FF8) 0x0B70 Windows SharePoint Services General 0 Medium ... includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at Microsoft.SharePoint.Publishing.TemplateRedirectionPage.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) at System.Web.HttpApplication.ResumeSteps(Exception error) at System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) at System.Web.HttpRuntime.Pro...
08/04/2009 14:28:57.95* w3wp.exe (0x0FF8) 0x0B70 Windows SharePoint Services General 0 Medium ...cessRequestInternal(HttpWorkerRequest wr) at System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr) at System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType)
Comments: ** Comment from web user: ishaisagi **

Also, I found this article:http://www.tech-archive.net/Archive/SharePoint/microsoft.public.sharepoint.windowsservices/2007-02/msg00073.html that also blames the XSL.
It could be that if the XSL is invalid, the CQWP does not properly dispose of some objects. I would look into that if I were you

Commented Issue: Potentially excessive number of SPRequest objects error

ishaisagi — Wed, 05 Aug 2009 02:09:31 GMT

So I ran SPDisposeCheck and was very surprised (considering I didnt have the tool and I dont know how strict I was with it when I wrote it) that it had 0 found.

That said, I have researched about the error in question and the problem is that the web part does create a lot of SPRequests - it creates one for every single list item in the results (which is why I do not recommend using it, and which is why I wrote a different one for my current customer that works much faster)

When such a number is used, sharepoint will raise the alarm. The number can be tweaked, and is by default 8. This means that if you have a web part (or component - for example a custom navigation control that loads a lot of SPWeb objects) does more than 8 requests in each page load, you will get the warning. See http://msdn.microsoft.com/en-us/library/aa973248.aspx:

The best threshold varies according to the nature of your site and the applications running on it. When your sites are experiencing problems with performance, you should monitor your installation's ULS logs to understand how many SPRequest objects your site applications are creating. This helps you determine whether the designs of your sites and applications are creating too many SPRequest objects. Even if incorrect disposal of objects is not the cause of your performance problem, you might need to redesign your sites or custom site applications to reduce overall memory consumption caused by excessive proliferation of SPRequest objects.

Because the very low default threshold may not apply to many sites, you can change this threshold by editing the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\HeapSettings

LocalSPRequestWarnCount = desired threshold value

Created Issue: Potentially excessive number of SPRequest objects error

jthake — Tue, 04 Aug 2009 08:13:49 GMT

Commented Issue: Error in ECQWP_SETUP.bat

PerryK — Tue, 28 Apr 2009 11:40:26 GMT

Activating the feature fails because it searches for the wrong directory:

--------------------------------------------------------------------------------
C:\Documents and Settings\Administrator>stsadm.exe -o activatefeature -name "CKS
.EnhancedContentQueryWebPart" -url http://mossdevelopment.localhost -force

Failed to find the XML file at location '12\Template\Features\EnhancedContentQue
ryWebPart\feature.xml'
--------------------------------------------------------------------------------

Workaround is to copy and rename the \Template\Features\CKS.EnhancedContentQue
ryWebPart to \Template\Features\EnhancedContentQue
ryWebPart
Comments: ** Comment from web user: PerryK **

command below should work:
stsadm.exe -o activatefeature -name "EnhancedContentQueryWebPart" -url "http://TypeHereYourSiteName" -force

Commented Issue: Show context menus for items not working

PerryK — Tue, 28 Apr 2009 11:36:24 GMT

Hi, We just installed the ECQWP and it's working fine, except one thing: Show context menus for items. I only see links to the files. How do i make it work properly? Should i and how do i associate an XSLT file?

Thanks for you help!
Comments: ** Comment from web user: PerryK **

Replace in the batchfile everything below 'echo Do you want to activate the...'
with
stsadm.exe -o activatefeature -name "EnhancedContentQueryWebPart" -url "http://TypeHereYourSiteName" -force
The Style Sheets library will then be generated with the correct Style Sheets included. Now also the context menus should work fine.

Commented Issue: Report Inappropriate Item Workflow redirects to builtin SharePoint Item Page

Dave_C — Wed, 26 Nov 2008 16:06:54 GMT

Dear all,

I wanted to report an issue with the "Report Inappropriate Item" workflow as part of the PKS September and October documentation. When you receive the email from SharePoint asking the administrator to review the potentially inappropriate item, the link takes you to the built-in SharePoint item view page, and not the podcastdetail.aspx page. I understand why this is happening, however it would be good if there was a way of sending out a custom email, with the link to the podcastdetail.aspx page instead.

Regards,

David.
Comments: ** Comment from web user: Dave_C **

Many apologies - I meant to post this to the PKS community on here. Administrator please close!

Created Issue: Report Inappropriate Item Workflow redirects to builtin SharePoint Item Page

Dave_C — Wed, 26 Nov 2008 16:06:12 GMT

Created Issue: Delete list item

tedeum — Thu, 13 Nov 2008 17:23:59 GMT

i´ve got a problem, i cannot delete an item of the list that is listed in my ECQ webpart... i think its a bug, have anyone fix it ??

Created Issue: copy cat

abc3rd — Thu, 14 Aug 2008 15:20:42 GMT

I read another post in the Issue Tracker that looks like someone is having a nearly identical problem.
using ECQW to display document library with context menu then displaying menu items for doclib using javascript in CEWP to filter. "..I am having issue for delete function. I am calling the same function from OWS.JS file but delete function is giving errors. .." Same issue. Are we targeting the right jscript library?

Created Issue: Delete from Doc Lib Context Menu using CEWP

mauleevadi — Thu, 14 Aug 2008 12:49:01 GMT

Hi Ishasagi,

I am using Enhanced Content Query webpart to display document library with context menu. I am displaying menu items for doc lib using javascript in CEWP. This way I am displaying only menu items that I need. I am having issue for delete function. I am calling the same function from OWS.JS file but delete function is giving errors. I have attached the Javascript that I am using in CEWP and if you can look at it and help me out would be the best..

This is a mendatory requirement for us so if you can help me even for work around would be great help.

Thanks,
M

Commented Issue: Recall: Cannot load the XSL file

junx13 — Mon, 04 Aug 2008 03:09:58 GMT

Just found another reason behind the "Cannot load the XSL file" error.

Imagine you activate the feature only to a site which is not the rootsite (like http://foo/sites/sitecollection).
The webpart will then search for the XSL at http://foo/styles... Of course the XSL is not there because the solution is not deployed in http://foo.

Workaround is to edit the .webpart file and alter the following properties:
<property name="MainXslLink" type="string">/sites/[sitecollection]/Style Library/ECQWP XSL Style Sheets/ECQWPMain.xslt</property>
<property name="ItemXslLink" type="string">/sites/[sitecollection]/Style Library/ECQWP XSL Style Sheets/ECQWPItems.xslt</property>
<property name="HeaderXslLink" type="string">/sites/[sitecollection]/Style Library/XSL Style Sheets/Header.xsl</property>

You can then import the webpart.

Works like a charm then, great stuff!!
Comments: ** Comment from web user: junx13 **

Just a question , has this been planned to be worked on ? Thanks for the great work!

Created Issue: Security Trimming

cduden — Fri, 13 Jun 2008 06:39:56 GMT

I noticed that there was a bug related to security trimming and the context menus. It appears that the menus are no longer available and the icons disappear but items I have no permissions to still show up as links. clicking on them does nothing. This is different than the default Content Query Web Part which does not show items I do not have access to.

COMMENTED ISSUE: Icons dont show up when viewing a document library

ishaisagi — Mon, 02 Jun 2008 06:38:00 GMT

When the checkbox is turned off for "Show Context Menus for Items" when viewing a document library the icons images for the documents are displayed with an red X indicating that the image isn't there.
Comments: ** Comment from web user: ishaisagi **

that is because of performance. the document icon can only be retrieved if we load the items (which makes the web part slow). that is why we have an option not to load data that is required for context menus.

CREATED ISSUE: Icons dont show up when viewing a document library

aehash — Thu, 29 May 2008 20:47:47 GMT

COMMENTED ISSUE: Context Menus not Security Trimmed

mauleevadi — Thu, 22 May 2008 18:19:45 GMT

Greetings,

I have installed the ECQWP Beta 2 Technical Refresh and have encountered a concern, the context menu's do not seem to be security trimmed. Specifically - I have a user with only view access to a document, yet through the ECQWP that user receives all of the options on the context menu dropdown (ie - edit properties, manage permissions, etc that they should not have access to). The result is an ugly access denied error and subsequent confusion that I would like to avoid.

Any insight?

Thanks!
Kathryn
Comments: ** Comment from web user: mauleevadi **

Ishaisagi,

If you can post your ideas how to resolve this security issue, would be a great help.

Thanks,

COMMENTED ISSUE: Show context menus for items not working

mauleevadi — Tue, 20 May 2008 14:21:37 GMT

Thanks for this post... I was facing this problems & this post help me resolved it.

COMMENTED ISSUE: Recall: Cannot load the XSL file

manosfloyd — Thu, 14 Feb 2008 13:34:23 GMT

Sorry, I 'didnt mention before.

I'm caling this code on the init event.

COMMENTED ISSUE: Recall: Cannot load the XSL file

manosfloyd — Thu, 14 Feb 2008 13:29:09 GMT

Just in case you're still interest on it:

I was already developping our own CQWP when I found out about yours. I was overwritting the xsl files and then I realize you were using a much better solution here, but when we tried our CQWP in a site collection, even when the feature was being activated at the root level, the xsl's were not being found.
So, by now think an option could be to add the server location on the code, something as:

SPSite currSite = SPContext.Current.Site;
this.MainXslLink = currSite.ServerRelativeUrl +this.MainXslLink ;
this.ItemXslLink = currSite.ServerRelativeUrl + this.ItemXslLink;

It's working Ok for US,

Cheers

COMMENTED ISSUE: Show context menus for items not working

Kien — Wed, 02 Jan 2008 18:31:45 GMT

Hello,

I'm sort of having the same problem.
If you get the source code, you will find that there are 2 files named ECQWPMain.xslt and ECQWPItems.xslt in the solution folder.

What I did was create a folder named "ECQWP XSL Style Sheets" under the Style Library folder of my site with SharePoint Designer. I then copied those 2 files into this folder and checked them in as a published main version. I then proceeded to add the reference to these 2 files in the webpart (under "Main XSL Link" and "Items XSL Link"). After I've done that, the webpart doesn't display anything at all. It's just blank white.

The strings are:
/Site Library/ECQWP XSL Style Sheets/ECQWPMain.xslt
/Site Library/ECQWP XSL Style Sheets/ECQWPItems.xslt

Am I doing something wrong?

Thanks.