Hi! A client of mine is are doing all the updates in Freeway (v5.2.1). This is the site: www.scenario.no. They have a Freeway document that has grown out of every proportions in terms of file size. They have problems working with the document. The freeway file itself is 1.93GB. I received the project today.
They did a: “file, save archive…”. I can see that the document is 1.93GB and takes a while to load and even more to upload/publish. With this size the program crashes often. Is there any function that let med “optimize” the pictures used throughout the document? If a picture is 320x240 in freeway and the reference file is 3200 pixels wide can I optimize it within freeway to 320x240 without taking all the image files into photoshop and rescaling them? 300+ pages within the document. I have done websites in this scale before (used photoshop optimized picture) and the file size of my Freeway document has been 120 mb or so not 1.93 GB!
One of the ways that a file can grow to this size is having lots of pasted graphics or lots of placed graphics that are all resized down a lot. Of course, having many hundreds of pages could do it, too. First thing I would try is to open Edit / Resources and press the Resample All button. And go out for a nice meal, by the sounds of things.
If that doesn’t help, you may need to start splitting the site into multiple Freeway documents.
Thanks for your suggestion. Ofcourse I have a lot of “missing” resources due to many of the files must be on the clients server. However. It shrunk from 1.93GB to 420MB. Not to bad
I do however get this message when I try to (re)publish (command+p): http://bildr.no/view/263615
The very latest version of Freeway has the ability to ignore missing graphics permanently. If you want to try this (in a Save As, naturally) then select one of your missing graphics in the Edit / Resources dialog, and then press the Edit button at the bottom of the dialog. In the resulting sub-dialog, check “Detached”. This should stop the missing graphics error (of course you will have to do this for each one – urgh!). Then save, then try publishing. One other thing to try is to restart your entire computer between the save and the attempt to re-publish. That last one is a bit of a large hammer, but it might help.
SP support can tell you what the precise error means, you might want to e-mail them directly in case they haven’t caught this thread here.