The master page is a completely different thing than a shared layer. A layer can be shared to states, but the master page can be used to repeat info toother pages. Layers and states are included in a page.
I don't know if i get the problem. You just want to create buttons and some simple rollover behaviors on a page?
If you want to apply many behaviors to one slice be careful, because this does not always work.
If a Master page is one layer then the only difference between it and a shared layer is that one (master) automatically goes to all pages. If it has a button on it, apparently, it also goes to all states. Create a secondary state on any page and it will have the "down" state of the button (third state hover etc). But now we are just talking semantics.
My solution, unless I get a better answer, is to have the email, faq and cart links on disjointed pages simply be links with no states.
It works but it is not what I wanted to do...
I'm working on Fireworks CS4. I don't think that a button symbol appears in other states. Creating a button does not add states on your document.
Actually, a button symbol does add states to a document (and it even adds a slice), but none of these appear on the main canvas, because the button is a symbol. If you go into symbol editing mode you'll see the slice and you'll find four states.
When you add a button symbol to a Master Page, it only creates the states on the Master page - you often need to add additional states to the subsequent pages to make all of the button states appear and work normally. (For example, a button symbol on the Master page creates four "invisible" states on the Master page, but not on every page in the document. If you export your site and the buttons do not behave correctly, try adding three additional states to each page and export again. Multi-state symbols on the Master page need the same number of states on every page that share the Master page in order to work. Oddly, each of the three states on the other pages will appear empty, but the button states are there - remember, they are hidden in the symbol.)
oh, i see, you add states after creating your button. Ok why don't you try to add simple rollover behaviors? How does the down (3rd) state of the button appear in the second state? You mean the hover state? Anyway, a button's state appearing in other states should not be a problem. If so, don't create button symbols, but only swap image and rollover behaviors. (Slices other than buttons' slices can have more behaviors.)
Just trying to understand what the problem is.I hope we find out.
There shouldn't be any problem doing this,, but posting a link to your
file will help us debug the problem more accurately.
Community MX Partner -
Adobe Community Expert
Author - Lynda.com
Author: Peachpit Press