Skip to content

About admin notifications - #3371

Open
adriendupuis wants to merge 4 commits into
5.0from
enh-notifications
Open

About admin notifications#3371
adriendupuis wants to merge 4 commits into
5.0from
enh-notifications

Conversation

@adriendupuis

Copy link
Copy Markdown
Contributor
Question Answer
JIRA Ticket
Versions
Edition

Inspired by ibexa/recipes-dev#257

Checklist

  • Text renders correctly
  • Text has been checked with vale
  • Description metadata is up to date
  • Redirects cover removed/moved pages
  • Code samples are working
  • PHP code samples have been fixed with PHP CS fixer
  • Added link to this PR in relevant JIRA ticket or code PR

@github-actions

Copy link
Copy Markdown

Preview of modified files

Preview of modified Markdown:

@github-actions

github-actions Bot commented Aug 28, 2026

Copy link
Copy Markdown

Summary

Status Count
🔍 Total 750726
🔗 Unique 15057
✅ Successful 6307
⏳ Timeouts 0
🔀 Redirected 0
👻 Excluded 744419
❓ Unknown 0
🚫 Errors 0
⛔ Unsupported 0

Full Github Actions output

@adriendupuis
adriendupuis marked this pull request as ready for review August 28, 2026 08:29
Comment thread docs/api/notification_channels.md Outdated
- `Ibexa\Share\Notification\ContentEditInvitationNotification` (alias `ibexa_content_edit_invitation`)
- `Ibexa\Share\Notification\ContentViewInvitationNotification` (alias `ibexa_content_view_invitation`)
- `Ibexa\Share\Notification\ExternalParticipantContentViewInvitationNotification` (alias `ibexa_external_participant_content_view_invitation`)
- `Ibexa\AdminUi\Notifier\Notification\UserInvitation`

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think it makes sense to explain the difference between Ibexa\AdminUi\Notifier\Notification\UserInvitation and Ibexa\Contracts\User\Notification\UserInvitation ?

Some kind of table where the action triggering the notification is described?

( understand this could be a follow-up)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mnocon
Yes, it would. While adding 451caef I was also thinking at a kind of table that would describe purpose, default recipients, maybe the actual notifier service when it exists (TriggerNotificationsSubscribers, …\PasswordReset\Notifier, etc.)

Comment on lines +87 to +89
```bash
php bin/console ibexa:debug:config notifications.subscriptions --siteaccess=admin
```

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could expose the default result. --json | jq is optional, it rturn unformmated but readable JSON by default. I don't know what to do with FormSubmitted from ibexa/recipes-dev#257
It seems not immediately needed but it could be needed in the rare case someone use the form builder for an admin form.

Suggested change
```bash
php bin/console ibexa:debug:config notifications.subscriptions --siteaccess=admin
```
```bash
php bin/console ibexa:debug:config notifications.subscriptions --siteaccess=admin --json | jq
```
```json
{
"ibexa_content_edit_invitation": {
"channels": [
"ibexa",
"email"
]
},
"ibexa_content_view_invitation": {
"channels": [
"ibexa",
"email"
]
},
"ibexa_external_participant_content_view_invitation": {
"channels": [
"email"
]
},
"Ibexa\\AdminUi\\Notifier\\Notification\\UserPasswordReset": {
"channels": [
"email"
]
},
"Ibexa\\AdminUi\\Notifier\\Notification\\UserInvitation": {
"channels": [
"email"
]
},
"Ibexa\\Contracts\\FormBuilder\\Notifications\\FormSubmitted": {
"channels": [
"email"
]
}
}
```

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants