Here are the latest versions available at ActionsForge. If you get one, get them all!
AjaxFileListing 0.4.3
CalendarView 0.4.6
Protaculous 0.6.4
Observer 0.2.4
Carousel 1.2.7
Carousel Pane 0.3.4
Carousel Button 0.9.4
Carousel Text Tab 0.2.5
Carousel Tab 0.7.4
ScriptyAccordion 0.6.3
ScriptyLightbox 0.3.5
Protaculous includes the other Actions indented below it in this list, so you only have to download 5 files here to get all these Actions.
Each Action that includes files from the Prototype/Scriptaculous library has had some minor tweaks (thanks to Joe Billings) to fix a timeout problem. There are no interface updates or feature changes in this version.
If you have experienced problems with Freeway “timing out” while publishing, this update should fix this problem for you.
Please note, if you have not kept current with the latest version of these Actions, you may need to go through the following “dance” to enable them in your documents. This is particularly true if you pick up an older document that you started with a previous version of any of these Actions.
Go through your document page by page, and make note of any Actions used on each page or the elements on each page. If any of the above Actions are used, or if you used any of the built-in FX Actions, or if you enabled an “effect” in the Target Show/Hide Actions, you must make these changes:
Wherever you find one or more of these Actions applied, remove them (noting their settings for later).
Publish the document (you do not need to upload, just publish once).
Just in case it wasn’t clear enough here in the first paragraph: if you update one of these Actions, you MUST update all of them. (Well, all of them that you have currently installed.)
If you haven’t updated recently, you really need to do this because there are major structural changes that impact any page that includes one or more of these Actions.
If we’ve used the actions on older site, then install the new actions, when we go back to edit these older sites, will the lightbox ‘simply’ update or do we have to re-apply in all instances?
Nathan Garner
Creative Director
Austin Wells Design Limited
One Elmgate Drive - Littledown - Bournemouth BH7 7EF
t 01202 301271 e email@hidden w http://www.austinwellsdesign.co.uk
Member of NAPP | Zen Affiliate | Dorset Business Member | YEC
Facebook | Twitter | LinkedIn
On 5 Jun 2010, at 19:11, waltd wrote:
Just in case it wasn’t clear enough here in the first paragraph: if you update one of these Actions, you MUST update all of them. (Well, all of them that you have currently installed.)
If you haven’t updated recently, you really need to do this because there are major structural changes that impact any page that includes one or more of these Actions.
That depends how old the previous versions were. I changed the internal structure of my Action bundle (the “package” format that holds all the various support files together in something your Mac recognizes as a single file). So when you move from one of the older versions to the current, you have a one-time process of re-applying the Actions from scratch.
Once that’s done, there shouldn’t be any need to do this again on minor point-version changes. Those changes should be confined to the content of the files in the bundle, not the internal structure of the bundle itself, which was what threw off Freeway in the first place.
OK thanks Walter - I only ask as I have about 8 sites using the old action and would rather not have any problems or spend a lot of time re-doing all the galleries.
Nathan Garner
Creative Director
Austin Wells Design Limited
One Elmgate Drive - Littledown - Bournemouth BH7 7EF
t 01202 301271 e email@hidden w http://www.austinwellsdesign.co.uk
Member of NAPP | Zen Affiliate | Dorset Business Member | YEC
Facebook | Twitter | LinkedIn
On 7 Jun 2010, at 14:14, waltd wrote:
That depends how old the previous versions were. I changed the internal structure of my Action bundle (the “package” format that holds all the various support files together in something your Mac recognizes as a single file). So when you move from one of the older versions to the current, you have a one-time process of re-applying the Actions from scratch.
Once that’s done, there shouldn’t be any need to do this again on minor point-version changes. Those changes should be confined to the content of the files in the bundle, not the internal structure of the bundle itself, which was what threw off Freeway in the first place.
When I goto actionsforge and see the Scripty Lightbox 0.3.8 - the downloaded file is version 0.2.1
Nathan Garner
AWD
FW5 Pro | MacBook Pro | Snow Leopard
On 5 Jun 2010, at 19:11, waltd wrote:
Just in case it wasn’t clear enough here in the first paragraph: if you update one of these Actions, you MUST update all of them. (Well, all of them that you have currently installed.)
If you haven’t updated recently, you really need to do this because there are major structural changes that impact any page that includes one or more of these Actions.
Ignore me, I hadn’t deleted the old version first…
Nathan Garner
Creative Director
Austin Wells Design Limited
One Elmgate Drive - Littledown - Bournemouth BH7 7EF
t 01202 301271 e email@hidden w http://www.austinwellsdesign.co.uk
Member of NAPP | Zen Affiliate | Dorset Business Member | YEC
Facebook | Twitter | LinkedIn
On 8 Jun 2010, at 10:26, Nathan Garner wrote:
Walter,
When I goto actionsforge and see the Scripty Lightbox 0.3.8 - the downloaded file is version 0.2.1
Nathan Garner
AWD
FW5 Pro | MacBook Pro | Snow Leopard
On 5 Jun 2010, at 19:11, waltd wrote:
Just in case it wasn’t clear enough here in the first paragraph: if you update one of these Actions, you MUST update all of them. (Well, all of them that you have currently installed.)
If you haven’t updated recently, you really need to do this because there are major structural changes that impact any page that includes one or more of these Actions.