currently, a user w/o enewsletter admin privs *cannot* post content that gets sent in the newsletter.
a user *with* admin privs sees a checkbox that is default unchecked for new content.
it's important to be able to default all new content to be included in the newsletter. maybe this would easy to implement as an addtional user_access slot? or a flag in settings.
thanks!
Comments
Comment #1
deanypop commentedYes! This would be really great.
I'll chip in $100 if we can get an enewsletter module that works in the "preferred way" for sites with numerous submitter/content creators - as above, provides a way for all* content to be submitted by default, and separates the idea of "node content creator" from "newsletter administrator" in a better way.
Right now, this module only works if ALL content creators are also acceptable admins for enewsletter, which is definitely not the case for my site, and I'm sure many others.
I just want to have certain people be able to post whatever they want as nodes, and then FORCE all their content into my newsletter by default (with handy extra selections for turning off items).
ALSO, there doesn't seem to be a way to prioritize the content (Announcement type stories first, then regular stories, then new book pages, then taxonomy term XXX, etc).
Comment #2
robert castelo commentedCheck out the new version of enewsletter.module, most of those features are now included.
Anything that isn't please open a new feature request (one post per feature request).
Comment #3
robert castelo commented