[Pro] ScriptyAccordion Errors

I cannot seem to get ScriptyAccordion to work. Javascript error occurs each time using Preview, Publish or Browser. Error: ‘An error was detected in the JavaScript of the action ScriptyAccordion’.

Undoubtedly I am doing something wrong but I can’t figure it out. Using a completely blank Master with no other content, script, action, etc that could be causing a conflict. Nothing on the page but the HTML box containing the exact text per instructions using H2 for header, etc.

To recap what I have done:

Installed ScriptyAccordion action. Appears to have installed without problem as components are showing in Edit/Actions. Restarted Freeway Pro after first instance of error to see if this would correct problem. It didn’t. Then removed Action in Finder and reinstalled. New set of components in place.

Created content following instructions. Applied action (selected item, then Item/Actions/ScriptyAccordion). Error occurs on previewing or publishing. Bypassing the error, I get the page with all the text visible.

Thought perhaps the proper resources had not been loaded for some reason on applying the action but the scriptaculous190packer, prototype1700packer, scriptaculous181packer and prototype1602packer files are all in the Resources folder.

After many futile attempts, I looked at the page created in Freeway Pro using a text editor. The script src and body (HTML box) are all there but the code that should be in the head tag is all missing (when compared to the page source on the demo).

Suggestions please.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Do you have more than one instance of the Action installed? You should only see one pair here: 190 + 1700, or 181 + 1602. Are there any other Actions applied on this page or others in the same document. Can you try a brand new empty site, with no other sites open at the time, and see if you get this specific error when there is only one page in the site with one accordion on it?

Walter

On Sep 10, 2012, at 6:36 AM, Jack Reynolds wrote:

Thought perhaps the proper resources had not been loaded for some reason on applying the action but the scriptaculous190packer, prototype1700packer, scriptaculous181packer and prototype1602packer files are all in the Resources folder.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

This would be the natural result of not being able to publish the page without errors. I can assure you that the Action works here and most places. Where it doesn’t, it’s because of conflicts with other versions of the same Action.

Walter

On Sep 10, 2012, at 6:36 AM, Jack Reynolds wrote:

After many futile attempts, I looked at the page created in Freeway Pro using a text editor. The script src and body (HTML box) are all there but the code that should be in the head tag is all missing (when compared to the page source on the demo).


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Thanks for your assistance Walter. I have no doubt the Action works. As I said in my post, undoubtedly I am doing something wrong/failing to do something, but I cannot see what it is.

To ensure there were no duplicates I uninstalled the Action in the Finder and reinstalled a fresh copy.

I then opened a brand new empty site, with no other site open. On a blank page I opened an HTML box, inserted the text and made sure it matched your instructions.

Once done, on clicking Preview I got the Javascript error box indicating the ‘Action took so long it timed out’. On closing that message I get the ‘could not publish due a Javascript error in the Freeway action message’.

I then closed the new site, quit the app, restarted the app and opened another new empty site, same result.

At that point I went back to the original site that caused the initial problems and, copying the code in the head tag on the demo, I pasted that code into the page using Page/HTML Markup. The accordion works fine although I don’t know if I have any extraneous code from the demo.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Aha. That I have seen here, and it’s always related to my network connection. If you disable your entire network (turn off Airport or Ethernet – however you connect your Mac to the net) and publish, it should work immediately.

Then check your network connection for timeouts or dropped packets. Turn your network back on. Open Applications/Utilities/Terminal and type the following cryptic command:

ping -c 100 ajax.googleapis.com

You should see a bunch of text scrolling up, and at the end of 100 tries, you will see a statistic of how many attempts to contact that server made it all the way there and back. Anything other than very high 99%+ is bad. My guess is you will see some measurable amount of packet loss, probably in the 9 - 10% range. That seems to be the threshold where this Action becomes the canary in the coal mine.

Walter

On Sep 10, 2012, at 12:55 PM, Jack Reynolds wrote:

Once done, on clicking Preview I got the Javascript error box indicating the ‘Action took so long it timed out’. On closing that message I get the ‘could not publish due a Javascript error in the Freeway action message’.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Thank you very much for the advice Walter. That solved the problem. Interestedly though I had no packet loss on the test:

‘100 packets transmitted, 100 packets received, 0.0% packet loss’


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

So disabling the network allowed the page to publish, but you still can’t publish with the network live? Make sure you have AppleScript enabled for Actions in your Freeway preferences. Also, what version of Freeway Pro are you using?

Walter

On Sep 10, 2012, at 1:21 PM, Jack Reynolds wrote:

Thank you very much for the advice Walter. That solved the problem. Interestedly though I had no packet loss on the test:

‘100 packets transmitted, 100 packets received, 0.0% packet loss’


freewaytalk mailing list
email@hidden
Update your subscriptions at:
List Options | FreewayTalk


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Sorry for not being clearer. Turning off the network allowed me to finally publish the page. Turning on the network again, the page continues to publish without any problem. Tried a second new site to confirm. I have to disconnect, publish, then reconnect and all works fine.

Applescript is enabled. Using Freeway Pro 5.6.5


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

That is genuinely odd. No idea why it would work after you toggle the network, and that’s definitely not how it should be working. Can you please open up the Console app (same folder as Terminal) and leave it open while you try to exercise this error? I would love to see if there is anything logged in the console while this problem is making itself known.

Walter

On Sep 10, 2012, at 1:32 PM, Jack Reynolds wrote:

Sorry for not being clearer. Turning off the network allowed me to finally publish the page. Turning on the network again, the page continues to publish without any problem. Tried a second new site to confirm. I have to disconnect, publish, then reconnect and all works fine.

Applescript is enabled. Using Freeway Pro 5.6.5


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

Here is the printout from Console app when the errors occurred. I’m wondering if the fly in the ointment might be ML’s Quarantine?

10/09/2012 18:43:49.993 Dock[202]: no information back from LS about running process
10/09/2012 18:45:49.696 Dock[202]: find_shared_window: WID 106295
10/09/2012 18:45:49.696 Dock[202]: CGSGetWindowTags: Invalid window 0x19f37
10/09/2012 18:45:49.697 Dock[202]: find_shared_window: WID 106294
10/09/2012 18:45:49.697 Dock[202]: CGSGetWindowTags: Invalid window 0x19f36
10/09/2012 18:45:49.698 Dock[202]: find_shared_window: WID 106293
10/09/2012 18:45:49.698 Dock[202]: CGSGetWindowTags: Invalid window 0x19f35
10/09/2012 18:45:49.699 Dock[202]: find_shared_window: WID 106292
10/09/2012 18:45:49.699 Dock[202]: CGSGetWindowTags: Invalid window 0x19f34
10/09/2012 18:45:49.699 Dock[202]: find_shared_window: WID 106291
10/09/2012 18:45:49.699 Dock[202]: CGSGetWindowTags: Invalid window 0x19f33
10/09/2012 18:45:49.699 Dock[202]: find_shared_window: WID 106290
10/09/2012 18:45:49.699 Dock[202]: CGSGetWindowTags: Invalid window 0x19f32


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Are you running a Mac App Store version of Freeway? Because you are able to make it work by disabling the network, then publishing, and then re-enabiling the network, I am inclined to say that it isn’t Quarantine, although that is a good suggestion – the Action is sending a shell command out to the Unix-y bits of Mac OS to get the current state of your network. Maybe that’s no longer allowed these days.

Joe, can you comment on this?

Walter

On Sep 10, 2012, at 1:57 PM, Jack Reynolds wrote:

Here is the printout from Console app when the errors occurred. I’m wondering if the fly in the ointment might be ML’s Quarantine?

10/09/2012 18:43:49.993 Dock[202]: no information back from LS about running process
10/09/2012 18:45:49.696 Dock[202]: find_shared_window: WID 106295
10/09/2012 18:45:49.696 Dock[202]: CGSGetWindowTags: Invalid window 0x19f37
10/09/2012 18:45:49.697 Dock[202]: find_shared_window: WID 106294
10/09/2012 18:45:49.697 Dock[202]: CGSGetWindowTags: Invalid window 0x19f36
10/09/2012 18:45:49.698 Dock[202]: find_shared_window: WID 106293
10/09/2012 18:45:49.698 Dock[202]: CGSGetWindowTags: Invalid window 0x19f35
10/09/2012 18:45:49.699 Dock[202]: find_shared_window: WID 106292
10/09/2012 18:45:49.699 Dock[202]: CGSGetWindowTags: Invalid window 0x19f34
10/09/2012 18:45:49.699 Dock[202]: find_shared_window: WID 106291
10/09/2012 18:45:49.699 Dock[202]: CGSGetWindowTags: Invalid window 0x19f33
10/09/2012 18:45:49.699 Dock[202]: find_shared_window: WID 106290
10/09/2012 18:45:49.699 Dock[202]: CGSGetWindowTags: Invalid window 0x19f32


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

No it is not a Mac App Store version, it’s the direct download from Softpress.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I’ve the same problem with ScriptyAccordion since Mountain Lion !
The action “ScriptyAccordion " on the page… mets too many time to be carried out (expired time)
It is very irritating because from time to time that goes while starting again Freeway but I lose very much time.
Grrrr… Same problem in new Freeway 5.6.5


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options