I’m wondering if anybody can tell me what, if anything, I’ve done wrong.
I always start my web pages with a Master and then make ‘slave’ pages from this, as the FW instructions demonstrate. This means that when I need to make a change to my header, CSS menu’s or anything else on the master - I do so on the ‘master’ and every other page reflects that change. - this all works as expected.
Now, on a site I have just built, some of the pages required a separate menu bar, so I dragged a ‘master’ down and then made that a ‘new master’.
I assumed (possibly wrongly) that if the second ‘master’ (we’ll call that ‘master2’) was based on ‘master1’ then any changes I make to ‘master1’ will not only show on any slave pages based on ‘master1’ but ‘master2’ and all the pages based on ‘master2’ would change accordingly.
That doesn’t seem to be happening - so, have I made it the wrong way, or is it not possible to implement this scenario - I know I used to be able to do this in DreamWeaver, so just assumed the same principle would apply to FW.
Masters only work at one level of remove. There’s no such thing as a master based on a master inheriting changes to the original master. Sorry.
Walter
On Nov 28, 2013, at 9:09 AM, Alex Rollo wrote:
I’m wondering if anybody can tell me what, if anything, I’ve done wrong.
I always start my web pages with a Master and then make ‘slave’ pages from this, as the FW instructions demonstrate. This means that when I need to make a change to my header, CSS menu’s or anything else on the master - I do so on the ‘master’ and every other page reflects that change. - this all works as expected.
Now, on a site I have just built, some of the pages required a separate menu bar, so I dragged a ‘master’ down and then made that a ‘new master’.
I assumed (possibly wrongly) that if the second ‘master’ (we’ll call that ‘master2’) was based on ‘master1’ then any changes I make to ‘master1’ will not only show on any slave pages based on ‘master1’ but ‘master2’ and all the pages based on ‘master2’ would change accordingly.
That doesn’t seem to be happening - so, have I made it the wrong way, or is it not possible to implement this scenario - I know I used to be able to do this in DreamWeaver, so just assumed the same principle would apply to FW.