Java Script Conflicts IE

Freeway
1

We have noticed an issue In IE 6, have not tested 7 or 8 as of yet, on pages that are using actions that put the “prototype1602packer.js” and the “scriptaculous18packer.js” scrip in the header of the page. It appears to conflict with our “lightview scripts”, “lightview.js” “prototype.js” “scriptaculous.js via Google link”. If we manually change the order of the lightview scripts to first, the Freeway Actions start behaving correctly but the lightview feature does not work, images just load into a new page.

-Is there a way to force where markup gets applied to the page?

-How do we correct the conflict between the two scripts?

-Could it be something other than a conflict that is causing lightview to not work after reordering all scripts?

Thank You, TeamSDA (Dave)

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

2

If you have applied an Action that loads prototype or scriptaculous to
your page, then you should not add any manual code to link to those
scripts again. Any of the Softpress FX actions will load both
Prototype and Scriptaculous (fairly recent, but not the very most
recent versions). There is never a need to load those base scripts
more than once.

These Actions (and my Protaculous Action and its kin) load these
libraries very early in the page code, so if you want to then load
scripts that depend on them, like lightview, all you have to do is use
the Page / HMTL Markup dialog and put your links to those scripts in
the before /head section. You can count on the proto-scripty libraries
already being loaded at that point.

Walter

On Sep 10, 2009, at 4:04 PM, TeamSDA wrote:

We have noticed an issue In IE 6, have not tested 7 or 8 as of yet,
on pages that are using actions that put the
“prototype1602packer.js” and the “scriptaculous18packer.js” scrip in
the header of the page. It appears to conflict with our “lightview
scripts”, “lightview.js” “prototype.js” “scriptaculous.js via Google
link”. If we manually change the order of the lightview scripts to
first, the Freeway Actions start behaving correctly but the
lightview feature does not work, images just load into a new page.

-Is there a way to force where markup gets applied to the page?

-How do we correct the conflict between the two scripts?

-Could it be something other than a conflict that is causing
lightview to not work after reordering all scripts?

Thank You, TeamSDA (Dave)

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

3

Hi Walt,

Not totally clear. Her is some further details as to our issue

Lightview requires the following code in the HEAD and we have been including it in the markup of other pages with 100% success on all IE 6,7,8 as well as Safari and Firefox.

What is happening on our Design Center pages is that we are aparently using an action that is also placing links to the Freeway Java Scrips you mentioned. You will note that it places the Freeway links above those that we have manually entered in the HTML Markup panel.

If we delete the links that have been put in the HEAD by Freeway and re-upload the page everything appears to work correctly, Lightview and all Freeway Actions. Here are our questions and a link to a Design Center page.

-Since things appear to be running correctly without the links applied by freeway does this mean that the manual links to our Java scripts are compatible for the needs of the Freeway Actions? We need the latest prototype.js and scriptaculous.js to run lightview properly.

-If this is the case, is there a more automated way to tell Freeway not to upload is Java Scripts?

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

4

On the pages where you want to use Lightview along with the Softpress
FX Actions, simply do this in the HTML Markup dialog:

It should just work. Prototype and Scriptaculous will be loaded (once)
before Lightview loads, which is the only rule you need to follow.

Walter

On Sep 10, 2009, at 6:13 PM, TeamSDA wrote:

Hi Walt,

Not totally clear. Her is some further details as to our issue

Lightview requires the following code in the HEAD and we have been
including it in the markup of other pages with 100% success on all
IE 6,7,8 as well as Safari and Firefox.

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

5

Hi Walt,

Understand what you are saying, but we have to use the latest versions of Prototype and Scriptaculous for light view to work. Just tested your suggestion and it breaks the lightview affect. Also tried manually ordering the code as lightview requires the CSS and the three Java Script links to be in a specific order and at the top of the HEAD tag. That also breaks.

As stated, when we delete the Freeway links Actions still appear to be working.

Any suggestions based on our previous thread?

Thanks, TeamSDA (Dave)

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

6

It sounds like the newer versions of the libraries you are using don’t
work with the bundled Actions. I’ll have a look and log a bug if
necessary.

Regards,

Joe

On 10 Sep 2009, at 23:50, TeamSDA wrote:

Hi Walt,

Understand what you are saying, but we have to use the latest
versions of Prototype and Scriptaculous for light view to work. Just
tested your suggestion and it breaks the lightview affect. Also
tried manually ordering the code as lightview requires the CSS and
the three Java Script links to be in a specific order and at the top
of the HEAD tag. That also breaks.

As stated, when we delete the Freeway links Actions still appear to
be working.

