Home › Toolset Professional Support › [Resolved] Toolset Messaging – Messages sent by other users showing in other users' inboxes
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|
8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
Tagged: How to build a site with Toolset
This topic contains 4 replies, has 3 voices.
Last updated by simonM-5 4 years, 8 months ago.
Assisted by: Christian Cox.
Hi Support
I have noticed that when logging in as other Nannies or Families, messages unrelated to those parties are showing in the Inbox.
For example, using the same test case which we previously made for the support ticket
https://toolset.com/forums/topic/toolset-messaging-system-unable-to-read-messages-80-characters-in-length/
** see support note 1 **
I am using following code for Inbox:
INBOX:
{!{wpv-view name='my-messages-received' orderby='date' order='desc' info="{!{wpv-current-user info='id'}!}"}!}
For Outbox the Query Filter in the view "Messages sent" = "Post author is the same as the logged in user" seems to work adequately.
I tried to redeclare the View within the Inbox Page and use the Query filters option to use [wpv-current-user info='id'], however it is complaining that that is not a valid number.
My understanding is that the code "{!{wpv-current-user info='id'}!}" should evaluate to a number (user ID) and that the view should be filtered on the shortcode attribute info as in the screenshot.
Thanks and best regards
Simon
Where is the message visible?
Can you add links to where we see the issue in the front end, and where edit this all in the backend?
Links to the Views, Content Templates and other elements also are of good help to locate the issue quickly.
It sounds like the View filter is not filtering the proper messages by nanny it belongs to.
Hi Beda
The messages are visible after logging in with the logins provided and clicking the Messaging icon in the menu bar.
(Can you please hide/remove the passwords from the previous post?)
I am using the same test case as we did in our previous ticket with you, where Family6 and Nanny6 sent messages to each other.
However Nanny2 should never see messages from Nanny6 or messages sent by Family6 to Nanny6.
Frontend:
hidden link
hidden link
hidden link
Backend - I'm just using the standard pages/views etc provided by the Toolset Messaging Module and have made minor styling changes, as indicated in our previous ticket with you:
Views:
Messages received: hidden link
Messages sent: hidden link
Related messages: hidden link
Content template:
Message - single: hidden link
Furthermore, I have just noticed that those test messages from our previous ticket are also visible when not logged in, this should not be the case either, as it should be excluded by the Toolset Access code provided in the ititial setup files for the Toolset Messaging module:
[toolset_access role="Guest" operator="deny"] [/toolset_access]
I included screenshots in my previous post of the filtering details, which I am presuming is not being applied at runtime.
Kind regards
Simon
My understanding is that the code "{!{wpv-current-user info='id'}!}" should evaluate to a number (user ID) and that the view should be filtered on the shortcode attribute info as in the screenshot.
Hi, I don't think you can apply the current user shortcode in the popup like you showed in your first comment here, you must manually add that shortcode attribute after you insert the shortcode. In the Inbox Tab content editor, I've added that shortcode attribute and now I don't see the two messages when logged in as Nanny2. I also removed the login credentials above as requested.
Can you check again?
My issue is resolved now. Thank you!