-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide a way to subscribe to a content type #31
Comments
The flag module looked back then as a best practice of marking on what the user want to follow. But then again OG have the OG membership which marks which content belong to which group and that sort of a "flag" as I can see it(in og8 the membership applies only to user and content reference and not content to content reference). So if you look for another work around it seems to me that we need to maintain another entity just like OG does. Another option is to create an entity reference field. Bu then again - why would you like to flag an article config entity? it's a config and I don't think someone would like to register to a change in that. |
This sounds like the right way to me. Flag already does the heavy lifting of access, export/import flags, etc' - so I don't think we should look for another way. Since Node type is a |
Flag has an open issue too: https://www.drupal.org/node/2678756 |
- Starts on #31 - Excludes any Views, as config entities do not readily work with Views
- Starts on #31 - Excludes any Views, as config entities do not readily work with Views
- Starts on #31 - Excludes any Views, as config entities do not readily work with Views
On several projects in the past, the request to subscribe to a content type has come up, and I'm seeing that request again now.
In 7.x, various workarounds included adding a flag to the user, and then having special handling to grab all users that had that flag and send out notifications for new content of a given type.
I'm wondering if there's a way this module can make that easier? Or how others are working through this issue?
One potential way would be to create a flag on config entities. The Flag module currently does not allow flags of config entities, which seems like that approach would make the most logical sense here (eg, a user flags 'article' config entity).
The text was updated successfully, but these errors were encountered: