After updating my actions, when uploading a previous site ‘Publish Problems’ shows that it cannot locate the packer.js files - I have looked in the protaculous package contents and they are there - how can FW not see them?
Does eveything need to be reapplied
Nathan Garner
Creative Director
Austin Wells Design Limited
One Elmgate Drive - Littledown - Bournemouth BH7 7EF
t 01202 301271 e email@hidden w http://www.austinwellsdesign.co.uk
Member of NAPP | Zen Affiliate | Dorset Business Member | YEC
Removed the action from the elements on the page and from the actions folder, restarted to make sure it’s no longer installed. Downloaded the latest Protaculous action, installed it, opened up the FW doc. made sure the sequence timer is working (v2.8), then applied the carousel and previewed. It does not work.
If I delete the sequence timer, then it works. They both worked together before.
If they no longer work together is there another action instead of the ST that can be used?
Nathan Garner
Creative Director
Austin Wells Design Limited
One Elmgate Drive - Littledown - Bournemouth BH7 7EF
t 01202 301271 e email@hidden w http://www.austinwellsdesign.co.uk
Member of NAPP | Zen Affiliate | Dorset Business Member | YEC
One thing you have to do that you left out – remove the Actions from the elements (or pages) they are attached to, then PUBLISH once. That clears the stack of cached Actions, which is at the root of most troubles with bundle-based Actions. Then go back through and re-build the effect.
If that doesn’t work for you, then please try creating a single-page document – from scratch – that demonstrates the problem, and send it to me off-list.
Austin Wells Design Limited
One Elmgate Drive - Littledown - Bournemouth BH7 7EF
t 01202 301271 e email@hidden w http://www.austinwellsdesign.co.uk
Member of NAPP | Zen Affiliate | Dorset Business Member | YEC
Facebook | Twitter | LinkedIn
On 11 Jun 2010, at 14:02, waltd wrote:
One thing you have to do that you left out – remove the Actions from the elements (or pages) they are attached to, then PUBLISH once. That clears the stack of cached Actions, which is at the root of most troubles with bundle-based Actions. Then go back through and re-build the effect.
If that doesn’t work for you, then please try creating a single-page document – from scratch – that demonstrates the problem, and send it to me off-list.
I’m not seeing any problems here. Safari 5 or Firefox 3.6. The carousel spins when I press the buttons, same as I would expect, in either browser. Is there a particular thing you’re trying there that is not working for you? Also, have you flushed your cache? You may have a mixture of old and new JavaScript somewhere.
Walter, I did a minor, minor tweek to the carousel action - it now works for me in this instance:
From
var select = (window.location.href.indexOf(‘?’)
To
var select = (window.location.href.indexOf(‘#’)
Nathan Garner
Creative Director
Austin Wells Design Limited
One Elmgate Drive - Littledown - Bournemouth BH7 7EF
t 01202 301271 e email@hidden w http://www.austinwellsdesign.co.uk
Member of NAPP | Zen Affiliate | Dorset Business Member | YEC
Facebook | Twitter | LinkedIn
On 11 Jun 2010, at 14:02, waltd wrote:
One thing you have to do that you left out – remove the Actions from the elements (or pages) they are attached to, then PUBLISH once. That clears the stack of cached Actions, which is at the root of most troubles with bundle-based Actions. Then go back through and re-build the effect.
If that doesn’t work for you, then please try creating a single-page document – from scratch – that demonstrates the problem, and send it to me off-list.
Oh, that makes sense then. I’ll have a look at the code and see if I
can sanitize that input a little better. There is a feature in
Carousel where you can specify a particular pane to load first by
adding its ID to the url in the querystring. I can see how a value in
the querystring that did not correspond to an element on the page
would cause a mess.
Walter
On Jun 11, 2010, at 9:41 AM, Nathan Garner wrote:
Walter, I did a minor, minor tweek to the carousel action - it now
works for me in this instance:
From
var select = (window.location.href.indexOf(‘?’)
To
var select = (window.location.href.indexOf(‘#’)