MuseJSAssert Bug in Dreamweaver?

Hey there. My company is getting started with their web site using Dreamweaver CC and hosting on Business Catalyst. We outsourced one page to a marketing firm, and they sent me a set of files created in Muse. I brought all of the files into Dreamweaver and placed them correctly within my root structure, including updating as many links as I could find.
When I go to preview the page in Business Catalyst (or with Live View) I immediately get a MuseJSAssert error of
MuseJSAssert:Error calling selector function:ReferenceError: WebPro is not defined
The only place I can find the string 'MuseJSAssert' is in the "museutils.js" file. There is also a "webpro.js" file in the directory.
I am not well-versed in Javascript, so if the fault lies with the marketing firm I'll send it back to them. However, if the fault lies with me for bringing a Muse file into Dreamweaver (or some other reason) I'd really appreciate any thoughts! I'm supposed to release this page by Monday for public viewing, and I'm kind of panicky.
Thanks very much in advance!

BW~Merlin,
You are truly a magician. Spacebar was all it took to make
the selection. It was still invisible, but I was able to proceed
sucessfully with the installation. Many thanks.
Still, I'm sure it's not what the developers intended. I hope
it's something funny about the configuration of my machine and not
a widespread issue!

Similar Messages

Question: Cannot afford cloud pricing (am retired). Have a bug in Dreamweaver 5.

OK, so I have been a customer of Adobe for many years. I am now retired and cannot afford the cloud structure pricing. I have several bugs in Dreamweaver 5, one of which replicates the editable region so there is a duplicate after the first one. I've managed to migrate my site to HTML5 without the benefit of Dreamweaver 6 (Ouch). Am I stuck up the river without a paddle?

Stuck? No, I don't think so. DW CS5 still works.
When things start to go wrong, See Deleting Corrupted Cache / DW Personal Configuration Folder: http://forums.adobe.com/thread/494811
Nancy O.

A BUG with Dreamweaver 8 when add flash button

There is a BUG with Dreamweaver 8 Chinese language version.
When I check the button "add flash button",show me a
message"There is an error,when the onChange run in Flash
Button.htm".
How to sovle the problem? Thanks.

Troubleshooting JavaScript errors in Dreamweaver
http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_19105#dat
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"cnlomo" <[email protected]> wrote in
message
news:fk0mas$31l$[email protected]..
> There is a BUG with Dreamweaver 8 Chinese language
version.
> When I check the button "insert flash button",show me a
message"There is
> an
> error,when the onChange run in Flash Button.htm".
> How to sovle the problem? Thanks.
>

FTP BUG in Dreamweaver CS6 after upgrading to build 5861

I just updated Dreamweaver CS6 to 12.0.1 build 5861. Now Dreamwearver fails to put files after several successful puts of the same file. Only symptom is that the background uploader window fails to appear. Only solution is to close and re-open Dreamweaver.
Further testing seems to indicate this condition only happens if I manually save a changed file before attempting the Put. It seems to consistently work correctly if I perform the Put and wait for Dreamweaver to prompt me to save the file.
THIS IS DEFINITELY A BUG THAT SHOULD BE FIXED - Dreamweaver CS6 Perpetual license (Not Cloud)

Ask in the DW forum.
Mylenium

[BUG?] Dreamweaver CS3 b3481 removes all source

Hello,
Since a few days I noticed that Dreamweaver (CS3 build 3481)
is removing all of my PHP-coded source if I didn't close the
PHP-tag; '
?>'.
This is how I found out;
First I created a new PHP-document and went to the Source of
it. After some typing of HTML and PHP, the document had to be saved
to a file. For example, the document's source is:
quote:
<?="Echoing a foobar!";?><br
/><table><tr><td>foo
bar</td></tr></table><?
More PHP source comes here
... without closing the PHP-tag.
The document will be saved to a file (f.e.: foobar.php). Now,
everything after '</table>' is gone.
How is this possible?
Thanks for any read and respond.
- Frank W.
Netherlands.

