Loading...

qDiscussionView Object expected error

qDiscussionView Object expected error

  • This topic is empty.
Viewing 3 reply threads
  • Author
    Posts
    • #5076
      Anonymous
      Anonymous
      Participant

      Try to clear your browser's cache and reload the page.

    • #5077
      Anonymous
      Anonymous
      Participant

      This is solved.  I misunderstood the directions and assumed the web.config changes were only necessary if you installed the webpart manually. 

    • #4173
      Anonymous
      Anonymous
      Participant

      I’ve installed the qDiscussionView webpart for Moss 2007 and activated it.   After configuring it I’m able to see the discussion view but when attemtping to expand a thread,  I get a javascript error.  This happens in Firefox 8 and Internet explorer 8.  I did an iisreset just to be sure the webpart was loaded correctly.  I included the error and the source at line 600.

      Webpage error details

      User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; User-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; http://bsalsa.com) ; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; Tablet PC 2.0)

      Timestamp: Thu, 8 Mar 2012 19:21:53 UTC

      Message: Object expected

      Line: 600

      Char: 1

      Code: 0

      URI: https://[site.com]/IDMS/default.aspx

      <td id=“ctl00_m_g_0d5827fe_229e_4b2e_9135_34effeccb6e5_ctl24_U” valign=“top”><table id=“ctl00_m_g_0d5827fe_229e_4b2e_9135_34effeccb6e5_ctl24_D” onclick=“aspxTLClick(‘ctl00_m_g_0d5827fe_229e_4b2e_9135_34effeccb6e5_ctl24’,event)” ondblclick=“aspxTLDblClick(‘ctl00_m_g_0d5827fe_229e_4b2e_9135_34effeccb6e5_ctl24’,event)” cellspacing=“0” border=“0” style=“width:100%;”>

    • #6301
      Anonymous
      Anonymous
      Participant

      Hi Darin,

        I'm glad to hear that.

      Please mark your question as answered so other people can benefit.

      Thanks,

Viewing 3 reply threads

You must be logged in to reply to this topic.