Consider the scenario where you have a Summary Links Web Part (part of the SharePoint Publishing functionality) configured on a page and you want to import the preconfigured Web Part on a different page on a different site. If you try this you’ll get “List does not exist”:
Note that importing the Web Part in the same site (same or different pages) works just fine.
This is because the Summary Links Web Part references the list that contains the page where the Web Part resides on. If you open the .webpart file in a text editor you’ll see ListName and ListId containing the GUID of that list. So it can be the “Site Pages” library, the “Pages” library, or any Document Library that has Web Part Pages.
You can verify this by navigating to the following URL (note to replace the actual GUID): http://sitename/_layouts/listedit.aspx?List=GUID
Bonus question: what is the value when the Summary Links Web Part is on the “default.aspx” of a site? Answer:
So what’s the solution? Just remove the ListName and ListId elements (or their values) from the exported .webpart file and you’ll have no issues importing it to other sites.
Issue is still present in May 2015 Cumulative Update and July 2015 Cumulative Update. Will contact Microsoft on this.
Microsoft has confirmed this issue and will roll out a fix in the next Cumulative Update.
Last week I was notified of an issue where bulk content approval failed for specific users. The list was configured with the default Content Approval.
They would select two or more items to approve and click the “Approve” button in the Ribbon, however that just kept “Working on it”.
Note that single item approval works just fine for them!
When watching with Fiddler and in the ULS logs it was clear that the bulk approval screen threw an Access Denied.
The user was configured with Read permissions on the site and Approve/Contribute permissions on the list (but even with Full Control on the list it failed).
After some playing around with the permission levels and permissions on the web level, it turns out that if the user has “Approve” permission on the site level it works!!
Obviously this may not be possible to grant to your users.
None so far. This was tested on Service Pack 1 (15.0.4605.1000) and September 2014 CU (15.0.4649.1001) individually.
For now either use single item content approval or give the user the “Approve Items” permission on the site level as well (workaround above).