Another possible issue is that you also have a missing link to prototype.js on this page – the script tag is there, but it does not include its src attribute, it’s just src=“”. This is happening from the SmoothScroll Action, and I recommend you follow these troubleshooting steps around this Action.
Before you do anything else, check your Freeway preferences, and make sure that “Allow AppleScript in Actions” (wording uncertain) is checked on.
Next, remove the Action from the page. If it appears on any other pages, remove it there as well. After the entire document is clear of the Action, publish once. If you have any other documents currently open, close them. Make sure that only one document is open, and it is the one you are trying to fix.
Then, follow one of the following steps, depending on how your page was constructed.
If this document has always been created / edited in Freeway 7, locate your Actions folder in ~/Library/Application Support/Freeway Pro/Actions. Look in the Actions folder or the General folder within it, and ensure that there is only one copy of SmoothScroll installed there. As a best practice, simply delete all copies of the Action you find there, and empty the trash. Then download the latest version of the Action, un-zip it, and drag its icon over the Freeway icon in your dock. You should be challenged that you are installing an Action. You should not be challenged that you are replacing an existing Action.
If this document began its life in Freeway 6, and then was edited in Freeway 7, then you need to follow the steps above again, only this time you may not find the Action. If what I suspect has happened here – that you are using the cached version of the Action from within the document – then you won’t actually find the Action in your Actions folder at all. Or you may find it in ~/Library/Application Support/Freeway 6/Actions/General. The Action won’t be sourced from there in Freeway 7.
Finally, apply the Action to one page, and preview in a browser to see if it does what you expect.
Walter
On May 22, 2015, at 6:22 PM, DeltaDave email@hidden wrote:
I think that the issue is with the javascript that responds to the click event.
It only responds to one item because of the way the script is written.
2 Responsive menus on the same page is not seen as a common use case if they share the same parent item.
That is my theory.
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options