Customer Portal

Get Involved. Join the Conversation.


  • Ernie Turner
    It sounds like you don't have the correct permissions to access that answer. I would try to either contact support and get your permissions changed, or just try searching for 'RightNow Integration' on the Customer Community answers section.
  • cjamerlan

    I am getting a page with the following copy:



    Permission Denied

    This answer is no longer available.


  • Ernie Turner

    Odd, the link still seems to be working fine for me. This is the URL I was trying to link to was



  • cjamerlan
    can you please repost the links to the documentation?  The link in the thread takes me to a blank page.  Thank you!!
  • Leif Wickland
    Dave posted an overview of WebDAV options here. The summary follows.Adobe Dreamweaver’s WebDAV client has significant shortcomings including
    • being unable to use an HTTP proxy,
    • being likely to fail when accessing servers across the Internet due to low latency tolerance,
    • and being slow due to making redundant requests.
    Unfortunately, all versions of Microsoft Windows except Vista SP1 have limitations that should make you think twice before using them as the WebDAV client for Dreamweaver.The best WebDAV solution on Windows is to use a third party WebDAV client, such as NetDrive or WebDrive, which can mount the remote folder as a local drive.Mac OS X’s WebDAV client can also be used to reliably make remote files available to Dreamweaver.Some networks are configured to require the use of HTTP proxies, to deny certain types of HTTP requests, or both. Such configurations either hinder or prohibit WebDAV access.

  • BJ
    Spot on!  Thanks so much for your help :)
  • Ernie Turner

    I was slightly incorrect in my description above about APPPATH. The path in that constant points to either the development folder or the production folder, depending on what mode you are viewing. So yes, if you deploy your pages the APPPATH constant will still be correct because it will point to production.


    CPCORE - Always the path to the 'rightnow' folder. This path does not change between production and development.


    APPPATH - The path to your customizable files. The location (either 'production' or 'development') is different depending on which mode you are viewing the page in. 


    Does that make sense?

  • BJ

    Thankyou - that did the trick in development!


    However when I deploy to production - will this path still be available as you mention it points to the development directory (euf/development)?  It would seem strange to have to change this to work on production?


    Also where can I get a listing of these constants (APPPATH, CPCORE) and what they map to? (sorry for being a newb) :)





  • Ernie Turner

    You need to change the CPCORE define to APPPATH. So it should look like this


    include(APPPATH . "widgets/custom/Input/FieldTypes/Text_view.php");

    The CPCORE define is the path to the 'rightnow' directory (euf/rightnow in WebDAV) and the APPPATH define is the path to the development directory (euf/development in WebDAV). Also, it is important to note that this is only true in the November '08 version and later.


    Hope that helps.


  • Ernie Turner
    When you use PTA to log a contact in, we disable the logout link within Customer Portal. This means that users cannot encounter scenario 1 so you only need to support scenario 2. The documentation for this is within the integration manual which you can find links to here.
  • cjamerlan

    is there documentation on how to code this?i have two scenarios that I need  to address:


    1.  clicking logout from CP will trigger our site's logout

    2.  clicknig logout from our server will trigger CP's logout


    I tried writing a PHP script that will delete the cookies to trigger a logout, but it doesnt allow me as I get an error message about headers already being written.

  • monique perkins

    In general when using PTA most customers just remove or disable logout functionality

    If you are running Nov 08 or later there are code hooks around the logout function that will allow you to write a model that hits your own server at logout. 

  • monique perkins

    Just for others reading this thread....


    Lesson 1:The url was {site}/

    This is a valid url for accessing a report but.....

    NEVER NEVER NEVER put the report id (r_id) in the url unless
    you are going to compare it against a hardcoded value later.  Anyone
    trying to hack your site will be able to get any report and thus any data from
    your database


    Lesson 2:

    if you are in Aug 08 you will need to add 


    $this->config->set_item('parm_segment', 3);



    either in the constructor of ajaxCustom or in the start of
    the function

    This is fixed in later versions


    Lesson 3:

    The correct calls for getting report data from a custom
    controller are

    $reportid = 166; // or other hardcoded value

    // filters is passed by reference. It should be null or an empty array

    // don't put anything else in it. This call sets it correctly for the
    // report model

    setFiltersFromUrl($reportid, $filters);
    $r_tok = create_token($reportid); // for Aug 08
    $r_tok = createToken($reportid); // for Nov 08 and later
    $results = $this->Report_model->getDataHTML($reportid, $r_tok, $filters, $format);
    echo json_encode($results);

  • Outspark
    Monique... thanks so much for your help... I was able to get things working! :D
  • Outspark
    Hi Monique... strangely, I am not seeing a MYSEC_LI_ERR_ENABLED in the control panel.... could you point me in the right direction?