Freeway caches the Actions used in a document within the document itself. For basic one-file .fwaction files, this works great. For bundled Actions (.fwactionb) it can have mixed results. Symptoms include alerts about missing files, references to hard disks of yore, etc. The solution is to go to ActionsForge (and naturally, pledge to help make the next version of said Forge) and download the latest version and install it. Sometimes, particularly if Freeway has gotten hung up on a missing Action, you will need to remove that Action from all pages in your site, publish once, then add it back (and reconfigure). This clears out the cache and makes it work again.
On May 18, 2012, at 11:56 AM, RavenManiac wrote:
What happens if you designed a previous website using an action that’s no longer available on your current system?
Does Freeway Pro notify you that the action is missing? Does any action code written remain, even though the action is no longer available on your system?