David , thank you for your tip also – I think ‘cleaning up’ the code has got me this far.
I am learning as I go (but its very frustrating!)

If you get the “This will be shown to users with no Flash or Javascript”, then the script is either failing over to HTML because the user doesn’t have Flash (or the correct version) installed, or [as you discovered] there’s poor formatting in the markup.

Regardless of if you’re using 2007 or 2010 (but more so with 2010), it’s not a great practice to put that markup directly in the CEWP. If you’re dynamically building markup, as is the case here with the XML that drives the cloud, storing it in the CEWP directly will often result in physically saving the dynamically written markup when you save the page (making it static). As a best practice, any sort of script files should be stored in a library, with the CEWP pointed to the script file in the library.

Regards,

David

Unfortunately it has been years (and a couple jobs ago) since I did it. You should be able to use that blog post verbatim, just changing the red text in the script to reflect the correct site URL, List Name, and fields (columns). This all assumes that you’ve got a list of all your tags, vs trying to actually pull categories from a SharePoint blog or something (which would be a little more complicated–though certainly possible).

The XML that’s built in the script (soapEnv) is the XML for the SOAP (web service) request. You’re essentially defining what you want the SharePoint web service to return to you. You need a FieldRef element in the ViewFields node, for every column in the list that you want to return, so this example assumes you have columns called “Tag”, “Link”, and “Style”. To make it simple, you could remove the “Style” field ref, and the related (style=’” + $(this).attr(“ows_Style”) + “) markup in the script.

You don’t need to touch the $.ajax lines of the script, this is the jQuery piece that sends off the SOAP request to the SharePoint web service (lists.asmx). The processResults function then takes the XML that the web service returns and parses it, building a string (“tags”) of the link for each row returned. Note that when you request fields in the SOAP XML you’re using “Link”, and when you work with the returned information you’re using “ows_Link” SharePoint’s Office Web Services will prefix an “ows_” on the front of your column names when the data is returned.

From there you’re wrapping the whole thing in a “tags” node, so your final script-generated XML should look something like this:

<tags>
<a href='http://link/a'>Link A</a>
<a href='http://link/b'>Link B</a>
<a href='http://link/c'>Link C</a>
<a href='http://link/d'>Link D</a>
</tags>

My advice would be to focus on getting that data to return correctly, before you add in the Flash component. If it’s blowing up, it’s probably more likely to be a result of the data being returned badly, as opposed to an issue with wp-cumulus. You could add an alert(tagDetails); to your script so the browser throws an alert box with the XML in it (for debug purposes).

Once you can validate that the data is correct, you can add in the SWFObject piece which loads the wp-cumulus and pushes the XML (tagDetails) variable to it for rendering.

Would you have an example of the code you used?
I am on a steep learning curve!

When I did this in 2007, it was through a CEWP. You can use SPServices to query the list/fields and build the XML markup that wp-cumulus consumes. You’d need to add jQuery and SPServices to a library, load them in your HTML/TXT file, then include the SPServices CAML query and JavaScript. You’d then want to point your CEWP to use that HTML/TXT file as its source.

Any chance of sharing your knowledge?

You should be using Get-SPWeb, not Get-SPSite. As long as a root web exists on the site collection it should work.

Cannot find an SPSite Object with ID or URL http://rootsitecollection/managedpath/sitecollection2

I figured out it is necessary to use the Collection ID if it is not the Root Site Collection, to make this Power Shell example with the CSV list of groups work in that circumstances.

But that’s where I’m stuck… I tried to use following instead w/ column 1 of CSV using ID, but no deal:
$ web = GetSPSite $group.Web

Suggestions?