Carousel Difficulties

Freeway
1

I’m attempting to use Carousel Action on a page that already has some other actions applied (CSS Menus, Template Helper, Form Element CSS) in a box design.

For whatever reason, I can get my trial Carousel to work on a blank page, but not on the page with stuff already going on.

Are there any know Carousel conflicts? Or am I just being thick (again)?

If there are known conflicts, any suggestion on alternative slide shows (any with ‘random’ would be great).

Thanks,
Robert

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

2

Forgot to mention, the page also has some ajax (Google apis) and other minor HTML scripting before and after . I think it may be interfering with Carousel.

On 17 Jun 2011, 9:48 pm, Robert wrote:

I’m attempting to use Carousel Action on a page that already has some other actions applied (CSS Menus, Template Helper, Form Element CSS) in a box design.

For whatever reason, I can get my trial Carousel to work on a blank page, but not on the page with stuff already going on.

Are there any know Carousel conflicts? Or am I just being thick (again)?

If there are known conflicts, any suggestion on alternative slide shows (any with ‘random’ would be great).

Thanks,
Robert

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

3

I think it may be interfering with Carousel.

Post a link Robert.

D

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

4

Dave,

The client doesn’t want me posting the link (not sure why).

I have, however, isolated the problem down to a line of code in the header to

When I remove this, the Carousel works just fine. However, I can’t simply strip out this line of code. So I’m off to explore other Carousel-esk solutions.

Robert

Post a link Robert.

D

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

5

Is this carousel done with my Carousel Action, or with a different
approach? If it is done with my Action, then it relies on
Scriptaculous being in the page. But if the carousel effect is based
on jQuery or MooTools, then you will have all manner of problems,
because those libraries don’t play nicely with Prototype/
Scriptaculous. Furthermore, Freeway uses Prototype internally to power
a number of the built-in effects, so you can’t use much of anything in
Freeway once you go down either of those rabbit holes.

Walter

On Jun 20, 2011, at 9:38 AM, Robert wrote:

Dave,

The client doesn’t want me posting the link (not sure why).

I have, however, isolated the problem down to a line of code in the
header to

When I remove this, the Carousel works just fine. However, I can’t
simply strip out this line of code. So I’m off to explore other
Carousel-esk solutions.

Robert

Post a link Robert.

D

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

6

Walter,

This is done using your Carousel ver. 1.2.16.

Robert

On 20 Jun 2011, 2:15 pm, waltd wrote:

Is this carousel done with my Carousel Action, or with a different
approach?

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

7

Then it cannot run without Scriptaculous in the page. There must be
another effect or library on the page that is conflicting. By itself,
my Carousel Action creates a working effect without any fuss. Try
this, and see if it fixes things:

  1. Remove all vestiges of Carousel from all elements on the page. Any
    navigation buttons or tabs, any carousel elements or satellite panes,
    etc. Publish once.
  2. Add the Actions back into the page, publish again, and preview.

Sometimes Freeway can get confused about the files it is supposed to
upload from within an Action, and following these steps can jog its
memory.

Walter

On Jun 20, 2011, at 10:21 AM, Robert wrote:

Walter,

This is done using your Carousel ver. 1.2.16.

Robert

On 20 Jun 2011, 2:15 pm, waltd wrote:

Is this carousel done with my Carousel Action, or with a different
approach?

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

8

Followed your instructions to a T — still no go.

My trial works on a blank page just fine. It also works on the “live” page as long as I carve out the line of code in the After noted above.

Robert

On 20 Jun 2011, 2:41 pm, waltd wrote:

Then it cannot run without Scriptaculous in the page. There must be
another effect or library on the page that is conflicting. By itself,
my Carousel Action creates a working effect without any fuss. Try
this, and see if it fixes things:

  1. Remove all vestiges of Carousel from all elements on the page. Any
    navigation buttons or tabs, any carousel elements or satellite panes,
    etc. Publish once.
  2. Add the Actions back into the page, publish again, and preview.

Sometimes Freeway can get confused about the files it is supposed to
upload from within an Action, and following these steps can jog its
memory.

Walter

On Jun 20, 2011, at 10:21 AM, Robert wrote:

Walter,

This is done using your Carousel ver. 1.2.16.

Robert

On 20 Jun 2011, 2:15 pm, waltd wrote:

Is this carousel done with my Carousel Action, or with a different
approach?

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

9

Please check carefully in your page to see if there are more than one
instance of that line of code referencing the scriptaculous library. I
could imagine that if you had two Actions applied to the page, or had
used the HTML Markup dialog to add more code, you might possibly end
up with multiple copies of the library in the same page. This could
also cause things to fail.

Walter

On Jun 20, 2011, at 11:17 AM, Robert wrote:

Followed your instructions to a T — still no go.

My trial works on a blank page just fine. It also works on the
“live” page as long as I carve out the line of code in the After

noted above.

Robert

On 20 Jun 2011, 2:41 pm, waltd wrote:

