There seems to be both a reference to the Google-hosted versions of the Prototype/Scriptaculous libraries and a partially-breken reference to local files on your server for the same two libraries. If ScriptyFader is the only Action on this page, then I can’t explain this. If there’s another Action on the same page that uses these libraries, then it’s possible that there’s a conflict between them.
Have you used any of the built-in FX Actions, or any other Scripty Actions (besides Fader) on this page?
Walter
On Oct 12, 2011, at 3:32 PM, Justin Easthall wrote:
Hi - bot sure if you will get this - my email is down whilst this iCloud mess gets sorted but anyway I died what you suggested but I don’t know what this means?
"I started fiddling with the settings in the ScriptyAccordion, turned the Initially open picker to a number at random, published, then turned it back to 0 and published again. Everything works, in all browsers.
If you could clarify this? I will email you once back up if I don’t hear from your here.
I clicked on the navigation menu item, and that opened up the ScriptyAccordion controls in the Action palette. I used the picker to choose one of the elements to be open by default, I think number 3, but I can’t recall specifically. I published once, and then changed the picker back to None, and published again. After that, everything worked – accordion and news fader.
Note that if you have a different (older) version of the Accordion Action installed, it won’t have this picker. You should upgrade the Action in that case.
At no time did I see the same mutilated code that your page had, with the (correct) two references to the Google Ajax CDN, followed by a (broken) reference to the effects.js library. I suspect that you can clear that part up by simply moving to a new Site folder on your Mac, which will force the Action to copy over the files correctly.
Walter
On Oct 13, 2011, at 1:37 PM, Justin Easthall wrote:
Hi - bot sure if you will get this - my email is down whilst this iCloud mess gets sorted but anyway I died what you suggested but I don’t know what this means?
"I started fiddling with the settings in the ScriptyAccordion, turned the Initially open picker to a number at random, published, then turned it back to 0 and published again. Everything works, in all browsers.
If you could clarify this? I will email you once back up if I don’t hear from your here.
0.6.4is what I downloaded today. I did what said but no luck so far… I don’t see an option to choose which element to be be open only an option to have the first element open on page load?
Then you need to remove the ScriptyAccordion Action from every element on every page in your document, publish once (very important) and then apply the Action again. You’re seeing the checkbox because you are actually using the cached version of the Action within your document. This is probably also why it’s acting broken).
Walter
On Oct 13, 2011, at 2:13 PM, Justin Easthall wrote:
0.6.4is what I downloaded today. I did what said but no luck so far… I don’t see an option to choose which element to be be open only an option to have the first element open on page load?
I just checked even though the action was being installed it was not updating the action in Freeway so I deleted it manually and added 0.7.1 I’ll see if this works…
Sadly, that is probably the #1 or #2 reason for support issues with my Actions. The caching mechanism built into Freeway is ordinarily a Very Good Thing, because it makes documents more portable, but for bundle Actions (multiple folders and files that masquerade as a single file) it just does more harm than good.
Walter
On Oct 13, 2011, at 2:22 PM, Justin Easthall wrote:
Awesome that did the trick… So prob was my freeway was not updating the new action? Never seen that happen before