Pages not working in latest Beta

Freeway
1

I can’t work this out -

My site which worked fine in the previous beta now seems broken.
http://www.petemackenzie.co.uk

The Home page has the Carousel action running the sample images and
Rollovers with Target Show/Hide Layer to work the menu items. These
have been constructed on a master page. All this works fine on the
Home page. Go to any of the linked pages and the menu rollovers don’t
work any more. Also there should be fading text with links appearing
when rolling over the gallery images. These don’t appear either (they
used to). I tried remaking the rollovers on the Design page but this
doesn’t work.

In the earlier version when the site was published two JS libraries
got loaded and called - prototype.js and prototypea.js. Apparently
this is a bad thing and but Walter and Joe have been working at the
problem. I notice that now prototype1602packer.js gets uploaded.
Would that be implicated in the non-functioning rollovers? But why
would the Home page work Ok?

I also have been afflicted with the border bug which now shows dotted
borders around all sides of items not just the bottom edge as they
should be. Again this worked in the previous Beta

Any thoughts/cures welcomed.

Cheers
Pete

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

2

Just to follow this up. I’ve just noticed that in Preview mode on the
affected pages if I go to the Home, Links and Contact rollovers they
work (or at least the colour changes as designed when moused over).
If I then roll onto Galleries the dropdown which should appear
doesn’t, but also the other rollovers then stop working if i go back
over them (no colour change happens)

Pete

On 15 Mar 2008, at 00:10, Pete MacKenzie wrote:

I can’t work this out -

My site which worked fine in the previous beta now seems broken.
http://www.petemackenzie.co.uk

The Home page has the Carousel action running the sample images and
Rollovers with Target Show/Hide Layer to work the menu items. These
have been constructed on a master page. All this works fine on the
Home page. Go to any of the linked pages and the menu rollovers don’t
work any more. Also there should be fading text with links appearing
when rolling over the gallery images. These don’t appear either (they
used to). I tried remaking the rollovers on the Design page but this
doesn’t work.

In the earlier version when the site was published two JS libraries
got loaded and called - prototype.js and prototypea.js. Apparently
this is a bad thing and but Walter and Joe have been working at the
problem. I notice that now prototype1602packer.js gets uploaded.
Would that be implicated in the non-functioning rollovers? But why
would the Home page work Ok?

I also have been afflicted with the border bug which now shows dotted
borders around all sides of items not just the bottom edge as they
should be. Again this worked in the previous Beta

Any thoughts/cures welcomed.

Cheers
Pete

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

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

3

You need to upgrade to the latest Carousel action. You are using an
older version of Carousel with the new loveliness of the Softpress
Scriptaculous actions.

http://freewaypro.com/actions/downloads/protaculous.fwactionb.zip

Walter

On Mar 14, 2008, at 8:10 PM, Pete MacKenzie wrote:

I can’t work this out -

My site which worked fine in the previous beta now seems broken.
http://www.petemackenzie.co.uk

The Home page has the Carousel action running the sample images and
Rollovers with Target Show/Hide Layer to work the menu items. These
have been constructed on a master page. All this works fine on the
Home page. Go to any of the linked pages and the menu rollovers don’t
work any more. Also there should be fading text with links appearing
when rolling over the gallery images. These don’t appear either (they
used to). I tried remaking the rollovers on the Design page but this
doesn’t work.

In the earlier version when the site was published two JS libraries
got loaded and called - prototype.js and prototypea.js. Apparently
this is a bad thing and but Walter and Joe have been working at the
problem. I notice that now prototype1602packer.js gets uploaded.
Would that be implicated in the non-functioning rollovers? But why
would the Home page work Ok?

I also have been afflicted with the border bug which now shows dotted
borders around all sides of items not just the bottom edge as they
should be. Again this worked in the previous Beta

Any thoughts/cures welcomed.

Cheers
Pete

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

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

4

Ah, righto, thanks Walter, I’ll give it a bash…

Hmmm, given it a bash and the problem is unchanged. I rebuilt the
carousel completely even though that was working OK but still all the
fades and show/hides on the following pages are broken.

Cheers
pete

On 15 Mar 2008, at 02:56, Walter Lee Davis wrote:

You need to upgrade to the latest Carousel action. You are using an
older version of Carousel with the new loveliness of the Softpress
Scriptaculous actions.

