Admittedly this is FW3.5 Pro, but wonder if anyone can explain this strange behaviour…
I have a site with sub directories with their own Resources folders. On a page in a sub-directory I have a graphic header which is a JPG. The JPG is imported into an html box with pass-through setting, an anchor applied and the name of the graphic given a title in the inspector (in this case ‘masthead-redline’)
When I publish I am getting an old masthead graphic which I no longer use. When I look at the page code, it is fetching this unused graphic from another sub-directory, ie. “…/shop/masthead1008a.jpeg”. Freeway is also not publishing the ‘masthead-redline’ graphic header to the current Resources folder - because there’s no masthead-redline.jpg in there.
Needless to say this is a complete pain! Freeway seems to have lost the plot and is stuck in some time warp. Or it’s just being nasty and refusing to publish my new graphics!
thanks for the tip, Dave. I did a resample and then re-publish and then looked at the source code again. I’t still trying to reference the header image from outside the sub-directory - although it has got the image filename, now.
I’ve…
deleted all the header images in the sub-directory pages and recreated the header graphics, importing a fresh image into each html passthrough box.
changed the titlename of the newly imported header image
updated all the graphics
resampled
…and still the code is showing me that it’s trying to get an image from …/subdirectory/Resources/headerimage
Why is the code not writing itself correctly and accessing the new image from the local directory Resources folder where it is being published?
Freeway internally optimizes the entire site structure that it exports. If two instances of an image are absolutely identical, but shown on two different pages, only one of them will be exported, and the URI to that image will be mapped to that one instance of the image regardless of which page requested it. This can and does jump subfolders as you have noticed.
You can force the issue by making the two images slightly different from one another – size will work, filename too, if you’re importing them as pass-through – and then Freeway will do what you expect. But if the two images are truly – at the binary level – identical, then Freeway will out-smart you.
Walter
On Nov 18, 2011, at 12:25 PM, hugh wrote:
I’t still trying to reference the header image from outside the sub-directory - although it has got the image filename, now.
Sorry Walter, I missed your (very astute) response.
I see! Well, it may be smart but it isn’t clever! Or at least I don’t think so. In optimising the site structure it’s breaking the logic of the structure…local files published to local folders.
This optimisation still doesn’t seem to stop Freeway producing oodles of replica files within the same resources folder for item00a.gif…item00aa.gif…item000aa0a.gif and so on…all of which are identical, at the binary level, even if their position may have moved by one pixel.