Skip to content
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

Open
jhedstrom opened this issue Sep 30, 2016 · 3 comments
Open

Provide a way to subscribe to a content type #31

jhedstrom opened this issue Sep 30, 2016 · 3 comments
Assignees
Milestone

Comments

@jhedstrom
Copy link
Collaborator

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).

@RoySegall
Copy link

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.

@amitaibu
Copy link
Member

amitaibu commented Oct 3, 2016

One potential way would be to create a flag on config entities

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 ConfigEntity, sounds like flag could be adapted.

@jhedstrom
Copy link
Collaborator Author

Flag has an open issue too: https://www.drupal.org/node/2678756

@jhedstrom jhedstrom removed the question label Oct 3, 2016
@jhedstrom jhedstrom self-assigned this Oct 3, 2016
@jhedstrom jhedstrom changed the title Provide a way to subscribe to a content type? Provide a way to subscribe to a content type Oct 3, 2016
jhedstrom added a commit that referenced this issue Oct 3, 2016
- Starts on #31
- Excludes any Views, as config entities do not readily work with Views
jhedstrom added a commit that referenced this issue Oct 3, 2016
- Starts on #31
- Excludes any Views, as config entities do not readily work with Views
jhedstrom added a commit that referenced this issue Oct 3, 2016
- Starts on #31
- Excludes any Views, as config entities do not readily work with Views
@jhedstrom jhedstrom modified the milestones: 8.x-1.0 beta, 8.x-1.0 rc Mar 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants