Customer Portal

Get Involved. Join the Conversation.

Topic

    domn
    Switching Between Interfaces in DW ProblemAnswered
    Topic posted February 25, 2009 by domn Bronze Medal: 1,250+ Points, last edited October 29, 2011 
    1189 Views, 8 Comments
    Title:
    Switching Between Interfaces in DW Problem
    Content:

    We have two interfaces and I've had no problem creating and publishing the second in DW. The problem I'm having is switching between the interfaces in DW. When I attempt to switch following the instructions on page 70 on the Nov 08 Customer Portal manual I get the follwoing error.

     

    error.jpg

     

     

     

     

     

     

     

     

     

     

     

     

    I've tried going directly into the Adobe Ext manager and removing the extension, reinstalling and I contnue to get the same message.

     

    The only way I can succesfully switch between interfaces is to close DW, unistall the extension directly in the Ext Manager, open the desired interface of the RN application and re-install the extension from there.

     

    Any idea as to why switching won't work as described on page 70?

    Best Comment

    Leif Wickland
    Domenic,

    I forgot that I'd already fixed that bug in Feb '09, which I believe is the first version in which we officially support CS4. Adobe broke the file download API, MMHttp.getFileCallback(), in Dreamweaver CS4, so I needed find another way to download the extension. Sorry for the hassle. I have proposed that the fix be included in service packs for older RightNow versions.

    You're already discovered a pretty good workaround. You should be able to skip the step of uninstalling the old extension before installing the new one. The Extension Manager should perform the uninstall implicitly when installing the new version.

    Please let me know if I've gotten something wrong.

    Thanks,

    Leif

    Comment

     

    • Leif Wickland
      Domn,

      Which version of Dreamweaver and RightNow are you using?

      Thanks,

      Leif Wickland
      Software Developer
    • domn

      DW CS4 and Nov 08.

    • Leif Wickland
      Domenic,

      I forgot that I'd already fixed that bug in Feb '09, which I believe is the first version in which we officially support CS4. Adobe broke the file download API, MMHttp.getFileCallback(), in Dreamweaver CS4, so I needed find another way to download the extension. Sorry for the hassle. I have proposed that the fix be included in service packs for older RightNow versions.

      You're already discovered a pretty good workaround. You should be able to skip the step of uninstalling the old extension before installing the new one. The Extension Manager should perform the uninstall implicitly when installing the new version.

      Please let me know if I've gotten something wrong.

      Thanks,

      Leif

    • domn

      Ok, thanks for the info. I wanted to ensure it wasn't something I was doing wrong. Probably some time before we go to Feb 09 since we're scheduled to go to Nov 08 on Monday so it would be great to see the fix implemented for older versions.

       

      Thanks again.

    • domn

      I'm having another problem with the extensions.

       

      When I try and re-download the extension for our english site I'm getting errors. The error from the RightNow Admin console is

       

      'An error occured when downloading the extension. You can download the extension from <URL>

      "The remote server returned an error.(500) Internal Server error."

       

      When I attempt downloading the extension directly from the Portal admin at ci/designer, I'm presented with a page full of code and the extension does not download.

       

       

      I have no problems downloading and installing the extension for our french interface.  This poses a significant problem as we're upgraing to Nov 08 at 6AM EST tommorrow and I still need to make some changes to the english interface. Hopefully this is a problem related to the PC I'm using and my work PC won't have the same issue?

    • Leif Wickland
      Domenic,

      Usually an error like that indicates that there's a problem in one of the custom widgets, often in a controller. If you go back to /ci/designer/download, get a pageful of code, and scroll to the bottom of the page, you should find an error message in the jumble. Usually these errors are caused by an invalid attribute data type of a syntax error.

      Alternatively, via private message, send me a URL and credentials and I'll figure out the problem for you.

      In May '09, such errors will be reported much more clearly.

    • domn

      Thanks Leif

       

      I actually worked this out this morning with Pat Lindman since it affected our upgrade.

       

      But hopefully you can answer something for me regarding custom widgets since I plan on creating more.

       

      If a widget has 3 components, view, controller and logic. Do all 3 have to be copied to the custom folder or only the view? Do all 3 have to be renamed? Do the folders they reside in also have to be renamed? The one custom widget I do have working correctly (MyStuffNav) does not have a controller or logic file. I run into problems when I attempt to edit widgets with these files.

       

      Going by the 'Working with Widgets" section of the Nov 08 portal manual, all I have to copy is the view.php. What I did with the MyStuffNav widget is rename the folder it resides in under Custom to MtStuffNavCustom.

       

      When I try with the same with either the MenuFilterdropdown or LoginForm widget I get an error.

       

      I'll sent a PM with the info.

       

      Thanks

    • Leif Wickland
      Domenic,

      I'm sorry you ran into troubles when you cut over. I'm really glad Pat could help you.

      When you create a custom widget, you only have to copy the view.php. The view contains references to the other files that it will use, such as controller, JavaScript, and CSS. If you copy a standard widget view and do not modify those attributes in the <rn:meta> tag, your custom widget will continue to use the standard components beside the view.

      The files comprising the widget (e.g, view.php, controller.php, and logic.js) must have the standard names for the system to find the files. If you created widgets/custom/mine/mine.php, it would not be a widget; a view.php is required.

      A widget gets its name from the folder that its view.php is in.

      You can name custom widgets the same as a standard widget, but unfortunately there are a few complications with doing so.

      1. You cannot have two different widgets with the same controller name on a single page. For example, if you copied widgets/standard/utils/RNTLogo to widgets/custom/mine/RNTLogo, modified the custom one to use a custom controller called RNTLogo, and tried to stick both on the same page, you'd receive an error.
      2. In May '09 I've fixed a bug with the Dreamweaver extension related to this. In previous versions if two widgets used different controllers with the same name (as in my example above), all widgets using controllers with those names would get the insert widget dialog of one of those controllers.

      So, while it is possible to have custom widgets with the same name as a standard widget, it's probably not advisable until May '09.

      Please let me know if I haven't answered your questions or if my answers are unclear.