The refreshing either in the preview or safari browser simply does not work esp when using inline boxes.
Browser cache problems can be annoying. That’s down to WebKit, which both Safari and Freeway’s own preview uses. Firefox can hit this too, as can any other browser, although not all are as aggressive about hanging on to content. You sometimes need to ‘option key-refresh’, occasionally quit and relaunch, and sometimes, if all else fails, renaming the reluctant item will do the trick. This is a fact of life with web design - no matter which software you use.
I don’t think inline layouts have anything to do with it. You’re probably just getting a little over-aware of issues due to the higher level of work and frustration inherent with the so-called box-model approach to layout.
I have weird numbers and or question marks, next to my page titles in the left page view bar
The question marks will be replaced with data sizes for each object once the page has been published. When you make changes those revert to question marks, until you preview/publish again. That’s when Freeway generates the items, so that’s when it can tell you how big they are.
When uploading, sometimes fine, sometimes decides it cant find a certain image so cancels the upload - after a few more attempts decides it can find the missing image and uploads fine…
Could you post the exact wording of the message you get when it bails out of uploading?
Inline box model on master pages… DONT EVEN GO THERE!
The only problem with this is that only the outer box will be ‘tracked’ by items on regular pages. Changes you make to inline contents in a master page will not follow through. This is known behaviour. It is a problem but it is not a bug. (It is a natural and logical result of how master pages, object and their contents work… not a mistake in the code. Although yes, it is something that we all would like to see change.)
I don’t think there’s a problem with your copy of Freeway. It is hard to be sure without seeing you actually put pages together, but I suspect treating layered items as if they were non-layered (and/or vice versa) might be part of it.
Please do post the wording of the message you get when your uploading process hiccups.
Is it possible that you have placed some images on your page which
were located in the Resources folder of the same document? This
behavior sounds precisely like that’s what’s you would see if you were
publishing from a document using resources from that same document.
Freeway actively manages the contents of the Resources folder (as well
as the rest of the Site folder), and as such, any files within it
cannot be relied on to be there at all times during the publish cycle.
The first thing that Freeway does when publishing is to delete any
files that are going to be re-generated during the current publish
cycle (that is, if they or their parent page have changed at all).
Then it re-generates those files from scratch and places the new
versions in the Resources folder.
If you need to use an image that is in the Resources folder of the
current site, then copy it into another folder somewhere else on your
disk – like the Media folder that Freeway creates for you whenever
you use any of the templates – and source it from there.
The only exception to the rule that you shouldn’t use a file from a
Resources folder is if that Resources folder belongs to a different
Freeway document. If that’s the case, then you can use it as the
source material for a different document’s layout. But realize that
those files can and will change each time the parent document publishes.
Walter
On Mar 21, 2010, at 7:19 PM, Justin Easthall wrote:
Just tried to upload and this time decided it couldnt find Back.gif
(I repeated and it uploaded fine) but the warning was:
After the yellow warning triangle: Cannot complete upload because
file not found