Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Error opening Alert messages.Error opening Alert messages.
Previous
 
Next
New Post
6/21/2015 5:17 PM
 
I have been able to fix this issue. There was bad data. I could see where it was but not what caused it. Deleted the offending records.
 
New Post
6/21/2015 10:17 PM
 

Spoke too soon. Or more to the point didn't make a test post.

Same thing happened. Sender alert flag pops up on sending a PM. And the Recipient gets the message "The message no longer has any valid recipents so replies have been disabled." I can now see what's happening. In the CoreMessaging_Messages table the MessageID should also be written to the ConversationID column ie. MessageID 1234 and ConversationID 1234 The Conversation ID is being written 0. If I UPDATE the ConversationID 1234 it all works.

 Is only happening on the opening post of a new Conversation, replies are written correctly.

 

Question is. How to fix it?

 
New Post
11/8/2015 2:01 PM
 
I realize this is slightly dated and I am guessing you found your fix but since I just bumped into the same issue on an installation I wanted to post a solution.

Check the CoreMessaging_SaveMessage stored procedure.

My proc had a check at line 60 that I did not see in the repo. I am not sure why my installation had it... I changed the <0 to <=0 which fixed the issue but I the repo shows the check is removed entirely which is probably the right fix. Not sure why the proc was not in sync with repo...

IF IsNull(@ConversationID, -1) < 0 -- no reply
UPDATE dbo.[CoreMessaging_Messages]
SET [ConversationID] = @MessageID
WHERE [MessageID] = @MessageID


You can compare to the repo version here:
https://github.com/dnnsoftware/Dnn.Pl...

The proc is built around line 1858 with the isNull check removed @ line 1903

If your installation has the isNull check then every initial insert has a 0 as it's ConversationId and cannot be replied to.
 
New Post
11/8/2015 4:14 PM
 

 Monster

Topic might be a little outdated but I have not found the solution. So thanks for the fix.

Checked the SP 

           IF @ConversationID Is Null -- no reply
                UPDATE dbo.[ald_CoreMessaging_Messages]
                   SET [ConversationID] = @MessageID
                 WHERE [MessageID] = @MessageID

Modified to your fix

            IF IsNull(@ConversationID, -1) <=0 -- no reply
                UPDATE dbo.[ald_CoreMessaging_Messages]
                   SET [ConversationID] = @MessageID
                 WHERE [MessageID] = @MessageID

 and thanks again, it works. One wonders how these bugs creep into the code when so few have the issue.  " IF @ConversationID Is Null -- no reply" even if Is Null was IsNull was never going to work.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Error opening Alert messages.Error opening Alert messages.


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out