Home › Forums › WordPress Plugins › digest adding additional threads
- This topic has 2 replies, 2 voices, and was last updated 5 years, 3 months ago by vinny.
December 27, 2017 at 2:15 pm #6541Julia ReyesParticipant
Having the following issue with the digest emails.
User has digests enables, notification preferences set to “Only allow subscriptions.” Is subscribed to one topic for replies and one forum for new topics (in different forums).
Expectation: receive a digest with link to replies to one topic and any new topics in other forum.
Test 1 (ok): create new topics and new reply for what user is subscribed to.
Result: Digest contains only includes the new topic and new reply as suspected.
Test 2 (incorrect): create new topics and new reply for what user is subscribed to. Also create a new topic in the same forum where the user is subscribed to new replies only on an existing topic.
Result: Digest contains the new topic, new reply (as subscribed), but also (incorrect), the new topic in the forum where he has a reply subscription only.
Test 3:(ok) Create new topics and new reply for what user is subscribed to. Also create a new reply in the same forum where the user is subscribed to new topics only.
Result: Digest contains the new topic, new reply (as subscribed) only.
In the attachment you can see the results of the database before sending situation 2’s digest out. Note the database entries are correct for user 13. He has only 2 entries, but he also receives the first entry in his digest which is incorrect. (He does h
Attachments:You must be logged in to view attached files.
December 27, 2017 at 2:19 pm #6543Julia ReyesParticipant
Couple more notes – may or may not be helpful.
This situation only happens when there is a topic entry in the digest table that the user is allowed to access.
Meaning, for one, I tried the “reverse” of this. I.e., if the user is subscribed to a forum, will she get all replies even if not subscribed and they are in the database for another user? Answer is no (which is correct).
February 8, 2018 at 9:30 am #6752vinnyKeymaster
This was happening due to aggressive caching. It was fixed in version 1.12.
- You must be logged in to reply to this topic.