I will shortly be upgrading to the latest version of Freeway [6.1?] and would like to keep v5.6.5 for my older websites. I intend using v6 only for new sites. I feel sure that it is possible to use two versions on the same machine, but can find no reference to it in the KB.
This was a much-discussed topic back when version 6 first came out. Instead
of searching the knowledgebase, maybe you do better to search the
FreewayTalk forum to pick up the threads of the discussion. As I recall,
it’s mostly trouble free, but the actions part was a little tricky.
–
Ernie Simpson
On Sun, Aug 25, 2013 at 11:35 AM, WildCottage email@hiddenwrote:
I will shortly be upgrading to the latest version of Freeway [6.1?] and
would like to keep v5.6.5 for my older websites. I intend using v6 only for
new sites. I feel sure that it is possible to use two versions on the same
machine, but can find no reference to it in the KB.
I have a vague recollection of some of the discussions when v6 first appeared but cannot find it on FT. I guess that I will need to check on ActionsForge for the latest/compatible versions of all those actions I use.
FW6 creates a new actions folder in Library>Application Support>Freeway Pro whereas the earlier version for Freeway 5 is at Library>Application Support>Freeway5
This means that you can have 2 different action sets 1 folder for 6 and retain your existing one for 5.
Make sure that you add 6 compatible versions to the correct folder.
FW6 creates a new actions folder in Library>Application Support>Freeway Pro whereas the earlier version for Freeway 5 is at Library>Application Support>Freeway5
This means that you can have 2 different action sets 1 folder for 6 and retain your existing one for 5.
Make sure that you add 6 compatible versions to the correct folder.
To avoid trouble, you need to go through all your actions manually (sadly there’s no automated way to do this) and compare the versions that you have to what are on ActionsForge. Once you have all your Actions up-to-date, just install FW6.
On first launch, FW6 will seek out your old FW5 actions and copy them into its own Actions folder named “Freeway Pro”. After that, any changes to Actions you make in FW6 will affect only the actions in the FW6 actions folder.
Also note that if you ever dig into the Library/Application Support folder and delete or move the “Freeway Pro” folder, that entire folder will get rebuilt on the next launch of FW6, and all the FW5 actions will get copied over for you automatically again.
To avoid trouble, you need to go through all your actions manually (sadly there’s no automated way to do this) and compare the versions that you have to what are on ActionsForge. Once you have all your Actions up-to-date, just install FW6.
On first launch, FW6 will seek out your old FW5 actions and copy them into its own Actions folder named “Freeway Pro”. After that, any changes to Actions you make in FW6 will affect only the actions in the FW6 actions folder.
Also note that if you ever dig into the Library/Application Support folder and delete or move the “Freeway Pro” folder, that entire folder will get rebuilt on the next launch of FW6, and all the FW5 actions will get copied over for you automatically again.
When you launch Freeway 6 for the first time, any Actions you have installed in 5.5(6) will be copied over for you to your newly-created Freeway Pro/Actions folder. This is a one-time step, and only happens if there wasn’t a Freeway Pro/Actions folder in your Application Support folder. This will just copy over the Actions, not any supporting files (some Actions look for their support files in named folders outside of the Actions folder), and it will just copy – not verify version and then copy.
In the ActionsForge, Actions that the authors have either tested or specially re-written for 6 get marked with a little icon indicating the status. There are also lots of Actions that work just fine, but have not gotten this mark.
You can help the authors (and me, your unpaid Forge-builder) keep this up to date by writing to the author when you find an Action that works in 6. It only takes a moment for an Action author to click a little check-box in the admin interface of the Forge to apply that badge of honor. We had a flurry of this activity when 6 was released, but by no means have all the Actions been vetted yet.
Thanks,
Walter
On Aug 26, 2013, at 3:28 AM, JDW wrote:
To avoid trouble, you need to go through all your actions manually (sadly there’s no automated way to do this) and compare the versions that you have to what are on ActionsForge. Once you have all your Actions up-to-date, just install FW6.