If you’ve already updated to Freeway Pro 5.6.2, you need the latest versions of these Actions:
AjaxFileListing 0.5
CalendarView 0.5
Carousel 1.3
Carousel Button 1.0
Carousel Pane 0.4
Carousel Tab 0.8
Carousel Text Tab 0.3
Observer 0.3
Protaculous 0.7
ScriptyAccordion 0.8
ScriptyFader 0.4
ScriptyLightbox 0.4
ScriptyLightbox2 0.6
SmoothScroll 0.5
Sticker 0.5
All of these are backward-compatible with earlier versions of Freeway, but if you use any of the built-in Scriptaculous effects in the newest Freeway along with any of my Actions, you must update mine to stay in synch with Freeway’s JavaScript libraries.
BONUS!!! One major new feature: ScriptyLightbox2 now can link to HTML content (not just photos and movies) – either within or outside of your site – in its little popup windows. It does so using an iframe, so you don’t have to go through all of the fuss with PHP Make Insert Page on your in-site pages, too. And unlike ScriptyLightbox, it does support a fixed dimension for the player window, so you can link to Vimeo or YouTube content without getting a gigantic-pixel-fest on your screen.
As with any upgrade to these Actions, I recommend that you follow this set of steps for the greatest compatibility with existing documents (anything you created using an earlier version of the Actions).
Close all currently open Freeway documents. (You may optionally leave Freeway running, but you may also quit it as well.) Open your Actions folder. In a stock install, the best place to look is within /Users/yourname/Library/Application Support/Freeway 5/Actions/General. (On Lion, you will need to use a specific command – which I don’t know but you can Google for it – to make your Library folders visible, as they are hidden by default.)
Locate all of the Actions listed above and delete them (and empty the trash). Note that Carousel [anything] and Observer are bundled inside of the Protaculous Action bundle, so don’t look for them under their own names.
Decompress them and drag them over the Freeway application icon in your Dock or in your Applications Folder. This will install them correctly (alerting Freeway to their presence directly).
Now, open your documents one at a time and follow the following sequence of steps:
Locate all instances of any of these Actions on all pages where they are used, and remove the Action from the page or item(s). If you had pasted any custom code into Protaculous or Observer, be sure to copy that to a text file for safe-keeping. You do not need to remove any elements that had the Actions applied to them (as in Carousel Pane instances, for example), just leave them wherever they lay.
Publish the document once.
Go back through the pages and re-apply the Actions.
Publish again, and upload. The new library code will be loaded and will run.
Please let me know if you spot any incompatibilities. If you see any errors, try to copy them (or screenshot them) and post them here or on your server so I can attack any problems.
Thanks, and have a great holiday and happy new year!
Not sure. I would follow these steps for any “bundle” Action (the filename of the Action will end in fwactionb when you un-zip it). That’s where I have seen the most trouble. Normal (fwaction) file-based Actions are just fine with the updates, but when there’s a bundle containing resource files that the Action needs to use and link to pages, Freeway can get confused when those files are changed after the document has been published at least once.
Walter
On Dec 20, 2011, at 11:17 PM, Kelly Crossley wrote:
Walter, I just followed your update instructions and they worked perfectly.
By the way, do I need to do this with all of my applied actions, including the ones pre-installed with Freeway Pro?