Reply "Collision detection"

PerBonomi

Hi! :-) thanks for sharing this. It's been one of our popular demands so we may use your code and test it out. It might come in handy specifically for expert days where we have many folks responding to customer question in the same time so chances of someone responding to a message that someone else is already working on, increases.

Just a quick question. Am I supposed to gather anything from your screenshot? I am not exactly sure what I am supposed to see or what should trigger me.

Thanks!
Wendy

Hi Wendy_S it's very subtle, I'll admit. If you look at the top, I logged in and hit reply on a topic. Then I also logged in with a different account and hit reply. Now, as that other user, I see that user Per hit reply 10 seconds ago.

Hi PerBonomi,

In your component code, you are calling the POST call to clear fields on mouseenter. It might possible, the page redirect (on button click) can happen before success of post call since both activities are asynchronous. This is why custom field is not clearing and displaying the user details on the other user page eventhough user not replying.

Call the post call on submit and wait untill endpoint returns success. Then perform form default action. This way the data for sure will get clear from custom field.

Example code:

$('input.lia-button-Submit-action, input.lia-button-Cancel-action').bind('click', function(e) {
e.preventDefault();
var formEle = $(this).parents().find('.MessageEditorForm');
$.post('Endpoint URL?id=${msg_id}',function(){
$(formEle).submit();
});
});

Hope this helps!

Thanks,

Phani

Hi PerBonomi,

Since it is form i do not think it will work. Yes you are right, we need to split the function to make cancel to redirct to previous page from code.

$('input.lia-button-Cancel-action').bind('click', function(e) {
e.preventDefault();
$.post('Endpoint URL?id=${msg_id}',function(){
window.location = "${http.request.referrer}"
;
});
});

Thanks,

Phani

hey phani. I tried doing what you suggested. I even tried doing a proper Ajax call and waiting for the .done, but the endpoint call isn't always successful. I went with the hover because Lithium forms don't like getting their defaults prevented. For now, this workaround works mostly, so I'll just wait for the Lithium implementation before sinking more time into this :)

Hi PerBonomi,

Great contribution! As Wendy_S mentioned, our users have been asking for something like this for a long time. 

I didn't realized I was having the same issue where the users were not deleted from the list. After some testing and google I *think* the issue is the form is interferring with the http request to the endpoint. 

I might have accidentally fixed the issue while using the .unload() event to call the endpoint. I was trying toremove the user when they click on a link or type a new URL directly on the address bar too. Here's the code.

<@liaAddScript>
		$( window ).unload(function() {			
			
			var url='${community.urls.communityPrefix}/plugins/custom/hp/${community.id}/collision-check-endpoint?id=${msg_id}';
    		$.ajax({        
    			url:url
    		});    		

		});
	</@liaAddScript>

Hope that helps!

One more quick comment.

I noticed that, in our communities, I was getting an "permission denied" error when replying to a reply -not the original question-, probably because the custom field was set up for just for first message in a thread. I'm not 100% sure.

Anyways, we want to keep a single list for the whole thread, regardless of whether the user replied to the original question or a reply, so I tweaked the code a little.

I replaced these two lines

<#assign msg_non_unique_id = http.request.url?substring(http.request.url?last_index_of("/") + 1, http.request.url?length)/>
<#assign msg_id = rest("/boards/id/${coreNode.id}/messages/id/${msg_non_unique_id}/id").value/>

With this:

<#assign msg_id = env.context.message.discussion.topicMessage.uniqueId />

(this gets the unique id for the first message on the thread, so no need to use another rest call)

Just an FYI in case you're having the same issue on your communities.

Regards!

PerBonomi

I want to say THANK YOU once more for sharing the code. fuenteso did a great job in making it a (beta) functionality in our communities and we're testing it as we speak.

This is what it looks like :-)

Thanks again! so so much! I will hug you next time we meet.