#177 ✓resolved
Priit Tamboom

Newsletter ui: draft indication

Reported by Priit Tamboom | January 6th, 2009 @ 09:40 AM | in Release 0.1.1

In the issue's show view (/newsletters/1/issue/1), please include an indication if the article is a draft. Maybe also include other details such as the planned publishing date.

Comments and changes to this ticket

  • Sven Fuchs

    Sven Fuchs January 9th, 2009 @ 11:45 AM

    • Milestone set to Release 0.1.1
    • State changed from “new” to “open”
  • Priit Tamboom

    Priit Tamboom January 19th, 2009 @ 10:20 AM

    • Tag changed from newsletter to draft, newsletter, state

    Sven: Do we need the draft field? For articles we use published_at.nil? to decide whether or not it's a draft. Suggestion: use the published_at timestamp

    Priit: Actually we might missing one state between draft and delivered, however don't know at the moment if it is useful to bring one more state to the issue.

    If I'm going to use published_at as draft, then I need to change editing UI and some logic, because issue logic differs from article cos:

    • first, you cannot unpublish when it's delivered already
    • second, i have to remove editing question: "Save as draft?", because draft will be managed by delivery logic.

    In short: do our users needs draft own issue dracking (for example to let other people to review draft newsletter before deliver etc) or we declare all undelivered issues as draft, but then why we use "draft", then we should use "undelivered" instead.

    Suggestion: What do you think we introduce new state "undelivered" or smth similar instead abusing "draft" for that and let's keep "draft" state as real draft.

  • Priit Tamboom

    Priit Tamboom January 19th, 2009 @ 10:22 AM

    • Assigned user changed from “Priit Tamboom” to “Sven Fuchs”

    I change responseble to you becasue then you can track when I wait your opinion. After change responsible back to me.

  • Priit Tamboom

    Priit Tamboom January 21st, 2009 @ 01:22 PM

    I'll remove draft and will bring in delivered_at. So newsletter publish_at logic is same as other engines.

  • Priit Tamboom

    Priit Tamboom January 21st, 2009 @ 01:22 PM

    • Assigned user changed from “Sven Fuchs” to “Priit Tamboom”
  • Priit Tamboom

    Priit Tamboom January 22nd, 2009 @ 11:43 AM

    • State changed from “open” to “resolved”

    Added state indications: draft, on hold (aka published), queued and delivered.

    Added delivery status info, so user knows when issue will be delivered etc.

  • ava james

    ava james March 17th, 2023 @ 04:16 PM

    Nice post thanks for sharing this check this Lightinthebox Discount Code

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<p>Cutting edge cms, blog, wiki, forum ... plattform.</p>

<p>Find the code on <a href="http://github.com/svenfuchs/adva_cms/tree/master">GitHub: adva cms</a></p>

<p>Part of the business application framework <a href="http://www.advabest.org/">adva best</a>.</p>

People watching this ticket