Hi all,
I have a navbar that I created in FW and exported as a DW
library item. When I drag and drop the library item (navbar) into a
site page, I get an error every time I try to save that page. The
error states that the body tag was in the wrong place and has been
moved to the right place. The problem is never fixed though and I
keep being spammed by the error dialog.
In reviewing the code, it appears that the library item has
its own body and preload. So adding the library item to the page
causes a duplication of the body tags and preload images code.
Any thoughts as to how I can fix this or avoid it would be
greatly appreciated.
|||
Mabou2 wrote:
> In reviewing the code, it appears that the library item
has its own body and
> preload. So adding the library item to the page causes a
duplication of the
> body tags and preload images code.
>
> Any thoughts as to how I can fix this or avoid it would
be greatly appreciated.
Never used library items but I would assume you can just
remove the
<body> and </body> from the pages code, together
with anything other
code you don’t want. Just keep the code which is directly
associated
with the library item. Then when you use the library item in
a page you
won’t be bringing in a lot of duplicate coding.
|||
Hi Osgood,
I have a vague recollection of hearing or reading that
library items are not supposed to have anything like a <body>
tag or code that makes them act like an html page, but I can’t
remember clearly enough to take action.
I would love to hear from someone who knows the library
paradigm.|||
You are right, no <htm> <body> or css styles go
into a library item.
–
Nadia
Adobe锟?Community Expert : Dreamweaver
————————————————-
http://www.DreamweaverResources.com
- CSS Templates|Tutorials
http://www.csstemplates.com.au
————————————————-
http://www.perrelink.com.au
- Web Dev
————————————————-
http://www.adobe.com/devnet/dreamweaver/css.html
CSS Tutorials for Dreamweaver
————————————————-
“Mabou2″ <webforumsuser@macromedia.com> wrote in
message
news:e906ap$ed8$1@forums.macromedia.com…
> Hi Osgood,
>
> I have a vague recollection of hearing or reading that
library items are
> not
> supposed to have anything like a <body> tag or
code that makes them act
> like an
> html page, but I can’t remember clearly enough to take
action.
>
> I would love to hear from someone who knows the library
paradigm.
>
|||
Thanks Nadia,
I am curious as to where the bug is then? I created the
navbar in FW and exported as a DW library item.
Why would either FW or DW write the <body> and preload
information in a library item if it is not supposed to be there?
Anyway, thanks for your reply.|||
> Why would either FW or DW write the <body> and
preload information in a
> library item if it is not supposed to be there?
using behaviors in Library items is something that worked
only in dw 6.
the library item could have js functions, a body tag with
behavior calls.
When the library item was inserted into a page, dw 6 put
those elements in
the proper places- the documents head section and the docs
body tag.
When you export from fireworks as a library item, that’s the
format it’s
using. It would work if you were using dw6.
It would also work if you exported as images/html and
inserted Fireworks
html into each page.
Using behaviors in library items broke when dw7 mx2004 came
out. There was
almost no notice that it was broken for a long time going by
topics on this
forum, then when a few people asked for help with it, the
general reply was
to not use behaviors in library items. It wasn’t addressed or
fixed in the
dw8 release
|||
Thanks Alan….
(lame that this problem still exists)|||
“Alan” <dont_mail_me_period@macromedia.com> >
> Using behaviors in library items broke when dw7 mx2004
came out. There
> was
> almost no notice that it was broken for a long time
going by topics on
> this
> forum, then when a few people asked for help with it,
the general
> reply was
> to not use behaviors in library items. It wasn’t
addressed or fixed in
> the
> dw8 release
Some third party systems can work fine as Library Items. The
code must
be well-written and certain steps followed.
http://www.projectseven.com/products/menusystems/pmm/avdemos/libray_un scripted.htm
–
Al Sparber – PVII
http://www.projectseven.com
Popup Menus | Image Galleries | CSS Tutorials & Templates
———————————————————————- ————–
Newsgroup: news://forums.projectseven.com/pviiwebdev/
CSS Newsgroup: news://forums.projectseven.com/css/
DW Newsgroup: news://forums.projectseven.com/dreamweaver/
|||
Okay…. I created a navbar in FW and did not associate any
links in the buttons. What came across is clean html with no
<body> tags.
Then, IN dreamweaver, I opened the library item (navbar) and
started adding mouse-over behaviors for the buttons. Now the
library item has <body onLoad> tags!! This means that when I
move this library item onto a page, I will start seeing the same
“Moved Body tag” spam error….
Please help again. If I need to manually remove some of the
code in the library item, can you be very specific as to what I
need to cut? I am going to enclose the code because I dont know
what to do to make this problem go away….thanks again.
Related posts:
- Turn-off CSS, HTML, Head and Body Tags?
- procedurally select multiple items in a list control
- navigation bar as library item
- referencing library items dynamically
- Sub Items in MenuBuilder
Related posts brought to you by Yet Another Related Posts Plugin.
