Possible to select content types to add sticky notes to, just as done when selecting content types to add taxonomy too?
Thanks for any info!

Comments

berliner’s picture

No it is not possible for the moment to add sticky notes to specific content types.

I will think about this. If it is useful there is no reason why this shouldn't be possible in the future.

AntiNSA’s picture

I think if you can say which content it is possible to add sticky notes to, and give different permissions for each content per user role that would be perfect

berliner’s picture

I could use some input from anyone who is interested.

The given feature request is possible, but it raises some questions.

1. Since sticky notes can primarily be attached to pages, not to nodes or any specific content, it is not obvious what "content" is. I could think of an admin setting where you choose to enable sticky notes for specific content types and then have sticky notes only available on all node/* pages (full page node views) of the specified types. But it would not easily work for lists of contents, because with modules like views you can create mixed lists of all types of content. How could I distinguish the desired contents from others. Wouldn't make much sense in my opinion.

2. When the specifications in 1. are possible, than it should also be possible to have sticky notes only available on certain taxonomy pages (vocabularies, core), certain user pages (different roles, core), certain views (not core). What about panels and all other kind of contributed modules?

Would it be sufficient maybe to have the ability to enter PHP code in the text area for the sticky notes page visibility (same as for block configuration)?

Would be glad about any ideas.

MGN’s picture

I think having a list of paths to exclude or include (as is done for blocks) would be a good choice for this. You could also allow php (with another role-based "allow use of php ... " permission) to return the list of included or excluded paths. (Re)using the same type of UI (three radios followed by a texarea) will also make it easily understood.

berliner’s picture

I just included those changes to the dev branch in the CSV repository. If you could have a look if this is sufficient for you (and if it is correctly working) that would be nice.

berliner’s picture

Status: Active » Fixed

marking this as fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.