Received: by 10.115.18.2 with SMTP id v2mr1117062wai.3.1209043139184; Thu, 24 Apr 2008 06:18:59 -0700 (PDT) Return-Path: Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174]) by mx.google.com with ESMTP id k36si202356waf.1.2008.04.24.06.18.58; Thu, 24 Apr 2008 06:18:59 -0700 (PDT) Received-SPF: neutral (google.com: 209.85.200.174 is neither permitted nor denied by best guess record for domain of ski...@skippy.net) client-ip=209.85.200.174; Authentication-Results: mx.google.com; spf=neutral (google.com: 209.85.200.174 is neither permitted nor denied by best guess record for domain of ski...@skippy.net) smtp.mail=ski...@skippy.net Received: by wf-out-1314.google.com with SMTP id 25so2540329wfa.31 for ; Thu, 24 Apr 2008 06:18:58 -0700 (PDT) Received: by 10.142.131.18 with SMTP id e18mr230379wfd.39.1209043138652; Thu, 24 Apr 2008 06:18:58 -0700 (PDT) Received: by 10.142.47.3 with HTTP; Thu, 24 Apr 2008 06:18:58 -0700 (PDT) Message-ID: Date: Thu, 24 Apr 2008 09:18:58 -0400 From: "Scott Merrill" To: habari-dev@googlegroups.com Subject: Re: [habari-dev] Re: Scheduled Posts In-Reply-To: <7d7a1076-7268-430a-9f1f-23dbd34f5d39@34g2000hsh.googlegroups.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8fd7fe00-3e5d-415d-bb58-579d542b0d72@l42g2000hsc.googlegroups.com> <20080418105951.GD8923@ns1.cs.rmit.edu.au> <480B9933.6090701@iamgraham.net> <7d7a1076-7268-430a-9f1f-23dbd34f5d39@34g2000hsh.googlegroups.com> On Thu, Apr 24, 2008 at 8:16 AM, rick c wrote: > For all who are interested in testing it, I've posted a patch to > ticket #36 incorporating scheduled posts as a cronjob into Habari. The > patch incorporates adding a new 'scheduled' status to the poststatus > table during installation, a new table on the dashboard showing > scheduled posts, and appropriate log entries when the post goes live. > Scheduling a post for the future entails only putting a future date in > the publication date edit box on the publish screen and hitting the > publish button. The user is then notified the post has been scheduled. > When the time comes, it goes live. A cursory overview of the patch looks good. A few comments / questions: In my opinion, the list of scheduled posts in the dashboard should only show up if there are, in fact, scheduled posts. When publishing a future-dated item, we should probably indicate to the user that the future-date has been preserved. Something along the lines of "Your post has been scheduled for publication at ... '. Have you tested this yourself, Rick? How has it worked for you? Cheers, Scott