http://freewaypro.com/actions/downloads/protaculous.fwactionb.zip

Walter

On Mar 14, 2008, at 8:10 PM, Pete MacKenzie wrote:

I can’t work this out -

My site which worked fine in the previous beta now seems broken.
http://www.petemackenzie.co.uk

The Home page has the Carousel action running the sample images and
Rollovers with Target Show/Hide Layer to work the menu items. These
have been constructed on a master page. All this works fine on the
Home page. Go to any of the linked pages and the menu rollovers don’t
work any more. Also there should be fading text with links appearing
when rolling over the gallery images. These don’t appear either (they
used to). I tried remaking the rollovers on the Design page but this
doesn’t work.

In the earlier version when the site was published two JS libraries
got loaded and called - prototype.js and prototypea.js. Apparently
this is a bad thing and but Walter and Joe have been working at the
problem. I notice that now prototype1602packer.js gets uploaded.
Would that be implicated in the non-functioning rollovers? But why
would the Home page work Ok?

I also have been afflicted with the border bug which now shows dotted
borders around all sides of items not just the bottom edge as they
should be. Again this worked in the previous Beta

Any thoughts/cures welcomed.

Cheers
Pete

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

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

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

5

Still struggling with this and it seems to me that the problem must
lie with the Rollover and target Show/Hide Layer actions. I made no
changes to the pages apart from moving from one Beta to another. An
additional symptom I have noticed is that on the malfunctioning pages
the Galleries menu rollover not only doesn’t cause the hidden layer
to appear but actually links back to the Home page. But this isn’t a
link as such, just a trigger for the layer. Any galleries links are
in the hidden layer which should appear below the menu bar so why
would it return a link to home? Deleting and reassigning the Actions
doesn’t improve matters.

The Rollovers and their targets are set to be self cancelling so
mousing over causes one layer to appear and the last visible to hide
(in an elegant fading way…) using a method demonstrated by Joe
Billings. It used to work so nicely. Unfortunately i deleted the 2nd
Beta dmg so cannot try going back to see if there are obvious
differences in the source code for the affected pages.

Puzzled
Pete

On 15 Mar 2008, at 09:36, Pete MacKenzie wrote:

Ah, righto, thanks Walter, I’ll give it a bash…

Hmmm, given it a bash and the problem is unchanged. I rebuilt the
carousel completely even though that was working OK but still all the
fades and show/hides on the following pages are broken.

Cheers
pete

On 15 Mar 2008, at 02:56, Walter Lee Davis wrote:

You need to upgrade to the latest Carousel action. You are using an
older version of Carousel with the new loveliness of the Softpress
Scriptaculous actions.

http://freewaypro.com/actions/downloads/protaculous.fwactionb.zip

Walter

On Mar 14, 2008, at 8:10 PM, Pete MacKenzie wrote:

I can’t work this out -

My site which worked fine in the previous beta now seems broken.
http://www.petemackenzie.co.uk

The Home page has the Carousel action running the sample images and
Rollovers with Target Show/Hide Layer to work the menu items. These
have been constructed on a master page. All this works fine on the
Home page. Go to any of the linked pages and the menu rollovers
don’t
work any more. Also there should be fading text with links appearing
when rolling over the gallery images. These don’t appear either
(they
used to). I tried remaking the rollovers on the Design page but this
doesn’t work.

In the earlier version when the site was published two JS libraries
got loaded and called - prototype.js and prototypea.js. Apparently
this is a bad thing and but Walter and Joe have been working at the
problem. I notice that now prototype1602packer.js gets uploaded.
Would that be implicated in the non-functioning rollovers? But why
would the Home page work Ok?

I also have been afflicted with the border bug which now shows
dotted
borders around all sides of items not just the bottom edge as they
should be. Again this worked in the previous Beta

Any thoughts/cures welcomed.

Cheers
Pete

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

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

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

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

6

Did you upload the new site to your server, or just test locally? If
so, I can’t see any changes in the files that are being published.
Perhaps the older version of Carousel got cached in your Freeway
document, and is being re-used in place of the new one that you
installed. Could you try a fresh new document, nothing recycled, and
see if you can use the two Actions together on a new page?

Walter

On Mar 15, 2008, at 5:36 AM, Pete MacKenzie wrote:

Ah, righto, thanks Walter, I’ll give it a bash…

