You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems we're having problems where when we integrate a message into a thread it does not retain the original date order in the thread. This is very problematic as we have some very badly behaved users that frequently need thread integration (and they are in a position where we can't force them to improve their behavior)... We need the plugin to somehow retain message metadata and integrate at the time-appropriate point in threads, please.
The text was updated successfully, but these errors were encountered:
@ylluminate can you confirm that when you say "integrate" you are referring to attaching messages to an existing thread? If so, the message metadata and time should be correct, but will require a channel reload.
I covered this behavior in more detail in the README FAQ.
Wranglered messages ar marked a "unread" od "new" which is annoying to users.
The timestamp is NOT preserverd which leads to old messages mix up the thread sequence (sorted by date/time)
I know, that the actual implementation is based on creating a new post. It simply would be enough, the give this post / thread the same timestamp as the original one. And mark it as read for all users.
It seems we're having problems where when we integrate a message into a thread it does not retain the original date order in the thread. This is very problematic as we have some very badly behaved users that frequently need thread integration (and they are in a position where we can't force them to improve their behavior)... We need the plugin to somehow retain message metadata and integrate at the time-appropriate point in threads, please.
The text was updated successfully, but these errors were encountered: