A bit of history: The first versions of the “Scripty” Actions (mine and Softpress’s and Paul Dunning’s – probably some others I have forgotten here, sorry) did not use the Google CDN to get their library code. Instead, everything was bundled inside the Action itself. There are two major libraries in these Actions – Prototype.js and Scriptaculous. These are toolkits of programming shortcuts for building JavaScript applications, and they let you write very neat and tidy code and have it work across all the wild range of different browsers and platforms.
When we decided to start using the Google CDN to deliver these libraries, we left all of that library code where it was, as a backup in case you were building your site on a desert island away from any network. (Even if you get that error that you did, if the Action still completes its publish pass, the page it generates will work, since it is still linking to the Google CDN for Prototype and Scriptaculous.) This decision introduced a subtle issue, which only came to light in the past year or so: if your network was just slightly imperfect, you would get time-outs while publishing, as Freeway would send a ping to Google to see if you had a live network connection, and if that single ping didn’t come back, Freeway would wait for it so long that the Action would time out and publishing would fail. The Action would be marked as degraded and wouldn’t run any more.
To fix this problem, I decided last year to completely give up on the bundled libraries, and always link to the CDN. This allowed me to build more complex Actions without polluting the head of the page with acres of JavaScript, and to ship single-file Actions that had no internal dependencies. Protaculous 2 and Carousel 2 were the initial result of that architectural decision.
To upgrade from Protaculous to Protaculous 2, what you need to do is go through your document (maybe duplicate it in Finder so you can open the two versions side-by-side) and copy the JavaScript you have pasted into the Function Body editors in Protaculous and paste it into the DOM Loaded Observer or Window Load Observer editors in Protaculous 2. You will also find that the interface for the “Libraries” picker is gone, replaced with a note that we always link to Prototype, and you can optionally add individual libraries from the Scriptaculous toolkit.
To upgrade from Protaculous to Carousel 2, you need to remove all instances of the Carousel Actions, publish once, then go through and re-apply the Carousel 2 equivalents to each element. The interface is identical, but the Actions work entirely differently from one another, so you can’t just pick one off and add the other without going through that step of publishing without the Actions applied.
Once you have done these steps, you should no longer be sourcing the cached versions of the Protaculous action bundle, and you will have a much leaner page that works across more browsers.
Walter
On Apr 9, 2013, at 8:54 AM, gfel wrote:
Thanks Walter,
When I upgraded to FW6 I removed the Protaculous and Carousel actions from the actions folder and replaced them with the Protaculous2.fwaction and Carousel2 so these are the ones I now have in the actions folder. I tried to follow the release notes Softpress issued with FW 6 in regard to updating the actions.
So do I need to use and reinstall an older action in FW6 to remove this error? I am slightly confused when you say Protaculous2 is written in a completely different manner…as this is probably why I am getting the error. Is Protaculous part of the new Carousel2 action which I have installed? Although my carousels seem to be working in preview?
Thanks
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options