As long as I can click a link here and see it in the browser, that’s where the testing can begin. Remember, not everything that you do with CSS in Freeway will be visible in the Freeway design interface. It’s hit-or-miss sometimes, particularly if you use multiple styles to adjust one element, or use the Extended interface to add special attributes. Previewing in a browser on your Mac should work exactly the same way as viewing it on line from the server, but what you see in Freeway may only be a partial picture.
Walter
On Mar 24, 2014, at 12:45 PM, Jill Hudson wrote:
Hi - no its not live and just putting it together, I could maybe show you whats happening so far if I ftp to my server?
No, please publish the site as HTML, and post it at a public address. If you want to use a link shortener to mask the URL (so you can take it down without worry before the search robots index it) then please do so. But I’m not going to open a Freeway file to figure out why it doesn’t look great in a browser. I need to see the published HTML for that.
Walter
On Mar 24, 2014, at 1:26 PM, Jill Hudson wrote:
Hi Walt,
please try this link - ive copied all the freeway files of the site in there. Maybe you can see something Ive done wrong, many thanks
The reason for all this is simple… Freeway Pro generates HTML for the
browser. That HTML tells us a lot about what you’ve done, what FWP has
done, and what browsers will expect from all that. Like an x-ray image.
Looking at your FWP file is a bit like poking at the lumpy surface and
trying to guess what’s underneath. It’s another layer of complexity to wade
through and obscure things.
If you have a publicly accessible server, say for your own website, it’s
worth taking time to create a subdomain where you can lock out the googles
and bots, and create invite-only spaces for sites you are working on. On my
site, it is http://myproof.thebigerns.com