I’ve recently turned a friend and colleague onto FWPro and he brought up an issue (coming from Dreamweaver) that I have to say, has been the bane of working in FWPro for all these years (since pretty much the beginning). I’m not a professional though and I only do one site … my own. So perhaps I’ve been labouring through unnecessary work all this time.
I have 15 master pages. On each page is a ‘block’ of navigation buttons. Whenever I change those buttons, even just nudging them 1 pixel, I have to go through each Master page, either making the same change, or doing a delete/paste of the ‘object’ from the first Master page. This is really laborious and I find myself doing this regularly in FWPro.
Is there a way in FWPro to make an ‘object’ a ‘master object’ linked to other Master pages on a site? So … edit once and it’s changed everywhere and obviously then flowed through to any child pages associated with those masters.
If I haven’t been missing something all these years and there is no way of achieving this in FWPro, then I would like to propose this as a new feature for FWPro 6 (or even 5.5)
Is there a way in FWPro to make an ‘object’ a ‘master object’ linked to other Master pages on a site? So … edit once and it’s changed everywhere and obviously then flowed through to any child pages associated with those masters.
If I haven’t been missing something all these years and there is no way of achieving this in FWPro, then I would like to propose this as a new feature for FWPro 6 (or even 5.5)
No, there isn’t a way to do this with Freeway alone, but you could use Tim Plumb’s Simple Include Pro Action suite to make one set of navigation for the entire site, and “share” it with all the Master pages.
You’re not alone in wanting this. I’ve been bringing it up every year since maybe 1998.
“The only think to watch out for when using these actions is that the ‘Create’ action should be placed on a page that is published before the ‘Use’ action for the include file to exist before it is needed. Keep this in mind and you should be OK.”
Does ‘published’ in this context mean, uploaded from FW? If so, I take it FW publishes from the top down?
Yes, you have it correctly. So I would put the navigation element on the first page in the list (which you can drag-sort, you know) and let all the other pages inherit from it.
Walter
On Feb 10, 2012, at 10:04 AM, grantsymon wrote:
Hey Walter,
nice to hear from you.
I thought there was no way …
Looking at Tim’s action :
“The only think to watch out for when using these actions is that the ‘Create’ action should be placed on a page that is published before the ‘Use’ action for the include file to exist before it is needed. Keep this in mind and you should be OK.”
Does ‘published’ in this context mean, uploaded from FW? If so, I take it FW publishes from the top down?
