DW8 messed my relative position layer behaviors

[Plastic Elvis]

I recently upgraded from MX to Studio 8. I have a website where I was using a
series of "set text of layer" behaviors to write copy to a relative positioned
DIV layer depending on which button the user clicks. It appears DW8 will no
longer recognize my relative positioned DIVs as layers, and has "reset" this
behavior on all of my pages so that the text is written to the first absolute
positioned layer on the page.

This "resetting" appears to have happened when I made a change to the page
template and updated it globally. How can I get DW8 to recognize my relative
positioned DIVs so that I don't have to re-do this whole thing?

When I go back and open the pages in DWMX it allows me to change the behavior
settings back to my original layers, but as soon as I make a change in DW8 it
will fudge it all up again.

[Murray *ACE*]

> It appears DW8 will no

> longer recognize my relative positioned DIVs as layers.

A relatively positioned element is not a layer.

> How can I get DW8 to recognize my relative
> positioned DIVs so that I don't have to re-do this whole thing?

Change the positioning to absolute. Apply the behavior. Change the
positioning back to relative. This should be fixed.

> but as soon as I make a change in DW8 it
> will fudge it all up again.

Give me an example of how this gets 'fudged'? I have a huge page with
monstrous STOL behaviors on it, all created in DW8, and no layers anywhere.
I have no such problems with this page -

[url]http://www.fairfaxboulevard.com/f_node-photos.shtml[/url]

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
[url]http://www.dreamweavermx-templates.com[/url] - Template Triage!
[url]http://www.projectseven.com/go[/url] - DW FAQs, Tutorials & Resources
[url]http://www.dwfaq.com[/url] - DW FAQs, Tutorials & Resources
[url]http://www.macromedia.com/support/search/[/url] - Macromedia (MM) Technotes
==================


"Plastic Elvis" <webforumsuser@macromedia.com> wrote in message
news:dv43fg$q28$1@forums.macromedia.com...

>I recently upgraded from MX to Studio 8. I have a website where I was using
>a
> series of "set text of layer" behaviors to write copy to a relative
> positioned
> DIV layer depending on which button the user clicks. It appears DW8 will
> no
> longer recognize my relative positioned DIVs as layers, and has "reset"
> this
> behavior on all of my pages so that the text is written to the first
> absolute
> positioned layer on the page.
>
> This "resetting" appears to have happened when I made a change to the page
> template and updated it globally. How can I get DW8 to recognize my
> relative
> positioned DIVs so that I don't have to re-do this whole thing?
>
> When I go back and open the pages in DWMX it allows me to change the
> behavior
> settings back to my original layers, but as soon as I make a change in DW8
> it
> will fudge it all up again.
>

[Plastic Elvis]

>A relatively positioned element is not a layer.
Yes, but MX did treat them as such in both the layers pallete and set text of
layer behavior. So I saw no reason not to use them that way. I support equal
rights for the relatively positioned :)

Here is what one of the pages looks like:
[url]http://www.compassbaby.com/product_B500.html[/url]
Clicking on More Description triggers the Set Text of Layer to the relative
positioned div ID "Description".

When I updated the top menu on my template for this page, all of my product
pages became fudged as below:
[url]http://www.compassbaby.com/product_B500fudge.html[/url]

I did a find and replace text to change "Layer 1" back to "Description", which
did repair the damage... It's annoying, but it will work. My main concern is
why the template update modified my behavior code when it was not part of the
template. I don't recall making any other changes to these files.

[Murray *ACE*]

> I did a find and replace text to change "Layer 1" back to "Description",

> which
> did repair the damage... It's annoying, but it will work. My main concern
> is
> why the template update modified my behavior code when it was not part of
> the
> template. I don't recall making any other changes to these files.

It should not. And if I understand your description, it could not. But -
maybe it was cosmic rays! 8)

But show me your template, please.

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
[url]http://www.dreamweavermx-templates.com[/url] - Template Triage!
[url]http://www.projectseven.com/go[/url] - DW FAQs, Tutorials & Resources
[url]http://www.dwfaq.com[/url] - DW FAQs, Tutorials & Resources
[url]http://www.macromedia.com/support/search/[/url] - Macromedia (MM) Technotes
==================


"Plastic Elvis" <webforumsuser@macromedia.com> wrote in message
news:dv4ljn$lrb$1@forums.macromedia.com...

> >A relatively positioned element is not a layer.

> Yes, but MX did treat them as such in both the layers pallete and set text
> of
> layer behavior. So I saw no reason not to use them that way. I support
> equal
> rights for the relatively positioned :)
>
> Here is what one of the pages looks like:
> [url]http://www.compassbaby.com/product_B500.html[/url]
> Clicking on More Description triggers the Set Text of Layer to the
> relative
> positioned div ID "Description".
>
> When I updated the top menu on my template for this page, all of my
> product
> pages became fudged as below:
> [url]http://www.compassbaby.com/product_B500fudge.html[/url]
>
> I did a find and replace text to change "Layer 1" back to "Description",
> which
> did repair the damage... It's annoying, but it will work. My main concern
> is
> why the template update modified my behavior code when it was not part of
> the
> template. I don't recall making any other changes to these files.
>