Since CB Conditional 5.0.0 has officially released it's that time again to change tasks! There has been a lot of pressure to support on-site notifications. It's finally happening! Check out the details below.
CB Activity introduced the first phase of the notifications API, but it didn't really work out how I expected. The notifications currently are basically sharing the same API and database as normal activity. The problem with this is first normal activity has to exclude notifications so that means a wildcard NOT LIKE 'notification.%' being added to the query slowing it down. Second there could be 100,000 notifications stored and that would negatively impact all activity streams performance for no reasons.
What all this means is a new separate API and database table are being implemented specifically for handling notifications. All existing "notification.%" activity entries will safely migrate over so you've nothing to worry about if you've some stored already. With this change will also of course be improvements to CB Auto Actions to handle storage of notifications. I will be reviewing implementing system actions for notifications regarding various things that you can freely enable. A few other changes are also coming as noted on our forge below.
https://forge.joomlapolis.com/projects/cb-activity/issues?query_id=111