Where is the editor email address set?
  • Vote Up0Vote Down Daniel JamesDaniel James
    Posts: 844Member, Sourcefabric Team

    Hi guys,

    The manual says that when writing an article:

    If you change the status to Submit, an email will be sent to the editors
    to check the new submission.

    In 3.5-alpha, I can't find the place where the editor(s) email addresses
    are set for this feature. I expected this to be found by clicking a
    Configure icon in the Publication List, or maybe in the Issue List if
    there's a high staff turnover :-) but it's not in either of those places.

    I set up a test user account with type: Editor, but there seems to be no
    obvious way to link a specific editor username or email address to a
    specific publication, issue or section. Any clues appreciated ;-)

    Thanks!

    Daniel
  • 7 Comments sorted by
  • Vote Up0Vote Down Sava TatićSava Tatić
    Posts: 113Member, Administrator, Sourcefabric Team
    Hi,

    Congratulations, you've probably bumped into the oldest unrewritten feature of
    Campsite. :)

    The mail address is specified in Users/Staff, for each user. To turn the
    notifications on, the option (user permission) to check is:

    "User will be notified on several events"

    As you can guess, the notifications are not granular. :(

    All the best,

    Sava

    On Monday, November 08, 2010 17:36:43 Daniel James wrote:
    > Hi guys,
    >
    > The manual says that when writing an article:
    >
    > If you change the status to Submit, an email will be sent to the editors
    > to check the new submission.
    >
    > In 3.5-alpha, I can't find the place where the editor(s) email addresses
    > are set for this feature. I expected this to be found by clicking a
    > Configure icon in the Publication List, or maybe in the Issue List if
    > there's a high staff turnover :-) but it's not in either of those places.
    >
    > I set up a test user account with type: Editor, but there seems to be no
    > obvious way to link a specific editor username or email address to a
    > specific publication, issue or section. Any clues appreciated ;-)
    >
    > Thanks!
    >
    > Daniel
    >
    >
    > To participate in the discussion, go here:
    > http://forum.sourcefabric.org/index.php?t=rview&frm_id=1 1

    --
    Sava Tatić
    Managing Director, Sourcefabric o.p.s.
    sava.tatic@sourcefabric.org

    Salvátorská 10
    110 00 Praha 1, Czech Republic
    +420222362540
    +420602653104 (mobile)
    Skype: tictactatic

    http://www.sourcefabric.org
    http://www.twitter.com/Sourcefabric

  • Vote Up0Vote Down Daniel JamesDaniel James
    Posts: 844Member, Sourcefabric Team

    Hi Sava,

    > The mail address is specified in Users/Staff, for each user. To turn the
    > notifications on, the option (user permission) to check is:
    >
    > "User will be notified on several events"

    Thanks for explaining that.

    I don't think this feature is actually working on
    http://campsite-dev.sourcefabric.org because this box is checked for my
    user account, but I didn't get a notification by email when I created a
    new article and changed its status to Submitted.

    Unless this feature only works for *other* users articles, or the server
    is not set up to send mail.

    > As you can guess, the notifications are not granular. :(

    I see there is already a ticket open for this:

    http://dev.sourcefabric.org/browse/CS-39

    In the meantime, I will remove the sentence about email notifications
    from the manual.

    Cheers!

    Daniel
  • Vote Up0Vote Down Sava TatićSava Tatić
    Posts: 113Member, Administrator, Sourcefabric Team
    On Tuesday, November 09, 2010 11:50:48 Daniel James wrote:

    > I don't think this feature is actually working on

    > http://campsite-dev.sourcefabric.org because this box is checked for my

    > user account, but I didn't get a notification by email when I created a

    > new article and changed its status to Submitted.

    >

    > Unless this feature only works for *other* users articles, or the server

    > is not set up to send mail.

    Hm, can't really recall whether it sends notifications for others' articles
    only (that'd be kind of smart), as I normally turn the notification off on
    my Campsite servers (I am a lone rider there). But I think the reason for it
    not working on the server you mention is that the server may not be
    configured to send mail.



    > > As you can guess, the notifications are not granular. :(

    >

    > I see there is already a ticket open for this:

    >

    > http://dev.sourcefabric.org/browse/CS-39


    I think it's time for a proper blueprint of the new notifications system
    (the concept can be replicated in Plastelina later).



    > In the meantime, I will remove the sentence about email notifications

    > from the manual.

    Let's check it again. I didn't have the time to test it today.

    All the best,

    Sava

  • I know this works, it's either that the cron task was not set or the email
    server. Andrey, could you check?

    Mugur Rus
    Senior Software Developer, Sourcefabric
    mugur.rus@sourcefabric.org

    Cluj-Napoca, Romania
    +40 (0)720 528408
    Skype: mugur_rus

    http://www.sourcefabric.org
    http://www.twitter.com/Sourcefabric


    2010/11/10 Sava Tatić <campsite-dev@lists.sourcefabric.org>

    > On Tuesday, November 09, 2010 11:50:48 Daniel James wrote:
    >
    > > I don't think this feature is actually working on
    >
    > > http://campsite-dev.sourcefabric.org because this box is checked for my
    >
    > > user account, but I didn't get a notification by email when I created a
    >
    > > new article and changed its status to Submitted.
    >
    > >
    >
    > > Unless this feature only works for *other* users articles, or the server
    >
    > > is not set up to send mail.
    >
    > Hm, can't really recall whether it sends notifications for others' articles
    > only (that'd be kind of smart), as I normally turn the notification off on
    > my Campsite servers (I am a lone rider there). But I think the reason for
    > it
    > not working on the server you mention is that the server may not be
    > configured to send mail.
    >
    >
    >
    >
    > > > As you can guess, the notifications are not granular. :(
    >
    > >
    >
    > > I see there is already a ticket open for this:
    >
    > >
    >
    > > http://dev.sourcefabric.org/browse/CS-39
    >
    >
    > I think it's time for a proper blueprint of the new notifications system
    > (the concept can be replicated in Plastelina later).
    >
    >
    >
    >
    > > In the meantime, I will remove the sentence about email notifications
    >
    > > from the manual.
    >
    > Let's check it again. I didn't have the time to test it today.
    >
    > All the best,
    >
    > Sava
    >
    >
    >

  • Vote Up0Vote Down Andrey PodshivalovAndrey Podshivalov
    Posts: 1,526Member, Administrator, Sourcefabric Team
    usually I'm switching off a notification in the cron tasks to avoid a
    spamming of all registered admins.

    >

  • Vote Up0Vote Down Sava TatićSava Tatić
    Posts: 113Member, Administrator, Sourcefabric Team
    and please keep it switched off on the dev server :)

    On Wednesday, November 10, 2010 10:51:12 Andrey Podshivalov wrote:
    > usually I'm switching off a notification in the cron tasks to avoid a
    > spamming of all registered admins.
    >
    >
    >
    >
    >
    > To participate in the discussion, go here:
    > http://forum.sourcefabric.org/index.php?t=rview&frm_id=1 1

    --
    Sava Tatić
    Managing Director, Sourcefabric o.p.s.
    sava.tatic@sourcefabric.org

    Salvátorská 10
    110 00 Praha 1, Czech Republic
    +420222362540
    +420602653104 (mobile)
    Skype: tictactatic

    http://www.sourcefabric.org
    http://www.twitter.com/Sourcefabric

  • Vote Up0Vote Down Daniel JamesDaniel James
    Posts: 844Member, Sourcefabric Team

    Hi Andrey,

    > usually I'm switching off a notification in the cron tasks to avoid a
    > spamming of all registered admins.

    Ah, that makes sense. I'll put back the mention of this feature in the
    end user manual.

    Cheers!

    Daniel