Any suggestions based on our previous thread?

Thanks, TeamSDA (Dave)

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

7

Hi Joe,

Sorry for any confusion if we are not communicating this issue clearly, let me try again.

We are using several actions on our Design Center pages and one of them seems to requires a “Prototype” and “Scriptaculous” java script. It appears the “Prototype” and “Scriptaculous” scripts that we are manually uploading and linking to for our third party “Lightview” feature also runs the Freeway Action features on those pages. Please note that the “Prototype” and “Scriptaculous” java scripts that we are using seem to be the absolute latest and are totally necessary if Lightview is to work on IE6,7 and 8.

Not Clear On The Following: We don’t consider ourselves web Guru’s by any means, just require a little clarification so we can be confident we are implementing things correctly.

-By linking a page to “Prototype” and “Scriptaculous” Java scripts does it satisfy the needs of any functionality on that page requiring these scripts?

-Any time we are using an action that uploads “Prototype” and “Scriptaculous” are these scripts all the same. Meaning are they like mini applications just different version?

-If the above is correct then it seems the Design Center pages should run fine by outputting the HTML page with the links to the newer “Prototype” and “Scriptaculous” scripts found in a “js” folder manually uploaded and deleting the links to the “Prototype” and “Scriptaculous” scripts that Freeway uploaded in the resources folder.

-Would love to do it all the other way around as Walt suggested just that our “Lightview” features require later versions than Freeway is uploading. If we do have to do things as I have outlined above are the Freeway features I am installing on my pages via Actions going to be OK running on the newer versions “Prototype” and “Scriptaculous” that we have manually uploaded and linked to?

-Also, is there a simpler, more “Freeway approach” to all of this, as we need to be using the newer scripts?

Thank You As Always, Team SDA (Dave)

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

8

On 11 Sep 2009, at 15:37, TeamSDA wrote:

Hi Joe,

Sorry for any confusion if we are not communicating this issue
clearly, let me try again.

We are using several actions on our Design Center pages and one of
them seems to requires a “Prototype” and “Scriptaculous” java
script. It appears the “Prototype” and “Scriptaculous” scripts that
we are manually uploading and linking to for our third party
“Lightview” feature also runs the Freeway Action features on those
pages. Please note that the “Prototype” and “Scriptaculous” java
scripts that we are using seem to be the absolute latest and are
totally necessary if Lightview is to work on IE6,7 and 8.

Not Clear On The Following: We don’t consider ourselves web Guru’s
by any means, just require a little clarification so we can be
confident we are implementing things correctly.

-By linking a page to “Prototype” and “Scriptaculous” Java scripts
does it satisfy the needs of any functionality on that page
requiring these scripts?

It depends, in the case of Lightview, as you rightly point out, it
requires the latest ones. It may be that the latest versions change
the way some things work breaking the functionality that’s in Freeway.
this is what I meant by we will need to run some tests on them before
we can change the versions being used in the Actions.

-Any time we are using an action that uploads “Prototype” and
“Scriptaculous” are these scripts all the same. Meaning are they
like mini applications just different version?

Yes, they are the same but different versions (so potentially doing
things differently).

-If the above is correct then it seems the Design Center pages
should run fine by outputting the HTML page with the links to the
newer “Prototype” and “Scriptaculous” scripts found in a “js” folder
manually uploaded and deleting the links to the “Prototype” and
“Scriptaculous” scripts that Freeway uploaded in the resources folder.

Possibly, but possibly not. A new version will do things differently
and may cause problems.

-Would love to do it all the other way around as Walt suggested just
that our “Lightview” features require later versions than Freeway is
uploading. If we do have to do things as I have outlined above are
the Freeway features I am installing on my pages via Actions going
to be OK running on the newer versions “Prototype” and
“Scriptaculous” that we have manually uploaded and linked to?

We won’t know until we test them unfortunately. I’d love to say yes
but don’t want to commit to it until we try it out.

-Also, is there a simpler, more “Freeway approach” to all of this,
as we need to be using the newer scripts?

Not until we can take a look at the Actions and make them use the up
to date library versions.

Thank You As Always, Team SDA (Dave)

No problem.

Joe

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

9

So very helpful Joe,

I will e-mail you the liview.js and most importunately the prototype.js, as for scriptaculous it is feed from the Google.

-We are going to test our pages later today using the upload and delete older scripts as outlined above. If for some reason the newer scrips are breaking the Freeway actions, is there a way to have lightview look to it’s Java scripts and Freeway to theirs with out conflicting?

-FYI The design center pages that are on line use the approach where the older scripts links have been deleted.

Thank You, Team SDA (Dave)

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