Library items with Javascript

I recently updated a library item and then updated/uploade *some* of the pages
that had the library item. I noticed on the pages I uploaded, the javascript
that was originally on the page is messed up. We had pull down menus that are
no longer working?? They worked fine with the original version of the library
item and I barely changed anything (removed and added text)? Anybody know how
I can fix this or WHY it messed up now?

Show me the code in the library item, please.

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

"1display" <webforumsuser (AT) macromedia (DOT) com> wrote

I recently updated a library item and then updated/uploade *some* of the
pages
that had the library item. I noticed on the pages I uploaded, the
javascript
that was originally on the page is messed up. We had pull down menus that
are
no longer working?? They worked fine with the original version of the
library
item and I barely changed anything (removed and added text)? Anybody know
how
I can fix this or WHY it messed up now?

I can't imagine what messed up the javascript. The only thing that's wrong
with the library item is that there is a link to a stylesheet in it. Remove
that link and see what happens.

--
--
--
DiMa
Team Macromedia Member for Dreamweaver MX
--------------------
WEB FORUM USERS: Please log on to the Newsgroup for quicker replies to
your posts: news://forums.macromedia.com/macromedia.dreamweaver
For Answers, check here first:
http://groups.google.com/advanced_group_search?q=+group:macromedia.dreamwea ver
http://www.macromedia.com/support/dreamweaver/technotes.html
http://www.projectseven.com/faqbase
http://dwfaq.com

http://www.macromedia.com/support/forums/etiquette.htm

www dot flyingtigerwebdesign dot com

Or better, show us a 'messed up' page.

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

"DiMa *TMM*" <diana (AT) YOURHATANDCOATflyingtigerwebdesign (DOT) com> wrote

I can't imagine what messed up the javascript. The only thing that's wrong
with the library item is that there is a link to a stylesheet in it.
Remove
that link and see what happens.

--
--
--
DiMa
Team Macromedia Member for Dreamweaver MX
--------------------
WEB FORUM USERS: Please log on to the Newsgroup for quicker replies to
your posts: news://forums.macromedia.com/macromedia.dreamweaver
For Answers, check here first:
http://groups.google.com/advanced_group_search?q=+group:macromedia.dreamwea ver
http://www.macromedia.com/support/dreamweaver/technotes.html
http://www.projectseven.com/faqbase
http://dwfaq.com

http://www.macromedia.com/support/forums/etiquette.htm

www dot flyingtigerwebdesign dot com

http://www.usdc.org/resources/resources_gov_mil.html

This is an example of a page where the pull down menus don't work anymore. I
have been going through the ones that don't work and just cutting and pasting
all the javascript from a page that did still work and that's working. I don't
understand why not ALL of the pages I updated didn't get the javascript messed
up though (not that I want them to)? Because some (I think most actually) just
updated the library item and nothing else happened. It's just a pain in the
butt to have to look at all of my pages and cut and paste because I have like
36 pages that use this library item and now I'm very wary of updating/using
it...

Hmm - I can see something you should think about -

It appears that your line break type is mismatched between your local
development environment and your host server. There are lots of blank lines
in the code on this page (check EDIT | Preferences > Code Format > Line
break type: and set the server type there.

The Library item code you showed me has no potential for messing with your
javascript. There is no javascript in the item, and not even any calls to
javascript in it. The only potential problem I see in there is the link to
the stylesheet which should not be in the Library item.

Based on this, I'd say that the cause of your problem is somewhere else. I
can see no likely candidate there.

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

"1display" <webforumsuser (AT) macromedia (DOT) com> wrote

http://www.usdc.org/resources/resources_gov_mil.html

This is an example of a page where the pull down menus don't work anymore.
I
have been going through the ones that don't work and just cutting and
pasting
all the javascript from a page that did still work and that's working. I
don't
understand why not ALL of the pages I updated didn't get the javascript
messed
up though (not that I want them to)? Because some (I think most actually)
just
updated the library item and nothing else happened. It's just a pain in
the
butt to have to look at all of my pages and cut and paste because I have
like
36 pages that use this library item and now I'm very wary of
updating/using
it...

I don't know. It has to be the library item though because I updated the
items, fixed the javascript that wasn't working, updated the item again and now
have to fix the javascript again. There weren't any other changes made to the
page after the javascript was working. But anyways, thanks for the feedback.

And what fix do you implement to make the menus work again?

As I said, the Library items have no way to interfere with the menus - they
don't even come close to them in the code! 8)

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

"1display" <webforumsuser (AT) macromedia (DOT) com> wrote

I don't know. It has to be the library item though because I updated the
items, fixed the javascript that wasn't working, updated the item again
and now
have to fix the javascript again. There weren't any other changes made to
the
page after the javascript was working. But anyways, thanks for the
feedback.

I basically just copy all the header information from a page that is working.
When I look at the code, it'd obvious where the library item is (stuck in way
below in the body of the document... although I admit I don't scrutinize the
javascript to see what actually changed there ) and I can't see why it would
mess anything up either but copying and pasting the seems to work.

Can you show me the code for before and after?

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

"1display" <webforumsuser (AT) macromedia (DOT) com> wrote

I basically just copy all the header information from a page that is
working.
When I look at the code, it'd obvious where the library item is (stuck in
way
below in the body of the document... although I admit I don't scrutinize
the
javascript to see what actually changed there ) and I can't see why it
would
mess anything up either but copying and pasting the seems to work.