Hmmm, given it a bash and the problem is unchanged. I rebuilt the
carousel completely even though that was working OK but still all the
fades and show/hides on the following pages are broken.

Cheers
pete

On 15 Mar 2008, at 02:56, Walter Lee Davis wrote:

You need to upgrade to the latest Carousel action. You are using an
older version of Carousel with the new loveliness of the Softpress
Scriptaculous actions.

http://freewaypro.com/actions/downloads/protaculous.fwactionb.zip

Walter

On Mar 14, 2008, at 8:10 PM, Pete MacKenzie wrote:

I can’t work this out -

My site which worked fine in the previous beta now seems broken.
http://www.petemackenzie.co.uk

The Home page has the Carousel action running the sample images and
Rollovers with Target Show/Hide Layer to work the menu items. These
have been constructed on a master page. All this works fine on the
Home page. Go to any of the linked pages and the menu rollovers
don’t
work any more. Also there should be fading text with links appearing
when rolling over the gallery images. These don’t appear either
(they
used to). I tried remaking the rollovers on the Design page but this
doesn’t work.

In the earlier version when the site was published two JS libraries
got loaded and called - prototype.js and prototypea.js. Apparently
this is a bad thing and but Walter and Joe have been working at the
problem. I notice that now prototype1602packer.js gets uploaded.
Would that be implicated in the non-functioning rollovers? But why
would the Home page work Ok?

I also have been afflicted with the border bug which now shows
dotted
borders around all sides of items not just the bottom edge as they
should be. Again this worked in the previous Beta

Any thoughts/cures welcomed.

Cheers
Pete

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

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

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

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

7

I have re-uploaded the site with the changes (but also tried out
different thoughts in Page/Preview mode to no avail) so what you see
is my latest attempt. I took the carousel apart, removed the Actions
from each element (the symbols disappeared in the site pane) and then
reassembled from scratch. I’ve Force Republished most of the pages
along the way. Is there a way to empty the Freeway cache?

Certainly, when i look at the source code, it is clear that the
prototype and scriptaculous libraries are being loaded in a different
way to when I built the version that worked. As you will recall both
prototype.js and prototypea.js got loaded and called. That has
changed so only prototypea.js is there along with scriptaculous and
the packer files. So something has changed…

What I find most puzzling is that the Home page, which contains the
Carousel and the Rollover-Target Show/Hide Layers Actions on the same
page, works as designed. It is all the other pages which have no
Carousel on them that have broken. You will know better what that
implies i’m sure, but I find i can’t see the cause and effect logic
in that scenario. I am reluctant to delete swathes of elements at
this stage (yes, lazy maybe!) as it would seem that the Betas should
be able to cope with the legacy of their predecessor - beta 2 coped
ok with stuff constructed in beta 1 - or maybe I’m too optimistic
with Betas.

I’ll try a Save As and work on some cleaner pages as you suggest.

Thanks for your ongoing thoughts.

cheers
pete

On 15 Mar 2008, at 16:07, Walter Lee Davis wrote:

Did you upload the new site to your server, or just test locally? If
so, I can’t see any changes in the files that are being published.
Perhaps the older version of Carousel got cached in your Freeway
document, and is being re-used in place of the new one that you
installed. Could you try a fresh new document, nothing recycled, and
see if you can use the two Actions together on a new page?

Walter

On Mar 15, 2008, at 5:36 AM, Pete MacKenzie wrote:

Ah, righto, thanks Walter, I’ll give it a bash…

Hmmm, given it a bash and the problem is unchanged. I rebuilt the
carousel completely even though that was working OK but still all the
fades and show/hides on the following pages are broken.

Cheers
pete

On 15 Mar 2008, at 02:56, Walter Lee Davis wrote:

You need to upgrade to the latest Carousel action. You are using an
older version of Carousel with the new loveliness of the Softpress
Scriptaculous actions.

http://freewaypro.com/actions/downloads/protaculous.fwactionb.zip

Walter

On Mar 14, 2008, at 8:10 PM, Pete MacKenzie wrote:

I can’t work this out -

My site which worked fine in the previous beta now seems broken.
http://www.petemackenzie.co.uk

