200 X-Frame-Options: SAMEORIGIN Content-Security-Policy: frame-ancestors 'self'; X-UA-Compatible: IE=Edge X-XSS-Protection: 1; mode=block X-Content-Type-Options: nosniff X-Telligent-Evolution: 12.x Pragma: no-cache Connection: close Accept-Ranges: bytes Cache-Control: no-store, no-cache, max-age=0 Date: Fri, 29 Nov 2024 22:38:42 GMT ETag: "0x8DD02F56CCD7D1F" Set-Cookie: .te.csrf=d9E54z7uKKUzAD0Em5JR0EorE8o2hKkgswtavzmkcug; path=/; secure; SameSite=Lax Set-Cookie: .te.auth=RTMcVkVcvlO5QXfTP%2bb9JpRM9zL4WFhETywawGiM3ukcdUffWDboZ4EcjlWPUEh5%2fXJPueqVKhkzxpHtsYO3K7jX5d26e53H%2bDiuODaq5ZtxivYqDcaAhzIKxyOOuUCk7qMld22mQR6OvuJOGai5GnJYWeGsMv5IKxcJ6eoZ7B4uXZeMwc4aBEpYHVerYlQwaSvpIS4XLXPQ1x5PjEjezYsJOpBw%2bCTIyo09xFC0PnGNESMTHytk2c1I52CjUPN6nxjrYsijWu5g0pxFI51%2b%2bQ%3d%3d; path=/; secure; HttpOnly; SameSite=Lax Set-Cookie: e14Guest=1; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Country=NL; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Language=en; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14TimeZone=Etc/UTC; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Server-Timing: cdn-cache; desc=MISS Server-Timing: edge; dur=5 Server-Timing: origin; dur=18 Server-Timing: ak_p; desc="1732919922503_34849654_146968211_2290_8804_8_11_-";dur=1 Strict-Transport-Security: max-age=86400 ; includeSubDomains ; preload #set ($UserId = $core_v2_user.Accessing.Id) #set ($Roles = $core_v2_utility.MakeList('Moderators', 'Almost Admins', 'Administrators')) #set ($IsAdminLike = $e14_utils.IsUserInRoleOrAdmin($UserId, $Roles)) #if($IsAdminLike == 'False') #end
Actions
Forum Thread Details
  • State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 12 subscribers
  • Views 319 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

No wider visibility to comments on old blogs

jc2048

I've just had a comment on one of my old blogs. This one:

/members-area/b/blog/posts/experimenting-with-mosfets-total-gate-charge

No notification for me, though. No evidence of it in the content stream. Invisible to anyone else who might be inclined to help the person with their question.

I only knew because the person took the trouble to draw my attention to it through the messaging system.

Thought I'd draw your attention to this just in case you weren't aware, though you probably realise this already and accept it.

  • +1

    Hi  ,

    It's a total frustration that I sympathise with. Verint inherently won't notify you about it unless you opt-in to notifications on your content, and there's no easy way to auto opt-in to all content, or opt out of all content either.

    It's especially difficult in the Community where we have a lot of older content, too. It is frustratingly not on Verint's list of priorities.

    Verint as a platform treats comments and content updates completely separately, which is why its widgets for listing content does not consider comments as activity or updates to that content. 

    I also have a few development tickets open in the queue with the Community dev' team to fix activity widgets to expose activity on the site, and I repeatedly take this up with Verint and its community too.

  • 0 in reply to cstanton

    Would it not be possible to create a script that goes through content and automatically sets the opt-in for notifications to the blog for the author, where that is not already set?  As a possible extension, to opt-in for the author and any commenter as well.

    I guess that might opt-in someone to content that they had specifically opted out of unless there is a way to tell that was done.  I should imagine there isn't many instances of that such that an affected user might have to go back to redo the opt-out.

  • 0 in reply to Andrew J
    Andrew J said:
    Would it not be possible to create a script that goes through content and automatically sets the opt-in for notifications to the blog for the author, where that is not already set?

    I have raised the question of adding that functionality. It raises further considerations:

    - Where would this feature live? What would the interface look like?

    - What impact might it have on the performance of the website if you have a lot of content?

    - This doesn't affect content created since clicking 'the button', what do we do about that and how do we communicate that to the user?

    Andrew J said:
    As a possible extension, to opt-in for the author and any commenter as well.

    That would upset a lot of people.

    Andrew J said:
    I guess that might opt-in someone to content that they had specifically opted out of unless there is a way to tell that was done.  I should imagine there isn't many instances of that such that an affected user might have to go back to redo the opt-out.

    This happens a bit with forums at present.

    If you comment in a forum or post in a group or forum, you automatically join the group.

    When you join a group, you're automatically subscribed to notifications about forums and their posts.

    If you comment in the forum, you may become resubscribed to notifications even if you've manually turned them off.

    This then upsets and confuses people.

    For some reason Verint only has this functionality of auto subscribing on forums, not on any other content types.

  • 0 in reply to cstanton

    I was thinking it would be a one-off scripted job to attach an opt-in to the old content (that transferred from the old system), it wouldn't need to be a constantly running thing as the functionality in place works for content created in Verint.  No UI, it's just a one-time script.  It could be done in batches over a number of days.

  • 0 in reply to Andrew J
    Andrew J said:
    I was thinking it would be a one-off scripted job to attach an opt-in to the old content (that transferred from the old system), it wouldn't need to be a constantly running thing as the functionality in place works for content created in Verint.  No UI, it's just a one-time script.  It could be done in batches over a number of days.

    I could request this from the development team for a particular user, say for yourself.

    I would not want to run this for every user by default. It seems to me it would be more valuable as an option for members to run if they want to, from say their user profile, and then it would complete over time to not have a major impact on the server. 

  • 0 in reply to cstanton

    That would work and I'd be happy to test it if it would help.