It would appear that the Navigation Popup Action is running after the Externalize code and is getting stripped from the page. In future I suspect I’ll have to have the Action log all of the code it is externalizing and then only eliminate this from the page to make sure that missed Actions like this don’t end up breaking pages.
For the moment I would suggest making a small change to the stock Navigation Popup Action. You can find it in the application bundle here;
/Applications/Freeway 5.5 Pro.app/Contents/SharedSupport/Actions/Standard.fwactionb/Contents/Resources/Actions/Other/Navigation Popup.fwaction
Open the Action up in a good text editor (Text Wrangler is great - http://www.barebones.com) and search for the line;
and change this to;
Save the Action (ideally in your Actions folder) so that when you update Freeway next the updated Action won’t be lost;
/Users/tim/Library/Application Support/Freeway 5/Actions/
You should now be able to externalize the page scripts again and have the script work as expected.
I’ll log a suggestion that the Navigation Popup Action runs earlier in the publishing process so this can be avoided in future.
On 26 Jan 2012, at 16:15, Justin Easthall wrote:
GREAT! yes I do (externalise) and had remove Java selected just redone and all good thanks