The Home page has the Carousel action running the sample images and
Rollovers with Target Show/Hide Layer to work the menu items. These
have been constructed on a master page. All this works fine on the
Home page. Go to any of the linked pages and the menu rollovers
don’t
work any more. Also there should be fading text with links
appearing
when rolling over the gallery images. These don’t appear either
(they
used to). I tried remaking the rollovers on the Design page but
this
doesn’t work.

In the earlier version when the site was published two JS libraries
got loaded and called - prototype.js and prototypea.js. Apparently
this is a bad thing and but Walter and Joe have been working at the
problem. I notice that now prototype1602packer.js gets uploaded.
Would that be implicated in the non-functioning rollovers? But why
would the Home page work Ok?

I also have been afflicted with the border bug which now shows
dotted
borders around all sides of items not just the bottom edge as they
should be. Again this worked in the previous Beta

Any thoughts/cures welcomed.

Cheers
Pete

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

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

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

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

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

8

Try starting a new document altogether. You should only see one copy
each of prototype-packer and scriptaculous-packer in the head of the
page, no matter how many of the Scriptaculous or Protaculous actions
you apply to the page or its elements.

Maybe there is something else on the page that is invoking the older
code. I don’t see that happening here in my testing, but then I have
not been working the same file over multiple beta versions, I
generally start with a fresh document each time.

It’s important to note that Freeway will cache all of the actions you
use in an entire document within the Freeway document itself. This is
a hedge against you sending the file to another person who does not
have the same Actions installed. What is supposed to happen in cases
like these is that the newest version of the Action is supposed to
“win”. But perhaps that is getting confused somehow, and a cached
version of the Action is being used in preference to the version you
have installed.

Another good testing point is to look inside your Actions folder:

[your user folder]/Library/Application Support/Freeway 5/Actions/General

See how many copies of Protaculous.fwactionb you see there.

Walter

On Mar 15, 2008, at 1:51 PM, Pete MacKenzie wrote:

way to when I built the version that worked. As you will recall both
prototype.js and prototypea.js got loaded and called. That has
changed so only prototypea.js is there along with scriptaculous and
the packer files. So something has changed…

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

9

I’ve started reworking the site with a Saved As version and new Site
folder and am making progress now.
I stripped out all the actions and saved the file, republished and
then closed the document. Then I re-opened it and have rebuilt the
Action items. The Actions seem to be working properly again.

Try starting a new document altogether. You should only see one copy
each of prototype-packer and scriptaculous-packer in the head of the
page, no matter how many of the Scriptaculous or Protaculous actions
you apply to the page or its elements.

Maybe there is something else on the page that is invoking the older
code. I don’t see that happening here in my testing, but then I have
not been working the same file over multiple beta versions, I
generally start with a fresh document each time.

When you say a fresh document, what exactly do you mean? Not
rebuilding a site from scratch…? Does a Save As generally suffice?

It’s important to note that Freeway will cache all of the actions you
use in an entire document within the Freeway document itself. This is
a hedge against you sending the file to another person who does not
have the same Actions installed. What is supposed to happen in cases
like these is that the newest version of the Action is supposed to
“win”. But perhaps that is getting confused somehow, and a cached
version of the Action is being used in preference to the version you
have installed.

That’s useful to know and must be what has happened. I’ve not had
that happen through successive upgrades of FW4 but as you say these
have been multiple Beta versions so I suppose I should expect glitches.

Another good testing point is to look inside your Actions folder:

[your user folder]/Library/Application Support/Freeway 5/Actions/
General

See how many copies of Protaculous.fwactionb you see there.

Just the one as I routinely overwrite the upgrades.

Anyway, thanks for your usual patient input.

By the way, I’ve never come across your Donate button. Is there a
link so i can find it?

All the best
Pete

On Mar 15, 2008, at 1:51 PM, Pete MacKenzie wrote:

way to when I built the version that worked. As you will recall both
prototype.js and prototypea.js got loaded and called. That has
changed so only prototypea.js is there along with scriptaculous and
the packer files. So something has changed…

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

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

10

On Mar 15, 2008, at 3:37 PM, Pete MacKenzie wrote:

I’ve started reworking the site with a Saved As version and new Site
folder and am making progress now.
I stripped out all the actions and saved the file, republished and
then closed the document. Then I re-opened it and have rebuilt the
Action items. The Actions seem to be working properly again.

Try starting a new document altogether. You should only see one copy
each of prototype-packer and scriptaculous-packer in the head of the
page, no matter how many of the Scriptaculous or Protaculous actions
you apply to the page or its elements.

