I’ve made one master page so far that is the basic layout for the whole site. I’d like to make a master page for each page in the site. A lot of the elements on the first master page will be on all the pages.
If I duplicate the master page and change, say, the navigation (content or layout) will it update on all the other master pages?
Also, this is a (more or less) box model style site.
I’d like to make a master page for each page in the site.
Why bother?
Unless you are creating more pages based on each of these NEW Masters then you are wasting your time as you are just as well making the changes on your individual pages.
As long as the elements you change on the master have not themselves
been changed on the child pages, yes. But anything you do on the child
pages to change one of those master elements will “detach” it from its
master. This happens quite easily. You can re-attach these lost
children by checking the User Master settings option in the Inspector.
One major caveat: so-called Box Model layouts cannot be controlled
effectively by a Master page. The reason is that Master pages don’t
provide granular control over the individual child elements within the
outer container. So the only thing your master could actually affect
would be the outer-most box, and not any of the inline boxes with your
actual content.
Walter
On Mar 12, 2010, at 1:03 PM, Robert B wrote:
So, basically make the one master, drop it down to the pages for all
subsequent pages, and make alterations to the regular page.
If I do that and change something on the master page, will it update
on all the other pages even though I’ve altered things on all those
pages?
As long as the elements you change on the master have not themselves
been changed on the child pages, yes. But anything you do on the child
pages to change one of those master elements will “detach” it from its
master. This happens quite easily. You can re-attach these lost
children by checking the User Master settings option in the Inspector.
I have a question.
I have a MASTER page. I drop it into the site panel it becomes a child page. When I alter say a graphical element on the child page by moving a button and then preview it. ALL the ‘action’ elements like rollovers/slaves etc do not function anymore, but the hand cursor still appears as if there is a link etc.
I then check the Inspector palette and both master settings/content are both still checked.
So why are the actions not displaying, I’m sure its something simple but its beginning to frustrate me!
Also if this is the case, to what extent can you design your master pages? Is there a general rule of thumb of what you can & cannot use/apply to the master pages?
I’m using a table layout and the master has protaculous ‘prototype library’ applied to it. Will this cause any issues?
I’m just testing things and the protaculous page action could be what’s causing the issues?!!
Still any expert advice/knowledge on this would be very helpful for future developments.
Page Actions, like Protaculous, have a few problems when used on Master Pages.
First, if you apply an Action to a master page after you have created children from it, the children will appear to be changed – they will get the bullet next to their name that indicates they have been modified – but the Action will not attach to them. New pages created from the master page will pick up the new Action, but existing pages will not.
Second, if you apply an Action to a master page, make changes to the child pages (as would be normal) and then try to make changes to the parameters set in the Actions palette on the Master Page (hoping that those changes will percolate down through all of the child pages based on that master) the changes may or may not be accepted by the children. The reason for this is not altogether clear to me.
Now there is some good news: Paul Dunning has written a version of Protaculous that you can apply as an Action-Item (an Action you draw on the page as if it was a picture or a text box) which gets around this Master/Child/Action problem very neatly. I will release it as soon as I get a chance to test it and integrate it with some other changes I have going on in all of the Scripty Actions.