Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8179110B0E for ; Thu, 25 Jul 2013 09:28:08 +0000 (UTC) Received: (qmail 75161 invoked by uid 500); 25 Jul 2013 09:28:07 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 75075 invoked by uid 500); 25 Jul 2013 09:28:05 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 75044 invoked by uid 99); 25 Jul 2013 09:28:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jul 2013 09:28:03 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jul 2013 09:27:57 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=eed88Ye5ME7VSflQfHfwdbO4GJ/eHaw24vAL/gIaSTk=; b=nO12+I06maXt1Y4Z9FpJlC54PeYvXbjKw6DtIU2a00GO05vXhPvvuAfKL1g2U6Ewvh+SBTLXEqmsyf1eoHs+nmq7Ns1Tp8kMZKByMXTFP1Z78crDnwwsp8H2sHv+iG7bIKmr+rbkt2BEBB6Pk8rZzWQBz4AojxvGi4iVEtOV0+o=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-2.v29.ch3.sourceforge.com) by sfs-alluradaemon-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1V2Hpg-0003kt-Q6 for allura-dev@incubator.apache.org; Thu, 25 Jul 2013 09:27:36 +0000 Content-Type: multipart/related; boundary="===============6092135557828339030==" MIME-Version: 1.0 To: "[allura:tickets] " <6446@tickets.allura.p.re.sf.net> From: "Igor Bondarenko" Reply-To: "[allura:tickets] " <6446@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #6446 Forum API should check for posts' status Message-ID:

Date: Thu, 25 Jul 2013 09:27:36 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============6092135557828339030== Content-Type: multipart/alternative; boundary="===============5060861591957404087==" MIME-Version: 1.0 --===============5060861591957404087== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Closed #400. `je/42cc_6446` --- ** [tickets:#6446] Forum API should check for posts' status** **Status:** code-review **Labels:** 42cc allura-api **Created:** Wed Jul 10, 2013 03:19 PM UTC by Dave Brondsema **Last Updated:** Thu Jul 11, 2013 08:36 AM UTC **Owner:** nobody The new API in the ForgeDiscussion tool doesn't check for posts' statuses, so it will show 'pending' and 'spam' posts too, which aren't shown on the regular forum view. This may apply to discussion thread APIs in other tools too (e.g. ticket comments via API). It's an issue for individual threads URLs and also the API endpoint for a forum which lists the threads (a new thread that is just 1 post that is not "ok" status, shouldn't be listed, just like the web interface) Perhaps easiest would be to only show "ok" posts no matter what. Would be a bit nicer if a user with the proper rights could see the pending & spam posts too. That might be best with an additional flag in the URL to control whether to show those? Doesn't seem necessary to do that extra stuff at this point though. --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============5060861591957404087== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

Closed #400. je/42cc_6446


[tickets:#6446] Forum API should check for posts' status

Status: code-review
Labels: 42cc allura-api
Created: Wed Jul 10, 2013 03:19 PM UTC by Dave Brondsema
Last Updated: Thu Jul 11, 2013 08:36 AM UTC
Owner: nobody

The new API in the ForgeDiscussion tool doesn't check for posts' statuses, so it will show 'pending' and 'spam' posts too, which aren't shown on the regular forum view. This may apply to discussion thread APIs in other tools too (e.g. ticket comments via API). It's an issue for individual threads URLs and also the API endpoint for a forum which lists the threads (a new thread that is just 1 post that is not "ok" status, shouldn't be listed, just like the web interface)

Perhaps easiest would be to only show "ok" posts no matter what. Would be a bit nicer if a user with the proper rights could see the pending & spam posts too. That might be best with an additional flag in the URL to control whether to show those? Doesn't seem necessary to do that extra stuff at this point though.


Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============5060861591957404087==-- --===============6092135557828339030==--