exclude page from upload

Hi,

Is there an easy way (or action available) to exclude a selected FW page from being uploaded?

Here is the situation. I developed a site in FW and EE. Now in the final stage of fine-tuning the external CSS, HTML and W3C validation.

What I would like to do is exclude the page I’m working on in FW from being uploaded again. I will then work on that specific page details in CODA. Going through the whole site page-by-page. At the end no pages are uploaded again and all code polishing was done in CODA.


actionsdev mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

It’s not possible in Freeway or the Actions API. It’s been requested over and over, but it’s not there. From your workflow, it sounds as though you might want to consider using a “shadow” Site Folder for your Coda workspace, and selectively copy files over to it as you go.

You could make an Alias of the Resources folder, since that’s not going to be edited in Coda at all, as well as any supporting files/pages that you don’t expect ever to edit in Coda, and then only move over one page at a time as you do your edits. Coda will honor Aliases when it uploads (at least Transmit does, and they’re deeply related) so you would do all your server file management in Coda, and Freeway for the initial design.

Walter


actionsdev mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Thanks walter,

Your suggested workaround will do.

For the guys at FW, adding the exclude functionality will help them overcome some of the other discussions regarding hand-coding or combined hand-coding in FW i.e the lack of the appropriate tools therefor in FW.

As described in my suggestion you will then create a simple workflow model in which you can get the best of both worlds: the initial design in FW → followed by hand-coding using the tools one likes best.


actionsdev mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options