2 Replies Latest reply: Aug 24, 2012 4:51 PM by PhilipChaseWilson RSS

    MuseJSAssert: Error calling selector function:ReferenceError:WebPro is not defined

    PhilipChaseWilson Community Member
    PhilipChaseWilson Aug 24, 2012 3:29 PM

      Hello Adobe Staff,

       

      Similar to post http://forums.adobe.com/message/4639911#4639911 I’m having trouble after updating Muse yesterday. The only change to the website was adding a single character; the letter “S”.

      Now everyone who views the site on Chrome, Safari, IE all see the above titled error, and when clicking OK, the captions on the slideshow are all visible layered on top of each other, with the last image showing.

      We host our website and use TortoiseSVN to keep a repro of all updates.

      While uploading the website I noticed nearly all files were changed, and Tortoise only updated the changed files. After seeing the error, it looked like a slideshow code issue, and since that was one of the enhancements included in the upgrade, I removed the old slideshow and rebuilt it in the event the code change was the cause.

       

      All the image files for the slideshow are present in the images folder.

       

      After clearing all cache and browsing histories, retested and it did not fix the problem.

      Our web address is www.qualnetics.com

      I have reverted the website back to before the problems, and the homepage loads without issue.

      I really love Muse, and would like to see the error of my ways so I can move on to other web projects using the new and improved Muse.

       

      Any ideas?

       

      Thanks,

      Philip Wilson 

      • 1779 Views
      • Tags:
        • 1. Re: MuseJSAssert: Error calling selector function:ReferenceError:WebPro is not defined
          adobelance Employee Hosts
          adobelance Aug 24, 2012 4:13 PM (in response to PhilipChaseWilson)

          This error would occur if not all the files for the site were uploaded.

           

          The 2.0 update includes numerous improvements in the generated HTML, CSS and JavaScript, so while you may have directly changed only certain pages, if you're using an external FTP client all the exported files and folders need to be uploaded. There are new javascript files exported by Muse 2.0 which were not exported by Muse 1.0, so be sure you upload the new files too.

           

          You might try using the Muse 2.0 FTP upload feature. The new built-in FTP upload feature automatically only generates and uploads files that have changed since the previous upload.


          You could also try publishing your muse site to a new BusinessCatalyst trial site, just to verify that it does work correctly when all the files are uploaded.

          • 2. Re: MuseJSAssert: Error calling selector function:ReferenceError:WebPro is not defined
            PhilipChaseWilson Community Member
            PhilipChaseWilson Aug 24, 2012 4:51 PM (in response to adobelance)

            Hello Adobelance,

             

            I'm completely amazed at the response time here.

            44 minutes after my post I had an answer. On a Friday afternoon no less.

            You guys rock!

             

            When I looked into uncopied files, I was looking at images. Upon further investigation, there were a few scripts not copied over.

            Since we just commit the files to the repo on the local side, then update the same folder on the server side, I didn't catch the new files Muse created that needed to be added to the repo upload.

            Once that was done, everything worked great.

             

            Reading over the latest release notes for V2 is akin to a designers Christmas list and nearly everything I wanted was included in the V2 release.

            Thanks.

             

            Philip Wilson