Hi Waltd – I have tried updating the carousel/protaculous actions for an existing site, but the Carousel action has stopped working.
I had to delete the related action on each object it applied to, and replace it with the updated action in order not to get a missing resources error on build/upload.
Just wondering if we have a conflict somewhere, or if I need to tear down the Carousels and remake them for the updated actions.
I have noticed this problem before, and I believe it has to do with
the way that Freeway caches Actions and file references in those
Actions within the current document. This can make updates such as the
one we just went through more painful than they should be.
For an interim step, yes, I would recommend removing the Actions
wherever they are employed in your document, publishing once, then re-
apply them (build the effects back up from scratch). It’s a one-time
pain, but a necessary one until (maybe) we see a new version of
Freeway that addresses this shortcoming in the Actions API.
Walter
On Apr 26, 2010, at 6:12 AM, Ian Halstead wrote:
Hi Waltd – I have tried updating the carousel/protaculous actions
for an existing site, but the Carousel action has stopped working.
I had to delete the related action on each object it applied to, and
replace it with the updated action in order not to get a missing
resources error on build/upload.
Just wondering if we have a conflict somewhere, or if I need to tear
down the Carousels and remake them for the updated actions.
Waltd, did you have any luck sorting out with Freeway this problem yet or am I just to eager???
Thanks
MIke
On 21 Apr 2010, 1:39 pm, waltd wrote:
Huh. You’re right. There must be something about the order of Actions
during the publish process that is causing this problem. I’ll follow
up with Softpress.
Walter
On Apr 21, 2010, at 4:18 AM, scoutdesign wrote:
By the way, I have indented the list by one level within the css box.
I just sent a sample document this morning, we’ll see what happens
from there. In the interim, you can work around this by hand quite
easily.
Go through the carousel and its panes, clicking once on each one
and writing down the name that you see in the Title field of the
Inspector while that item is selected. Be sure to note the name
exactly – this is case-sensitive.
Open up your CSS Menus list and delete all of the Action items from
within it. Then type in the navigation text you want to have appear
for each option.
Select the link text for the first option, then press Apple K to
open the Hyperlink dialog. Click on the External tab in that dialog,
and enter a hash mark (octothorp) followed by the exact name of the
first pane. F.e.: #item3
Repeat for each of your other options.
Publish and enjoy.
This is the only thing that the Action does, and the only reason it’s
done as an Action is to simplify the process for you (make it
impossible to get the ID of the pane wrong). The inter-relation
between these two Actions is puzzling, because the Carousel Text Tab
Action is a very lightly re-written version of the Text Rollover
Action from Softpress.
Walter
On Apr 26, 2010, at 10:36 AM, scoutdesign wrote:
Waltd, did you have any luck sorting out with Freeway this problem
yet or am I just to eager???
Thanks
MIke
On 21 Apr 2010, 1:39 pm, waltd wrote:
Huh. You’re right. There must be something about the order of Actions
during the publish process that is causing this problem. I’ll follow
up with Softpress.
Walter
On Apr 21, 2010, at 4:18 AM, scoutdesign wrote:
By the way, I have indented the list by one level within the css
box.
Many thanks Waltd - will give this a go when I can, and report back to this thread on the efficacy.
On 26 Apr 2010, 2:33 pm, waltd wrote:
I have noticed this problem before, and I believe it has to do with
the way that Freeway caches Actions and file references in those
Actions within the current document. This can make updates such as the
one we just went through more painful than they should be.
For an interim step, yes, I would recommend removing the Actions
wherever they are employed in your document, publishing once, then re-
apply them (build the effects back up from scratch). It’s a one-time
pain, but a necessary one until (maybe) we see a new version of
Freeway that addresses this shortcoming in the Actions API.
Walter
On Apr 26, 2010, at 6:12 AM, Ian Halstead wrote:
Hi Waltd I have tried updating the carousel/protaculous actions
for an existing site, but the Carousel action has stopped working.
I had to delete the related action on each object it applied to, and
replace it with the updated action in order not to get a missing
resources error on build/upload.
Just wondering if we have a conflict somewhere, or if I need to tear
down the Carousels and remake them for the updated actions.
No, I was actually referring to using normal HTML text. It’s nice that
you got the tabs to work using graphics, but that’s swimming upstream
with regard to the normal workings of CSS Menus.
What I meant by creating the CSS menu as it should be from scratch was
to use the CSS Menus Action the way you would use it when linking to a
page in your site or on another site. You enter the text you want to
have appear in the menu – as HTML text – and then you select that
text and apply a link to it within Freeway. In this case, rather than
selecting a page in your site while making that link, you would enter
an “external” link in the Hyperlink dialog, but target an ID on the
same page (anchor link style).
In other news, I should be able to release a patched version of
Carousel Text Tabs today that works around this problem, but this will
then need to be updated again whenever a new version of CSS Tabs is
released (since that’s where the bug is).
Walter
On Apr 27, 2010, at 8:51 AM, scoutdesign wrote:
Waltd,
I think I have it working! When creating the tabs inside the HTML
CSS menus box, they need to be graphic inserts, not HTML inserts.
Am I just stating the obvious, is that what you originally meant.
But I do have css menus and carousel working together for drop down
tabs. Yeh!
Thanks Walter. I would also prefer to use it ‘as it should be used’, but this has got me out a spot. Link to page where it works is www.steeringdevelopments.co.uk/news.html
Hi Walter – I’ve stripped the test site down to a single page, removed all the actions, republished and re-applied them to no avail, even going so far as to delete, republish, reapply and republish them one at a time. Still no joy.
I think the next step is to completely redo the carousel layouts in Freeway and see what happens.
I have noticed this problem before, and I believe it has to do with
the way that Freeway caches Actions and file references in those
Actions within the current document. This can make updates such as the
one we just went through more painful than they should be.
For an interim step, yes, I would recommend removing the Actions
wherever they are employed in your document, publishing once, then re-
apply them (build the effects back up from scratch). It’s a one-time
pain, but a necessary one until (maybe) we see a new version of
Freeway that addresses this shortcoming in the Actions API.