Maybe there is something else on the page that is invoking the older
code. I don’t see that happening here in my testing, but then I have
not been working the same file over multiple beta versions, I
generally start with a fresh document each time.

When you say a fresh document, what exactly do you mean? Not
rebuilding a site from scratch…? Does a Save As generally suffice?

I was proposing that you make a single-page test document, entirely
from scratch, as a debugging step. I wanted to rule out the cached
actions.

What I think worked in your particular case was to remove the
actions, then publish. That must have cleared out the cached actions.
I think that the subsequent save and re-open were nice, but not what
did the work.

It’s important to note that Freeway will cache all of the actions you
use in an entire document within the Freeway document itself. This is
a hedge against you sending the file to another person who does not
have the same Actions installed. What is supposed to happen in cases
like these is that the newest version of the Action is supposed to
“win”. But perhaps that is getting confused somehow, and a cached
version of the Action is being used in preference to the version you
have installed.

That’s useful to know and must be what has happened. I’ve not had
that happen through successive upgrades of FW4 but as you say these
have been multiple Beta versions so I suppose I should expect
glitches.

Another good testing point is to look inside your Actions folder:

[your user folder]/Library/Application Support/Freeway 5/Actions/
General

See how many copies of Protaculous.fwactionb you see there.

Just the one as I routinely overwrite the upgrades.

Anyway, thanks for your usual patient input.

By the way, I’ve never come across your Donate button. Is there a
link so i can find it?

It’s at the top of the downloads page on my repository:

http://freewaypro.com/actions/downloads/

You’re welcome!

Walter

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

11

An update to all this

I am currently still having a problem with one page http://
www.petemackenzie.co.uk/linkspage.html

All pages were working again as designed. I decided on a whim to use
the Softpress badge and linked to them on this links page. That is
the only change to it since it resumed working after the last surgery
and now the menu bar fails to work again in Firefox. It works OK in
the FW Preview pane and online using Safari (and, strangely, if I
Preview In Browser using Firefox) but not if I access the page online
with Firefox. I can see the red rollover state loading as the page
loads so it is there.

Could anybody else try the link please in Firefox and see if the
rollovers in the menubar works for them. Just to note - I have purged
my Firefox cache (a few times) and tried binning the Firefox plist
but this has no effect. I have rebuilt the rollovers and republished
(but of course that all seems to be OK as it functions in Safari).
This is Firefox 2.0.0.12 by the way.

Many thanks
Pete

On 15 Mar 2008, at 20:22, Walter Lee Davis wrote:

On Mar 15, 2008, at 3:37 PM, Pete MacKenzie wrote:

I’ve started reworking the site with a Saved As version and new Site
folder and am making progress now.
I stripped out all the actions and saved the file, republished and
then closed the document. Then I re-opened it and have rebuilt the
Action items. The Actions seem to be working properly again.

Try starting a new document altogether. You should only see one copy
each of prototype-packer and scriptaculous-packer in the head of the
page, no matter how many of the Scriptaculous or Protaculous actions
you apply to the page or its elements.

Maybe there is something else on the page that is invoking the older
code. I don’t see that happening here in my testing, but then I have
not been working the same file over multiple beta versions, I
generally start with a fresh document each time.

When you say a fresh document, what exactly do you mean? Not
rebuilding a site from scratch…? Does a Save As generally suffice?

I was proposing that you make a single-page test document, entirely
from scratch, as a debugging step. I wanted to rule out the cached
actions.

What I think worked in your particular case was to remove the
actions, then publish. That must have cleared out the cached actions.
I think that the subsequent save and re-open were nice, but not what
did the work.

It’s important to note that Freeway will cache all of the actions
you
use in an entire document within the Freeway document itself.
This is
a hedge against you sending the file to another person who does not
have the same Actions installed. What is supposed to happen in cases
like these is that the newest version of the Action is supposed to
“win”. But perhaps that is getting confused somehow, and a cached
version of the Action is being used in preference to the version you
have installed.

That’s useful to know and must be what has happened. I’ve not had
that happen through successive upgrades of FW4 but as you say these
have been multiple Beta versions so I suppose I should expect
glitches.

Another good testing point is to look inside your Actions folder:

[your user folder]/Library/Application Support/Freeway 5/Actions/
General

