-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue With Same Inbox Subject as Multiple Objects #104
Comments
To show messages as threads, try to filter like this:
All messages where parent_msg is not null are replys in a thread. You might need to replace the inbox_for filter with something like filter(Q(sender=user) || Q(recipient=user)) so that outgoing threads are also displayed. |
@arneb, I tried this.. but it's not working fine. When I check my inbox [/messages/inbox] as the sender, no message will show up. But when I check as the receiver, I will see the message in my inbox and it won't show up multiple times. It's working for the receiver and not the sender. What am I missing? |
did you replace the inbox_for filter with two or'ed Q queries? with inbox_for it will only work for the receiver, because inbox_for does a receiver=user filter. you want receiver=user || sender=user |
@arneb Thanks! Now working. I did this.
Another issue I have is how to make 1. a message that has not been read and replied have the em tag. 2, message that has been replied and not read have the em tag. So I did this.
But not working! I'm on Django 1.11 . What am I missing? |
Messages in the inbox with the same subject keeps showing up more than once depending on the number of times a sender and the recipient receives messages. I want a situation whereby messages with the same subject will only show up once in the inbox and not twice or thrice. Kindly check the attached image for what I mean.
[url=https://ibb.co/b3AGQ7][img]https://thumb.ibb.co/b3AGQ7/Screenshot_35.png[/img][/url]
I've looked into the code and I did this
But still not working.
The text was updated successfully, but these errors were encountered: