i can’t get ScripyAccordion to work with FW 7/elcapitan.
it’s an old FW 6 document, which worked fine in 2013 (!) … but even when i open it in FW 6, i get java script- or timeout-errors .
i’ve read the questions/answers on actionsforge and i’ve tried all (new document, de-installation of the action, activate apple script etc.).
any ideas? compatibility-issue? is there a new action for this perhaps?
sorry, if i missed some infos here - I’m using freeway/freewaytalk only from time to time.
I’d like to add, that exactly the same happened to me with ScriptyLightbox and ScriptyCarousel!!! (FW5.5 but this didn’t matter at all, ELCapitan as well). So obviously you’re not alone.
Do you have this problem with a new, (non-template) blank document, with one accordion on the one and only page (and obviously, no other Actions)?
Walter
On Feb 25, 2016, at 3:52 AM, Dieter email@hidden wrote:
i can’t get ScripyAccordion to work with FW 7/elcapitan.
it’s an old FW 6 document, which worked fine in 2013 (!) … but even when i open it in FW 6, i get java script- or timeout-errors .
i’ve read the questions/answers on actionsforge and i’ve tried all (new document, de-installation of the action, activate apple script etc.).
any ideas? compatibility-issue? is there a new action for this perhaps?
sorry, if i missed some infos here - I’m using freeway/freewaytalk only from time to time.
I wrote that without testing first, but I just tested and yes, it works perfectly. Freeway documents change internally from generation to generation, and a document created in 7 is (probably) measurably different than one started in 5 or 6 and then “upgraded”. From the sounds of things, the fact that your accordion doesn’t work may be a symptom of another issue entirely, maybe not even that Action at all.
Also, the way that Freeway decides (in older Actions) whether you are currently online or not has been known in the past to be an effective “canary in the coal mine” for subtle networking errors on your Mac or its Internet connection. Search this site for the term “packet loss” and see what you turn up in the way of troubleshooting suggestions.
Walter
On Feb 25, 2016, at 9:14 AM, Walter Lee Davis email@hidden wrote:
Do you have this problem with a new, (non-template) blank document, with one accordion on the one and only page (and obviously, no other Actions)?
Walter
On Feb 25, 2016, at 3:52 AM, Dieter email@hidden wrote:
i can’t get ScripyAccordion to work with FW 7/elcapitan.
it’s an old FW 6 document, which worked fine in 2013 (!) … but even when i open it in FW 6, i get java script- or timeout-errors .
i’ve read the questions/answers on actionsforge and i’ve tried all (new document, de-installation of the action, activate apple script etc.).
any ideas? compatibility-issue? is there a new action for this perhaps?
sorry, if i missed some infos here - I’m using freeway/freewaytalk only from time to time.
yes - i have this problem with a new blank one page document, only with one text-item, accordion applied to it.
it will not publish.
how can i get rid of all action (which are not freeway-implemented)? whats the best way to make sure, freeway has only this one action?
I assume the cause maybe some old actions … or elcapitan.
Walter, you tested under elcapitan?
This has NOTHING to do with ElCapitan cause I altered my file some days ago and it worked like a charm!! Some days later it failed. The more interesting question is, what is it then? Both - file and action (under the same condition of OS) worked as a charm. I suspect this SPARKLE thing (but just a guess).
You can get rid of actions by NOT using them at all. No need to uninstall them or any further thing to do. That’s my practice today. My file in question is currently under “reconstruction”. And it won’t have any action applied anymore. Unfortunately it will take me some weeks to substitute.
Obviously it has to do with some actions.
After turning off all actions in the actions-window (edit > actions) while the document is opened, and turning on again only scriptyaccordion, i could publish again with success.
unfortunately i can’t tell which combination of actions will cause these problems.
When I get these timing out/Javascript errors, I temporarily turn off the WiFi on the Mac – or if hard-wired I’d either turn off Ethernet or disconnect the cable. Publish the site locally, (Command-P), and it should work. Reconnect, and try uploading again.
This usually solves it but if not, you do now have an up to date site folder containing all the correct html and Javascript to manually upload.