See how many copies of Protaculous.fwactionb you see there.

Just the one as I routinely overwrite the upgrades.

Anyway, thanks for your usual patient input.

By the way, I’ve never come across your Donate button. Is there a
link so i can find it?

It’s at the top of the downloads page on my repository:

http://freewaypro.com/actions/downloads/

You’re welcome!

Walter

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

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

12

You have the option for frames on somewhere, and no frames anywhere
on the page. Firebug shows an error when you try to access a frame
during the rollover.

Walter

On Mar 16, 2008, at 3:12 PM, Pete MacKenzie wrote:

An update to all this

I am currently still having a problem with one page http://
www.petemackenzie.co.uk/linkspage.html

All pages were working again as designed. I decided on a whim to use
the Softpress badge and linked to them on this links page. That is
the only change to it since it resumed working after the last surgery
and now the menu bar fails to work again in Firefox. It works OK in
the FW Preview pane and online using Safari (and, strangely, if I
Preview In Browser using Firefox) but not if I access the page online
with Firefox. I can see the red rollover state loading as the page
loads so it is there.

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

13

??? Thanks Walter - I have never even tried to use a frame anywhere
near this site and most of it works off the same master page. I’ll
see what I can find… It’s all gone a bit Alice In Wonderland at
the moment…

cheers
Pete

On 16 Mar 2008, at 20:28, Walter Lee Davis wrote:

You have the option for frames on somewhere, and no frames anywhere
on the page. Firebug shows an error when you try to access a frame
during the rollover.

Walter

On Mar 16, 2008, at 3:12 PM, Pete MacKenzie wrote:

An update to all this

I am currently still having a problem with one page http://
www.petemackenzie.co.uk/linkspage.html

All pages were working again as designed. I decided on a whim to use
the Softpress badge and linked to them on this links page. That is
the only change to it since it resumed working after the last surgery
and now the menu bar fails to work again in Firefox. It works OK in
the FW Preview pane and online using Safari (and, strangely, if I
Preview In Browser using Firefox) but not if I access the page online
with Firefox. I can see the red rollover state loading as the page
loads so it is there.

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

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

14

No the rollovers on the Links page aren’t working for me in Firefox 2.0.0.12 or Opera

Have you tried reapplying the master to this page? Select and copy everything you want to keep, delete the rest and then reapply master and paste back the other stuff.

You could try previewing/uploading to test before pasting back.

An aside to this is the forward and back buttons on your gallery page are the wrong way round.

David

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

15

Thanks David

I have tried reapplying the Master but will try deleting various
elements to see if anything has got entangled that shouldn’t be there
(although as Walter noticed, there doesn’t appear to be anything
there anyway).

Re the forward/back buttons do you mean the ones in the Carousel on
the home page? If so, I know what you are getting at but I did try
both ways of setting these up. As it stands, at least when I view it,
when you click the arrow that points to the right the images move to
the right even though it is technically the previous button. Doing it
the other way means you click the right arrow and stuff moves to the
left which I found to be awkward visually. Maybe it is like those
image puzzles where a black area in the shape of an urn on a white
background can also be seen as two white faces with a black area in
between - a question of perception. Then again if you are clicking
the right arrow and the images are moving to the left something
strange is going on…

Pete

On 16 Mar 2008, at 23:49, DeltaDave wrote:

No the rollovers on the Links page aren’t working for me in
Firefox 2.0.0.12 or Opera

Have you tried reapplying the master to this page? Select and copy
everything you want to keep, delete the rest and then reapply
master and paste back the other stuff.

You could try previewing/uploading to test before pasting back.

An aside to this is the forward and back buttons on your gallery
page are the wrong way round.

David

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

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

16

OK I have now gone through the various elements and it seems the
Amazon search box is the culprit. It is pasted in as a Markup item
and here is the code, which I now see says iframe.

As it was pasted in from my old site and worked fine until this last
Beta I hadn’t looked at it again. Why would it interfere with the
rollovers, and more to the point, why does it work in Freeway
Preview, Firefox offline and Safari online but not Firefox or Opera
online? I’d quite like to keep it but if it is going to be messing up
the page there is no point. Is this a Beta bug…?

Cheers
Pete

On 17 Mar 2008, at 08:45, Pete MacKenzie wrote:

Thanks David

