[XB] Keyword Alerts: Post Alerts & Email Digests

[XB] Keyword Alerts: Post Alerts & Email Digests [Paid] 1.0.6

No permission to buy ($45.00)
Overview Updates (9) Reviews (2) History Discussion
Painbaker

Painbaker

Well-known member
Licensed customer
Painbaker submitted a new resource:

[XB] Keyword Alerts - Notify users when new content matches their defined keywords

Notify users when new content matches their defined keywords.

This add-on scans content and triggers alerts based on configured keyword rules, with a focus on accuracy and performance.

Features:​

  • 🔑 Multiple Keywords per Alert: Define several keywords within a single alert.
  • 📏 Keyword Length Limits: Configure minimum and maximum keyword length.
  • 🎯 Flexible Match Types: Support for word, exact, and partial matching.
  • 🧹 BB Code...
Click to expand...

Read more about this resource...
 
Do alerts generated by XB Keyword Alerts invoke XenForo web push for logged-out users, and does every newly matching thread create a push even when an earlier keyword alert remains unread?
 
elsparkodiablo said:
Do alerts generated by XB Keyword Alerts invoke XenForo web push for logged-out users, and does every newly matching thread create a push even when an earlier keyword alert remains unread?
Click to expand...
Yes. Logged-out users can receive XenForo web push if push is enabled
 
Thank you. Will every newly matching thread generate a separate web-push notification even if the user has not visited the forum or marked an earlier keyword alert as read?
 
elsparkodiablo said:
Thank you. Will every newly matching thread generate a separate web-push notification even if the user has not visited the forum or marked an earlier keyword alert as read?
Click to expand...
Yes, it does not count whether the content has been viewed or not
Instead, you can set a pause before sending the notifications so that they are grouped together (immediately/with a configurable delay in the ACP, once a day, once a week, or once a month)
 
Painbaker updated [XB] Keyword Alerts: Post Alerts & Email Digests with a new update entry:

1.0.5

  • Added unsubscribe links to keyword alert emails, with an option to stop only keyword alert emails.
  • Fixed queue processing for content types without saved rules and prevented logs for alerts that were not delivered.
  • Kept email notifications queued until the mail transport accepts them.
  • Added keyword alerts for XenAddons Sportsbook events, member bets, and comments.
  • Added keyword alerts for XenAddons Pick'em pools and comments.
  • Added keyword alerts for...
Click to expand...

Read the rest of this update entry...
 
I had this bug under 1.0.4 and just updated to 1.0.5. Can you this bug been fixed in 1.0.5?

Bug: Keyword Alerts crashes while processing XFRM resource updates

We’re seeing repeated InvalidArgumentException: Accessed unknown getter 'User' on XFRM:ResourceUpdate errors during the xf:run-jobs background job.

The stack trace points to PB/KeywordAlerts/KeywordAlert/XFRM/ResourceUpdate.php:64, where the handler accesses $resourceUpdate->User. XFRM resource updates do not have a direct User relationship, so processing one can fail.

Could you update the XFRM resource update handler to determine the appropriate content user without assuming that relationship exists? It should also handle updates with no attributable user.
 
Andy.N said:
I had this bug under 1.0.4 and just updated to 1.0.5. Can you this bug been fixed in 1.0.5?

Bug: Keyword Alerts crashes while processing XFRM resource updates

We’re seeing repeated InvalidArgumentException: Accessed unknown getter 'User' on XFRM:ResourceUpdate errors during the xf:run-jobs background job.

The stack trace points to PB/KeywordAlerts/KeywordAlert/XFRM/ResourceUpdate.php:64, where the handler accesses $resourceUpdate->User. XFRM resource updates do not have a direct User relationship, so processing one can fail.

Could you update the XFRM resource update handler to determine the appropriate content user without assuming that relationship exists? It should also handle updates with no attributable user.
Click to expand...
Yes , that should be fixed in 1.0.5
 
You must log in or register to reply here.
Back
Top Bottom