Issue with custom notifications

Hi,

First of all, I know there are some major changes coming with notifications as specified here in the forge

Also as this is a user defined trigger to insert a row into #__comprofiler_activity, I am not expecting any support.

Still I wanted to bring the following issue to your attention.

In this example, I will refer to User A with ID 170 and User B with ID 1706
If the following asset is inserted into the activity table:
Both user A and B see the notification

I expect you have already spotted the issue but for clarity the following tests and results:

Both user A and B see the notification


User A and User B do not see the notification, User with ID 1716 sees it.



Thanks
David

The user that sees the notification is the user specified in the asset of the activity. This is defined as follows.

notification.USER_ID

USER_ID is the user that should see the notification. The owner of the activity is whom the notification is from. Regardless you're trying to use an incomplete feature that will be completely redesigned with its own storage table to better handle notification assignment and also makes it a lot less hard to send notifications to the wrong user, etc..

In short the changes that are coming are a new notification table with 2 new database columns. 1 specifies the recipient user and 1 specifies the read state (this is currently a separate table, but will be removed). Assets would then no longer need "notification.USER_ID" prefixed.

krileon wrote: The user that sees the notification is the user specified in the asset of the activity. This is defined as follows.

notification.USER_ID

Yes I understand this and to have multiple notifications a suffix need to be concatenated.
The issue is notification.170% matches notification.1706

Anyway I did state I wasn't expecting support, I just wanted to let you know that this has issues: notification.USER_ID%

That's not an issue. It's working exactly as it's supposed to. It's due to % starting the wildcard location. You should be using the below.

notification.170.%

The wildcard should begin after the first period. The notification.USER_ID is a prefix. This means there should be an asset in addition to it. If you're using only "notification.170" for the asset of an activity entry then the asset of that activity entry is wrong and when the migration code migrates it it won't have an asset at all since "notification.170." will be stripped away.

Edit: Ah, I see what you're saying. There's a bug in the library code it self when converting "notifications" asset to "notifications.USER_ID%". Will fix for next nightly.