If they were linked from the page that changed, then they would be uploaded as well. This is a pain, I agree. When a page gets “dirtied”, every resource referenced from it is also dirtied as well.
I have had to split the PDF index pages out of sites in the past, and publish them from a separate Freeway document, in order to get around this problem (large number of large PDFs, and it could take hours for the entire site to upload).
Also, I always have to Publish Everything in order to see changes in the browser preview. Does this change times on the files? Could that be the culprit?
GoLive uses a different metaphor for pages and publishing, much more “down to the metal” than Freeway. So I’m not surprised that it was seeing no changes on individual elements on the page. Freeway takes a different approach, and if anything changes on the page, the entire dependency tree for that page is re-built. Normally (that is to say, with web-sized graphics) this is a great approach and keeps things from getting messed up or becoming a combination of new dimensions and stale graphics. But if you have used Actions to link to large files, then this conservative approach will shoot you in the foot.
As to Publish Everything being the culprit, I would say enthusiastically, YES! That deletes all trace of your site in your local publish folder and builds everything again from scratch. Which would change the modification date (naturally) on every last thing in your site.
Best to get to the bottom of why you need to use this large gun, because that’s surely the root of problem you are experiencing here.
When you do Publish Everything, what sorts of changes are you trying to see, and failing to see?
Well, my “partner in crime” is at another location and I send her the Site folder to look at it in a browser on her HD. Many times she has told me that things I changed weren’t changed even though she refreshed pages. I checked at my end and had the same problem. Once I Publish Everything, all is OK.
I did think it was odd that I had to do that all the time. Had to do that on the other site I finished in FW, also.
That’s not normal, just so you know. There must be something unique about your situation that is forcing it to behave this way. The vast majority of Freeway users don’t have to do this. It would be good to get to the bottom of this, since clearly it impacts your workflow.
Well, not sure what info I can provide that would be different than others.
I let FW set up the site in a folder. The FW file resides in the folder with all my elements. In there is the Site folder also. So the FW file is outside the Site folder and they both reside in another folder that contains all the elements that I place (which may also be in yet another folder, but IN the same folder as everything else).
When you are forced into using Publish Everything, what are you trying to see and not getting in Preview or Preview in Browser? What sorts of changes are you making, and where in your site, and not seeing reflected in the previews?
Instead of using the ‘publish everything’ command why no just use the
“Force Publish” in the Page menu. This way your changes will be
published for the specific page and when you send the site file the
changes should be there.
Robert Bovasso wrote:
I never use FW’s preview. I preview in Firefox 22.214.171.124. Intel iMac running 10.4.11.
Well, it’s happened a few times during the creation of the to sites I was working on.
Eventually, I just automatically Published Everything after a few updates or before I sent it to my co-worker.
Publish Everything is a big gun, to be brought out when nothing else seems to work. If you have Actions on your page that publish external files, then sometimes you will need to use that to “wake up” the Action and get it to publish updated information. But it’s hidden behind the Control key for a reason – it’s not a day-to-day thing that you need.
Often, especially when you are working locally, you will see an aggressive cache in your browser insist on holding on to the old version of the site and not showing you changes that you know you made.
One way around this is to add a question mark at the end of the URL. Then click Return to load the “new” URL.
Another is to hold down the Shift key while pressing the reload button.