Skip to:

Opened 4 months ago

Last modified 3 weeks ago

#9098 assigned enhancement

Rethink Site (Wide) notices

Reported by: imath's profile imath Owned by: imath's profile imath
Milestone: Up Next Priority: high
Severity: normal Version: 1.0
Component: Messages Keywords: needs-patch early


Today, this feature is included into the BP Messages component (although it might be more consistent to have it in the Notifications one). The legacy reason for this is probably due to the fact writing Site Notices was done from the Private Messages front end UI.

To warn Site Admins about important BP information, we used a workaround for the Admin notifications feature in 11.4.0, see #9007.

Recently we had this discussion about it working on the new BP Documentation project and I remember we also discussed about it with @espellcaste from a Messages component ticket.

I believe we need a Core feature to send important notices to Admins (The Notifications/Messages component can be deactivated). We experienced this need in 11.4.0 because of the BP Rewrites API important changes and I'm sure we'll need it again soon (See roadmap).

I think Admin users shouldn't need to activate the Messages component to send important notices to all their members. We can improve these Site Notices to play some other role like warn only Site writers about important information.

Let's move it out of the Messages component & transform it as a Core feature!

Change History (11)

This ticket was mentioned in Slack in #buddypress by imath. View the logs.

4 months ago

This ticket was mentioned in Slack in #buddypress by emaralive. View the logs.

4 months ago

#3 @shawfactor
4 months ago

This should not be a core feature, it should be its own component. Not everyone is going want it and not everyone will want it done the buddypress way.

In terms of its own component, why not just use a custom post type? The current db schema for notifications is pretty limited…

#4 @imath
4 months ago

Thanks for your feedback @shawfactor

Actually the first people needing it to be a Core feature is us the Core team :)

The new direction I want to move Site Notices towards is like a BuddyPress "approaching" way of doing something that is taking way too long to happen in WordPress =>

Although it seems to still be under development, it's been 6 years since it started...

We first need this to be a Core Feature to:

  • Inform about important changes happening in BuddyPress: the "Admin notifications" workaround we used for 11.4.0 is not satisfying to me as people expressed the need to be able to read again dismissed Admin notifications.
  • It could be used to inform about a getting started guide like it was suggested in Slack.
  • It could still be used by site Admins to inform users widely on the front-end and in the back-end.
  • It could be used by site Admins to warn specific roles like "author" about important thing to consider when contributing to content, etc..

About using a "custom post type", this is not the reply to every need. I wonder why the WordPress feature as a plugin is not using the CPT feature 😉

Finally, if it should be in its own component, then it needs to be outside of BuddyPress as a BP Addon like BP Attachments. The new direction we took is to shrink BuddyPress progressively to move optional components into BP Addons: we won't add new BP Optional components anymore.

#5 @shawfactor
4 months ago

Actually your approach is logical. The existing site wide notices functionality should move to the notification component and be compatible with the feature as a plugin.

Two issues though

  1. How does this schema all map to the actions/componenf logic we currently use in notifications?
  1. How would this interact with Multisite. The issue I have atm is segregating sitewide notices by site. This is impossible for me atm as the message component is shared across all sites. The notification comment is also shared so the same issue may still exist.

This ticket was mentioned in Slack in #buddypress by imath. View the logs.

3 months ago

This ticket was mentioned in Slack in #buddypress by imath. View the logs.

6 weeks ago

This ticket was mentioned in Slack in #buddypress by imath. View the logs.

5 weeks ago

#9 @imath
3 weeks ago

  • Keywords needs-patch early added; 2nd-opinion removed
  • Milestone changed from 14.0.0 to Up Next

I need more time. I won't be able to make it for 14.0.0, sorry.

#10 @emaralive
3 weeks ago

@imath I didn't realize the Legacy template pack behaved differently than Nouveau, apparently Site Notices are rendered across all front-end pages. Since BuddyPress 12.0.0 restricts JavaScript and Style assets loading to BuddyPress pages only; this seems to be a dilemma as to how Site Notices should work as it pertains to the Legacy template pack.

See WP Admin -> Users -> Site Notices (Support Forum post) as reference.

#11 @imath
3 weeks ago

Thanks for the alert @emaralive I agree this needs a fix, I'll work on it from another specific ticket.

Note: See TracTickets for help on using tickets.