I looked over many threads and posts on many sites and wasn’t able to find code that worked for me. Some of it would be close. Others buggy. Below I’ve outlined the JQuery code that worked perfectly for my needs and I hope you find it helpful too.
This example was deployed to a SharePoint page so the “/_layouts/images/plus.gif” was used to leverage the OOTB graphics for a plus/minus icon feel.
// bind to accordion object
$(document).ready(function(){
$('#container').accordion({
header: “h3?
});
});
// actions taken upon clicking the expand all (collapse all) link
$('#container #expand').click( function() {
// if link was expand then show and toggle text
var currHTML = $('#container #expand').html();
if (currHTML.indexOf(“Expand All”)>0) {
$('#container .section').slideDown();
$('#container #expand').html(“
Collapse All”);
} else {
// if link was collapse then hide and toggle text
$('#container .section').slideUp();
$('#container .section').each(function(i){
if (i==0) $(this).slideDown();
});
$('#container #expand').html(“
Could not find the file ‘C:WINDOWSTEMPf611fafc-73d8-4b48-bc1e-f9ef6d7cb991Exportsettings.xml’
This error message comes up when performing a SharePoint Designer 2007 site export and import above 25 MB. There are some helpful blog articles already written on this like farhanfaiz’s post with a sample XML file with cabsdk workaround. And this Technet post encourages server side changes to allow for larger files. However, you might find yourself like me without server access and unable to resolve the issue.
Backup Steps
Open SharePoint Designer to the source site
Click [ Site Administration Backup Web Site ]
Provide a local file name to save output
Do not trust the success message. If your site was over 25 MB it actually just failed. Delete the CWP file, it’s worthless.
Browse to the site’s Recycle Bin and restore all of the files with a crazy GUID number prefix
Open the site’s root folder in SharePoint Designer
Highlight these GUID files, right click Publish, and send them to your local file system
Create a New Folder on the local file system
Extract the content of all the CMP files to this folder
Use [ CABARC N newfile.cmp *.* ] to build a single large CMP file
This new CMP file contains all of the files of the disparate ones. It’s easy to manage and provide a reliable import mechanism.
If restoring to another MOSS farm first move this new CMP file to that remote machine
Restore Steps
Open SharePoint Designer to the target site
Click [ Site Administration Restore Web Site ]
Browse for [ newfile.cmp ]
Enjoy seeing the restored files in the target site’s home folder
Go open a cold beer!
NOTE: You can also use [ STSADM -O IMPORT -URL FILENAME newfile.cmp ] for the restore if you have console access on the destination MOSS server.
NOTE: If the target MOSS farm lacks Feature Definitions (SPFeature) the source had activated the import will fail. To resolve you can:
Install the features
Open the Manifest.xml and Requirements.xml inside of the CMP to remove those references with Notepad. Re-create the CMP with CABARC and then run the import again.
In this brief movie clip I walk through how to create rich Data View Web Parts with Conditional Formatting to provide a smarter display of numerical data. Colors and icons helps readers to better understand the data than what numbers alone can do.
Thank you for watching and please leave any feedback in the comments for my future posts.