Vingerverf wrote:
> Since a few days I noticed that Dreamweaver (CS3 build
3481) is removing all
> of my PHP-coded source if I didn't close the PHP-tag; '
?>'.
I haven't come across this. If you have reproducible steps,
file a bug
report with Adobe:
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of
ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Seasonal Time Change Bug crashes Dreamweaver 9 (CS3)- still no fix?

The fact that Adobe has produced a new version of CS3 does not in my opinion give them a reason not to fix the CS3 bug that causes Dreamweaver to crash when any attempt is made to edit the ASP or PHP components of a file.
This bug is caused by daylight time adjustments.
The podge that is recommended by Adobe is to delete the WinFileCache-AD76BB20
While this works, as it happens only every 6 months, it is easy to spend time working out why your existing files all crash the system, but newly created ones do not.
You can find the solution at http://kb2.adobe.com/cps/402/kb402776.html
Bookmark this as it may save you the 4 hours or so that I spent trying to find a solution.
It would cost Adobe nothing to send out an e-mail to all existing owners of CS3 containing this bug fix, and would certainly improve their reputation in many quarters.

well.
it feels bad, after paying money.
not being able to use a software full.
and ADOBE must be ashamed to give such service
(by not updating these softwares which has still lots of unknonw! bugs and also must be ashamed to put a page for unknown bugs. and trying to make customers be their own software engineers instead of the company's hundreths of engineers)
and this, which they do not fix their program is not important or the issue.
it is a sad subject that, they think the people will give money to fix their unusable programs which they already bought.
and to customers who has paid about 1000$ to a software suit are having a bad vision that ADOBE started to work for money instead of customer happiness.
when they understand their
1000$ program has no support at all. no update or fixes at all.
which can not do a simple action
which the simplest editor WORDPAD editor does.

Is this the right replace to report a bug in dreamweaver CS4?

if so,
i have noticed that when using dreamweaver cs4
on windows vista business(build 6001) with multiple monitors
and dreamweaver is open on a screen that is not the primary screen
the tooltip box (that comes up when entering a function name and gives details on the parameters) that should appear above and right of the mouse location appears to stretch in the direction of the primary screen, and you cannot see the text that should be inside it.
see screenshot

To report bugs or suggest improvements:
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Workaround Site for too many Bugs in Dreamweaver

I am using Dreamweaver Software since 1996 and I must say
that I am very unhappy with 8(.02). I did not buy 2004 MX as I have
been reading about all the bugs in Forums. But I did not want to be
back to far and upgraded from very good working 4 -> 8. Still
regular functions a Webdesign Company needs daily are not working
properly. I think that Adobe themselfes do not use Dreamweaver -
they would already have busted the bugs month ago.
I have been writing again and again. But only 1 time I
received an answer - all the other messages about missing features
like choose a profile in the dropdown menue with the letter (which
is very needfull if you have 400 projects). Broken links are not
getting repaired without busting Dreamweaver ...
Only one Computer is now working with Dreamweaver 8 - all the
others will remain Dreamweaver 4. I am not willed to pay only for a
nicer look of the software and less comfort and stability.
Do you agree?
Thanks, Michael

You have 400 sites listed in the site dropdown list? Or maybe
I am not
understanding what you mean by "project". I'll be honest with
you,
scrolling that list is all I've ever done since I started
with DW2.
> 2. (STRG F8) If I repair the broken Links of a project
and I get a wrong
> link
> 10 times I can repair it. If the broken link check only
shows up 1 broken
> link
> - when I repair it - Dreamweaver crashes fully. This
makes lot of fun when
> you
> have 8 single broken links cause this means that
Dreamweaver has to be
> crashed
> 8 times.
I have never had Dreamweaver crash on a broken link check.
Nor can I
reproduce that in a test I just performed.
> 3. (STRG F8) If I want to repair the links only of a
specific tree or
> files -
> the whole project is being changed and not only the
selected.
I assume you have use "Selected Folders" for this - again, I
cannot
reproduce your finding. Selected folder selections have
always worked as
expected for me.
> 4. (STRG F) If I want to change content only of a
specific tree or files -
> the
> whole project is being changed and not only the
selected.
Again, I cannot reproduce this.
> 5. Problems with other central files ...
Sorry - I don't know what this means.
Murray --- ICQ 71997575
Adobe Community Expert
(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
==================
"Kohlfuerst" <[email protected]> wrote in
message
news:[email protected]...
> @Murray *ACE* thanks for your comment.
>
> OK - let me know how you solve this:
>
> 1. If I want to select one of my over 400 projects - let
me take for
> example
> compaq-at. In Dreamweaver 4, I was pressing the "C"
Button as often until
> I
> reached the project. Now I have to scroll and search
through the 400
> project
> bunch.
>
> 2. (STRG F8) If I repair the broken Links of a project
and I get a wrong
> link
> 10 times I can repair it. If the broken link check only
shows up 1 broken
> link
> - when I repair it - Dreamweaver crashes fully. This
makes lot of fun when
> you
> have 8 single broken links cause this means that
Dreamweaver has to be
> crashed
> 8 times.
>
> 3. (STRG F8) If I want to repair the links only of a
specific tree or
> files -
> the whole project is being changed and not only the
selected.
>
> 4. (STRG F) If I want to change content only of a
specific tree or files -
> the
> whole project is being changed and not only the
selected.
>
> 5. Problems with other central files ...
>
> Would you like 50 more ? Use a search engine and you
will find hundreds of
> comments like this.
>
> Thanks, Michael
>

Is there a fix to the scrolling bug in Dreamweaver on Surface Pro 3?

On my SP3 with the latest update of Dreamweaver CC I experience the code window merging lines over each other when scrolling. This is hard to explain but say I pull the scroll bar down the lines of code appear to stay where they are but the line numbers move as expected. This results in say line 30 displaying the contents of line 1. Does that make any sense when reading...??!? Anyway it is more than infuriating! To get over this it sometimes helps to select the text in the window - but not a fullproof solution as it doesn't always work. Any suggestions appreciated.
Thanks.

OK, here goes. Dreamweaver is currently not enabled to support touch devices.
There isn't much that I can share at this moment except that we have registered this request and are looking towards addressing it in the future.
Until then, we request you to continue using Dreamweaver similar to how you have been using it previously on your desktop.
Also feel free to use the Ideas section on this forum to post your request and canvass for it.
Thanks,
Preran

Source Formatting Bug in Dreamweaver CS5.5?

Dreamweaver is formatting my THEAD code unfavorably. It is correctly set in the Source Formatting Settings, but is doing some weird indentation. In the attached image, note the first TH is aligned with the opening THEAD, and the closing THEAD is indented past the last TH. Not pretty. Is there a fix?

The <th></th> tags should be within a set of <tr></tr> tags. Like this...
<table>
     <thead>
          <tr>
               <th></th>
               <th></th>
               <th></th>
          </tr>
     </thead>
     <tbody>
          <tr>
               <td></td>
               <td></td>
               <td></td>
          </tr>
     </tbody>
     <tfoot>
          <tr>
               <td></td>
               <td></td>
               <td></td>
          </tr>
     </tfoot>
</table>
Since the lack of <tr> is technically invalid code, that may be throwing DW off.

Very strange JavaScript bug in Dreamweaver CS6 for Mac

I'm not sure if this works only on a Mac, but it definitely works on any documents containing JavaScript that I create.
Type these characters exactly on a new line or at the end of any line of JS code in Dreamweaver. Works in a <script> tag in an HTML file and in a .js file. Copy/paste also works if you don't feel like typing, but watching the transformation is kinda worth the work.
// Boolean to prevent multiple instances of keystrokes from being recorded
Note what happens to the first / and the end of 'instances'... If you change any of these characters, even add a space at the end, it doesn't work. It has to be that phrase exactly.
Is this just happening to me?

Hmmm.. I'm using 5808. It's nothing serious, just kind of comical.
Here's a screenshot of what happens on my machine. I'll update my Dreamweaver and see if it fixes it.

Image Map Bug in Dreamweaver CS4

I've included a video sample of Dreamweaver's inability to
draw polygonal hotspots in Design view on an image map. The image
is inside an absolutely positioned div tag. After clicking the
first corner, the drawing tool is deactivated. A second click to
create the next corner point selects the underlying image.
In this video sample, I'm using Dreamweaver CS4 on a MacBook
Pro with a 2.4 GHz Intel processor and OS X 10.5.6. The image is
actually a transparent PNG. I'm very careful to click on an opaque
area, but that shouldn't make a difference.
The workaround is to open the image in a blank HTML file,
create the polygonal hotspots there and then copy and paste the
code back into the original HTML page. Adobe should really consider
fixing this.
The video can be viewed here:
http://www.youtube.com/watch?v=tRZGUi53PbI

Good review, David. Thanks for the analysis!
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"David Powers" <[email protected]> wrote in message
news:gqdp6t$70c$[email protected]..
> Murray *ACE* wrote:
>> Or whether it is an issue. For example, the fact
that others are not
>> able to reproduce the problem doesn't bode well in
that regard....
>
> I've just been reading the comments on the CS3 Livedocs
about the same
> problem. Two things stood out: the problem seems to
arise when the image
> is inside a div, and several people said the answer was
to create the
> image map in a new page. Being inside a div should not
present a problem,
> because all my tests have used an image directly inside
a div.
>
> What interested me was that there was no problem
creating an image map in
> a new page. Dreamweaver uses JavaScript in the
background to run a lot of
> its functionality. If there are any errors in the
underlying code, or if
> the code is complex, Dreamweaver can't analyze the page
properly. Another
> possible cause of problems is insufficient memory. If
you have the minimum
> RAM, but other programs are running, this is likely to
cause Dreamweaver
> to fail to function correctly, particularly on large,
complex pages.
>
> So, if Dreamweaver fails to create a hotspot on an
existing page, try it
> on a new page. If it works in the new page, it sounds as
though it's a
> problem with the complexity of the page and/or memory.
If it fails to work
> on the new page, it's back to square one. :(
>
> --
> David Powers
> Adobe Community Expert, Dreamweaver
>
http://foundationphp.com

FTP Bug in dreamweaver 5.5

I just upgraded to DW 5.5 included in my master collection, I'm connecting to FTP no problem, but I'm unable to upload to the ROOT folder only.
I can upload to any other folder, for example, images in the assets, swf in the flash folder etc.
Premission are correct, godaddy hosting upper tier support thought they fixed a rare problem on there end.
Turns out they can upload to the root folder on there end but not on mine through dreamweaver 5.5. FTP
Any else have this problem and know how to fix it? Fillezilla is my only option right now.
Big thanks.

Yet another GoDaddy/DW ftp problem... Since DW works pretty well with everything BUT GoDaddy, I keep saying this is a GoDaddy problem.
They may be the biggest, but that CERTAINLY doesn't mean they're the best.

I found a bug in dreamweaver spry tabs

have a good day to all
i designed a popup menu in fireworks and inserted it in the
header part of the page that contains the spry tabs
if i open the menu then the menu is coming back of the spry
tabs i need help

This is an iPad user to user forum. Apple doesn'y read or respond.
Send feedback to Apple.
http://www.apple.com/feedback/ipad.html
 Cheers, Tom
PS Your English is good!!!!!!!!!!!

Bindings panel bug in Dreamweaver

I'm using a flickr rss feed which uses tags like
<media:thumbnail url="pathtoimage" height="75" width="75" />
When you open the dataset in the bindings tab the xpath
displays properly: "rss/channel/item/media:thumbnail/@url".
However if you expand the dataset it gets confused and when
you try to insert it you get: "{thumbnail/@media:url}" and it
should be "{media:thumbnail/@url}".
Looks as if this happens with semi-colons in the tag name.

BW~Merlin,
You are truly a magician. Spacebar was all it took to make
the selection. It was still invisible, but I was able to proceed
sucessfully with the installation. Many thanks.
Still, I'm sure it's not what the developers intended. I hope
it's something funny about the configuration of my machine and not
a widespread issue!

MuseJSAssert Bug in Dreamweaver?

Similar Messages

Maybe you are looking for