I have tried reapplying the Master but will try deleting various
elements to see if anything has got entangled that shouldn’t be there
(although as Walter noticed, there doesn’t appear to be anything
there anyway).

Re the forward/back buttons do you mean the ones in the Carousel on
the home page? If so, I know what you are getting at but I did try
both ways of setting these up. As it stands, at least when I view it,
when you click the arrow that points to the right the images move to
the right even though it is technically the previous button. Doing it
the other way means you click the right arrow and stuff moves to the
left which I found to be awkward visually. Maybe it is like those
image puzzles where a black area in the shape of an urn on a white
background can also be seen as two white faces with a black area in
between - a question of perception. Then again if you are clicking
the right arrow and the images are moving to the left something
strange is going on…

Pete

On 16 Mar 2008, at 23:49, DeltaDave wrote:

No the rollovers on the Links page aren’t working for me in
Firefox 2.0.0.12 or Opera

Have you tried reapplying the master to this page? Select and copy
everything you want to keep, delete the rest and then reapply
master and paste back the other stuff.

You could try previewing/uploading to test before pasting back.

An aside to this is the forward and back buttons on your gallery
page are the wrong way round.

David

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

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

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

17

The exact error you are seeing is a permissions error. JavaScript is not allowed to ask questions of another frame if that frame is hosted from a different domain than the rest of the page/frameset. This is a security check, and a good thing. I’m not sure why it is only cropping up now, but perhaps something changed in the Rollover action that made it necessary to check frames.

Walter

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

18

I see what you are saying but how does one then deal with an inserted
bit of code like this Amazon (or other sort of affiliated scheme)
item? Is this a Softpress problem?

Pete

On 17 Mar 2008, at 12:13, waltd wrote:

The exact error you are seeing is a permissions error. JavaScript
is not allowed to ask questions of another frame if that frame is
hosted from a different domain than the rest of the page/frameset.
This is a security check, and a good thing. I’m not sure why it is
only cropping up now, but perhaps something changed in the Rollover
action that made it necessary to check frames.

Walter

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

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

19

I think so, yes. The issue you are having is being triggered by a
code call that is happening within the Rollover-inserted javascript.
I know that there are interface choices you can set in that Action
governing frame behavior. I would start by experimenting with those
settings to see if you can get the problem to stop.

Walter

On Mar 17, 2008, at 8:26 AM, Pete MacKenzie wrote:

I see what you are saying but how does one then deal with an inserted
bit of code like this Amazon (or other sort of affiliated scheme)
item? Is this a Softpress problem?

Pete

On 17 Mar 2008, at 12:13, waltd wrote:

The exact error you are seeing is a permissions error. JavaScript
is not allowed to ask questions of another frame if that frame is
hosted from a different domain than the rest of the page/frameset.
This is a security check, and a good thing. I’m not sure why it is
only cropping up now, but perhaps something changed in the Rollover
action that made it necessary to check frames.

Walter

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

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

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

20

I have now tried changing every setting in the Rollover and Target
Show/Hide Layer actions and nothing cures the problem (apart from
removing the Amazon markup). I see nothing that specifically refers
to frame behaviour though.

I thought that maybe, because the target layer overlaps the html item
that contains the markup, if I moved the items so that they weren’t
overlapping that might help but it didn’t.

And just to reiterate, the page worked fine in the previous Beta (as
far as I’m aware).

Pete

On 17 Mar 2008, at 12:41, Walter Lee Davis wrote:

I think so, yes. The issue you are having is being triggered by a
code call that is happening within the Rollover-inserted javascript.
I know that there are interface choices you can set in that Action
governing frame behavior. I would start by experimenting with those
settings to see if you can get the problem to stop.

Walter

On Mar 17, 2008, at 8:26 AM, Pete MacKenzie wrote:

I see what you are saying but how does one then deal with an inserted
bit of code like this Amazon (or other sort of affiliated scheme)
item? Is this a Softpress problem?

Pete

On 17 Mar 2008, at 12:13, waltd wrote:

The exact error you are seeing is a permissions error. JavaScript
is not allowed to ask questions of another frame if that frame is
hosted from a different domain than the rest of the page/frameset.
This is a security check, and a good thing. I’m not sure why it is
only cropping up now, but perhaps something changed in the Rollover
action that made it necessary to check frames.

Walter

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

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

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

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