Then it cannot run without Scriptaculous in the page. There must be
another effect or library on the page that is conflicting. By itself,
my Carousel Action creates a working effect without any fuss. Try
this, and see if it fixes things:

  1. Remove all vestiges of Carousel from all elements on the page. Any
    navigation buttons or tabs, any carousel elements or satellite panes,
    etc. Publish once.
  2. Add the Actions back into the page, publish again, and preview.

Sometimes Freeway can get confused about the files it is supposed to
upload from within an Action, and following these steps can jog its
memory.

Walter

On Jun 20, 2011, at 10:21 AM, Robert wrote:

Walter,

This is done using your Carousel ver. 1.2.16.

Robert

On 20 Jun 2011, 2:15 pm, waltd wrote:

Is this carousel done with my Carousel Action, or with a different
approach?

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

10

Went through each item in Page view to make sure that each item belonged and that none had any vestiges of the Carousel action. Nope, all clear.

I went through every line of code in Page > HTML Markup… The only scriptaculous call is in After 

 http://ajax.googleapis.com/ajax/libs/scriptaculous/1.8.2/scriptaculous.js

I then checked every element on the page. Nothing else carried any added HTML code referencing the scriptaculous library.

There is another googleapis call

However, Carousel still doesn’t work when this prototype line of code is removed.

The Carousel test works on a blank page and on my “live” page — but only with the scriptaculous line of code removed.

Robert

On 20 Jun 2011, 3:46 pm, waltd wrote:

Please check carefully in your page to see if there are more than one
instance of that line of code referencing the scriptaculous library. I
could imagine that if you had two Actions applied to the page, or had
used the HTML Markup dialog to add more code, you might possibly end
up with multiple copies of the library in the same page. This could
also cause things to fail.

Walter

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

11

I think there must be something else on the page that is adding those
lines in. Freeway FX Actions use these, as does Paul Dunning’s Spawn
New Window in iPod compatibility mode. The issue isn’t that they are
there or not, but that they must be added to the page in a specific
order, and not more than once each. Part of how they work is that they
rewrite each other in subtle ways, so one loads as a foundation, then
the next one extends that, then the next one extends further. If you
then suddenly reload Prototype or Scriptaculous, the changes made by
Glider.js to both Scriptaculous and Prototype will be overwritten, and
the carousel effect will stop working altogether.

Click on the word Site at the top of the left pane in Freeway. It will
switch over to read Page, and you will see a list of all elements on
the page. Anything with an Action “cog” badge applied to it is
potentially the cause of this problem. Click on each item with a badge
in the left-hand list, and look at the Actions palette to see what
Action is applied. This isn’t coming from nowhere.

Walter

On Jun 20, 2011, at 1:00 PM, Robert wrote:

Went through each item in Page view to make sure that each item
belonged and that none had any vestiges of the Carousel action.
Nope, all clear.

I went through every line of code in Page > HTML Markup… The only
scriptaculous call is in After 

http://ajax.googleapis.com/ajax/libs/scriptaculous/1.8.2/scriptaculous.js

I then checked every element on the page. Nothing else carried any
added HTML code referencing the scriptaculous library.

There is another googleapis call

However, Carousel still doesn’t work when this prototype line of
code is removed.

The Carousel test works on a blank page and on my “live” page — but
only with the scriptaculous line of code removed.

Robert

On 20 Jun 2011, 3:46 pm, waltd wrote:

Please check carefully in your page to see if there are more than one
instance of that line of code referencing the scriptaculous
library. I
could imagine that if you had two Actions applied to the page, or had
used the HTML Markup dialog to add more code, you might possibly end
up with multiple copies of the library in the same page. This could
also cause things to fail.

Walter

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

12

Those lines are definitely part of the existing site design. I’m simply doing so slight modification work.

I wasn’t clear enough in my previous posts. The lines of code I’ve posted come from Page > HTML Markup… in the Insert: After section.

As this markup must remain, is there any way of turning the Glider.js off or have it accept the first call made by the page?

Robert

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

13

Once you have applied Carousel to the page, there is no need to add
either Prototype.js or Scriptaculous.js to the page manually using
HTML Markup. The Action already adds it – and adds it very very early
in the page code, in a place where I don’t believe you can get ahead
of it manually.

What I recommend you do on this page is continue to use Carousel, but
remove all hand-coded (Page / HTML Markup) references to either
Prototype or Scriptaculous. When you do that, any remaining code you
have added to the page that uses either of those libraries will
continue to work correctly.

There should be no need to turn off Glider – in fact if you do so you
will have destroyed the entire Carousel effect.

Walter

On Jun 20, 2011, at 2:32 PM, Robert wrote:

Those lines are definitely part of the existing site design. I’m
simply doing so slight modification work.

I wasn’t clear enough in my previous posts. The lines of code I’ve
posted come from Page > HTML Markup… in the Insert: After
section.

As this markup must remain, is there any way of turning the
Glider.js off or have it accept the first call made by the page?

Robert

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

14

I’ll give your recommendation a shot…

Robert

What I recommend you do on this page is continue to use Carousel, but
remove all hand-coded (Page / HTML Markup) references to either
Prototype or Scriptaculous. When you do that, any remaining code you
have added to the page that uses either of those libraries will
continue to work correctly.

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