Okay. . . things are working out and looking much better now thanks to everybody’s insightful suggestions - thank you. But I’ve encountered another snag. Why are my links at the very bottom of each page not working (eNews | FAQ | Contact):
They work on the home page, but do not work on any of the other pages (again, the ones at the very bottom of each page (eNews | FAQ | Contact). I’ve tried them in Safari 3.1.2 and Firefox 2, and the cursor does not respond as though there was a link present. I’ve tried “clicking” all over them and none of them take me anywhere.
Does it work for anybody else? That’s really weird.
Is there another layer overlapping them, by any chance?
Walter
On Oct 9, 2008, at 3:55 PM, Buck wrote:
They work on the home page, but do not work on any of the other
pages (again, the ones at the very bottom of each page (eNews | FAQ
| Contact). I’ve tried them in Safari 3.1.2 and Firefox 2, and the
cursor does not respond as though there was a link present. I’ve
tried “clicking” all over them and none of them take me anywhere.
Does it work for anybody else? That’s really weird.
Not that I am aware. . . how do I check? The footer is separated by two spacer boxes. The html box which contains the links has been inserted inside the footer box.
I see that, something’s goofy. It also appears that a HTML item named “BottomSpacer2” is covering up the links. An empty DIV item. Switch in Freeway to “Item View” using the Cog and down arrow in the lower left of the main window and find it and delete it.
Thanks Dan. I just finished discovering that before checking back in here to find your post. That’s exactly what the problem was. I had added that final empty DIV as a spacer for the bottom of the page, so it didn’t cut off immediately below the links. Evidently, I didn’t need it. Getting rid of that DIV took care of the problem
I have to visit the local library to use their PCs to see the difference. As my clients have PCs I design for PCs and not Macs.
I also find that FW does not update code consistently on all pages - so I have to use Source Code Snooper to hand amend the page code on some of the pages.
Sometime around 11/10/08 (at 02:51 -0400) NicolasAllan said:
I also find that FW does not update code consistently on all pages -
so I have to use Source Code Snooper to hand amend the page code on
some of the pages.
This reminds me of the famous line from Homer Simpson:
“To alcohol! The cause of… and solution to… all of life’s problems”
Source Code Snooper is a great tool when really necessary[*], but it
can also wreak havok if you’re not very careful.
Regarding that ‘when necessary’ qualification: I haven’t found a
need for it in years, and in fact even the times when I have used it,
it wasn’t strictly necessary then either.
What I’m trying to say to everyone here is this: DON’T use Source
Code Snooper as a way to ‘solve a failing in Freeway’. The odds are
the underlying cause is not what you think.