Customer Portal

Get Involved. Join the Conversation.

Comments

  • Ernie Turner

    The directory structure changed quite a bit between Aug '08 and Nov '08. I would recommend reading the Upgrade Guide for Nov. 08.

     

    In short, everything that you have privileges to edit is now located under /euf/development and everything you cannot edit (e.g. standard widgets/models) is located under /euf/rightnow.

  • Leif Wickland
    Jim,

    I suggest that you take a look at the standard/display/SlaDiv widget. Specifically, SlaDiv may allow you to show the information you want conditionally. Even if it doesn't meet your needs, looking at the controller will likely show you how to get the data you need.

    Please let me know how that works for you.

    Thanks,

    Leif Wickland
    Software Developer
  • domn

    Thanks Chris

     

    I had no problem copying and editing that particular widget. But I'm trying to do the same with 3 others. All are under standard/search

     

    MenuFilterDropdown

    KeywordText

    Searchbutton

     

    I've copied the 3 files for each into the custom folder, renamed and 'put' all of them. But once I change the folder structure to reflect custom/ I'm getting the following error on the page for each

     

    Widget: custom/search/KeywordTextCustom (Translation failed on the server (500))

    Widget: custom/search/MenuFilterDropdownCustom (Translation failed on the server (500))

    Widget: custom/search/SearchButtonCustom (Translation failed on the server (500))

     

    Is there something else I'm missing here?

     

     

     

     

  • Leif Wickland
    Dustin,

    In a page, you should be able to use $this->page to get "home" or the like. (Donning lawyer cap...) Admittedly, that's undocumented, so it could potentially change.

    Alternatively, you could use the $_SERVER['REQUEST_URI'] to get the URL as requested by the browser. That is documented although more complicated. You could also use $this->uri->segment(3), which is a built in part of CodeIgniter.

    Leif
  • DustinTuft

    That makes since, I have not yet attempted to idnetify what page is being servered, is there an object that tells me where I am at?

     

    Thanks

  • Leif Wickland
    Dustin,

    It wouldn't be required to have /app/home produce a redirect for not-logged-in users. If you wanted to serve a page to those users without a redirect, you'd need /app/home to not use a template or move the redirect logic to the top of its template and only redirect conditionally if the page being served was the home page.

    Leif


  • DustinTuft

    So just so I understand, I need to have my home page be blank, and use the model to decide where to redirect to? So even my current defualt not logged in page would be part of the model return to routing code?

     

    Thanks

  • Leif Wickland
    Dustin,

    It sounds like you want to send an HTTP redirect header based on the SLA model. Potentially the best route to go is to add another method to your SLA model that translates the SLA level into the correct home page.

    Then you could change the home.php to consist of only something like:

    <?php

    $this->load->model('custom/Sla_model');

    $newUrl = $this->Sla_model->getHomePageUrl() . sessionParm();

    header("Location: $newUrl");

    exit("Redirecting to $newUrl...");

    ?>

    <html><head></head><body></body></html>

    You probably wouldn't want this page to have a template.  The minimal HTML document is required to satisfy our the deploy process.  The sessionParm() is recommended to ensure that you are not double billed for requests if visitors have cookies turned off.

     

    This seemed to work in the quick test that I ran.

     

    Additionally, you'll probably want to make sure that you have the

    <rn:meta clickstream='home'/>

     

    tag in your alternate home pages so that stats are collected correctly. 

     

    Please let me know how this works.

     

    Thanks,

     

    Leif Wickland

    Software Developer

  • DustinTuft

    We do the same thing in our KB, but not for all answers. We use a custom answer field that controls the out put type, then based on that the end user pages will change out the titles, or remove the question field all together.

     

    I supect you could remove the question field from the Admin console by editing the Workspace for it, but you still need to deal with the end user pages so the end user will see the article as you would like it to be display. How ever, I have not found a way to alter the Admin console preview function. So that will still show the RNT style Question and Answer.

  • Ernie Turner
    I think you probably want to post in the Customer Forum, maybe under 'General Product Discussion'.
  • bbenscoter

    No, not solved.

     

    I guess I'm just in the wrong place.  Where does one post questions that relate to just the RNT application, and not a specific feature such as Customer Portal?

  • 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.

  • monique perkins

    PTA for classic pages has not changed.  When you switch to CP you will need to reformat the url you are using for pta to the new enduser url and parameters.  The encoded string stays the same.

     

    If you are concerned you should test your pta integration on your upgrade test site.

  • 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

    DW CS4 and Nov 08.